Bug 75188 - Wrong font name in PS output
Summary: Wrong font name in PS output
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mozilla (Show other bugs)
(Show other bugs)
Version: 8.0
Hardware: i386 Linux
Target Milestone: ---
Assignee: Christopher Blizzard
QA Contact: Ben Levenson
: 62966 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2002-10-05 08:44 UTC by Tim Waugh
Modified: 2007-04-18 16:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-11-07 16:40:02 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
fix for bad font (952 bytes, patch)
2002-10-12 19:48 UTC, Gene Czarcinski
no flags Details | Diff

Description Tim Waugh 2002-10-05 08:44:13 UTC
Description of Problem: 
Mozilla uses 'Helvetica_Oblique' instead of 'Helvetica-Oblique' in PS output. 
Version-Release number of selected component (if applicable): 
How Reproducible: 
Steps to Reproduce: 
1. Browse to www.redhat.com 
2. Print (to file mozilla.ps) 
3. grep Helvetica.Oblique mozilla.ps 
Actual Results: 
    /Helvetica_Oblique findfont 
Expected Results: 
    /Helvetica-Oblique findfont 
Additional Information: 
This in turn causes the jetdirectprint print filter to receive errors from 
JetDirect printer, which it isn't prepared for. 
In 0.9.9 at least, the object file concerned was 
/usr/lib/mozilla/components/libgfxps.so and the source file was 
gfx/src/ps/nsAFMObject.cpp, line nsAFMObject.cpp.

Comment 1 Gene Czarcinski 2002-10-12 19:47:17 UTC
Yup. Got the SRPM, change the font to Helvetica-Oblique and rebuilt the rpms. 
Mozilla and galeon work fine now.

I hope an errata come on this soon.  The patch is trivial and the biggest
problem is rebuilding the rpms.

Comment 2 Gene Czarcinski 2002-10-12 19:48:34 UTC
Created attachment 80145 [details]
fix for bad font

Comment 3 Gene Czarcinski 2002-10-12 19:59:14 UTC
*** Bug 62966 has been marked as a duplicate of this bug. ***

Comment 4 Christopher Blizzard 2002-10-15 03:36:40 UTC
I'm pretty sure this has already been fixed upstream.

Comment 5 Gene Czarcinski 2002-10-15 04:52:35 UTC
Likely, but until that upstream product is incorporated into Red Hat's product
it leave a lot of users out in the cold.  The fix is simple and (given the huge
rebuild times) beyeond many users.  Pesonally, I fixed it.  While putting the
fix in rawhide may be a solution, it is not really a good one since may users
will not user rawhide updates.

Many printers in use are postscript printers.  Mozilla and galeon have majpor
problems without this fix.

Comment 6 Tim Waugh 2002-10-15 08:57:12 UTC
I don't think a mozilla errata would be necessary if the jetdirectprint filter 
worked properly.  But despite several requests for someone to try 'lpr 
-Phost%9100' where 'host' is hostname or IP address of the JetDirect printer, 
no-one has tried this out (or at least no-one has told me the results). 
If someone could *please* try that, and gets positive results, we can do a 
printconf errata for this.

Comment 7 Gene Czarcinski 2002-10-15 10:22:25 UTC
I used galean to print to a file.  I then did:

  lpr -P192.168.00.200%9100

This simply "hung".  I am using LPRng for my print system.

Comment 8 Gene Czarcinski 2002-10-15 10:41:49 UTC
OK, the above comment was a bit stupid!

It hung because I did not supply any file to be printed.  Here is what I got
when I did supply a file:

[genec@amber genec]$ lpr -P192.168.71.200%9100 test.ps
Status Information:
 sending job 'genec@amber+249' to
 connecting to 'localhost', attempt 1
 connected to 'localhost'
 requesting printer
 job 'genec@amber+249' transfer to failed
  sending str '^B192.168.71.200%9100' to
 error msg: 'bad printer name'

I still believe that mozilla is in error since changing the mozilla code will
fix the problem.

On the other hand, you may have something when you say that the printfilter
should handle it.

I created a print queue specifying a Unix Queue with the jetdirect address as
the server and a queue name of raw [I had previously used this method before the
jetdirect/9100 support was in linux.]

To my surprise, the pages printed fine to this queue.

Comment 9 Gene Czarcinski 2002-10-15 10:43:00 UTC
Oops, forgot to mention that the unix queue was defined as "postscript".  Since
postscript was the input, it should have passed it along.

Comment 10 Gene Czarcinski 2002-11-07 16:39:56 UTC
This really should be closed since the redhat-config-printer package in rawhide
fixes the problem.

BTW, why hasn't an errata for redhat-config-printer been issued.  This seems to
me it could be a major problem for many users.

Comment 11 Christopher Blizzard 2002-11-11 18:03:54 UTC
Marking rawhide.

Note You need to log in before you can comment on or make changes to this bug.