Issue 58562 - Numbering messed up when opening MS PowerPoint document
Summary: Numbering messed up when opening MS PowerPoint document
Alias: None
Product: Impress
Classification: Application
Component: open-import (show other issues)
Version: OOo 2.0.1
Hardware: PC Windows XP
: P3 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: ms_interoperability, oooqa
Depends on:
Reported: 2005-11-28 13:57 UTC by sajjen
Modified: 2013-08-07 15:21 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

.ppt file illustrating the problem (9.50 KB, application/
2005-11-28 13:59 UTC, sajjen
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description sajjen 2005-11-28 13:57:07 UTC
To reproduce the bug:

1. Create new document in PowerPoint
2. Enter text on multiple lines, with one blank line between each text line.
3. Add automatic numbering to the lines.
4. Save and open in Impress.
5. The numbering skips a number for each blank line. IE the first line gets the
number 1. The second line is empty and doesn't get a number. The third line gets
the number 3, in PowerPoint it gets number 2.
Comment 1 sajjen 2005-11-28 13:59:17 UTC
Created attachment 31862 [details]
.ppt file illustrating the problem
Comment 2 wolframgarten 2005-11-28 14:10:09 UTC
Reproducible. Reassigned.
Comment 3 tsealex 2006-01-27 02:21:07 UTC
Successfully reproduced the bug on OOo 2.0.1 with WinXP SP2 and Powerpoint 2003.
Reproducing the bug as follow:

1. Create new document in Powerpoint
2. Within a textbox, type in text as the following: "Hello" , a blank line, "World"
3. Select the textbox and add auto-numbering.
4. Save the file as "foo.ppt" and close Powerpoint.
5. Open the same "foo.ppt" using Impress.

Note that the "World" was numbered with "2." in Powerpoint, but numbered with
"3." in Impress.

Follow-up test as follow:

Number keep on increasing with new lines.
1. Insert another blank line on the blank line between "Hello" and "World"
Note that the word "World" is now numbered with "4."

Undo has no effect on the increased number when the textbox has the focus.
1. After the step on the above follow-up test, press "Undo".
Note that the word "World is still numbered with "4." instead of "3."

This bug is crucial since it doesn't display what the author of the original
file intended to display.  As the list contains more blank lines, the numbering
wouldn't serve its purpose.
Comment 4 zhouyihua 2006-01-27 18:13:40 UTC
1. I reproduced the bug with OOo 2.0.1 
My OS is Window XP Professional Version 2002 Service Pack 2.
The replicate steps as follows:

1.1 Open the title.ppt attached by the reporter with MS PowerPoint, I found the
document with number 1,2,3,4 displays correctly.
1.2 Open the title.ppt with Impress, and I found the numbers
1,2,3,4 became 1,3,5,7, which is incorrect.   

2.  I tested following cases:
2.1 In MS PowerPoint, I opened the file “title.pptâ€, deleted the “Numbering†and
blank lines between the original text lines; and then clicked on Numbering
button in the Toolbar to re-Numbering the text lines. I opened the file with OOo
2.0.1 again and it displayed correctly.

2.2 In MS PowerPoint, I inserted a blank line after each numbering line. Then,
opened the file with OOo 2.0.1 again and it displayed incorrectly with just the
same problem as mentioned in 1.2.
2.3 I tested another PowerPoint file in Chinese on my own computer disk, it
displayed correctly no matter me inserted the blank lines or not.

3. When using MS PowerPoint to open the file, if you click on the blank lines in
between of item lines, then, you can see the number in light grey color as same
as the previous line number showed there. I guess that just those numbers
prevent the numbering from counting error in MS Powerpoint. 

Comment 5 sven.jacobi 2006-04-03 07:58:22 UTC
sj->tl: This issue is about an outliner problem. In OOo the third paragraph is not 
capable to have a numbering of 2. I think this issue is double to an existing issue, 
but I couldn't find it.