reLyXdoc (oops)
Forgot to attach this! -Amir reLyX.lyx.gz
Re: reLyXdoc (oops)
> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: Amir> Forgot to attach this! -Amir So, what shall we do wih it? Setting apart the amazing technical feat, what is the feeling of doc people about whether this should go in docs? JMarc
Re: reLyXdoc (oops)
On Wed, Jan 20, 1999 at 07:10:49PM +0100, Jean-Marc Lasgouttes wrote: > > "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: > > Amir> Forgot to attach this! -Amir > > So, what shall we do wih it? Setting apart the amazing technical feat, Next I'm going to write a perl script to make lyx documents turn cartwheels... > what is the feeling of doc people about whether this should go in > docs? Can we assume that the deafening lack of response implies that people either agree it should go in or don't care? I didn't really think most people would have a very strong opinion on this. Basically, it adds a few K to the distribution and most people will never look at it. The only reason I could think of that someone wouldn't want to put it in is that having too many manuals in the help menu could be confusing. But it seems to me that if it's called "Importing LaTeX Documents", it won't really increase confusion any. Again, if we do add this doc, we'll have to mention it in the intro as well as the UG and tutorial. Is Mike unreachable in Hawaii? -Amir
Re: reLyXdoc (oops)
On Mon, Jan 25, 1999 at 06:14:19PM +0100, Jean-Marc Lasgouttes wrote: > > "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: > > Amir> The only reason I could think of that someone wouldn't want to > Amir> put it in is that having too many manuals in the help menu could > Amir> be confusing. But it seems to me that if it's called "Importing > Amir> LaTeX Documents", it won't really increase confusion any. > > If it is named like this, it should make first how to import documents > from LyX. A man page is not really done for this. And if we add it in > Help menu, we'll have to check all the i18n files, so that the Help > file comes out properly translated. > > Just to add to your confusion. Hm. OK, then we've got at least two options. (1) Call it reLyX, which can be translated as reLyX in all (latin-1) languages. Unless you want to call it réLyX or something, to sound fancier. (In america, accents make words foreign and hence exotic. Perhaps the joke is lost on the few non-American readers of this list.) (2) Call it Importing LaTeX Documents. We would of course change the Title. Then we'd have Section 1 be "Two Ways to Import". 1.1 would describe importing from LyX (very simple, at least until Asger adds to the popup the input field for adding options to the reLyX call). 1.2 would be the current sections 1 and 2. (When Asger does add that input field, we could have the options be section 2). Then sections 2-n would be the current sections 3-n. They describe things like what reLyX can translate, syntax files, etc. which is important to know whether you're using reLyX from the command line or from LyX. Finally, we'll need to contact all the translators and ask them to update the menu translations. #1 is *way* easier, so why don't we do that now. There are other things that we need to do this week (I was hoping I could send in a reLyX with a semi-large bugfix, fix the revtex template... and I'm sure others have things to do too) -Amir
Re: reLyXdoc (oops)
> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: Amir> The only reason I could think of that someone wouldn't want to Amir> put it in is that having too many manuals in the help menu could Amir> be confusing. But it seems to me that if it's called "Importing Amir> LaTeX Documents", it won't really increase confusion any. If it is named like this, it should make first how to import documents from LyX. A man page is not really done for this. And if we add it in Help menu, we'll have to check all the i18n files, so that the Help file comes out properly translated. Just to add to your confusion. JMarc
Re: reLyXdoc (oops)
> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: Amir> #1 is *way* easier, so why don't we do that now. There are other Amir> things that we need to do this week (I was hoping I could send Amir> in a reLyX with a semi-large bugfix, fix the revtex Amir> template... and I'm sure others have things to do too) Personally, I probably will not have time this week to do thing which require a brain. I will probably manage to commit Jose's patch for man support (did you have a look at the file, Amir?), but not much more. So don't count on me for that. Oh, and I will probably not be able to refrain from sending random nonsensical e-mails to the list. JMarc
Re: reLyXdoc (oops)
On Mon, Jan 25, 1999 at 06:59:31PM +0100, Jean-Marc Lasgouttes wrote: > > "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: > > Amir> #1 is *way* easier, so why don't we do that now. There are other > Amir> things that we need to do this week (I was hoping I could send > Amir> in a reLyX with a semi-large bugfix, fix the revtex > Amir> template... and I'm sure others have things to do too) > > Personally, I probably will not have time this week to do thing which > require a brain. I will probably manage to commit Jose's patch for man > support (did you have a look at the file, Amir?), but not much > more. So don't count on me for that. OK. In that case... HELP! I don't know how to add things to menus and I don't have lyxdoc access (or maybe I do?) Can a devvie help me out with this? > Oh, and I will probably not be able to refrain from sending random > nonsensical e-mails to the list. I thought you had an AI that did that even if you didn't come in to the office. -Amir
Re: reLyXdoc (oops)
On Mon, Jan 25, 1999 at 07:06:53PM +0100, Asger K. Alstrup Nielsen wrote: > > (1) Call it reLyX, which can be translated as reLyX in all (latin-1) > > languages. Unless you want to call it réLyX or something, to sound fancier. > > (In america, accents make words foreign and hence exotic. Perhaps the joke > > is lost on the few non-American readers of this list.) > > The joke is American readers. > > Oh sorry. It's not Friday. Hm. Perhaps the joke is the French and Danish readers who still can't get "reply" to send just one copy of e-mails... > I'm not sure we want to add that input field for reLyX. If > we should do anything, it would be a fancy dialog such that > the options are transparent to the user. > I'd prefer that importing of LaTeX is a non-brainer. If this > is unattainable, we should at least provide a user friendly > interface. > > Maybe a part of this interface is a generic input field, > but I think it would be wrong to let it stand alone. Hm. Interesting. For example, you could have a combobox to select the layout (which is just the same as the list in the Layout->Document popup and gets passed to -c), radio buttons for -d and -p (and have LyX check that a -c is chosen if -p is selected), and input fields for regular environments (-r). Plus an input field for extra syntax files (-s) with a browse button. I would think it would be pretty simple to build this, no? > Regarding whether to include the documentation inside LyX: > I think not. Since you have to do the work at the command > line never the less, there is really no point in having > a largish document inside LyX that basically says: > Go to a prompt and do this. A man page serves this > purpose beautifully. > > So at this point, it does not make much sense to put > the documentation as a separate item under the help > menu. What I propose is this: Insert it by hand > into one of the exisiting documents, preferably the > Extended Editing, or whatever it's called, with > a proper disclaimer attached. Later, when we get > the fancy dialog, we can then adjust the disclaimer > appropriately. > Aha! Well, at least we got someone to talk. Asger, you should probably argue with Jean-Marc, who originally had this idea. I only really did this because Jean-Marc seemed quite in favor of it. I guess his point was that he liked having all the documentation within LyX. I'm a bit wary of sticking this inside Extended Editing. Does it really fit? And it's kind of big Once the dialog has been perfected, it would make somewhat more sense I suppose. OTOH, maybe this would belong in the LyX and LaTeX chapter of UG. Is this really an extended feature? I can't tell. -Amir
Re: reLyXdoc (oops)
> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: Amir> On Mon, Jan 25, 1999 at 07:06:53PM +0100, Asger K. Alstrup Amir> Nielsen wrote: >> > (1) Call it reLyX, which can be translated as reLyX in all >> (latin-1) > languages. Unless you want to call it réLyX or >> something, to sound fancier. > (In america, accents make words >> foreign and hence exotic. Perhaps the joke > is lost on the few >> non-American readers of this list.) >> >> The joke is American readers. >> >> Oh sorry. It's not Friday. Amir> Hm. Perhaps the joke is the French and Danish readers who still Amir> can't get "reply" to send just one copy of e-mails... You are unfair. Lately I have stripped your name from at least half the messages I sent to you. Amir> Aha! Well, at least we got someone to talk. Asger, you should Amir> probably argue with Jean-Marc, who originally had this idea. I Amir> only really did this because Jean-Marc seemed quite in favor of Amir> it. I guess his point was that he liked having all the Amir> documentation within LyX. Me? I just proposed that to Amir as a challenge. I did not really though he would do it :) Now Amir, you can use this (and Jose's man textclass I have not commited yet) to edit the man page directly from inside LyX. Aren't you glad? JMarc
Re: reLyXdoc (oops)
> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: Amir> I thought you had an AI that did that even if you didn't come in Amir> to the office. Yes, I have one, and he is a very nice one. From what Altavita tells me, an Aï is what you would call a ``Pale-Throated Three Sloth (Bradypus Tridactilus)''. In French we call them `lazy' too. It is exactly the kind of pet I needed in my office. We happen to share most of our way of life, although he tends to do more typing errors than I do. JMarc
Re: reLyXdoc (oops)
On Mon, 25 Jan 1999, Amir Karger wrote: > Again, if we do add this doc, we'll have to mention it in the intro as well > as the UG and tutorial. Is Mike unreachable in Hawaii? I'm actually more reachable than usual right now. After I get our instrument up and running tomorrow, I'll actually have quite a bit of time for LyX doc tinkering since I'm only supporting the instrument, not actually observing with it. So I've been collecting doc suggestions over the last couple of weeks and intend to do a major dump on Friday or so. Just let me know what you want ... Mike [EMAIL PROTECTED]
Re: reLyXdoc (oops)
> (1) Call it reLyX, which can be translated as reLyX in all (latin-1) > languages. Unless you want to call it réLyX or something, to sound fancier. > (In america, accents make words foreign and hence exotic. Perhaps the joke > is lost on the few non-American readers of this list.) The joke is American readers. Oh sorry. It's not Friday. > (2) Call it Importing LaTeX Documents. We would of course change the Title. > Then we'd have Section 1 be "Two Ways to Import". 1.1 would describe > importing from LyX (very simple, at least until Asger adds to the popup > the input field for adding options to the reLyX call). 1.2 would be the > current sections 1 and 2. (When Asger does add that input field, we could > have the options be section 2). Then sections 2-n would be the current > sections 3-n. They describe things like what reLyX can translate, syntax > files, etc. which is important to know whether you're using reLyX from the > command line or from LyX. Finally, we'll need to contact all the translators > and ask them to update the menu translations. I'm not sure we want to add that input field for reLyX. If we should do anything, it would be a fancy dialog such that the options are transparent to the user. I'd prefer that importing of LaTeX is a non-brainer. If this is unattainable, we should at least provide a user friendly interface. Maybe a part of this interface is a generic input field, but I think it would be wrong to let it stand alone. Regarding whether to include the documentation inside LyX: I think not. Since you have to do the work at the command line never the less, there is really no point in having a largish document inside LyX that basically says: Go to a prompt and do this. A man page serves this purpose beautifully. So at this point, it does not make much sense to put the documentation as a separate item under the help menu. What I propose is this: Insert it by hand into one of the exisiting documents, preferably the Extended Editing, or whatever it's called, with a proper disclaimer attached. Later, when we get the fancy dialog, we can then adjust the disclaimer appropriately. Greets, Asger
Re: reLyXdoc (oops)
> OK. In that case... HELP! I don't know how to add things to menus and I > don't have lyxdoc access (or maybe I do?) Can a devvie help me out with > this? Adding something to the menu is as simple as editing menus.C appropriately. However, as I just wrote, I think the better option is to embed the information in an existing manual. Greets, Asger
Re: reLyXdoc (oops)
On Mon, Jan 25, 1999 at 01:22:51PM -0500, Amir Karger wrote: > I'm a bit wary of sticking this inside Extended Editing. Does it really fit? > And it's kind of big Once the dialog has been perfected, it would make > somewhat more sense I suppose. OTOH, maybe this would belong in the LyX and > LaTeX chapter of UG. Is this really an extended feature? I can't tell. Depending upon its size, it probably should be a section [and a prominent one] in the LaTeX chapter of UG, called "Importing LaTeX Files." Consider this a semi-definitive edict [I haven't read reLyXdoc yet] from the former DocProject Grand-Poohbah. -- John Weiss
