Changes

{{todo|this page needs to be reviewedis under construction}}

 Fonts are complicated. Moreover, those for indic languages have to provide for rules for the formation of several complicated conjuncts. Each of these conjuncts can consist of several forms occurring simultaneously, which have to be positioned correctly relative to the base glyph. OTF documentation notwithstanding, font designers have their own interpretations of the specifications leading to a variety of implementations of the font features. Most of the available fonts are tested against Harfbuzz and/or ICU (sometimes only the former). Since ConTeXt uses its own OTF loading system, many indic fonts do not just work right away. In early 2022, Hans made some nice improvements to the indic font system in ConTeXt. This was accompanied by some testing with various available fonts for some indic languages. As a result, there is an improved support for Indic fonts in ConTeXt. Various typescripts were then bundled into the ConTeXt distribution for easy use in documents.  The following table lists fonts that have been tested for use with ConTeXt. The list is by no means extensive: most of the fonts are relatively new and some (ubiquitous) old fonts are absent. If you find a font missing in this list and that works well in ConTeXt, please add it to the list. To use indic fonts place <texcode>\usetypescriptfile[indic]</texcode>in the document head and use {{cmd|definetypeface}} and/or {{cmd|setupbodyfont}} with the following typescripts: {|cellpadding="5"|class-style="wikitablebackground-color:#e1effa;"! style="width:17.5%;" | Sans ! style="width:17.5%;" | Serif! style="width:35%;" | Notes! Typescript(s)|-style="background-color:#fef6e7;"! colspan="34" | Devanagari

| 4 different designs; many weightsand styles; good conjunct coverage; IAST support| <code>adishila</code></br><code>adishila-semibold</code></br><code>adishila-heavy</code></br><code>adishila-dev</code></br><code>adishila-dev-guru</code></br><code>adishila-san</code></br><code>adishila-san-letterpress</code></br>

| several five weights| <code>baloo</code></br><code>baloo-semibold</code></br><code>baloo-extrabold</code></br>

| <code>jaini</code></br><code>jaini-purva</code></br>|-style="background-color:#fef6e7;"! colspan="34" | Malayalam

| an elegant font good conjunct coverage; four two weights; italic style; one of the most complete fonts available| <code>rit-rachana</code>

== Devanagari =Supported Scripts and Font Features =

The following One can of course use fonts work well in ConTeXt* Adishila* Shobhika* Baloo Devanagari 2* Jaini & Jaini Purva* Amitanot listed above. This section provides some details to this end.

== Malayalam Font feaures ==

The following fonts work well in ConTeXtOTF specification has two shaping implementations for the indic scripts:* RIT Rachana* Panmana* Ezhuthu* Karumbi* Chilanka* Anjali Old Lipi* Dyuthi* TN Joy* Gayathri* Manjari* Baloo Chettan 2* RIT Sundarthe 'older' v1 and the 'newer' v2. [https://docs.microsoft.com/en-us/typography/script-development/devanagari See here] for further details.

<blockquote>The following font works well in ConTeXt: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').* Murty Kannada</blockquote>

The following fonts work well These are specified in ConTeXtby the following font features:* Murty Telugu* Baloo Tammudu 2

{| cellpadding="5"! style= Bengali "text-align:left;" | Script! style="text-align:left;" | OTF v1 script tag! style="text-align:left;" | OTF v2 script tag|-| Devanagari| <code>devanagari-one</code>| <code>devanagari-two</code>|-| Malayalam| <code>malayalam-one</code>| <code>malayalam-two</code>|-| Telugu| <code>telugu-one</code>| <code>telugu-two</code>|-| Kannada| <code>kannada-one</code>| <code>kannada-two</code>|-| Bengali| <code>bengali-one</code>| <code>bengali-two</code>|-|}

One of the common problems one might encounter with indic fonts is that of incorrect rendering of conjuncts involving the rakaar. In case any problems are encountered, one can try setting the <code>indic</code> feature (in addition to relevant <code>-one</code> or <code>-two</code> features above) appropriately as follows:<texcode>\definefontfeature […] […] [indic= Basic Sample {matra=auto,conjuncts=quit}]</texcode>

== Sanitizer ==Sometimes, some fonts might still have issues with certain conjuncts. To overcome this a <code>sanitizer</code> option may be used in defining font features. A very basic sample with Indic scripts goodies file accompanies this option. An example is the followingillustrated below:

%\definefontfamily return { name = "myfont", version = "1.00", comment = "Goodies that complement myfont.", sanitizers = { dev2rkrf = { mapping = { ["के्र"] = "क्रे", ["कै्र"] = "क्रै", ["खे्र"] = "ख्रे", ["खै्र"] = "ख्रै", ["गे्र"] = "ग्रे", ["गै्र"] = "ग्रै", ["घे्र"] = "घ्रे", ["घै्र"] = "घ्रै", ["चे्र"] = "च्रे", ["चै्र"] = "च्रै", ["छे्र"] = "छ्रे", ["छै्र"] = "छ्रै", ["जे्र"] = "ज्रे", ["जै्र"] = "ज्रै", ["झे्र"] = "झ्रे", ["झै्र"] = "झ्रै", ["ञे्र"] = "ञ्रे", ["ञै्र"] = "ञ्रै", ["णे्र"] = "ण्रे", ["णै्र"] = "ण्रै", ["ते्र"] = "त्रे", ["तै्र"] = "त्रै", ["थे्र"] = "थ्रे", ["थै्र"] = "थ्रै", ["दे्र"] = "द्रे", ["दै्र"] = "द्रै", ["धे्र"] = "ध्रे", ["धै्र"] = "ध्रै", ["ने्र"] = "न्रे", [kannada"नै्र"] = "न्रै", [rm"पे्र"] = "प्रे", [Kedage"पै्र"] = "प्रै", [features"फे्र"] =kannada-one"फ्रे", ["फै्र"] = "फ्रै", ["बे्र"]= "ब्रे",\definefontfamily [kannada"बै्र"] = "ब्रै", [ss"भे्र"] = "भ्रे", [Tunga"भै्र"] = "भ्रै", [features"मे्र"] =kannada-one"म्रे", ["मै्र"]= "म्रै", ["ये्र"] = "य्रे", ["यै्र"] = "य्रै", ["वे्र"] = "व्रे", ["वै्र"] = "व्रै", ["से्र"] = "स्रे", ["सै्र"] = "स्रै", ["शे्र"] = "श्रे", ["शै्र"] = "श्रै", ["षे्र"] = "ष्रे", ["षै्र"] = "ष्रै", ["हे्र"] = "ह्रे", ["है्र"] = "ह्रै", } } }}</texcode>

Suppose that for a certain font (say <code>myfont</code>), using <code>devanagari-two</code> features, the above listed ra + consonant + vowel forms are not rendered properly. The above goodies file is then saved as <code>myfont.lfg</code> and used while defining the features thus:<texcode>\definetypeface definefontfeature [kannadamyfontfeatures] [mmdevanagari-two] [math] [modern]goodies=myfont.lfg, sanitizer=dev2rkrf,\setupbodyfont [kannada indic={movematra=auto,conjuncts=quit}] \starttextಇದು ಹೇಗಿದೆ? ನಾನು ಹೀಗೆ ತುಂಬ ಬರೆಯಬೇಕೆಂದು ಯೋಚಿಸುತ್ತಿದ್ದೇನೆ.\stoptext

= Supported Scripts = The list of Indic scripts supported by ConTeXt MkIV Script and LMTX are: * Devanagari* Bengali* Gujarati* Gurmukhi* Kannada* Malayalam* Oriya* Tamil* Telugu In order to get the proper OpenType language features, you need to select the proper feature from the following list: * <code>devanagari-one</code>* <code>bengali-one</code>* <code>gujarati-one</code>* <code>gurmukhi-one</code>* <code>kannada-one</code>* <code>malayalam-one</code>* <code>oriya-one</code>* <code>tamil-one</code>* <code>telugu-one</code> Depending on your font, you might need instead: * <code>devanagari-two</code>* <code>bengali-two</code>* <code>gujarati-two</code>* <code>gurmukhi-two</code>* <code>kannada-two</code>* <code>malayalam-two</code>* <code>oriya-two</code>* <code>tamil-two</code>* <code>telugu-two</code> == Script Versions == [https://docs.microsoft.com/en-us/typography/opentype/spec/scripttags Script tags from the OpenType specification] contains second versions for what might be some (or all [I’m afraid I don’t know]) 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. = Hyphenation =

* Sanskrit {|cellpadding="5"! style="text-align:left;" | Script/Language! style="text-align:left;" | Conversion set! style="text-align:left;" | Hyphenation|-| Devanagari| <code>devanagarinumerals</code>| |-| Malayalam| <code>samalayalamnumerals</code>* Hindi | <code>hi\language[ml]</code>* |-| Kannada | <code>kannadanumerals</code>| <code>\language[kn]</code>* |-| Telugu | <code>telugunumerals</code>| <code>\language[te]</code>|-| Bengali| <code>bengalinumerals</code>| <code>\language[bn]</code>* |-| Tamil | <code>tamilnumerals</code>| <code>\language[ta]</code>|-| Gujarati| <code>gujaratinumerals</code>| <code>\language[gu]</code>* Malayalam |-| Gurmukhi| <code>gurmukhinumerals</code>||-| Hindi| <code>devanagarinumerals</code>| <code>ml\language[hi]</code>* Bengali |-| Sanskrit| <code>bndevanagarinumerals</code>* Gujarati | <code>gr\language[sa]</code>|}

A pattern is activated with {{cmd|language}}. The Sanskrit hyphenation patterns <code>sa</code> support hyphenation of Sanskrit written using the Malayalam, Telugu, Kannada, Bengali and Latin with IAST. = Numbers and Conversion sets =The following number conversion sets are available:* Devanagari <code>devanagarinumerals</code>* Malayalam <code>malayalamnumerals</code>* Tamil <code>tamilnumerals</code>* Kannada <code>kannadanumerals</code>* Telugu <code>telugunumerals</code>* Bengali <code>bengalinumerals</code>for use used as values of the keys <code>numberconversion</code>, <code>conversion</code> (wherever applicable) and with {{cmd|convertnumber}}.

! style="width: 65%; text-align: left;" | Transliteration Scheme!style="text-align: left;" | Vector