![](https://secure.gravatar.com/avatar/46562c7d27388490d62e8d7a5bc960dd.jpg?s=120&d=mm&r=g)
On 10/1/2018 11:42 AM, Ulrike Fischer wrote:
Can you tell me when this change happend? Perhaps I can build an older fontloader as a fall back.
no, probably a while ago when some other clash in private area use was solved .. i'm not going to mess with the code now as 0xE000-0xEFFF is used in context for various things
in your case the glyphs have no real useful names so basically i wonder what their use it (are they meant for direct access?)
The question on tex.sx claimed that it has the name uniF58C. I never used the font and don't know how Therese accessed the glyphs before, but the libertine package has long lists of mappings like this:
\DeclareTextGlyphY{LinBiolinum_K}{uniE18C}{57740}
A funny definition ... is that access by name or number?
I don't see a use of accessing this glyphs by index - index positions can change if the font is updated. This can only be a last resort for glyphs without unicode position.
So can private unicodes as they are as undefined.
The only sensible access is by unicode number (which works).
Anyway, for generic (so not for context) I can keep these glyphs in the 0xE000-0xEFFF range for now (also the names so larger files ... actually a mess as that font has Uni and uni so who's to know). 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. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------