From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
David Carlisle <davidc@nag.co.uk>
Subject: Re: accessing glyphs in the private area
Date: Tue, 2 Oct 2018 11:13:35 +0200 [thread overview]
Message-ID: <3c3a4c23-88bc-8c16-8c0c-d1337b9aa288@xs4all.nl> (raw)
In-Reply-To: <c45e4ea7-8cea-cf5c-8ef0-df6f5e888eaf@nag.co.uk>
On 10/1/2018 11:11 PM, David Carlisle wrote:
> If you need to allocate a block for internal use wouldn't it be possible
> to use one of the high areas Supplementary Private Use Area-A or B
> (U+F0000 - U+FFFFF) (U+100000 - U+10FFFF) ?
>
> The BMP PUA block (U+E000 U+F8FF) just has so many documented uses in
> existing fonts.
that's what i now do when the font loader is used outside context (no
beta uploaded yet)
(fyi: we use U+E000 U+F8FF in context for other purposes ... and when we
need something special from the font we use glyph names)
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-02 9:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 21:11 David Carlisle
2018-10-02 9:13 ` Hans Hagen [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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=3c3a4c23-88bc-8c16-8c0c-d1337b9aa288@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=davidc@nag.co.uk \
--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).