Bug 144894 - Numbering capter
Summary: Numbering capter
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.1.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-03 11:34 UTC by Ivo
Modified: 2021-12-20 15:57 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenprints of both LO versions with examples (684.40 KB, image/png)
2021-10-19 05:16 UTC, Ivo
Details
test file for 144894 (11.52 KB, application/vnd.oasis.opendocument.text)
2021-12-20 14:58 UTC, Cor Nouws
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ivo 2021-10-03 11:34:07 UTC
Description:
The prefix does not appear annymore if numbering is off. But I would like to used is with "meeting " and then the date. So i don't need a generated number. It worked well till fore last version

Steps to Reproduce:
1. define capter number, no numbering but do use a prefix
2. type tekst
3. ^1 to apply heading 1.

Actual Results:
3 oktober 2021

Expected Results:
Meeting: 3 oktober 2021


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.2.1.2 (x64) / LibreOffice Community
Build ID: 87b77fad49947c1441b67c559c339af8f3517e22
CPU threads: 6; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: nl-NL
Calc: CL
Comment 1 Ivo 2021-10-19 05:16:12 UTC
Created attachment 175827 [details]
Screenprints of both LO versions with examples

screenprints with both versions of LibreOffice
Comment 2 Ivo 2021-10-19 05:17:00 UTC
What more comments is needed?
Comment 3 Dieter 2021-10-24 10:21:53 UTC
I can't confirm this.

Tested with following steps:
1. Tools => Chapter numbering
2. For level 1 in Separator => Before add "Meeting" => OK
3. Change paragraph style to Heading 1

Actual result: "Meeting" appears

Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 56883788d0090383dad58552f5a11044ffe64a44
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL

Ivo, do you get a different result with same steps? If this is the case, you should try in SafeMode 8Help => Restart in SafeMode)

=> NEEDINFO
Comment 4 Ivo 2021-10-24 15:16:46 UTC
Tools: chapternumbering
level 1: number = none (where default is 1,2,3, ...)
prefix: meeting

If I use numering 1,2,3, ... it works
If I use non than I don't see the prefix anymore. 

I think you used numbering 1,2,3 ... instead of none
Comment 5 Dieter 2021-10-24 15:58:55 UTC
(In reply to Ivo from comment #4)
> I think you used numbering 1,2,3 ... instead of none

 No  I used "none". Does it also happen in SafeMode?
Comment 6 Ivo 2021-10-24 16:48:27 UTC
version 7.2.1.2 (x64)
safemodus
if i don't use a number, i don't see the prefix

the document reacts the same as the previes window right of leven an numbering
Comment 7 QA Administrators 2021-10-25 03:56:40 UTC Comment hidden (obsolete)
Comment 8 Ivo 2021-11-02 07:33:28 UTC
Just re-installed version 7.2.0.4 en there it works fine
Comment 9 Ivo 2021-11-24 09:38:47 UTC
sorry
7.2.0.4 doesn't work fine.
Try first lever numbering, second level none. You get "2. chapter" in stead of "chapter"
Comment 10 Cor Nouws 2021-12-20 14:58:29 UTC
Created attachment 177041 [details]
test file for 144894

Hi Ivo,

Your description is clear. For me it works in the attached document (7.3.0 Alpha0)
Comment 11 Dieter 2021-12-20 15:09:15 UTC
Ivo, ould you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/current.html ? You can install it alongside the standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Comment 12 Ivo 2021-12-20 15:55:18 UTC
Perfect! Thank you.
Best regards
Ivo
Comment 13 Ivo 2021-12-20 15:56:15 UTC
I mean, everything is working as it should be. De bug is resolved
Comment 14 Dieter 2021-12-20 15:57:54 UTC
(In reply to Ivo from comment #13)
> I mean, everything is working as it should be. De bug is resolved

=> RESOLVED WORKSFORME