Created attachment 120570 [details] DOCX file Attached DOCX file created using MS Office Word. It contains numeration list: 1.1.1 A 1.1.2 B 1.1.3 C But LibreOffice Writer display it wrong: 1.1.1 A 1.1.2 B 1.1.1 C LibreOffice version: 5.0.3.2 MS Office version: 14.0.6129.5000
Created attachment 120571 [details] MS Word screenshot
Created attachment 120572 [details] LO Writer screenshot
Current behavior from 3.6. It was worse before.
This may be related to Bug 94819 or maybe Bug 76817 or even Bug 50774. <w:p w:rsidR="00B8717E" w:rsidRPr="00B03AA7" w:rsidRDefault="00184B0E" w:rsidP="00C367F5"> <w:t>A</w:t> <w:p w:rsidR="00B8717E" w:rsidRPr="00B03AA7" w:rsidRDefault="00184B0E" w:rsidP="00C367F5"> <w:t>B</w:t> <w:p w:rsidR="008D18EC" w:rsidRPr="00641F6C" w:rsidRDefault="00184B0E" w:rsidP="00184B0E"> <w:t>C</w:t> https://blogs.msdn.microsoft.com/brian_jones/2006/12/11/whats-up-with-all-those-rsids/ w:rsid XML tags are inserted in the document file when Track Changes is turned on, or when you use the Compare Documents feature. LO doesn't read that well, but it's easy to say: continue previous numbering.
The key to fixing this will be to pruning out identical list styles. <w:num w:numId="1"> <w:abstractNumId w:val="24"/></w:num><w:num w:numId="2"><w:abstractNumId w:val="23"/></w:num><w:num w:numId="3"><w:abstractNumId w:val="27"/></w:num><w:num w:numId="4"><w:abstractNumId w:val="35"/></w:num><w:num w:numId="5"><w:abstractNumId w:val="39"/></w:num><w:num w:numId="6"><w:abstractNumId w:val="24"/></w:num>
The key to fixing this will be to pruning out identical list styles. In this case, both style1 and style6 both use abstract style 24 with no modifications. <w:num w:numId="1"> <w:abstractNumId w:val="24"/> </w:num> <w:num w:numId="6"> <w:abstractNumId w:val="24"/> </w:num> <w:pPr> <w:pStyle w:val="-3"/> #para style Пункт-3 using list numId=6 ilvl=2 </w:pPr> <w:r> <w:t>B</w:t> </w:r> <w:pPr> <w:pStyle w:val="-3"/> <w:numPr> <w:ilvl w:val="2"/> <w:numId w:val="1"/> </w:numPr> </w:pPr> <w:r> w:t>C</w:t> </w:r>
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
so it looks like a "list" in Word is defined by a w:abstractNum instance and everything derived from it via w:num is part of the list? i don't find that documented anywhere, but i just read the OOXML numbering stuff for the first time, but this is consistent with a couple documents i made in Word 2013. hmmm comment #6 has a relatively easy to implement fix for this document, but in general a w:num can contain a w:lvlOverride which would require a numbering style in writer's model. perhaps the w:lvlOverride properties could all be set on the paragraph itself where it's applied, but that doesn't appear to be ideal. but it looks like SwList can actually hold arbitrary SwTextNodes - while it does have a "default" list style, you can manually set ListId property on any SwTextNode to add it to a SwList. i'll try to get DomainMapper to do that...
Michael Stahl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/7992bd73a2307edce96a145e954f8e4c3ab9f57d%5E%21 tdf#95848 writerfilter: DOCX import: fix mapping of w:abstractNum It will be available in 6.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Michael Stahl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/1f6b7030cbdc81e8e408e3a13bfcd01fcbdd7550%5E%21 tdf#95848 sw: DOCX export: crude implementation of abstractNum mapping It will be available in 6.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Michael Stahl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/632ee9aae6d5f3cf08b6d6b2789310c20db713b7%5E%21 tdf#95848 sw: DOCX export: export w:lvlOverride elements It will be available in 6.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
fixed on master; also fixed the export somewhere in the ECMA spec i find this which could be read as implying that a numbering definition corresponds to a "list" / "number tree" ... but the attached document is evidence that this isn't the case; the hypothesis that an abstract numbering definition corresponds to a list is more likely. "The numbering at any particular numbering level is restarted when a paragraph in the current document from the same numbering definition uses the level specified in the lvlRestart element for this numbering level."
*** Bug 94819 has been marked as a duplicate of this bug. ***
*** Bug 50774 has been marked as a duplicate of this bug. ***
*** Bug 102264 has been marked as a duplicate of this bug. ***
Michael, kudos for your work. You deserved an all-included visit to Spain for this one :) I hope I'm right with those duplicates.
*** Bug 108557 has been marked as a duplicate of this bug. ***
Another one fixed is attachment 152672 [details], wrongly attached in Bug 51168.
This one also fixed attachment 119772 [details] from Bug 95189, but it regressed later so bug is still open.