Issue 20558 - some doc files by 1.0.3 view correct and view distorted by 1.1 RC5
Summary: some doc files by 1.0.3 view correct and view distorted by 1.1 RC5
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC5
Hardware: Other Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: ulf.stroehler
QA Contact: issues@sw
URL: http://optimum2.mii.lt/~jonas2
Keywords:
: 19752 (view as issue list)
Depends on:
Blocks:
 
Reported: 2003-10-01 17:30 UTC by mockus
Modified: 2004-01-09 11:15 UTC (History)
2 users (show)

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

Attachments
the image of a good doc file imported by OO-1.1.RC5 (23.53 KB, image/gif)
2003-10-01 17:36 UTC, mockus 		no flags Details
this is the successful image of doc file by OO-1.0.3 which ws bad by 1.1RC5 (22.53 KB, image/gif)
2003-10-01 17:42 UTC, mockus 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description mockus 2003-10-01 17:30:50 UTC 
the same doc file loo querry that
ks correct by 1.0.3  and very bad by 1.1 RC5,
the corresponding gif files I attach to may e-mail to
webmaster@openoffice.org because I dont know how to attach
gif files to issuezilla
Regards
Jonas Mockus
Comment 1 mockus 2003-10-01 17:36:30 UTC 
Created attachment 9877 [details]
the image of a good doc file imported by OO-1.1.RC5
Comment 2 mockus 2003-10-01 17:42:07 UTC 
Created attachment 9878 [details]
this is the successful image of doc file by OO-1.0.3 which ws bad by 1.1RC5
Comment 3 mci 2003-10-02 07:21:31 UTC 
reassigned to mru
Comment 4 utomo99 2003-10-03 04:11:27 UTC 
Please Attach the documents which make this problem, so we can test
it/faster to confirm.  
(Without the documents, we cannot confirm the problem easily/need more
time)
Don't forget to cut other part of the documents, so the file size is
small, but we still able to see the problem.
Comment 5 michael.ruess 2003-10-06 09:26:03 UTC 
MRU->US: It looks like the "Timews New Roman" replacement on Linux. Do
you know anything further about this (known, fixed...)?
Comment 6 michael.ruess 2003-10-07 11:11:08 UTC 
*** Issue 19752 has been marked as a duplicate of this issue. ***
Comment 7 ulf.stroehler 2003-10-07 14:38:29 UTC 
@submitter: pls. provide a bugdoc as already mentioned by utomo99.
Otherwise I can not do anything for you.
Comment 8 utomo99 2003-10-30 08:34:28 UTC 
Utomo > mru & us:
as your comment in issue 19752 can we set this to new ? 


------- Additional Comments From mru@openoffice.org 2003-10-07 03:11
PDT -------

Yes, this is known. See issue 20558 for further information and
progress on it.

*** This issue has been marked as a duplicate of 20558 ***
Comment 9 tamblyne 2003-10-30 21:37:44 UTC 
Unable to confirm RH9/1.1.0 -- using sample docs attached to dup Issue
19752.  Opening these documents, text was displayed as expected.
Comment 10 alex.thurgood 2003-11-01 08:59:29 UTC 
Copied from issue 19752 :

I opened the oo103win_good_oo11rc4lin_bad file on my Linux MDK 9.1
with the OOo680m11 build.

The file opens and displays fine. However, in the font dropdown menu,
it states that two fonts are present : Thorndale, and Times New Roman,
separated by a semi-colon. How can this be ? I thought that Thorndale
was only present in StarOffice and not OOo. I seem to remember that
1.0.3 contained a reference to Thorndale even though it wasn't present
in the fonts installed with OOo.

Does the fact that there are two fonts indicated mean that the first
is replaced by the second ?

Alex.


Tried the XP file under the 680m11 build on Linux MDK 9.1. The file
opens fine. The font is displayed as Times New Roman.


Alex.
Comment 11 mockus 2003-11-24 16:49:19 UTC 
the problem just disaapeared when redhat 9 downloaded a new set of 
fonts,
that include iso-8859-13 versions,
now oo-1.1 works pefectly
Comment 12 ulf.stroehler 2004-01-09 11:15:35 UTC 
Submitter seems to consider this task as resolved.
Closing as I can not reproduce the issue on RH9 either.