Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Table of Contents not correctly exported to Word format | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Writer | Reporter: | bvankuik <ooo> | ||||||
Component: | code | Assignee: | michael.ruess | ||||||
Status: | CLOSED FIXED | QA Contact: | issues@sw <issues> | ||||||
Severity: | Trivial | ||||||||
Priority: | P3 | CC: | issues | ||||||
Version: | OOo 1.1 Beta | ||||||||
Target Milestone: | --- | ||||||||
Hardware: | PC | ||||||||
OS: | Linux, all | ||||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||||
Developer Difficulty: | --- | ||||||||
Attachments: |
|
Description
bvankuik
2003-04-28 08:08:39 UTC
Created attachment 5920 [details]
A testdocument with a table of contents, created in 1.1beta
Created attachment 5921 [details]
How the testdocument looks like, when opened in Word 2000 (on Windows 2000)
reassigned to mru 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? 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! . estimated effort disappeared ready for QA Ready for QA Checked fix in CWS hbqea101. Verified. Reopened. Issue still exists after integration of CWS. Tested with 680m41. MRU->HBRINKM: problem still occurs in 680m41. AMA->FME: Please have a look. *** Issue 37044 has been marked as a duplicate of this issue. *** 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? FME->MRU: Please have a look. 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. Closed. |