Created attachment 168007 [details]
Steps to reproduce:
1. Open attached document
2. Save it as DOCX
3. Open it in MSO Word ( I'm using Word 2010 )
-> The numbers and the tabs in the numbering list are gone. See screenshot
Build ID: 84af20ef3ea72190784e9e7be820684c2558ba8c
CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
[Bug found by office-interoperability-tools]
Created attachment 168008 [details]
Comparison before and after RT ( MSO 2010)
Regression introduced by:
author Michael Stahl <Michael.Stahl@cib.de> 2020-10-19 19:41:36 +0200
committer Michael Stahl <email@example.com> 2020-10-20 09:00:25 +0200
commit 9e455724e50bf512683b1cddfeb7493e047c19ae (patch)
parent aa99b57cdc8cb3763aa935ed84e7d80c4e56a172 (diff)
sw: DOCX export: don't export numPr to style from outline numrule
Bisected with: bibisect-linux64-7.1
Adding Cc: to Michael Stahl
hi Michael Stahl,
should 9e455724e50bf512683b1cddfeb7493e047c19ae be reverted? I found other files with the same problem mentioned in this issue ?
(In reply to Xisco Faulí from comment #3)
> hi Michael Stahl,
> should 9e455724e50bf512683b1cddfeb7493e047c19ae be reverted? I found other
> files with the same problem mentioned in this issue ?
Michael is probably much braver than I am, but anytime there is a problem with numbering, I would revert and start over again - numbering is way too goofy to be sure about anything. Better to just start again from a clean slate.
Proposed revert at https://gerrit.libreoffice.org/c/core/+/109864
P.S. I got the same results testing with Word 2016.
*** Bug 139089 has been marked as a duplicate of this bug. ***
Reverted in https://cgit.freedesktop.org/libreoffice/core/commit/?id=32d11fb200d45cdacb973b625488d0b8bbee6d81
Closing as RESOLVED FIXED
Xisco Fauli committed a patch related to this issue.
It has been pushed to "master":
tdf#138780: sw_ooxmlexport12: Add unittest
It will be available in 7.2.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:
Affected users are encouraged to test the fix and report feedback.