nice plan sven! crisp and simple :o) and yes - the documentation should be a lyx document so you see for yourself how the lyx formatting is actually done - with the help of notes and cross-references. i myself would always read the documentation in lyx and not as pdf or dvi - i only use those to compare with the lyx document to see the result of the formatting.
while the lyx documentation should contain all the relevant documentation to get the most out of lyx, the important wiki should IMHO contain everything else; such as guide showing how to complete more specific tasks etc. i see an evolution of documentation where a certain issue is discussed on the mailing list, then it is compiled as an item in the wiki, and if this item in due time is deemed important enough - it will be included in the lyx documentation. however, the documentation should not be overloaded! relevant is a keyword here :o) martin On 7/18/06, Sven Schreiber <[EMAIL PROTECTED]> wrote:
Helge Hafting schrieb: > On Mon, Jul 17, 2006 at 01:06:05PM +0200, Sven Schreiber wrote: > > If you do a lot of searching, consider making a document > consisting of User's guide + extended features in one > document. Just paste one into the other, > perhaps as part I and part II. Perhaps with Customization > as part III if you need that one too. > Ok, so I would suggest a perfect trinity: Introduction, Tutorial, Manual. The manual would consist of what is now the user guide, extended features, and customization. I guess using latex book "parts" would be right for that. As a normal lyx user, you would only need the manual, the first two docs are for beginners. > > Of course, these days LyX have document branches which could be > used to turn on/off the parts one want to see, so a single big > document makes more sense now. The documentation was created > with a more limited LyX, after all. I take that as approval. When I have the time (not this month), I will try to cook something up. ( Or maybe someone else has more time in the short term ;-) Note that I'm not talking about the wiki. It's nice and everything, but I think the first point of reference should always be the included documentation. Cheers, Sven
