Issue 94525 - WW8: custom Outline numbering imported with wrong level assignment
Summary: WW8: custom Outline numbering imported with wrong level assignment
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: OOO300m7
Hardware: All All
: P4 Trivial (vote)
Target Milestone: 4.1.1
Assignee: openoffice
QA Contact:
URL:
Keywords: regression
Depends on: 78498
Blocks:
  Show dependency tree
 
Reported: 2008-10-01 11:22 UTC by osmium
Modified: 2017-05-20 10:35 UTC (History)
3 users (show)

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

Attachments
Sample doc (43.00 KB, application/msword)
2008-10-01 11:23 UTC, osmium 		no flags Details
Sample docx (12.45 KB, application/msword)
2008-10-01 11:24 UTC, osmium 		no flags Details
The contract broken (!!!) by us because of OpenOffice 3.0.1 (49.50 KB, application/msword)
2009-05-26 12:49 UTC, azimut 		no flags Details
Bug OpenOffice 3.0.1 (WinXP) (147.37 KB, image/jpeg)
2009-05-26 13:16 UTC, azimut 		no flags Details
Goog OpenOffice 2.4.2 (Windows) (62.94 KB, image/gif)
2009-05-26 13:17 UTC, azimut 		no flags Details
Good MS Word 2007 (152.32 KB, image/jpeg)
2009-05-26 13:18 UTC, azimut 		no flags Details
Good IBM Simphony (157.73 KB, image/jpeg)
2009-05-26 13:19 UTC, azimut 		no flags Details
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 osmium 2008-10-01 11:22:36 UTC 
Outline numbering resets to 1.x for each heading. This is quite a big issue 
that has been around for quite a while but never fixed.

I have 2 sample documents, one doc and one docx. Both created in Office 2007.
Comment 1 osmium 2008-10-01 11:23:35 UTC 
Created attachment 56942 [details]
Sample doc
Comment 2 osmium 2008-10-01 11:24:16 UTC 
Created attachment 56943 [details]
Sample docx
Comment 3 michael.ruess 2008-10-21 14:44:07 UTC 
MRU->OD: the level assignment of this custom outline rule is imported like the
default settings. But here, Heading 2 has been assigned to Level 1 and Heading 4
to Level 2, which is not recognized by the import.
Comment 4 Oliver-Rainer Wittmann 2008-10-21 15:17:58 UTC 
OD->HBRINKM: Please take over.
Comment 5 kpalagin 2009-05-26 12:25:28 UTC 
By the way, this is regression.
Comment 6 azimut 2009-05-26 12:49:02 UTC 
Created attachment 62526 [details]
The contract broken (!!!) by us because of OpenOffice 3.0.1
Comment 7 azimut 2009-05-26 12:57:43 UTC 
My company has broken contract signing since has printed it in OpenOffice 3.0.1.
I'm give you its first page. We have found out that this problem was not in
OpenOffice 2.4 Pro! You have spoilt the program! Precisely same problem in
KWrite. You have agreed? Why in OOo 2.4 Pro and IBM Symphony there is no such
problem? Over them competent programmers worked?
Comment 8 azimut 2009-05-26 13:16:41 UTC 
Created attachment 62530 [details]
Bug OpenOffice 3.0.1 (WinXP)
Comment 9 azimut 2009-05-26 13:17:35 UTC 
Created attachment 62531 [details]
Goog OpenOffice 2.4.2 (Windows)
Comment 10 azimut 2009-05-26 13:18:27 UTC 
Created attachment 62532 [details]
Good MS Word 2007
Comment 11 azimut 2009-05-26 13:19:14 UTC 
Created attachment 62533 [details]
Good IBM Simphony
Comment 12 azimut 2009-05-26 13:23:15 UTC 
We refuse use OpenOffice 3.x while this problem will not be corrected. Also we
aspire to extend as much as possible the information on this problem in
mass-media. It not defect.
Comment 13 azimut 2009-06-25 06:30:47 UTC 
Oct 2008-Jun 2009 = 9 month issue!
Fucking OpenOffice Developers!!! Fucking Sun!!
Comment 14 azimut 2009-08-21 13:27:43 UTC 
Oct 2008-Aug 2009 = 10 month issue!
FUCKING OPEN OFFICE!
Comment 15 Mathias_Bauer 2011-02-17 15:18:05 UTC 
According to our new regression issue handling for the 3.4 relrease the field
priority is now used as the order we want to work on them, no longer as a
"severity". The high number of regressions in the WW8 filters makes it necessary
to prioritize them as we won't be able to fix all of them for 3.4. We decided to
first focus on the export. Thus most regressions in the import filter now get
priority "P4", what means that they will be reevaluated in the next release cycle.
Comment 16 Oliver-Rainer Wittmann 2014-07-01 15:29:16 UTC 
fixed by changes made for issue 78498