That is how I manage this sort of thing as often as I can. I import the MS-Office file (remove it from the network, if possible), format as required for OOo and export as a PDF.
In the case of a manual, the general users cannot be permitted to change it, anyway. If I place it on the intranet as a PDF, the users can read it using their browser or the Acrobat Reader and I can edit it as an OOo ODT (I'm using the v2.0 beta) so everybody is happy.
Documents that everyone is permitted to edit are another story. I have been "campaigning" for users to edit documents as rich text or even get them to switch to OOo using future readability of the document as the main argument. If you use RTF for interoperability, you should be aware that MSO has "extended" this standard, so this is not a perfect approach, either.
Learn about Linux
Download Linux
Get Linux help
How about exporting the manual as a PDF?
Posted by: fmcgowan on August 03, 2005 02:34 AMIn the case of a manual, the general users cannot be permitted to change it, anyway. If I place it on the intranet as a PDF, the users can read it using their browser or the Acrobat Reader and I can edit it as an OOo ODT (I'm using the v2.0 beta) so everybody is happy.
Documents that everyone is permitted to edit are another story. I have been "campaigning" for users to edit documents as rich text or even get them to switch to OOo using future readability of the document as the main argument. If you use RTF for interoperability, you should be aware that MSO has "extended" this standard, so this is not a perfect approach, either.
#