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

Justin L <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #5 from Justin L <[email protected]> ---
Fixed in 26.2.0 by 26.8 commit a4514488d92be420c4bfac0e0c0dea4c48bec37c
Author: Miklos Vajna on Mon Dec 22 08:26:50 2025 +0100
    tdf#169949 sw num rule defaults: let numbering type none imply follow by
none

    Load the document, press Ctrl-1 to set a heading 1 paragraph style, an
    unexpected leading tab shows up before the paragraph text.

    This went wrong with commit a7d9837a8aa6d1233f4c21e4db5d32428a3ffc58
    (tdf#148360: sw: do not ignore list label followed by, 2022-08-02),
    previously "followed by" was ignored by the layout if the numbering
    portion before the separator was empty. This is needed to correctly lay
    out DOCX files.

    Fix the problem by changing the default Outline numbering rule in
    Writer: the numbering type is set to "none", so also set the "label
    followed by" property to "nothing". Note that this doesn't affect DOCX
    files which already have heading styles configured, nor documents where
    the DocumentSettingId::NO_NUMBERING_SHOW_FOLLOWBY compatibility option
    is off.

    There was one handy side-effect of having "followed by" as "tab": once
    the UI was used to change the numbering type from "none" to e.g. Arabic,
    the user didn't have to explicitly ask for the tab separator, which is
    usually wanted. Continue supporting this scenario by checking for the
    "number type none + followed by nothing" scenario: if the number type
    changes to something else, then also change "followed by" to the old
    "tab" default.

    Change-Id: I60905623e6c4b6ded56a1a089ae0fb3af3b2bd3a
    Reviewed-on: https://gerrit.libreoffice.org/c/core/+/195706

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

Reply via email to