Some how, it remembers me about LyX, a graphical interface to LaTeX but not WYSIWYG. It took me a while to "switch" from "instant visual" to something different but I liked the result. in those days, there was not StarOffice available. I think LyX had xforms graphical interface when Linux Slackware was at version 3, if I remember right...
I think making official documentation will remain for development team. If users want to provide doc, then can be in OpenOffice, to have a standard and then, dev. team can convert it... It will be hard for others to learn a new "scripting" package. And not everyone has artistic inclinations or teaching so, not a task for everyone. I think "The Scripting Man" (Sebastien) found the right tool. Vasi On Sep 27, 12:10 pm, Sebastien Lelong <[email protected]> wrote: > > Well, I have tried both DITA and OO and here's what I think. > > > DITA + SYNTEXT: > > 1. very professional looking > > 2. hard to use, it takes time to put your projects into it, not good > > for new users. > > 3. It makes it a bit easier if you copy another XML file and edit it. > > Someone from jallib group has to add your xml file to the main ditamap > > file. > > 4. I am not able to BOLD or change text size. Well, I am able to, but > > it would take me much more time to do so. You need to know what > > element to use, and there are too many elements with weird names (I'm > > sure this can be changed) > > In Serna editor, there are dedicated button for this (bold, italic, > underline, new section, new paragraph, new bullet list, new ordered list, > ...) > > You can't change text size, by design, it's done by stylesheets, and this is > where you have consistent looking. > > > 5. command line is nice > > 6. more then one person can work on the book at the same time through > > seperate xml files. > > And even work on the same file, because changes can be merged. > > > > > Open Office: > > 1. can be professional looking if we put work into it. I suggest > > making an nice template for everyone to use for their projects. > > 2. Cannot have more then one person working on it as it is only 1 > > file. > > You can have master document. > > > 3. I worry about the size of the book. In the end, with all the pics, > > it may be 50mb +, so every time you do an edit, you must upload 50+mb > > to svn. > > 4. Very easy to use! I can choose my font size, bold, etc. Also, I am > > able to copy/past entire pages into OO. This is good for me and new > > users, but may be bad for the book if everyone uses different text. > > > Is there any way we can have one document for each project in OO and > > compile them together? > > Yes, with a master document. But it's less flexible than DITA. Master > document is "just" inclusion of other docs. With DITA, and ditamaps, you can > take a document, and put it anywhere in the TOC. A dita doc can thus be a > chapter (at heading 1 level), a section (at heading 2 level), a sub-section > (at heading 3 level), ... > > Thanks for your feedback. > > Cheers, > Seb --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
