https://issues.apache.org/ooo/show_bug.cgi?id=121329
--- Comment #5 from orcmid <[email protected]> --- @alg, (It's orcmid - pronounced about the same in both English and Italian [hard c, like k]. Not sure about other languages.) EXPERIMENT #1 Interesting. I think we could make some test documents that have the same OLE binary used in more than one image frame. There's nothing in ODF that would prevent this, but the implementation would need to preserve the shared copy and not split them up. It would be easy to see if sharing that much breaks anything. EXPERIMENT #2 Also, in the past, OLE objects were stored with Sun MIME types and a Sun wrapper (although they converted to OLE embeddings in Office documents correctly). It would be interesting to see how those work. I assume AOO 3.4.1 does the same thing, but it would be interesting to check it out. Another thing to check is what is ordinarily a common OLE characteristics. That is, the binary OLE object carries a static image (usually a WMF) that is part of it so the object can render properly even if the OLE application is not present. This is done in a standard way, since the application is not available to interpret the application-specific persisted part. EXPERIMENT #3 In that case, the way that ODF image objects carry multiple renditions is wasteful to the degree that a separate static rendering is also created and might not be as good as the WMF. That may or may not be important. It may be necessary to still carry an alternative graphic or bitmap for non-Windows implementations where there is no attempt to interpret an OLE object. But for AOO (and presumably LibO) which have cross-platform implementations, it would usually be desirable to have the OLE object earlier in the list of alternatives and to use the static image that it carries when possible, even if no OLE "server" application is ever available. -- You are receiving this mail because: You are the assignee for the bug.
