Issue 5037 - Slant and bold truetype faces aren't printed correctly after pspfontcache is created on Linux.
Summary: Slant and bold truetype faces aren't printed correctly after pspfontcache is ...
Status: CLOSED DUPLICATE of issue 4366
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: PC Linux, all
: P4 Trivial (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2002-05-19 09:45 UTC by ccasteyde
Modified: 2003-09-08 16:56 UTC (History)
2 users (show)

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


Attachments
minimalist document + correct and incorrect PostScript files + pspfontcache (20.52 KB, text/plain)
2002-05-19 09:47 UTC, ccasteyde
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description ccasteyde 2002-05-19 09:45:49 UTC
The first time OpenOffice is started, every Truetype fonts
are really ***awful***. Then the second time (that is, AFTER
~/OO/user/psprint/pspfontcache is built), fonts looks very nice,
but are not preinted correctly on SGENPRT printer (everything
is either roman / italic bold, no more roman bold and italic
medium - may vary yet). rm pspfontcache solves the printing
problem... untill  OO recreates it.

In fact, when pspfontcache exists, printing (in a file) shows
that TT fonts are partly embedded in the PostScript file
(whereas everything is OK is it's printed after the first
start of OO).

Truetype fonts are therefore either printable and not presentable,
or presentable but not printable. Critical (by the way, I do not
understand why generic printer configuration is necessary
to display correctly the fonts).

This bug only appears on Linux (XFree 4.2.0 + X font server,
Windows 2000 TT fonts installed with different encodings but
Unicode). Setup was done with /net, then a user account was
created. No pspfontcache in install path, only the one
created by OO on the user account. Reproduced both with
X11 TT fonts used natively and after installing the fonts
with spadmin (which, by the way, creates the pspfontcache too),
either globally or in the user account.

Have a tarball with the minimalist document, generated PostScript
files either with the bug or not, and the pspfontcache that seems
to cause problem. Ask me for it at casteyde.christian at free dot fr
for it.

Didn't find how to attach file in IssuZilla (quite complicated).

CC
Comment 1 ccasteyde 2002-05-19 09:47:29 UTC
Created attachment 1696 [details]
minimalist document + correct and incorrect PostScript files + pspfontcache
Comment 2 ccasteyde 2002-05-20 08:50:35 UTC
OK, seems to be the same issue than 4366.


*** This issue has been marked as a duplicate of 4366 ***
Comment 3 ccasteyde 2002-05-20 10:40:29 UTC
Sorry, 4366 only deals with display and do not address
the printing problem.

I reopen this issue because the pspfontcache problem does
seem to prevent printing truetype fonts, but I do not
know if it is really a consequence of 4366.
By the way, deleteing pspfontcache does solve the printing problem,
but messed up truetype fonts on display as shown on the last
screenshot of 4366.

Comment 4 prgmgr 2002-07-12 21:18:25 UTC
PM->CMC or SBA

Should we mark this as a duplicate of 4366.

It sounds very close to the same issue experienced in 4366.
Comment 5 prgmgr 2002-07-14 04:33:02 UTC
Mr./Ms Casteyde, I'm going to mark this as a duplicate of 4366.

If the problem still appears in the next release, we'll take a look at
your issue again.

Thanks for all your efforts.

*** This issue has been marked as a duplicate of 4366 ***
Comment 6 michael.bemmer 2003-03-11 17:23:39 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 7 michael.bemmer 2003-03-11 17:29: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. First step in IssueZilla is
unfortunately to set them to verified.
Comment 8 michael.bemmer 2003-03-11 17:29:41 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 9 michael.bemmer 2003-03-11 17:40:54 UTC
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details.