https://bugs.documentfoundation.org/show_bug.cgi?id=69795
--- Comment #19 from Mike Kaganski <[email protected]> --- (In reply to Andreas Heinisch from comment #18) As I mentioned in https://gerrit.libreoffice.org/c/core/+/132120, I see how it's logical that getString should be symmetrical to setString (or whatever the underlying functions are called). So if getString uses code to use system-specific line ends, then setString should use the same conventions. I see also how this potential change could likely cause regressions - we may have many places that rely on specific asymmetrical behavior of existing code. The current state is inconsistent anyway - the "good" situation on Linux is already not good: the paragraphs got converted into line breaks. Using system-dependent line ends, combined with the internal difference between paragraphs and line breaks, without a uniform convention like "paragraphs get represented as CR, and line breaks as LF, regardless of system", gives such a mess. (In reply to bugs.kde.attila from comment #17) > The last working version on Windows was OO 1.1.4. So that means, it has > worked on Linux, Windwos and MacOS. Of course, it would be interesting to see what was the result back then - was it always converting paragraphs into line breaks, too? Regardless, as said, the state on Linux is already a bug. I'd think that copying text by using String property should not be used, or should be used in a paragraph iterator (which is how the macro should be changed, but not a solution of this problem per se). Even if we suddenly decided to break everything by settling on "this character will mean paragraph, and this line break", we would still have multiple other things that would "looks different" - like not copying fields as fields, or footnotes, etc. -- You are receiving this mail because: You are the assignee for the bug.
