[cl-pdf-devel] encoding question

Marc Battyani marc.battyani at fractalconcept.com
Wed May 9 07:21:43 UTC 2007


"Cyrus Harmon" <ch-lisp at bobobeach.com> wrote:

> So, now that I'm finally getting around to exploring cl-pdf a bit,  I'm 
> running across issues that others have run into before. Is there  any 
> documentation on the encoding besides just seeing what's in 
> encodings.lisp and in the pdf file? I don't know a lot about SBCLs 
> encodings either, much less other lisps, but it would be nice if  there 
> were some mappings between the encodings of the lisp and the  pdf 
> encodings. As it is it seems like there are mappings on top of a  single 
> encoding (different for each lisp of course) and that the  codes of that 
> encoding, not the characters per se, are then remapped  to postscript 
> encodings. I used trial and error to see what was what.  While it's nice 
> that #\COPYRIGHT_SIGN does the right thing, it would  be even nicer if 
> #\LEFT_DOUBLE_QUOTATION_MARK, e.g. and the rest of  the 
> postscript-available symbols worked with their equivalents in the 
> encoding of the host lisp.

 The character encoding is an tricky issue, you have to match the 
Lisp/OS/PDF encodings if you want this to work.
Or you can try to use Unicode but right now it's more difficult to use. (see 
the unicode read-me)

The default cl-pdf encoding is :win-ansi-encoding which probably a not a so 
good choice. Maybe latin-1 would be better.

Marc





More information about the cl-pdf-devel mailing list