Created attachment 181865 [details] The example file in current nightly and Word 2010 The attachment 181863 [details] of bug 150474 contains a hidden paragraph end mark at the end of the first Lorem ipsum paragraph. In Word this causes the following empty paragraph to move up when formatting marks are hidden. In Writer the empty paragraph would remain. 1, Open attachment 181863 [details] 2, Hide formatting marks. There is an empty paragraph between the Lorem and the Nunc paragraphs, unlike in Word. Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 8475b367298de73aec6abc60a159cc015baf9734 CPU threads: 14; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: threaded Also happens way back to 3.5
Created attachment 181866 [details] The example file in current nightly and Word 2010 with formatting marks hidden
Gabor, I confirm the described difference when hiding formatting marks, but I don't understand, why behaviour in Writer is wrong. I won't expect layout change when hiding formatting marks. Could you please explain? => NEEDINFO Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 4c96abd81460977d413d4d28e891bbbac5769ede CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL
Hi Dieter This is the Hidden character property. Characters with this attribute are hidden - so the layout changes - when - you try to print the document and turn the Print Preview on (and on paper as well) - turn ON the Options - Writer - Formatting Marks - Hidden Characters setting and after that press the PI icon. (This is not the default setting in Writer, but it is in Word) In this example file the hidden attribute of the paragraph end sign is not imported, so it is not hidden in these cases.
ah sorry for setting this to new.
It works now thanks to https://git.libreoffice.org/core/commit/a25eda715591cfa96136bcfd95360156516239d1 tdf#131386 writerfilter: RTF import paragraph mark formatting *** This bug has been marked as a duplicate of bug 131386 ***