From: Hans Hagen <j.hagen@xs4all.nl>
To: news3@nililand.de, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: accessing glyphs in the private area
Date: Mon, 1 Oct 2018 19:29:40 +0200 [thread overview]
Message-ID: <ae072a59-b43d-908b-f871-a3dfd259bb7c@xs4all.nl> (raw)
In-Reply-To: <1ih4s1lzjxhph$.dlg@nililand.de>
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
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2018-10-01 17:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-30 20:08 Ulrike Fischer
2018-10-01 8:20 ` Hans Hagen
2018-10-01 9:42 ` Ulrike Fischer
2018-10-01 9:53 ` luigi scarso
2018-10-01 17:29 ` Hans Hagen [this message]
2018-10-01 17:55 ` Ulrike Fischer
2018-10-01 20:42 ` Hans Hagen
2018-10-02 4:55 ` luigi scarso
2018-10-02 7:29 ` Ulrike Fischer
2018-10-02 9:29 ` Hans Hagen
2018-10-02 11:39 ` Ulrike Fischer
2018-10-02 12:42 ` Hans Hagen
2018-10-01 21:11 David Carlisle
2018-10-02 9:13 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae072a59-b43d-908b-f871-a3dfd259bb7c@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=news3@nililand.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).