Le 2010-11-03 20:18, Jean Hollis Weber a écrit :
Some comments from my (limited) experience: wiki -> odt generally produces a poor result even when a good template is applied IF the material includes a lot of graphics, as in the user guides. Much manual tweaking is then required to end up with an attractive, well laid out odt to convert to pdf. Starting with odt and then outputting to other formats generally works well, IF the odt is created using an appropriate template and layout rules. However, some of the layout in the current OOo books does not work when output to HTML and some is a bit messy when output to wiki format. Post-processing may clean it up, but more manual intervention may be necessary. I have not found time to rework the layout and template to avoid (or at least minimise) these problems. I should have a list somewhere of the specific problems I've noted; I'll try to find it. This is something to consider --and test-- when deciding which output formats and layouts are wanted. --Jean
Thanks for the insight. From what I read on the documentation mailist is that, most are interested in keeping the ODT format central to the workflow format and output, which to me is great. I have seen some grumblings here and there who have suggested other methods, perhaps for the sake of expediency, dropping the ODT format in cases such as these.
Always important showcase the ODF in this way. Thank you for giving it the importance in your workflow that it deserves.
Would it be correct for us to point to the LibO documentation process as an example of the ODF being used in a real corporate-style endeavour? We could, for example use it this way, for marketing purposes, as a working example for individuals/corporations to examine for adoption/migration considerations.
I am looking at this from a marketing point of view. Marc -- E-mail to [email protected] for instructions on how to unsubscribe List archives are available at http://www.libreoffice.org/lists/documentation/ All messages you send to this list will be publicly archived and cannot be deleted
