Xprint does not print ISO 8859-2 (Latin 2) page correctly...

VERIFIED FIXED in mozilla0.9.3


Core Graveyard
Printing: Xprint
17 years ago
10 years ago


(Reporter: Roland Mainz, Assigned: Roland Mainz)



Dependency tree / graph

Firefox Tracking Flags

(Not tracked)




(3 attachments)



17 years ago
[more or less a spin-off of bug 63737]
Xprint does not print ISO 8859-2 pages like http://moo.pl/ogonki/main.html
I'll attach a output from Xprt to demonstrate the problem...

Question to Jay Hobson:
Solaris 7 has some encoding tables like
/usr/openwin/lib/X11/fonts/encodings/iso8859-2.enc - but does Xprt
(S7+108376-24) use it ?

Comment 1

17 years ago
Oups... I forgot to CC: Jay... ;-(
Swapping owner<-->QA, setting target milestone to 0.9.3...
This depends on bug 57820 to get the images in the example page "right"...
Depends on: 57820
Target Milestone: --- → mozilla0.9.3

Comment 2

17 years ago
Created attachment 38057 [details]
http://moo.pl/ogonki/main.html printed with Xprint module (character coding set to ISO-8859-2)...

Comment 3

17 years ago
Assign to Roland.

Roland, you have to mention this problem happens when Xprt uses
printer's PostScrit font.

It seems that Xprt still uses latin1encofing font .e.g Times-Roman
even for iso-5589-2 characters.

Does anyone know the correct PostScript font name of iso-8859-2?
Or the name should be the same with Times-Roman and should
contain iso-8859-2 characters?

Assignee: katakai → Roland.Mainz
QA Contact: Roland.Mainz → katakai

Comment 4

17 years ago
Mhhh, is bug 82982 somehow related to this one ?

Comment 5

17 years ago
A posible testcase would be to remove the printer internal fonts from Xprt
config and see what happens... (raw guessing)... going to test that theory

Comment 6

17 years ago
Xlib-toolkit shows exactly the same symptoms. Looks like a bug in Xprint module
code (nsFontmetricsXP.cpp)...
(Xlib-toolkit is always a nice way to test this as Xprint module is only a good
mix between native PostScript module (mozilla/gfx/src/ps/) and Xlib-toolkit

Filed bug 85811 for the matching bug in Xlib-toolkit. Once the bug has been
fixed there we can pull-over the fix from there... :-)))
Depends on: 85811
Keywords: intl

Comment 7

17 years ago
Bug 80224 has a solution for this - but it heavily depends on bug 66082... ;-(
Depends on: 66082, 80224

Comment 8

17 years ago
Bug 85811 ("Xlib-toolkit does not show ISO 8859-2 (Latin 2) page correctly...")
has been fixed.

In theory Xprint should work now - but I see problems with ISO-8859-2 glyphs not
rendered correctly...
I'll add a PostScript file and a GIF image from to demonstrate the problem...


Accepting bug...

Comment 9

17 years ago
Created attachment 40441 [details]
http://moo.pl/ogonki/main.html printed with 2001-06-27-08-trunk using Xprint module

Comment 10

17 years ago
Created attachment 40443 [details]
http://moo.pl/ogonki/main.html printed with 2001-06-27-08-trunk using Xprint module, 1st page as GIF image from sdtimage (400% zoom)

Comment 11

17 years ago
It looks that the ISO-8859-2 glyphs are rendered over other glyphs - or other
chars are rendred over the ISO-8859-2 glyphs. BAD.
Or is this a bug in sdtimage ?

Can anyone (katakai/jay) check this with a real printer or GSview, please ?

Comment 12

17 years ago
Fix in bug 89851...
Depends on: 89851

Comment 13

17 years ago
Fixed by patch in bug 89851. Xprint PostScript output now matches the
Xlib-toolkit display on framebuffer... :-)
Last Resolved: 17 years ago
Resolution: --- → FIXED

Comment 14

17 years ago
Verfied on 2002011614.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.