Closed
Bug 85399
Opened 23 years ago
Closed 23 years ago
Xprint does not print ISO 8859-2 (Latin 2) page correctly...
Categories
(Core Graveyard :: Printing: Xprint, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9.3
People
(Reporter: roland.mainz, Assigned: roland.mainz)
References
()
Details
(Keywords: intl)
Attachments
(3 files)
[more or less a spin-off of bug 63737] Xprint does not print ISO 8859-2 pages like http://moo.pl/ogonki/main.html correctly... 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 ?
Assignee | ||
Comment 1•23 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
Assignee | ||
Comment 2•23 years ago
|
||
Comment 3•23 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
Assignee | ||
Comment 5•23 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 tomorrow...
Assignee | ||
Comment 6•23 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 (mozilla/gfx/src/xlib/)...). 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... :-)))
Assignee | ||
Comment 7•23 years ago
|
||
Bug 80224 has a solution for this - but it heavily depends on bug 66082... ;-(
Assignee | ||
Comment 8•23 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...
Status: NEW → ASSIGNED
Assignee | ||
Comment 9•23 years ago
|
||
Assignee | ||
Comment 10•23 years ago
|
||
Assignee | ||
Comment 11•23 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 ?
Assignee | ||
Comment 13•23 years ago
|
||
Fixed by patch in bug 89851. Xprint PostScript output now matches the Xlib-toolkit display on framebuffer... :-)
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Updated•16 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•