Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.postscript > #3748
| From | Carlos <carlos@cvkm.cz> |
|---|---|
| Newsgroups | comp.lang.postscript |
| Subject | Re: Printing UTF8 (Unicode) |
| Date | 2022-02-10 15:05 +0100 |
| Message-ID | <20220210150537.00002cd7@cvkm.cz> (permalink) |
| References | <4fe53d50-e66a-82b8-48fd-d0928e149698@davidnewall.com> <61ecbe1b$1@news.ausics.net> <20220123133511.00003a2f@cvkm.cz> <61f0c70f$1@news.ausics.net> |
On Wed, 26 Jan 2022 14:59:09 +1100 David Newall <davidn@davidnewall.com> wrote: > No font is guaranteed to use any of these names and many fonts that > I've examined use different names for unicode values (and different > values for some names.) > > > If you know you are dealing with modern fonts that include the uni/u > > aliases, you can get rid of the Adobe table lookup altogether... You > > don't need the canonical glyph names for those fonts. > > No font that I've examined includes uni/u names for every glyph, or > even for most glyphs. > > One can't rely on any pre-determined glyph name, nor any > pre-determined lookup table. What a mess. Well, that's disappointing... > After your comment about older fonts, I examined Courier, a Type 1 > font > (https://web.archive.org/web/20010617080950/http://www.ctan.org/tex-archive/fonts/psfonts/courier/). > The CharStrings array breaks my assumptions and my code completely > fails. What assumptions? C.
Back to comp.lang.postscript | Previous | Next — Previous in thread | Next in thread | Find similar
Printing UTF8 (Unicode) David Newall <davidn@davidnewall.com> - 2022-01-21 21:56 +1100
Re: Printing UTF8 (Unicode) Carlos <carlos@cvkm.cz> - 2022-01-21 14:23 +0100
Re: Printing UTF8 (Unicode) David Newall <davidn@davidnewall.com> - 2022-01-22 12:27 +1100
Re: Printing UTF8 (Unicode) David Newall <davidn@davidnewall.com> - 2022-01-23 13:31 +1100
Re: Printing UTF8 (Unicode) Carlos <carlos@cvkm.cz> - 2022-01-23 13:35 +0100
Re: Printing UTF8 (Unicode) David Newall <davidn@davidnewall.com> - 2022-01-26 14:59 +1100
Re: Printing UTF8 (Unicode) Carlos <carlos@cvkm.cz> - 2022-02-10 15:05 +0100
Re: Printing UTF8 (Unicode) David Newall <davidn@davidnewall.com> - 2022-02-16 13:55 +1100
Printing UTF8 (Unicode) - opinions please David Newall <davidn@davidnewall.com> - 2022-01-23 14:10 +1100
Re: Printing UTF8 (Unicode) - opinions please Carlos <carlos@cvkm.cz> - 2022-01-23 13:56 +0100
Re: Printing UTF8 (Unicode) - opinions please luser droog <luser.droog@gmail.com> - 2022-01-24 08:37 -0800
Re: Printing UTF8 (Unicode) - opinions please luser droog <luser.droog@gmail.com> - 2022-01-24 08:33 -0800
Re: Printing UTF8 (Unicode) - opinions please David Newall <davidn@davidnewall.com> - 2022-01-26 15:06 +1100
csiph-web