ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: Ulrike Fischer <news3@nililand.de>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: accessing glyphs in the private area
Date: Tue, 2 Oct 2018 06:55:02 +0200	[thread overview]
Message-ID: <CAG5iGsDSMFb1wEHDTcK-2UH2kuxxfqhxMVa0nh4W=3Zz-z=i-w@mail.gmail.com> (raw)
In-Reply-To: <vc3xsf8d8lz8$.dlg@nililand.de>


[-- Attachment #1.1: Type: text/plain, Size: 643 bytes --]

On Mon, Oct 1, 2018 at 7:56 PM Ulrike Fischer <news3@nililand.de> wrote:

>
> For what do you reserve the space in the PUA?
>

 http://www.pragma-ade.nl/general/manuals/fonts-mkiv.pdf
page 32 of the document :

As we already mentioned in a previous chapter, in ConTeXt we use Unicode
internally.
This also means that fonts are organized this way. By default the glyph
representation
of a Unicode character sits in the same slot in the glyph table. All
additional glyphs, like
ligatures or alternates are pushed in the private unicode space. This is
why in the lists
shown in the figures the ligatures have a private Unicode number.

-- 
luigi

[-- Attachment #1.2: Type: text/html, Size: 1746 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
___________________________________________________________________________________

  parent reply	other threads:[~2018-10-02  4:55 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
2018-10-01 17:55       ` Ulrike Fischer
2018-10-01 20:42         ` Hans Hagen
2018-10-02  4:55         ` luigi scarso [this message]
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='CAG5iGsDSMFb1wEHDTcK-2UH2kuxxfqhxMVa0nh4W=3Zz-z=i-w@mail.gmail.com' \
    --to=luigi.scarso@gmail.com \
    --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).