Thread View: comp.lang.postscript
1 messages
1 total messages
Started by David W. Smith
Wed, 09 Sep 1992 16:52
Q: problems encoding for ISOLatin1
Author: David W. Smith
Date: Wed, 09 Sep 1992 16:52
Date: Wed, 09 Sep 1992 16:52
29 lines
1738 bytes
1738 bytes
Apologies if this is a FAQ. My need is recent, and there's no trace of a FAQ in our scant archives. We need to reencode Courier to support ISOLatin1. This would seem to be a straightforward problem, using the reencoding example on pp 115-6 of the Green book, and the character code/name table on pp 254-5 of the Red book. Unfortunately, we have not been able to make this work. After reencoding the font, we attempt to print out a table of the upper half of the font, via (\200 ... \207) show ... (\270 .. \277) show Which gives us an Error: invalidfont. The character code that PostScript chokes on seems to be dependent on fontsize. For 12 point re-encoded Courier, the culpret seems to be \300 (Agrave). For 16 point, we make it as far as \340 (agrave) before getting deep sixed. Are we running into a known problem? We're using a LaserWrite II NTX, and have heard that there may be a known problem there. If anyone has run up against this and solved it, we would love to learn the particulars. Any help/suggestions/pointers will be greatly appreciated. If this isn't a FAQ, I'll summarize and repost. -- Dave Smith, Cadre Technologies Inc. - Database Tools Division 4500 Bohannon Drive, Suite 150, Menlo Park, CA 94025
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads