Issue 25591 - Word filter incorrectly wraps text in table cells
Summary: Word filter incorrectly wraps text in table cells
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1
Hardware: PC Linux, all
: P4 Trivial (vote)
Target Milestone: ---
Assignee: ulf.stroehler
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-17 00:14 UTC by zoowiez
Modified: 2004-02-18 16:30 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 zoowiez 2004-02-17 00:14:16 UTC
When opening a MS Word file in OOo Writer, text that fills an entire cell of a
table is wrapped and takes up two lines even though it only takes up one line
when opened in Word.
Comment 1 mci 2004-02-17 07:48:29 UTC
reassigned to mru
Comment 2 michael.ruess 2004-02-17 11:14:07 UTC
please attach the offending document to this issue, so that we can reproduce and
fix the problem here. You can also send the document directly
(mru@openoffice.org) for the case it contains confidential data. Feel free to
re-open the issue when you've done.
Thanks for supporting us!
Comment 3 zoowiez 2004-02-17 19:19:06 UTC
I attached the document that I was having trouble with.
Comment 4 michael.ruess 2004-02-18 12:55:44 UTC
MRU->US: does not look like a problem of the import. Only OO for Linux shows
this problem (SO on Linux also o.k.). Seems to be with the font which is
supplied with OO and "Arial" becomes mapped to...
Comment 5 ulf.stroehler 2004-02-18 16:29:48 UTC
us: yes, mru is right.
Because Arial is obviously not available on the Linux system OOo substitutes the
font with the closest match, which is Helvetica. But the tracking and the size
of Helvetica of course differs. That's why it comes to admittedly unpleasant
layout changes. The only solution is to have exactly the same fonts on the
different platforms.
Sorry, but invalid.
Comment 6 ulf.stroehler 2004-02-18 16:30:53 UTC
Closing as Resolved Invalid.