Setting keyword regression.

Bugdoc sent to AMA.

Andreas, Eric,
any chance to fix this in 2.3.1 as this is regression?

WBR,
KP.

AMA: There is always a chance :-)
There are two OLE objects in this document which causes the error message.

This is no real regression, only the error messages are new.

The document objects seem to be broken, the internal streams of the object are
written in wrong format. It would be interesting to know how the document was
generated. It looks like a bug has happened on document generation.

According to the user file was generated by OOo2.1.
I would suggest suppressing error messages to be more user-friendly.

More users report this problem and all claim that files were generated by 
prior versions of OpenOffice.

Mikhail,
less than a month has left untill code freeze.
Are we on track for 2.4 with this issue?

Thanks a lot for your attention.
WBR,
Kirill Palagin.

As I have written, the error message is correct. Suppressing of error reporting
is no user-friendly solution.

This bug is more about the corrupted documents, but it seems to be impossible to
generate such a document with a newer office. So the only thing that can be done
for this bug is to try to repair the embedded document if it is possible,
although even in this case the error notification should be done.

Currently I am not completely sure that the change will get to 2.4, but it
stands a good chance.

Unfortunately the repairing is allowed only with correct UI notification.
Otherwise the behavior cood look even worse, as it happens in this case. The
broken objects are not only in wrong format, they also represent empty
documents, so they are really corrupted.
In case they are not repaired, the user just gets the objects that can not be
activated. In case they are repaired, the activation shows empty document. So
the unexperienced user could loose even the replacement images. Such a behavior
is acceptable only if the user has previously accepted the repairing, means he
knows what he is doing.

So I must confess, in this case it really makes sense to go back to the old
behavior. The error message is acceptable only if it could be turned off using
checkbox or something like this ( just imagine a document with hundred broken
embedded objects ), that is not allowed after feature-freeze.

Fixed in cws fwk82, the error message should not appear any more.

Mikhail,
thank you very much!!

WBR,
KP.

MAV->AS: Could you please verify the issue.

as: Verified.

This issue is closed automatically and wasn't rechecked in a current version of
OOo. The fixed issue should be integrated in OOo since more than half a year. If
you think this issue isn't fixed in a current version (OOo 3.1), please reopen
it and change the field 'Target Milestone' accordingly.

If you want to download a current version of OOo =>
http://download.openoffice.org/index.html
If you want to know more about the handling of fixed/verified issues =>
http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues