Valdis Kletnieks to me: > Hmm... you've never worked in an enterprise where half the people have > upgraded to the new release of Word, and the other half haven't installed > the plugin that lets their old Word not vomit when they get documents from > the new Word.
"worked in" (or "for") no, but "with those that do" yes. First, and I'm no MS apologist, the problem set you describe has usually been avoidable _if_ the IT folk at said enterprise actually do the job, read the fine manuals and roll out the new version with policies enforcing the "use format X" option (or even just push such policies as part of their standard environment management stuff. Of course, that requires that said enterprise has IT staff marginally capable of doing their job (so probably rules out 75-90% of the field). Second -- and much bigger -- is that while it can be a PitA to Email the sender back and explain how to "Save as... and choose the 'correct' file format" that is rather different than the situation where the OOO user sent a Word-capable format document that does not open properly, or that does, but is clearly seriously munged or quickly becomes that way after you, say, decide that there needs to be a comma after that word in the opening sentence. My "complaints" with OOO are not that it does not (natively) do MS formats, but that it is incomprehensibly buggy in _all_ its format- handling capabilities. Regards, Nick FitzGerald _______________________________________________ Fun and Misc security discussion for OT posts. https://linuxbox.org/cgi-bin/mailman/listinfo/funsec Note: funsec is a public and open mailing list.
