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 ___________________________________________________________________________________
