Am Mon, 1 Oct 2018 19:29:40 +0200 schrieb Hans Hagen:
>> \DeclareTextGlyphY{LinBiolinum_K}{uniE18C}{57740}
>A funny definition ... is that access by name or number?
By number, it uses \char at the end to get the glyph.
> Anyway, for generic (so not for context) I can keep these glyphs in the
> 0xE000-0xEFFF range for now
That would be great. Thanks.
What about the rest and the other PUA's?
U+F000–U+F8FF, U+F0000–U+FFFFD, U+100000–U+10FFFD
And when will the change be available? I will have to update
luaotfload.
> (also the names so larger files ... actually
> a mess as that font has Uni and uni so who's to know).
It is not only that font. Actually the libertine package broke,
fontawesome broke, and Coelacanth was only used by Thérèse in the
example as it is free, her real problem was with using Goudy
fleurons.
The private use area is there for every font to use. And quite often
they document this code points and tools like fontforge show them.
I don't think that it is a good idea if an application comes along
and pushes the glyphs from the seats because it wants the space for
itself.
> I have no clue if it clashes with some features at some point so
> that you can use numbers but probably those features are context
> specific anyway.
For what do you reserve the space in the PUA?
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
