Bug 169233 - AutoNumLgl Not Imported Correctly
Summary: AutoNumLgl Not Imported Correctly
Status: RESOLVED DUPLICATE of bug 61619
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
25.8.2.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-03 17:32 UTC by jhoggood
Modified: 2025-11-07 05:26 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample document showing AutoNumLgl legacy field. (18.10 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2025-11-03 17:41 UTC, jhoggood
Details
Libre Office 25.8.2.2 version (10.49 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2025-11-04 15:54 UTC, jhoggood
Details
MS Word 365 version (15.35 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2025-11-04 16:01 UTC, jhoggood
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jhoggood 2025-11-03 17:32:39 UTC
Description:
Here's a Heading Level 3 (Chapter 14) as it was in MS Word 365 via an AutoNumLgl field. It's missing the "." separator character but generally that field type doesn't appear to come over correctly.  For example:

5.2.1. 14 Firm: Key Questions for Vetting Fees and Compensation

Steps to Reproduce:
1. Open the attached sample doc.
2. Look at the Heading Level where I added the Tools/Heading Numbering but also the lingering AutoNumLgl field from MS Word 365.


Actual Results:
1. Open the attached sample doc.
2. Look at the Heading Level where I added the Tools/Heading Numbering but also the lingering AutoNumLgl field from MS Word 365.

Expected Results:
Correctly import Word AutoNumLgl and other field types.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Correctly import Word AutoNumLgl and other field types.
Comment 1 jhoggood 2025-11-03 17:41:00 UTC
Created attachment 203707 [details]
Sample document showing AutoNumLgl legacy field.

There is also a LibreOffice Tools/Heading Numbering inserted just prior to the AutoNumLgl field.
Comment 2 GJord 2025-11-04 11:48:06 UTC
Thank you for reporting the bug.

I tested the attached sample document with:

Version: LibreOfficeDev 26.2.0.0.alpha0 (x86_64)
Build ID: [copy from Help ▸ About LibreOfficeDev]
OS: Windows 11

Result:
The AutoNumLgl numbering in the heading now imports correctly.
It displays “1.16 Evaluating Services…” with the dot separator,
matching the behavior in Microsoft Word 365.

Also tested on:
Version: LibreOffice 25.8.2.2 (x86_64)
Build ID: d401f2107ccab8924a8e2df4...
OS: Windows 11

Result:
The same correct behavior.

Comparison with MS Word 365 on Windows 11:
Word also shows “1.16 Evaluating Services and Expertise for Retirees,”
and LibreOffice displays the same numbering format.

→ The issue is not reproducible on my current stable and master builds on Windows 11.
Comment 3 jhoggood 2025-11-04 15:54:00 UTC
Created attachment 203728 [details]
Libre Office 25.8.2.2 version
Comment 4 jhoggood 2025-11-04 16:01:48 UTC
Created attachment 203729 [details]
MS Word 365 version
Comment 5 jhoggood 2025-11-04 16:05:04 UTC
I'm not seeing the same results.  I have now attached an original MS Word 365 source file that I then opened in LibreOffice 25.8.2.2. You will see in LibreOffice missing Heading Numbers and the "." heading suffix. In some documents, like the one I shared yesterday, you see the Heading Numbers aren't 1., 1.1, 1.1.1 but rather 1, 2, 3, ... also. If you save the Word document in LibreOffice and then re-open in Word you will then see missing Heading Numbers like the save in LibreOffice changed the field.
Comment 6 Buovjaga 2025-11-07 05:26:41 UTC
(In reply to jhoggood from comment #4)
> Created attachment 203729 [details]
> MS Word 365 version

The issue is seen with this file in LibreOffice after doing Tools - Update - Update All, but I found an older report about this.

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