Bug 61619 - : Word import AUTONUMLGL fields
Summary: : Word import AUTONUMLGL fields
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.0.0.3 release
Hardware: All All
: low enhancement
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: filter:doc
Depends on:
Blocks: DOC-Fields
  Show dependency treegraph
 
Reported: 2013-02-28 14:42 UTC by John
Modified: 2023-08-25 16:44 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Example document has autonumlgl fields in it which get imported as 1 to 8 (28.00 KB, application/msword)
2013-02-28 14:42 UTC, John
Details
Contains ListNum LegalDefault field codes (31.00 KB, application/msword)
2013-02-28 17:34 UTC, John
Details

Note You need to log in before you can comment on or make changes to this bug.
Description John 2013-02-28 14:42:36 UTC
Created attachment 75697 [details]
Example document has autonumlgl fields in it which get imported as 1 to 8

Writer does not import the AUTONUMLGL field as expected, it converts to a simple number sequence.  
This is also reported in OpenOffice Issue 25362            
Operating System: Windows 7
Version: 4.0.0.3 release
Comment 1 Joel Madero 2013-02-28 17:02:24 UTC
Thank you for reporting this issue! I have been able to confirm the issue on:
Version 4.1.0.0.alpha0+ (Build ID: b8e0455f201198b1deb8f8ca0181e6c9cadc335)
 Date:   Sat Feb 23 16:04:37 2013 -0600 
Platform: Bodhi Linux 2.2 x64
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

As I've been able to confirm this problem I am marking as:

New (confirmed)
Enhancement (this is requesting additional features that currently are not supported by LibreOffice)
Low

The reason why I put low is because even my MS threads on office.microsoft.com I see "AutoNumLgl field numbers....is considered obsolete but is provided for compability with older version of MS Office"


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link:
https://wiki.documentfoundation.org/QA/BugTriage and join us on freenode at #libreoffice-qa

Also, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant 

Lastly, if you don't have time to donate, please consider monetary donation to our great non profit by looking here: http://donate.libreoffice.org/ so we can continue to provide the infrastructure, support, bug fixes, etc... that we all enjoy so much. Remember even $5 goes a long way :)
Comment 2 John 2013-02-28 17:34:57 UTC
Created attachment 75702 [details]
Contains ListNum LegalDefault field codes

Thankyou for your prompt response.
I have replaced the field with {ListNum LegalDefault} which seems to be the new format MS Word is useing.
Now when I import the number it mostly retains the legal structure but the numbers are now in a random order.
I have attached a new document as an example, which should have same numbering as the original.
Comment 3 Joel Madero 2013-02-28 17:40:04 UTC
Indeed - that is a separate issue. If you write up a new bug and CC me on it I'll confirm it. I'll mark that as a true bug not an enhancement as it's clearly screwing up the numbers.
Comment 4 Alexander Borouhin 2023-08-25 16:44:14 UTC
The bug is still present in the latest version:

Version: 7.6.0.3 (X86_64) / LibreOffice Community
Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: CL threaded

AUTONUMLGL fields upon opening MS Word document are not displayed at all, just thin shades (if field shading is on), without any numbers. After toggling display field names setting (Ctrl+F9) on and back off, the numbers appear, but they are just a single one-level sequence, completely ignoring the outline level of a paragraph.

This bug together with #44319 (non-working LISTNUM LegalDefault fields) is absolutely critical for dealing with highly structured documents having multi-level numbering. As automatic multi-level list numbering and multi-level list styles are not very predictable in MS Word, these 2 fields are extensively used by professionals in legal documents, technical writing etc.