Summary: | FILESAVE DOCX Dots appear IN MS WORD for custom numbering | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Gabor Kelemen (allotropia) <kelemeng> |
Component: | Writer | Assignee: | Justin L <jluth> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | aron.budea, cno, jluth, stephane.guillou, vasily.melenchuk |
Priority: | medium | Keywords: | bibisected, bisected, regression |
Version: | 7.2.0.1 rc | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.documentfoundation.org/show_bug.cgi?id=148455 https://bugs.documentfoundation.org/show_bug.cgi?id=146257 https://bugs.documentfoundation.org/show_bug.cgi?id=156105 |
||
Whiteboard: | target:24.8.0 | ||
Crash report or crash signature: | Regression By: | Vasily Melenchuk | |
Bug Depends on: | |||
Bug Blocks: | 108770, 160789 | ||
Attachments: |
The example file saved by Writer master
The original file in Writer, with its docx version in Word and Writer screenshot of results for 3 versions of LO, DOCX opened in Office 365 Web |
Description
Gabor Kelemen (allotropia)
2022-05-24 10:23:46 UTC
Created attachment 180326 [details]
The original file in Writer, with its docx version in Word and Writer
Adding CC to: Vasily Melenchuk Created attachment 180487 [details] screenshot of results for 3 versions of LO, DOCX opened in Office 365 Web I've tried saving attachment 179687 [details] as DOCX with different versions of LO, and opening in Office 365 web: - with LO 6.4.7.2, I get headings (a) to (e) - with LO 7.3.3.2, I get headings (1.1.a) to (1.1.e) - with a recent LO 7.4 build, I get headings (1.1.a) to (1.1.c) then (1.1.a) and (1.1.b) again. Version: 7.4.0.0.alpha1+ / LibreOffice Community Build ID: 3676fb9d7b505d9f8079008b41e423b54663a86a CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Results are slightly different for me (see attachment 180487 [details]) but setting to NEW as things that should be hidden are now back.
repro 7.6+ So there are two problems here most likely. So far we have been tracking the export ODT->DOCX bug. There is also an import bug - LO doesn't import the resulting file in the same bad way. The import was the same as MSO (showing the dots) starting in 7.0 with commit 7459b9ecb54a298f02d19089620149718f8d8d48 Author: Vasily Melenchuk on Mon Apr 13 11:06:29 2020 +0300 tdf#116883: sw: support for lists level format string Multilevel lists are more flexible in case of DOCX. There is supported custom format for any level in DOCX unlike in LO and ODT where we are limited only with prefix and suffix for hardcoded list levels separated by dot. At the same time DOCX can have lists not only "1.2.3.4", but "1/2/3/4" or even "1!2>3)4" and such format can vary on each list level. The dots disappeared in the same 7.2.5 commit already mentioned for ODF. commit bf2b46aa15665dde63ceff4e7686b99b3990354f Author: Vasily Melenchuk on Sun Dec 26 20:38:30 2021 +0300 tdf#146257: sw: better handling for list numbering = NONE Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/71c49057deb1a696e4b0ce9d2091aaa28572b57a tdf#149258 sw ms export: no separator for NONE numbering level It will be available in 24.8.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. (In reply to Justin L from comment #7) > So there are two problems here most likely. So far we have been tracking the > export ODT->DOCX bug. fixed by comment 8's patch - with the caveat that since we don't import-display like MSO, we will simply lose that separator (for that level) in a round-trip. > There is also an import bug - LO doesn't import the resulting file in the > same bad way. Not really an import issue, since we import all the info - we just don't show the separator for a NONE level. Since it is highly unlikely that a document would be intentionally designed to show multiple separators, I'd say don't worry about this layout-visualization issue. (It would require yet another compatibility flag.) |