Issue 2325 - MS Word Filter Incorrectly Chnages Font Size
Summary: MS Word Filter Incorrectly Chnages Font Size
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: 641
Hardware: PC Windows ME
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords:
: 2494 (view as issue list)
Depends on: 2400
Blocks:
  Show dependency tree
 
Reported: 2001-11-29 06:24 UTC by Unknown
Modified: 2003-09-08 16:56 UTC (History)
2 users (show)

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


Attachments
Sample Document (4.45 KB, application/octet-stream)
2001-11-29 06:25 UTC, Unknown
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2001-11-29 06:24:50 UTC
Refer to attachment. There are two problems.

See the line with the characters "3M"

1. OO cannot properly retain the tab size. A shorter tab size is causin the 3 
lines being mis-aligned.

2. In the original document, the characters "3M" are of size 14 pts. But after 
import to OO, the "3" has size 14 pts while the "M" changed to 18 pts.
Comment 1 Unknown 2001-11-29 06:25:56 UTC
Created attachment 738 [details]
Sample Document
Comment 2 stefan.baltzer 2001-11-29 15:21:21 UTC
REassigned to Michael.
Comment 3 michael.ruess 2001-11-30 11:09:19 UTC
MRU->CMC: Another FastSave issue? When I re-save it in my copy of WW
and import it to Writer, the tabs in the lines with 1), 2)... appear
correctly (on 3 cm), the FontSizes are o.k. and the font replacement
works fine. Also the filesize decreases from 32 to 19 k.
Comment 4 caolanm 2001-11-30 15:11:48 UTC
Well I can see why its happening, and its reasonably easy to figure
out what should happen instead. Implementing the fix inside the
existing property scanning structure is a bit more tricky and might
take a few iterations to get right :-)
Comment 5 caolanm 2001-11-30 17:54:29 UTC
The fastsave stuff fontsize is under control with
sw/source/filter/ww8/
ww8scan.cxx Rev 1.33
ww8scan.hxx Rev 1.20
The tab stops are actually in the right place, but the text is being
rendered narrower than in word, and narrower than in an imported
fastsave document. Which is passing strange. I wonder if there is a
subtle language issue relating to how its rendered that is getting
confused. Have to investigate that part of it further.
Comment 6 caolanm 2001-12-03 12:09:08 UTC
Fairly sure that the tabstop issue is a layout issue of some kind,
perhaps related to the fact that the font the document is in is
missing on our setups and is replaced with an alternative. In the
resaved new word documents word adds an alternative font of "arial
unicode" and when opened in writer that is added as the alternative,
and writer will use that alternative because the original is missing.
With that arial font the tabstops work ok. Either the standard
alternative font is the problem, or the use of the fallback font shows
up some issue with how tabstops work with text positioning.
Comment 7 caolanm 2002-01-11 17:07:56 UTC
*** Issue 2494 has been marked as a duplicate of this issue. ***
Comment 8 caolanm 2002-02-20 11:16:55 UTC
Working in SRC651a (linux pro)
Comment 9 michael.ruess 2002-04-19 10:52:25 UTC
Yeah, looks good. The fix will be public in a version like OpenOffice 65x.
Comment 10 michael.ruess 2002-06-03 13:01:07 UTC
*** Issue 5271 has been marked as a duplicate of this issue. ***
Comment 11 michael.ruess 2002-11-07 13:22:17 UTC
Fix introduced in OpenOffice 643.