The history of luaTEX 2006–2009 / v 0.50 - Pragma ADE
The history of luaTEX 2006–2009 / v 0.50 - Pragma ADE
The history of luaTEX 2006–2009 / v 0.50 - Pragma ADE
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
number <strong>of</strong> changes in the code needed to do this is not that large but it only makes sense<br />
when we have many fonts in a list and don't change fonts to frequently.<br />
This whole treatment is rather extensively optimized and so the process is reasonable fast<br />
(you really don't want to know how much time was spent on guring out fast methods,<br />
testing and reimplementing this). While I was implementing the Lua code, Taco made<br />
sure that access to the information in nodes was as fast as possible and in our usual chat<br />
sessions we compared the output with the one produced by the FontForge preview.<br />
It was for this reason that more and more debugging code was added but even that made<br />
tracking <strong>of</strong> what really happened cumbersome. <strong>The</strong>refore a more visual method was<br />
written, which will be shown laster on.<br />
You can enable tracing using the designated commands:<br />
\enabletracker[otf.ligatures,otf.singles]<br />
and disable them for instance with:<br />
\disabletracker[otf.*]<br />
Or you can pass directives to the command line:<br />
context --track=otf.ligatures myfile.tex<br />
With regards to OpenType handling we have the following tracker keys available:<br />
otf.actions<br />
otf.alternatives<br />
otf.analyzing<br />
otf.applied<br />
otf.bugs<br />
otf.contexts<br />
otf.cursive<br />
otf.details<br />
otf.dynamics<br />
otf.features<br />
otf.kerns<br />
otf.ligatures<br />
otf.loading<br />
otf.lookups<br />
otf.marks<br />
otf.multiples<br />
otf.positions<br />
otf.preparing<br />
show all replacements and positioning<br />
show what glyph is replaced by what alternative<br />
color glyphs according to script specic analysis<br />
applied features per font instance<br />
show diagnostic information<br />
show what contextual lookups take place<br />
show cursive anchoring when applied<br />
show more details about lookup handling<br />
show dynamic feature denitions<br />
show what features are a applied<br />
show kerning between glyphs when applied<br />
show what glyphs are replaced by one other<br />
show more information when loading (caching) a font<br />
keep track <strong>of</strong> what lookups are consulted<br />
show mark anchoring when applied<br />
show what glyph is replaced by multiple others<br />
show what glyphs are positioned (combines other trackers)<br />
show what information is collected for later usage in lookups<br />
Tracking 251
Change language