Bug 120396 - FILEOPEN 2nd level numbering doesn't increase properly in attached DOC (DOCX OK)
Summary: FILEOPEN 2nd level numbering doesn't increase properly in attached DOC (DOCX OK)
Status: RESOLVED DUPLICATE of bug 104239
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: All All
: low normal
Assignee: Not Assigned
Keywords: filter:doc
Depends on:
Blocks: DOC-Bullet-Number-Lists
  Show dependency treegraph
Reported: 2018-10-07 23:49 UTC by Aron Budea
Modified: 2021-04-21 09:11 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Sample DOC (29.50 KB, application/msword)
2018-10-07 23:49 UTC, Aron Budea
PDF exported in Word (4.85 KB, application/pdf)
2018-10-07 23:51 UTC, Aron Budea

Note You need to log in before you can comment on or make changes to this bug.
Description Aron Budea 2018-10-07 23:49:39 UTC
Created attachment 145458 [details]
Sample DOC

Open the attached document.
Numbering should increase like this: 1, 1.1, 2, 2.1, 2.2.
Instead it's: 1, 1.1, 2, 1.2, 1.3.
Observed using LO (2018-09-22, 8b1501d80dc9d3f42c351c6e026fa737e116cae5) & 3.3.0 / Windows 7.
Comment 1 Aron Budea 2018-10-07 23:51:55 UTC
Created attachment 145459 [details]
PDF exported in Word
Comment 2 MM 2018-10-08 00:27:12 UTC
Confirmed on windows 7 x64 with Version: (x64)
Build ID: 5d2cb2a5dd04fe174b336488731eb50bbb5faed3
CPU threads: 3; OS: Windows 6.1; UI render: default
Comment 3 Timur 2019-09-06 12:20:42 UTC
Messy DOC with Heading3 is 2nd level numbering. So I set to Low.
But repro with today's 6.4+. No repro if DOC saved in MSO as DOCX.
Comment 4 Justin L 2020-04-23 19:41:49 UTC
*** Bug 40272 has been marked as a duplicate of this bug. ***
Comment 5 Justin L 2021-04-21 09:11:19 UTC
Duplicate of bug 104239.

Heading 3 is not considered to be part of Chapter Numbering (because iLvl[1] and OutLvl[2] don't match). So they can't share the same numbering style. One is the secret "Outline", and the other is WWN8um2

*** This bug has been marked as a duplicate of bug 104239 ***