https://bugs.documentfoundation.org/show_bug.cgi?id=159554
Mike Kaganski <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |1974, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |2158 --- Comment #3 from Mike Kaganski <[email protected]> --- (In reply to Tex2002ans from comment #2) > - On Copy/Paste to new document, trying to carry over these compatibility > flags becomes a nightmare (and has caused many large regressions in the > past). Right. Carrying compat flags was accidentally happening in the past, and became visible after commit a7d9837a8aa6d1233f4c21e4db5d32428a3ffc58, and caused bugs 151974, 151728, 152158 (see bug 151728 comment 4). It was fixed by commit 2d0a87f97e2c9ac50cd6ce329ca8256daf94ead4. Carrying flags would mean that, while the copied data would look as it was in the source, the *already existing text* in the target document could suddenly change its formatting. It is the sad outcome of having compatibility flags at all; and we indeed try hard to allow working with external formats, with their differences in behavior. The problem here is invisibility of the compatibility flag(s) to user. Making flags accessible is of course important, but even when we add that flag to the Options->Writer->Compatibility, will anyone really find out that some specific (of tens, potentially hundreds) flag there is responsible for the difference? MS Word adds a "[Compatibility Mode]" decoration to the document's title bar. Would it help? Maybe. Yet, given the huge amount of compat flags, it is easily possible, that both of your documents are is "compatibility modes" (i.e., some of the compatibility flags are in non-default state), but in *different* compatibility modes... -- You are receiving this mail because: You are the assignee for the bug.
