|
Scott Klement <klemscot@klements.com> writes: > That's interesting. So you're suggesting that we don't need to map the > characters at all? Just define the CCSID in the PDF itself? Basically, yes. > Is there a downside to this approach? Downsides are that the PDF gets a little bigger including the encoding information, and that the encodings need to get generated in the first place. I suppose there may be a few tools out there that expect the text in a PDF to use an ASCII-compatible encoding, but Acrobat Reader, xpdf and Ghostscript all work fine, including search, and copy and paste. On the plus side, the same encodings could be used by scs2ps, and CCSIDs like 870, that use characters not in WinAnsiEncoding, will need their own encodings defined in the PDF anyway. -- Carey Evans http://home.clear.net.nz/pages/c.evans/ Cave canem.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.