Changes

== Script Versions == The OTF specification has two shaping implementations for the indic scripts: the 'older' v1 and the 'newer' v2. [https://docs.microsoft.com/en-us/typography/script-development/devanagari See here] for further details.  [https://docs.microsoft.com/en-us/typography/opentype/spec/scripttags Script tags from the OpenType specification] contains second versions for some Indic scripts. Why are those second versions available? From their own explanation: <blockquote>The OpenType script tags can also correlate with a particular OpenType Layout implementation, with the result that more than one script tag may be registered for a given Unicode script (e.g. 'deva' and 'dev2').</blockquote> Features ending in <code>-one</code> use the older OpenType implementation, while the ones ending in <code>-two</code> deploy the newer implementation. These are specified in ConTeXt by the following font features:

== Script Versions == [https://docs.microsoft.com/en-us/typography/opentype/spec/scripttags Script tags from One of the OpenType specification] contains second versions for what common problems one might be some (or all [I’m afraid I don’t know]) Indic scriptsencounter with indic fonts is that of incorrect rendering of conjuncts involving the rakaar. Why In case any problems are those second versions available? From their own explanation: encountered, one can try setting the <blockquotecode>The OpenType script tags can also correlate with a particular OpenType Layout implementation, with the result that more than one script tag may be registered for a given Unicode script (e.g. 'deva' and 'dev2').indic</blockquotecode> Features ending feature (in addition to relevant <code>-one</code> use the older OpenType implementation, while the ones ending in or <code>-two</code> deploy the newer implementation.features above) appropriately as follows:<texcode>\definefontfeature […] […] [indic={matra=auto,conjuncts=quit}]</texcode>