Bug 143680 - header displays incorrect chapter number
Summary: header displays incorrect chapter number
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.0.1 rc
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-01 19:53 UTC by TorrAB
Modified: 2022-05-03 11:15 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
file with Headings 1…5 (16.72 KB, application/vnd.oasis.opendocument.text)
2021-08-01 19:53 UTC, TorrAB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description TorrAB 2021-08-01 19:53:01 UTC
Created attachment 174017 [details]
file with Headings 1…5

In Header.odt, the first page contains 5 paragraphs, styles Heading1…5.
These appear in the header in the 2nd page (№ 1). The last 3 fields are numbered, with each number separated by a colon (Tools>ChapterNumbering) Each colon is (unexpectedly) repeated — ‘::’.
Comment 1 Robert Großkopf 2021-08-02 10:32:51 UTC
Couldn't confirm colon is repeated in Heading 3, 4 and 5.

My system: OpenSUSE 15.2 64bit rpm Linux
LO:
Version: 7.2.0.2 / LibreOffice Community
Build ID: 614be4f5c67816389257027dc5e56c801a547089
CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: en-US
Calc: threaded
Comment 2 TorrAB 2021-08-02 13:25:48 UTC
(In reply to Robert Großkopf from comment #1)
> Couldn't confirm colon is repeated in Heading 3, 4 and 5.
> 
> My system: OpenSUSE 15.2 64bit rpm Linux
> LO:
> Version: 7.2.0.2 / LibreOffice Community
> Build ID: 614be4f5c67816389257027dc5e56c801a547089
> CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb)
> Locale: de-DE (de_DE.UTF-8); UI: en-US
> Calc: threaded

Correct. I was using Version: 7.2.0.1
Bug gone in Version: 7.2.0.2.
Comment 3 Xisco Faulí 2022-05-03 11:15:56 UTC
Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been
identified.