From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: decomposed and precomposde glyphs
Date: Fri, 24 Feb 2017 10:35:34 +0100 [thread overview]
Message-ID: <irng3jn1ss8k$.dlg@nililand.de> (raw)
In-Reply-To: <20170223162005.GI523905@phare.normalesup.org>
Am Thu, 23 Feb 2017 17:20:05 +0100 schrieb Arthur Reutenauer:
>> I looked at the code and it actually uses an idea that I had already
>> tried. The problem I couldn't solve was do decompose a glyph.
>> Looking at an context example it seems that context can do it. The B
>> with dot below (U+1E04) ends as BU+0323 in the pdf. But how does
>> context does it?
>
> It uses the Unicode composition information (part of UnicodeData.txt),
> they’re made into a Lua table in ConTeXt (named char-def.lua, if it
> hasn’t changed).
I know of char-def.lua but the question was more *how* the
information is used and *when*. In an input call back? Through a
font feature?
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___________________________________________________________________________________
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:[~2017-02-24 9:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 10:58 Ulrike Fischer
2017-02-23 12:19 ` Hans Hagen
2017-02-23 12:35 ` Ulrike Fischer
2017-02-23 13:08 ` Hans Hagen
2017-02-23 14:05 ` Ulrike Fischer
2017-02-23 15:10 ` Hans Hagen
2017-02-23 15:12 ` Ulrike Fischer
2017-02-23 15:55 ` Hans Hagen
2017-02-23 17:26 ` Ulrike Fischer
2017-02-23 17:41 ` Hans Hagen
2017-02-23 17:47 ` Ulrike Fischer
2017-02-23 17:45 ` luigi scarso
2017-02-23 17:50 ` Ulrike Fischer
2017-02-23 18:28 ` luigi scarso
2017-02-23 17:47 ` Hans Hagen
2017-02-23 16:20 ` Arthur Reutenauer
2017-02-24 9:35 ` Ulrike Fischer [this message]
2017-02-24 11:52 ` 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='irng3jn1ss8k$.dlg@nililand.de' \
--to=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).