https://bugs.documentfoundation.org/show_bug.cgi?id=150835
Justin L <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |7637, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=13 | |3522 CC| |[email protected] Priority|medium |lowest Summary|FILESAVE RTF Images in |FILESAVE ODT->RTF: Images |table jump out of table in |in table jump out of table |Word |in Word --- Comment #4 from Justin L <[email protected]> --- This is the RTF equivalent of DOC export bug 157637. In LO, the default for tables/shapes is NOT to follow text flow, while the default for Word is to layoutInCell. This problem is compounded by the fact that when layoutInCell is not true, Word does NOT treat the cell paragraph that the image is anchored in as "the paragraph", but instead it treats the paragraph containing the entire table as "the paragraph", and so any positioning is done relative to "column/para" are done outside of the table. But there are so many exceptions and special cases with layoutInCell that any kind of mapping would be extremely hard to do. Plus layoutInCell is not a native RTF capability, but is handled via an application-specific-extension name/value pair. Basically, if LO's shape is (fully contained within the cell OR is wrap-through) AND is vertically and horizontally oriented "to entire paragraph", then export should flag it as "layoutInCell". It is worth noting that DOCX compat15 ALWAYS treats everything as layoutInCell, even if it is set to false. That suggests the best solution might be to always flag as layoutInCell if vertical/horizontal orientation is related to paragraph instead of page. -- You are receiving this mail because: You are the assignee for the bug.
