https://bugs.documentfoundation.org/show_bug.cgi?id=146917

            Bug ID: 146917
           Summary: FILESAVE DOCX: Direct formatting is applied to
                    paragraph thus negative first line indent is lost
           Product: LibreOffice
           Version: 7.4.0.0 alpha0+ Master
          Hardware: All
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Created attachment 177700
  --> https://bugs.documentfoundation.org/attachment.cgi?id=177700&action=edit
testFirstLineIndent.odt

In the attached test odt file, the paragraph "FIELD NUMBER 1.0" and "FIELD
NUMBER 2.0" has paragraph style "Field Number" applied, which has a first line
indent of -5cm and a "before text" indent of 5cm. There is a tab stop after the
":".  There is no direct formatting on any part of the text, as can be observed
from the "Styles Inspector" sidebar deck.

When this document is exported to DOCX, the *direct* formatting of "Para First
Line Indent" (with the value 0) is applied two these two paragraphs, thus the
format has changed.

Steps to Reproduce:
1. Open the attached odt and save as DOCX.
2. Reopen the saved DOCX.

Current Result:
The paragraph "FIELD NUMBER 1.0" and "FIELD NUMBER 2.0" has direct formatting
applied which set the first line indent to 0. As a result, the first line goes
to the 5cm position rather than in the -5+5=0cm position.

Expected Result:
The paragraph "FIELD NUMBER 1.0" and "FIELD NUMBER 2.0" should use the para
style "Field Number", without any direct formatting.

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: e8b45704fc8d41a42d2272cb14bb40ee59516768
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: zh-CN (zh_CN.UTF-8); UI: zh-CN
Build Platform: Fedora34@X64, Branch:master, bibisect-linux-64-7.4-CN
Calc: threaded
Fedora 34, gnome x11.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to