Issue 67551 - OO.o/word 2000 v-text interop problem
Summary: OO.o/word 2000 v-text interop problem
Status: CLOSED DUPLICATE of issue 25140
Alias: None
Product: Writer
Classification: Application
Component: save-export (show other issues)
Version: OOo 2.0.3
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-19 13:14 UTC by nmailhot
Modified: 2006-07-20 11:03 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description nmailhot 2006-07-19 13:14:06 UTC
Exporting an OO.o document containing vertical (90°:
format->char->character->rotation) text to .doc format does not work : Office
2000 does not recognize the text orientation, and you have to rework the whole
document using the Office 2000 text orientation tool.
Comment 1 michael.ruess 2006-07-20 07:27:41 UTC
Could you please attach an .odt file containing vertical text?
There are different possibilities of having rotated text.
If you speak of normal text which is rotated via "Format.Character" dialog, I
can tell you that this is not possible to export in a meaningful manner. MS Word
only offers such text on one sole page, not in between of non-rotated text...
Comment 2 nmailhot 2006-07-20 07:47:56 UTC
Yes it's via Format.Character
If there are another way to rotate text in OO.o (in table cells?)
Format.Character is the only text orientation control I could discover
Comment 3 michael.ruess 2006-07-20 08:31:20 UTC
It is possible in a table (see Table properties dialog, tab "Text flow") and for
page styles (if the Asian Language support is enabled in Tools.Options.Language).
Comment 4 nmailhot 2006-07-20 09:30:54 UTC
Ok, I'll requalify it as "OO.o" v-text in table control is difficult to find and
only allows vertical text in one orientation then (as my luck goes, it's not the
one I wanted)
Comment 5 michael.ruess 2006-07-20 11:02:23 UTC
Same as issue 25140.

*** This issue has been marked as a duplicate of 25140 ***
Comment 6 michael.ruess 2006-07-20 11:03:50 UTC
Closing duplicate.