Hans, hello. I have a question regarding a new version of my font setup in context: \definefontfeature[generalfeatures][default][ kern=yes, % enables kerning extrakerns=yes, % enables extra kerning trep=yes, % Enables single and double quotes to show up correctly in text, perhaps does more liga=yes, % Enables ligatures. itlc=yes, % Activates italic correction. mark=yes, % Used for positioning diacritical marks (accents, dots, etc.) relative to base characters. mkmk=yes, % positions diacritical marks relative to other marks locl=yes, ccmp=yes, % Composes multiple characters into a single glyph or breaks down ligatures. mode=node, protrusion=yes, expansion=yes, language=dflt, ] \definefontfamily [myfonts] [rm] [Times New Roman] [features=generalfeatures,dlig=yes,cpsp=yes,] % dlig enables times new roman ligatures, and cpsp is used by tnr, not aptos \definefontfamily [myfonts] [ss] [Aptos] [features=generalfeatures,] \definetypeface [myfonts] [mm] [math] [stixtwo] [features=generalfeatures,] \setupbodyfont[myfonts,12pt] 1. is extrakerns setup correctly? how can I tell if extrakerns will work? Since only kerns shows up in the OpenType features for TNR and Aptos. I wonder if it is like trep, which seems to be a context option for fonts. 2. What exactly does locl do if in tnr and aptos the option supports the latin script? (aptos also supports cyrl, and tnr also supports arab) 3. mode=node. I see that base is also an option in the settings sig page in context wiki, and ChatGPT told me node is the more 'complete', accurate, glyph based option that is typographically better, but takes more time to produce when used in a doc. Is this the case?