Bug 37991 - [docx import] Numeric list starting at 0 starts at 1 in Writer
Summary: [docx import] Numeric list starting at 0 starts at 1 in Writer
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.4.0 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-06 07:21 UTC by Chris Douglass
Modified: 2015-05-14 18:57 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
.docx created by Word containing a list that begins at 0 (13.53 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2011-06-06 07:21 UTC, Chris Douglass
Details
Screenshot as rendered in Word 2010 (9.10 KB, image/png)
2011-06-06 07:26 UTC, Chris Douglass
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Douglass 2011-06-06 07:21:16 UTC
Created attachment 47601 [details]
.docx created by Word containing a list that begins at 0

Creating a numeric list beginning at 0 in MSWord, saving as .docx and opening in LibreOffice 3.4.0 (000340m1 build:12) results in LibreOffice displaying a list starting at 1.

Attached is a minimal .docx that demonstrates the error.
Comment 1 Chris Douglass 2011-06-06 07:26:01 UTC
Created attachment 47602 [details]
Screenshot as rendered in Word 2010

Numeric list begins at 0 for Item 0
Comment 2 Andras Timar 2011-06-06 23:57:30 UTC
Cedric, can you please look into this?
Comment 3 Rainer Bielefeld Retired 2011-06-10 02:57:39 UTC
RC2 is bit by bit identical with release version, so separate items in the version picker are useless. Changes have been discussed with Michael Meeks.
Comment 4 A (Andy) 2013-04-27 11:08:37 UTC
reproducible with LO 4.0.2.2 (Win7 Home, 64bit)
Comment 5 Cédric Bosdonnat 2014-01-20 08:57:39 UTC
Restricted my LibreOffice hacking area
Comment 6 Joel Madero 2015-05-02 15:43:26 UTC
** 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 (4.4.2 or later)
   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 your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
Comment 7 Gordo 2015-05-14 18:57:06 UTC
Could not reproduce.

Windows Vista 64
Version: 4.4.3.2
Build ID: 88805f81e9fe61362df02b9941de8e38a9b5fd16

4.3.6.2

Bug still present in 4.2.8.2.

Changed to RESOLVED WORKSFORME.