Re: Printing and non-latin1 pages

[PILCH Hartmut <phm@xxxxxx>]

> Proposals?  It would be neat to have a comment in the postscript file
> stating what was the original encoding of the page.  That way I could
> automatically convert the file without having the user specify the
> encoding.  That is, if we get the original strings, if we get UTF8 or
> UTF16 in the poscript file there would be no need for that.

Sounds great.

But I must be missing something here, because I just installed the Wadalab
Japanese Postscript fonts in the /usr/lib/ghostscript/ path as usually
done in Japanese distributions, and everything works wihthout any
postprocessing filter.

We have the t1utils and ttf2pfb for perfectly converting TTF to PFB (type
1 postscript, compressed), and it should be not too difficult to create
some Unicode PFB files, and even CID files, which work with Ghostscript
>=5.5.  Ken Lunde has made CID versions of the Wadalab fonts available.

Already now, EUC-JP, SJIS and Latin-1 all print correctly under my
Netscape 4.6 without postprocessing, and with everything unified to UCS,
everything should be even more straightforward.

-phm

-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/