| Summary: | FILESAVE: Numbering style not saved correctly on DOCX export | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Gabor Kelemen (allotropia) <kelemeng> |
| Component: | filters and storage | Assignee: | Justin L <jluth> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ilmari.lauhakangas, jluth |
| Priority: | medium | Keywords: | filter:docx |
| Version: | 3.5.0 release | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=95114 | ||
| Whiteboard: | target:6.2.0 target:6.1.0.2 | ||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 108770 | ||
| Attachments: |
Test document in odt
Test document in docx Side by side view of the two docs - Numbering style setting Side by side view of the two docs - Next style setting Next Style in MSO2013 |
||
|
Description
Gabor Kelemen (allotropia)
2016-09-27 08:43:39 UTC
Created attachment 127661 [details]
Test document in odt
Created attachment 127662 [details]
Test document in docx
Created attachment 127663 [details]
Side by side view of the two docs - Numbering style setting
Created attachment 127664 [details]
Side by side view of the two docs - Next style setting
View of the Organizer panel, the Next Style settings don't match.
The Inherit from and Category fields don't match either.
Created attachment 127715 [details]
Next Style in MSO2013
Opening the example document in MSO 2013 results in a correct Next Style being read.
Repro. Win 7 Pro 64-bit Version: 5.3.0.0.alpha0+ Build ID: e2f6c7f0d0cc14f851d7028ff846c5dc658a81c6 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-10-10_23:08:02 Locale: fi-FI (fi_FI); Calc: group LibreOffice 3.5.0rc3 Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735 proposed fixes for Question's Follow: https://gerrit.libreoffice.org/57074 tdf#102619 writerfilter: first create style, then set FollowStyle https://gerrit.libreoffice.org/57075 ~NFC related tdf#102619 writerfilter: use ConvertStyleName() The way DOCX numbering/lists are exported is garbage. Extremely complicated on the Microsoft side already, and then we need to emulate it to fit the LO model. A recipe for complete disaster. Leaving the bug open for someone else to deal with that problem. Justin Luth committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=39a4f21fc4a16f7c57a9b6f1ddd5ce2953781576 tdf#102619 writerfilter: first create style, then set FollowStyle It will be available in 6.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Justin Luth committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=ab16d43dd649b111e095a06f3b75ab77721830fe ~NFC related tdf#102619 writerfilter: use ConvertStyleName() It will be available in 6.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Justin Luth committed a patch related to this issue. It has been pushed to "libreoffice-6-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=3d9e0874becde20d901fda561633202e2e478eff&h=libreoffice-6-1 backport combined tdf#95115 and tdf#102619: writerfilter It will be available in 6.1.0.2. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Looks like this can be closed, thanks! |