Charles Plessy wrote: (Not a DD but in NM.) > 2) There are simple text versions of those documents Then, I'd say, dump the original format and distribute files that users can actually use. You can stick the originals on a project website if there is some reason to do so. >, but they have many > pages, so I was considering to convert them to PDF or HTML. However, the > converter which gives the nicest results in my hands is openoffice. Is > ther a way to run it from the command line? Would it be considered as > buildd sabotage ? Build the usable files upstream and put those into CVS/etc., then you can exclude the MSWord documents from the dist tarball. The conversion then becomes an issue only for those who need to build from CVS/whatever. Depending how often the originals change, you might not have to automate this process. Make sure you specify a licence for the generated files too. GFDL with no invariant sections could be usable. What's in these files, anyway? What is the licence for the originals? > 3) In general, is there a policy about MSWord documents? What is the content? Documentation should be HTML. If users are expected to be able to use these files, they need to be in a different format. If users aren't expected to use the files, don't package them in the first place. :-) -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
signature.asc
Description: OpenPGP digital signature