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

Stéphane Guillou (stragu) <stephane.guil...@libreoffice.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stephane.guillou@libreoffic
                   |                            |e.org
                 OS|Linux (All)                 |All
            Version|7.3.7.2 release             |7.2.7.2 release

--- Comment #6 from Stéphane Guillou (stragu) 
<stephane.guil...@libreoffice.org> ---
Back in 7.1, the dot was not included:

Version: 7.1.0.3 / LibreOffice Community
Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

But back then, the behaviour was very inconsistent:
- only "before" character: kept
- only "after" character: stripped
- both "before" and "after" characters: both kept

Since 7.2, all "before" and "after" characters are kept:

Version: 7.2.7.2 / LibreOffice Community
Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

That was introduced by https://gerrit.libreoffice.org/c/core/+/117156, which
mentions: "changed cross-references values to lists: they are now including
full list label string"

However, the fix for bug 144563 restores the stripping of the final dot since
7.3.3 and 7.4.0 for MS Word compatibility reasons, but only when the full
reference ends with it. E.g. "1." becomes "1", but "1.(a)" stays the same (as
you've noticed already).

In my opinion, keeping all characters is more consistent. Why should the dot be
stripped but not the parentheses? But I can understand the appeal of having the
option to strip them or not, which could be done as described in bug 149635#c11

Also adding Heiko to CC, as he participated in related discussions.

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

Reply via email to