Hi
> So my statement would be:
> Stay with ODF as master (as long as there is not a more conveniant
> solution) and try to offer PDF /and/ HTML in addition. Ideally, the PDF
> and HTML conversion should be done as automatically as possible, so no
> need for additional manpower.You've hit in an important point Nino. The doc team does not have the
manpower available to create and maintain independent documentation
streams. HTML is a fine idea, but not as a leading/primary format.
If there is a need for HTML, then do it as an output/publishing format
from the ODT sources.Clayton
Generation of pdf is easy for LO, under FILE >> Export as PDF in Writer
and you have your pdf. I would do this after the document has been
finalized for release. We can plug this feature, saying something "pdf
files where generated using LO ...." This will tell people the can
generate a pdf file for LO without having to prep it for import into
Acrobat or use Acrobat to generate the document.
When friends ask about getting Acrobat, I tell them to use the export
feature in LO/OOo instead and save the money. The feature has been OOo
for several years and is one of the reasons I would use OOo and now LO.