Issue 74222

Summary: The MSOLE links are lost on import from .doc file.
Product: General Reporter: mikhail.voytenko
Component: codeAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: freuter, issues
Version: 680m199   
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
A document with two embedde MSOLE objects. The second one is the link. none

Description mikhail.voytenko 2007-02-06 13:39:56 UTC
When the attached file is imported the linked object ( second object ) is lost.
Comment 1 mikhail.voytenko 2007-02-06 14:10:49 UTC
Created attachment 42791 [details]
A document with two embedde MSOLE objects. The second one is the link.
Comment 2 mikhail.voytenko 2007-02-08 11:29:42 UTC
mav->hbrinkm: There seems to be even no try to import the second object ( at
least I have detected no activity regarding the second object in the filter ).
The object just seems to be quietly ignored. Could you please take a look.
Comment 3 michael.ruess 2007-05-11 13:30:06 UTC
*** Issue 76775 has been marked as a duplicate of this issue. ***
Comment 4 openoffice 2007-07-20 09:51:23 UTC
Changed Target
Comment 5 Mathias_Bauer 2008-01-11 14:42:05 UTC
target 3.0
Comment 6 openoffice 2008-05-30 15:21:12 UTC
reset target due to lack of resources
Comment 7 flr 2008-08-18 15:21:33 UTC
flr->mav: Had a look at this issue and enabled import of "linked OLEs". However
it seems that the OLE code can not handle linked OLEs. When I click on an object
on Linux I get a "General error". When I do it on Windows then "Excel" is
started instead of Calc. Regardless what the import settings are....
mav --- as the master of the OLE magic --- is there code to handle "linked OLE
Word/Excel and PP docs"?
Comment 8 mikhail.voytenko 2008-08-19 09:48:28 UTC
The import settings control the import of embedded documents of specified
formats, not more. The links are standalone documents that are not really a part
of loaded document so they are not converted on import, and not affected by the
settings.

The linked document could be opened in OOo in case the system does not support
MS links as in case of Linux, that would be a nice feature. But this feature
needs a new implementation in the import filter or in the OLE handling itself,
so that the link object is parsed and converted to OOo link. We would probably
need an additional entry in import settings to control import of the linked
objects in this case. But I am not sure that this feature is worth the efforts.

Anyway, the MS links are currently handled as they are ( as any other MSOLE
object except the objects that can be imported ). They are just imported on
document open and stored on storing, so that no information is lost. They can be
used, but only on Windows systems, as any other non converted MSOLE object.
Comment 9 mikhail.voytenko 2008-08-19 11:42:17 UTC
...Anyway, the MS links are currently handled as they are ( as any other MSOLE
object except the objects that can be 
imported )...
^^^^^^^^ sorry a typo, "converted" was meant instead
Comment 10 flr 2008-08-19 16:18:52 UTC
flr->mav: Thanks for confirming my findings.

I currently modified the WW8 import such that "OCommonEmbeddedObject" type
linked objectes are inserted -- because I need the linking to work on Linux too.

This works so far and I was even able to preserve the replacement graphics.

However my main problem now is: On export "Embedded OLE" objects are written to
the .DOC stream, but I need "Linked OLE" objects. When I understood you
correctly there is currently no code which will generate these kind of OLE
stream for me, right ;-)

Comment 11 mikhail.voytenko 2008-08-19 16:52:11 UTC
Yes, there is no implementation to convert OOo links to OLE links currently.

But, if you do not need the explicit export of OOo link to OLE link and only
need the possibility to activate the OLE link on Unix, the workaround could be
used. Currently, if a MSOffice document is opened without conversion of OLE
objects, it is still possible to activate the OLE object readonly. The embedded
object implementation just tries to convert the object on the fly in this case (
without changing the persistence of the object ). The same could be done for the
OLE links, the link could be  parsed by the object and the related document
could be opened.

In this case you would not need to implement the export for this scenario.
Although it would be nice to have it in general with the new entry in
import/export settings and etc. ;)
Comment 12 flr 2008-08-21 09:58:45 UTC
Mav, Thanks again for the help.

Unfortionately I need the full story on Linux ;-) In fact its even more
complicated, since WW LINKs also allow do display a different replacement
object: Eg. a Excel OLE can have an Excel-Chart replacement graphics etc...

Additionally it looks like that the .DOC format wants an OLE2-LINK embedded.
[Funny is that RTF wants an OLE1-LINK] and that DOCX don't need an OLE-OBJECT at
all. There it is done using the OPC links...

However -- Thanks so much for your help.
Let me know if you want me to keep you updated...

~Florian
Comment 13 Marcus 2017-05-20 10:47:34 UTC
Reset assigne to the default "issues@openoffice.apache.org".