Bug 94247 - Export to DOCX: List numbering continues on other list in specific ODT
Summary: Export to DOCX: List numbering continues on other list in specific ODT
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: All All
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2015-09-15 15:10 UTC by xuanngo2001
Modified: 2016-09-23 06:55 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample file contains only 2 lists (5.99 KB, application/vnd.oasis.opendocument.text)
2015-09-15 15:10 UTC, xuanngo2001
Details

Note You need to log in before you can comment on or make changes to this bug.
Description xuanngo2001 2015-09-15 15:10:53 UTC
Created attachment 118748 [details]
Sample file contains only 2 lists

My odt file contains 2 lists: List 1 and List 2. They are listed as followed:

List 1
1. item 1
2. item 2
3. item 3

List 2
1. item 1
2. item 2
3. item 3

When I saved as "Microsoft Word 2007/2010/2013 XML(.docx)". It listed as followed:

List 1
1. item 1
2. item 2
3. item 3

List 2
4. item 1
5. item 2
6. item 3

List 2 numbering is continued from the List 1. I expect List 2 numbering to start from 1.

See list-numbering-to-export.odt attached as an example.
Comment 1 Buovjaga 2015-10-09 17:37:41 UTC Comment hidden (obsolete)
Comment 2 Buovjaga 2015-10-12 10:07:53 UTC
Reproduced.

Kubuntu 15.04 64-bit KDE Plasma 5.4
Version: 5.0.2.2
Build ID: 00m0(Build:2)
Locale: en-US (en_US.UTF-8)
Comment 3 Timur 2015-10-13 14:41:54 UTC
Regression with the attached document. Not reproduced from scratch.
Comment 4 Xisco Faulí 2016-09-20 16:10:38 UTC
Adding keyword 'bibisectRequest' to see whether this regression is already present in the oldest build of bibisect-43all repository or not.
In case it's already present, change 'bibisectRequest' to 'preBibisect'.
Otherwise, change 'bibisectRequest' to 'bibisected' and add a comment with the output from 'git bisect log'
Comment 5 Timur 2016-09-22 16:09:54 UTC
I don't know if this is worth bibisecting and possible. 
We should've figured out how this specific document was created, because this is not reproducible creating those lists from scratch. xuanngo, can you help please?
Comment 6 xuanngo2001 2016-09-22 22:38:54 UTC
@Timur 
I no longer remember how this doc is created.
I'm therefore closing this bug.
Comment 7 Timur 2016-09-23 06:55:08 UTC
Thank you. As a note, I tried creating from scratch with 4.3.2.2 on Windows and with 5.0. in Linux and couldn't reproduce. 
Maybe it's about some combination, maybe about the exact steps how it was created. ODT itself also seems not valid, when looked directly. 

It's true there is sth. wrong here, because LO before and MSO now still save it properly, but not being able to reproduce and having the issue on a specific document only will almost certainly hinder solving it indefinitely. 
I agree with having this bug closed, and the moral here is to test and write all the details while it's fresh, and not to confirm before it's all clear.