Created attachment 110512 [details] A .doc file with automatically-numbered headings "Heading 2" automatic numbering is mysteriously lost on DOC import. Actions: 1. Load the attached .doc file into LibreOffice with automatically-generated heading numbers. These created by linking the paragraph types "Heading 1" and "Heading 2" to a list type named "Headings" ( per http://shaunakelly.com/word/numbering/numbering20072010.html ). Expected behavior: The first "Heading 2", with text "More stuff", should be preceded with the numbering "1.1" (as it is in Microsoft Word). Actual behavior: The "Heading 2" automatically-generated numbering is completely missing; only the text appears. This may be related to #87052. I tried working around the bug in #87052 involving DOCX import by creating a DOC file, and ended up with this probably-different bug. Which means I'm stuck!
Confirmed. Lowering severity a bit per https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg Win 7 64-bit Version: 4.5.0.0.alpha0+ Build ID: 170616e9f2d30c1302bbb5a7a4b588bc05cd5cc9 TinderBox: Win-x86@39, Branch:master, Time: 2014-12-12_01:58:46
Confirmed in Word viewer that More Stuff really has 1.1 preceding it. This bug is already present in 3.3.0. Ubuntu 14.10 64-bit LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
Reproducible with LO 5.1.0.1, Win 8.1
** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
still repro in Version: 6.3.0.0.alpha0+ Build ID: 2b9739b9b009de93efa4f24995469c3bb9d82261 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2018-12-18_23:09:56 Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded
repro with today's 6.4+
Created attachment 157727 [details] A .doc file compared MSO LO Repro LO 7.0+.
The Heading * styles in LO have special meaning, so it is dangerous to play with them. Check out tools - Chapter numbering and you will see that level 2 is empty. After fixing this I was able to round-trip it in LO. So the question now is, why is Word accepting the numbering, but LO isn't? repro 7.0+
This looks like the same thing as bug 106541
Ok, let's dupe to the newer report this time. *** This bug has been marked as a duplicate of bug 106541 ***