Issue 13886 - Table of Contents not correctly exported to Word format
Summary: Table of Contents not correctly exported to Word format
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 Beta
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords:
: 37044 (view as issue list)
Depends on:
Blocks:
 
Reported: 2003-04-28 08:08 UTC by bvankuik
Modified: 2013-08-07 14:41 UTC (History)
1 user (show)

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

Attachments
A testdocument with a table of contents, created in 1.1beta (5.70 KB, application/octet-stream)
2003-04-28 08:09 UTC, bvankuik 		no flags Details
How the testdocument looks like, when opened in Word 2000 (on Windows 2000) (863.34 KB, application/octet-stream)
2003-04-28 08:11 UTC, bvankuik 		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 bvankuik 2003-04-28 08:08:39 UTC 
When a table of contents is generated in Writer and the resulting document is
exported to Word, the page numbers don't align right neatly.

To reproduce:
Start writer or go to File -> New -> Text Document
Type two lines
Give line 1 the style 'Heading 1'
Give line 2 the style 'Heading 2'
Press CTRL+Home
Press CTRL+Enter
Press CTRL+Home again
Go to Insert -> Index and Tables -> Indexes and Tables
Click OK
Go to File -> Save As...
Save the file with filetype 'Microsoft Word 97/2000/XP (.doc)'
Load file in Word 97 or 2000
Notice how the page numbers do not correctly align to the right

Behaviour occurs in both 1.0.3.1 and 1.1beta. Opened the documents in both Word
97 and 2000 on Windows 2000.
Comment 1 bvankuik 2003-04-28 08:09:46 UTC 
Created attachment 5920 [details]
A testdocument with a table of contents, created in 1.1beta
Comment 2 bvankuik 2003-04-28 08:11:48 UTC 
Created attachment 5921 [details]
How the testdocument looks like, when opened in Word 2000 (on Windows 2000)
Comment 3 mci 2003-09-18 16:14:24 UTC 
reassigned to mru
Comment 4 michael.ruess 2003-09-23 10:49:09 UTC 
MRU->AMA: Interoperability. Writer does not display Tab Stops outside
the thext Area (such as: Tab of 18 cm on a default page). Word does.
Another one for the compatibility options?
Comment 5 andreas.martens 2003-09-25 09:58:23 UTC 
It's simple a bug in our index updating where the tab position is
calculated. It should be inside the text area for heading1 as well as
for heading2!
Comment 6 openoffice 2003-09-25 10:15:55 UTC 
.
Comment 7 openoffice 2004-02-03 15:56:49 UTC 
estimated effort
Comment 8 openoffice 2004-05-10 13:37:13 UTC 
disappeared
Comment 9 openoffice 2004-05-12 10:54:02 UTC 
ready for QA
Comment 10 openoffice 2004-05-12 10:55:43 UTC 
Ready for QA
Comment 11 michael.ruess 2004-05-13 15:04:53 UTC 
Checked fix in CWS hbqea101.
Comment 12 michael.ruess 2004-05-13 15:05:10 UTC 
Verified.
Comment 13 michael.ruess 2004-06-09 09:13:57 UTC 
Reopened. Issue still exists after integration of CWS. Tested with 680m41.
Comment 14 michael.ruess 2004-06-09 09:14:33 UTC 
MRU->HBRINKM: problem still occurs in 680m41.
Comment 15 andreas.martens 2004-12-03 13:35:33 UTC 
AMA->FME: Please have a look.
Comment 16 frank.meies 2004-12-09 12:11:46 UTC 
*** Issue 37044 has been marked as a duplicate of this issue. ***
Comment 17 frank.meies 2004-12-09 12:20:29 UTC 
FME->SBA: The calculation of the tab stop positions for tables of contents has
been corrected recently. Therefore we do not have any tab stop positions outside
the right margin in our tables of contents anymore. So this problem cannot occur
anymore with
a) new documents
b) existing documents whose tables of contents have been updated.
After discussing this with AMA, we agreed that we should consider this bug
'fixed'. Do you agree?
Comment 18 frank.meies 2004-12-09 14:08:20 UTC 
FME->MRU: Please have a look.
Comment 19 michael.ruess 2004-12-16 13:36:08 UTC 
Yes, I agree. For new documents created with OO 2.0 builds the problem does not
occur anymore. TOC's handling in OO 2.0 has changed a bit for more compatibility.
Comment 20 michael.ruess 2004-12-16 13:36:25 UTC 
Closed.