[Foomatic] [patch] PPD.pm: handle non-ASCII in PPDs

Helge Blischke h.blischke at srz.de
Mon Nov 29 07:28:56 PST 2004


In article <mailman.151.1101721671.215.foomatic-devel at linuxprinting.org>, Tim
Waugh <twaugh at redhat.com> writes:
> 
> 
> --bFsKbPszpzYNtEU6
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> 
> On Sun, Nov 28, 2004 at 11:58:09PM +0100, Till Kamppeter wrote:
> 
> > Is there no hint in the PPDs in which encoding they are encoded?
> 
> Well "LanguageEncoding" says MacStandard -- which iconv -f/-t string
> does that correspond with?  Another value I've seen is ISOLatin1 --
> presumably that's iso-8859-1.  Do we have a mapping from
> LanguageEncoding strings to locale strings?
> 
> Tim.
> */
> 
> --bFsKbPszpzYNtEU6
> Content-Type: application/pgp-signature
> Content-Disposition: inline
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.6 (GNU/Linux)
> 
> iD8DBQFBqvUbHU/d4jnpWe0RArJLAJwNyPinl/JUQJWUXZH3ZuAhDSCvHgCfYZmQ
> Ebsub63xxTjx+kmAOYXRtj8=
> =CCsC
> -----END PGP SIGNATURE-----
> 
> --bFsKbPszpzYNtEU6--
> 

Adobe's PPD specification is somewhat sparse in talking about encoding. But
there
are some hints, e.g. in section 3.2 "Main Keywords":

> Main keywords can contain anx printable ASCII characters within 
> the range of decimal 33 to decimal 126 inclusive, except for the 
> characters colon and slash ...

I'd emphasize "printable" and "ASCII"; thus the question of selecting an
encoding should not arise.

A different issue is the "character set" used for the keyword values. There the
spec allows any code from (dec) 32 up to and including (dec) 255. The stuff
within the double quotes has to follow the PostScript syntax, for the other
stuff it is good practice to encode characters that are not ASCII printables as
hex, e.g. as in <0A> for a linefeed.

Helge



More information about the Printing-foomatic mailing list