Subject: Re: Type 1 postscript font support questions...
From: sam th (sam@bur-jud-118-039.rh.uchicago.edu)
Date: Fri Jun 02 2000 - 03:45:04 CDT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 2 Jun 2000, Mike Meyer wrote:
> I'm not sure if this is going to the correct list, but I am going to
> talk about the code, so forgive me if I blew it.
This is certainly the right list.
> After working through xap_UnixPSParseAFM.c, I decided that the problem
> was the DOS origins of the AFM files. The CR in the files was
> confusing the tokenizer. Changing the parsing code to use the isspace
> library routine solved that problem - it no longer died trying to
> parse the AFM file. That's why this is going to the developer list -
> is there some portability reason that isspace wasn't used? If not, I
> can create a patch file pretty trivially. If so - well, another patch
> is needed.
Well, my isspace() man page says that it's in ANSI C, so there shouldn't
be much of a problems. And I suspect that all the systems that we build
the Unix build on will have it available. So, unless other people object,
I think we would be happy to take your patch. Just remember to add to the
changelog at the top of the file (since it's adobe code).
sam th
sam@uchicago.edu
http://sam.rh.uchicago.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE5N3QRt+kM0Mq9M/wRAlNHAKDVdnVt6DmbUcRQxCgvPsGxK3nqPgCfRQTR
MLmRTaBMNTEXg22CPnl3ol8=
=LTTE
-----END PGP SIGNATURE-----
This archive was generated by hypermail 2b25 : Fri Jun 02 2000 - 03:33:01 CDT