Closed Bug 287362 Opened 19 years ago Closed 19 years ago

UNICODE utf-8 symbol is displayed correctly but printed as space on HP LaserJet 4050N

Categories

(Firefox :: General, defect)

x86
Windows 98
defect
Not set
minor

Tracking

()

RESOLVED EXPIRED

People

(Reporter: Dieter.Ebner, Assigned: bugzilla)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

In http://de.wikipedia.org/wiki/Lebesgue-Integral after the bold line "Definition"
there comes a capital Omega, which is a 2 byte utf-8. It is printed as a space
on my HP LaserJet 4050N and also on an older HP Laser Jet 4M+.
When viewed and printed by Internet Explorer, the Omega is displayed and printed
correctly.  

Reproducible: Always




HPLaserJet is actually two printers (because there are two device drivers): PCL6
and PS (= postscript). The problem occurs with both printers, with a small
difference: in PS the UNICODE symbol is printed as a bullet instead of an Omega,
whereas in PCL6 it is printed as space instead of Omega.
I am fairly sure that any character will print only if you have you have a glyph
for it in the printer's repertoire or character map - that is, some font which
is available to you.

You might want to check with the documentation for your printer, that you do 
indeed have a glyph for the capital Omega.

In the case of the 4M+, you will probably be able to print by rasterising the
page yourself using Ghostscript. This may be slow.

Greek characters are tricky things, and it may be that IE is not using Unicode
but some proprietary encoding.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.