Company converting to OOo

[Floyd]

I am in need of an expert in converting documents to OO. My company is considering making the move to OOo. Although I realize that there are some unavoidable problems when converting between Microsoft Office and OO, I need to ensure that none are too major. If someone considers themselves well versed in conversion problems, I would really like to get in contact with them via email. I have noticed some of the same questions that I have are left unanswered in this forum, specifically regarding embedded objects so if anyone believes they can help, it would be much appreciated.

[bartgymnast]

Floyd a big thing to do is.

export your files as PDF
that is universal
_________________
If you jump to the otherside of the galaxy,
It is still not the END.

[The Liquidator]

Hi

Yes there are conversion "issues" which seem to reduce in terms of numbers and severity the more that OOo "grows up".

The major ones are graphics (caused principally by the rather more formal structure OOo applies to anchoring). This means that OO sometimes will struggle putting graphics in the right place when opening a document created within MS Word. Things are much better the other way around.

Numbers and bullets. OOs numbers and bullets lose their indent when opened in MS Word, which seems to have been fixed in OOo1.1 beta.

Macros. Documents containing macros in either package are a problem for the other. Can't really say much more as I wouldn't recognise a macro if one hit me in the face!

Couple of suggestions I can make:

1. you should only use the MS format for documents that are to be sent for editing by people who only have Ms Word. If it's to be read (which is most of them I suspect) then do as bartgymnast suggests and use pdf.

2. Keep the 2 running side by side on your machine, while you learn what works and what doesn't.

Ian

[Floyd]

Thanks for the tips, they really are much appreciated, any more are always welcome.
Thanks again