Issue 3254 - OO generated TOCs don't cross over to Word
Summary: OO generated TOCs don't cross over to Word
Status: CLOSED DUPLICATE of issue 3232
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: 641
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: caolanm
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-02-28 09:21 UTC by osavill
Modified: 2013-08-07 14:41 UTC (History)
1 user (show)

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


Attachments
TOC's get messed up exporting to Word (41.00 KB, application/octet-stream)
2002-03-01 14:31 UTC, osavill
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description osavill 2002-02-28 09:21:05 UTC
If you generate a TOC from OO and then export to Word to things happen :
1) The table is no longer justified
2) Word seems to have trouble even recognising that it is a TOC at all !

I will try and generate an example and attach
Comment 1 stefan.baltzer 2002-03-01 12:03:55 UTC
PLease attach an example.
Reassigned to Michael.
Comment 2 osavill 2002-03-01 14:31:53 UTC
Created attachment 1127 [details]
TOC's get messed up exporting to Word
Comment 3 osavill 2002-03-01 14:32:59 UTC
Look at the attached example in OO - lovely full width TOC, now look 
at it in Word - oops !
Comment 4 michael.ruess 2002-03-05 11:51:44 UTC
MRU->CMC: There seems to be a problem with the tabs. When we load the
file in Writer, the paragraphs in the Index have all hard tab attributes.
When the doc is loaded in Word, it seems that the paragraph style
values are used to build the index. Do we have a chance to get this right?
Comment 5 caolanm 2002-05-23 15:31:46 UTC
The reason they look different is because the tab stops in the
paragraph styles of the toc paragraphs are ignored in writer, and
honoured in word. Right now word is displaying it correctly, but the
writer core ignores tab stops in the table of contents. So its not
really a filter problem that there are no tabs used in writer's toc.
Remove the tabs from the TOC styles and the document should export
correctly.

An important question here is where did those tab stops come from in
the first place, the default writer TOC styles have no tab stops, and
neither do the default word styles. Perhaps either on import or export
of the original .sxw/.doc there is a problem that created the tabs.

cmc->Owen: Was this document created in word or writer originally ?. I
want to know where the tabs on the content styles came from. If they
are really meant to be there, then I think this turns into a feature
request for layout to honour tab stops in table of contents, but I
want to confirm that its not a bug of the filter that introduced the
tabs in the first place.
Comment 6 osavill 2002-05-23 16:04:11 UTC
It was created in OO, but NEVER saved in .sxw format but straight to
.doc format.
Comment 7 Unknown 2002-09-18 21:32:21 UTC
I'm having the same issue.  Multi-heading level TOC with right-tabbed
page numbers, and after "Save As... Word 97/2000/XP", open the new
.doc in Word 2000, the different TOC levels are tabbed differently
instead of being on the right margin.

If another file (that was (months ago) originally Word 95 format,
edited into .sxw, and now exporting back to .doc) would help narrow
this down, I'll attach a fragment of my file as well.
Comment 8 caolanm 2002-10-11 14:15:02 UTC
The problem here is the tabs inside a field (toc), the tabs are really
there and ideally should have been shown by writer itself. As such its
another case of issue 3232.

*** This issue has been marked as a duplicate of 3232 ***
Comment 9 caolanm 2002-12-13 09:40:04 UTC
Set target
Comment 10 michael.bemmer 2003-03-11 17:22:11 UTC
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 11 michael.bemmer 2003-03-11 17:26:44 UTC
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 12 michael.bemmer 2003-03-11 17:27:59 UTC
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 13 michael.bemmer 2003-03-11 17:38:26 UTC
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details.