From: David Carlisle <davidc@nag.co.uk>
To: ntg-context@ntg.nl
Subject: accessing glyphs in the private area
Date: Mon, 1 Oct 2018 22:11:59 +0100 [thread overview]
Message-ID: <c45e4ea7-8cea-cf5c-8ef0-df6f5e888eaf@nag.co.uk> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1550 bytes --]
Ulrike and Hans wrote
> > 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.
> in context i strongly advice against using numbers instead of names
It's not just explicit numbers via \char, it's character data in
documents using specific fonts with documented PUA characters
Many fonts use this for assorted reasons
https://en.wikipedia.org/wiki/Private_Use_Areas#Vendor_use
notably SIL fonts using it for minority languages not in Unicode and
Microsoft for all kinds of CJK stuff.
Given how many reports are appearing in the few days that this has been
exposed to a larger number of uses via LaTeX, use of PUA characters
really isn't a rare occurrence at all.
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.
David
Disclaimer
The Numerical Algorithms Group Ltd is a company registered in England and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.
This e-mail has been scanned for all viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business.
[-- Attachment #1.2: Type: text/html, Size: 2276 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 bytes --]
___________________________________________________________________________________
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 reply other threads:[~2018-10-01 21:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 21:11 David Carlisle [this message]
2018-10-02 9:13 ` Hans Hagen
-- 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=c45e4ea7-8cea-cf5c-8ef0-df6f5e888eaf@nag.co.uk \
--to=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).