Closed Bug 247185 Opened 20 years ago Closed 18 years ago

[ps] Can't print non-ASCII characters

Categories

(Core :: Printing: Output, defect)

x86
Linux
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: kazhik, Unassigned)

Details

Attachments

(3 files)

Recent builds can't print non-ASCII characters.
Attached file Simple HTML file
Trunk builds or branch (which?) builds?
Trunk.
WTF with last Linux nightly using Xprint module (the sample output is from the PostScript module - everything horked... ;-() ...
Summary: Can't print non-ASCII characters → [ps] Can't print non-ASCII characters
Attachment #150977 - Attachment mime type: text/plain → application/postscript
Attachment #150978 - Attachment mime type: text/plain → application/postscript
Attachment #150976 - Attachment description: Simple HTML file in EUC-JP → Simple HTML file
Attachment #150976 - Attachment mime type: text/html → text/html; charset=EUC-JP
with ggv-2.6.0 (and gs 7.07), I get a page with empty squares for the non-ASCII squares using linux trunk and 1.6 builds. With xprint, it just shows a blank page (with both builds). with ggv-2.0.1 (and gs 7.05), I got an "invalid postscript" error with a file generated from a linux 1.7 branch build.
The non-working sample is missing the unicode-to-native logic that's supposed to be inserted for japanese text. In nsPostScriptObj.cpp, either the language group table gLangGroups isn't being initialized correctly, or else nsPostScriptObj::setlanggroup() is getting a NULL language group from its caller. Either way, setlanggroup() is setting the language group to default instead of "ja" when printing the japanese text.
I can't reproduce on recent Firefox trunk build. It may be marking WFM.
The problem seems to resolve. I'm marking worksforme.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: