M. Fioretti wrote:
On Wed, Jul 19, 2006 11:41:16 AM +0200, Nicolas Mailhot
([EMAIL PROTECTED]) wrote:
Hi,
I have several complex corp documents which make OO.o go crazy one
way or another. I'd like to report the bugs to get them fixed, but
OO.o devs will just ignore me without test documents and there's no
way I'll post internal company info in the wild. [...]
hmmm... This same discussion happened here 2/3 years ago. I already
pointed out, back then, that I had had to give up OO.o on the job
because it would *not* exchange complex documents (patent
applications, scientific papers...) with MS Office in any acceptable
way, AND that I could not submit confidential company docs as test
documents.
<SNIP>
Luckily, in another year or two it will be Microsoft which will have
to be able to render OpenDocument correctly, not the other way
around. Then, at least for new documents, it won't be an OO.o problem
anymore.
Ciao,
Marco
Well stated.
This is the issue I have run into a few times. I manually changed the
document to ensure it was clean. In some cases, I have created test
documents to upload as I did yesterday.
The legal issues are a major show stopper. With employee's even getting
fired for making a post on a blog, it would be allot worse if you
released company documents.
There is one benefit to making the changes manually. You may find the
part of the document that is causing the problem. I hate to bring up an
old thread of Reveal Codes (issue 3395) like feature, but this is one
place that they may actually be useful to a user.
There can be some pretty awful formatting practices that could just
create the problem.
--
Robin Laing
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
