Issue 120438 - The third level numberings all become 1.x until next section when open the docx file
Summary: The third level numberings all become 1.x until next section when open the do...
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: 3.4.0
Hardware: All All
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-02 02:14 UTC by Xiu Li Xu
Modified: 2012-08-31 05:26 UTC (History)
2 users (show)

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

Attachments
sample file (42.71 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2012-08-02 02:14 UTC, Xiu Li Xu 		no flags Details
screenshot (8.77 KB, image/png)
2012-08-02 02:21 UTC, Xiu Li Xu 		no flags Details
patch for level numberings use it at writerfilter (468 bytes, patch)
2012-08-30 05:30 UTC, Bo.Tian 		no flags Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Xiu Li Xu 2012-08-02 02:14:13 UTC 
Created attachment 78813 [details]
sample file

Open the sample docx file, all the third level numberings become to 1.x, please see the attached screenshot.
Comment 1 Xiu Li Xu 2012-08-02 02:21:42 UTC 
Created attachment 78815 [details]
screenshot
Comment 2 Regina Henschel 2012-08-02 16:36:49 UTC 
The document uses different styles for the first and second item. Therefore it is imported with a restart of numbering. I don't know, why it is shown a,b,c in Word. If I set "continue numbering" explicitly in Word, the numbering is continues in AOO too.

The items should only show 1 sub-level in numbering, but show two. I don't know, where this is set in Word. But the feature to set the number of sub-levels is available in AOO and should be used.
Comment 3 Bo.Tian 2012-08-30 05:30:36 UTC 
Created attachment 79223 [details]
patch for level numberings
use it at writerfilter
Comment 4 Bo.Tian 2012-08-30 05:37:06 UTC 
I have find that the calculation of "GetParentNumbering" is wrong when level numberings has no parentnumbering

And the to (a) bug of this issue is not easy
the two (a) in the picture has different numId but the same abstractNumId.
So Aoo threat them as two different numbering :"WWNum46" and "WWNum26"
Does anyone have an idea how to fix it?