Created attachment 103336 [details] SourceDocument I am seeing some distortion when opening specific DOCX file, which is attached to the issue. This file is correctly opens in MS Word but have some broken parts in numbering when try to open it with LO Writer.
please post a comparative screenshot of the file in MS Word and LibO highlighting what you call "distortion"
HI Orbel, thanks for your bug report. I do see some odd indent behavior (complete text forced to the right margin of the page. Is that what you meant? If not, can you please attach a screenshot of what you mean with 'some broken parts in the numbering'. If there are multiple issues which doesn't related to each other, please do create a bug report for each separate issue. Kind regards, Joren
Hi Jorendc Yes, you're right, I do see the same behavior as you mentioned. Best regards, Orbel Mkrtchyan
(In reply to comment #3) > Hi Jorendc > Yes, you're right, I do see the same behavior as you mentioned. Okay, I'll attach a screenshot after I did run this bibisect. It is a regression. Kind regards, Joren
Created attachment 103338 [details] bibisectlog
Created attachment 103339 [details] Text forced completely to the right
Probably a regression of http://cgit.freedesktop.org/libreoffice/core/commit/?id=2123ede032ca64f696ef54af4ad3238974ca2b5d Thing is that Header3 style doesn't have a big indent, but the paragraph style of the erroneous text (header 3-style) do. So somehow this paragraph formatted differently (?direct formatting?). Paragraph Indent before text = 45,06 which is causing this big shift to the right. Kind regards, Joren
I did revert http://cgit.freedesktop.org/libreoffice/core/commit/?id=14d6cf1f8f86027d58fe56feae3139c314fbb058 and the huge right-shift is no more. So probably that patch is also related to this particular bug.
Created attachment 103342 [details] reduced test document
perhaps CC:ing the author of the commit in comemnt #8 is a good idea :)
(This is an automated message.) It seems that the commit that caused this regression was identified. (Or at least a commit is suspected as the offending one.) Thus setting keyword "bisected".
This issue is still present in Version: 5.0.1.2 Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261 Locale: es-ES (es_ES) on Windows 7 (64-bit)
Migrating Whiteboard tags to Keywords: (bibisected) [NinjaEdit]
Adding Cc: to Miklos Vajna
Corrupt document. I wouldn't worry too much about this one. In MSWord, go to the bullets and numbering context menu, and then without any further looking or changing, hit OK. The text will change to look like it does in LO.
(In reply to Justin L from comment #15) > Corrupt document. I wouldn't worry too much about this one. In MSWord, go > to the bullets and numbering context menu, and then without any further > looking or changing, hit OK. The text will change to look like it does in LO. Ok, let's close.