Indic Layout Requirements (original) (raw)
Abstract
This document describes the basic requirements for Indic script layout and text support on the Web and in Digital Publications. These requirements provide information for Web technologies such as CSS, HTML, and SVG about how to support users of Indic scripts. The current document focuses on Devanagari, but there are plans to widen the scope to encompass additional Indian scripts as time goes on.
Status of This Document
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in theW3C technical reports index at https://www.w3.org/TR/.
This document describes the basic requirements for Indic script layout and text support on the Web and in eBooks. These requirements provide information for Web technologies such as CSS, HTML and SVG about how to support users of Indic scripts. The current document focuses on Devanagari, but there are plans to widen the scope to encompass additional Indian scripts as time goes on.
The editor's draft of this document is being developed by the Indic Layout Task Force, part of the W3C Internationalization Interest Group. It is published by the Internationalization Working Group. The end target for this document is a Working Group Note.
Note
Sending comments on this document
If you wish to make comments regarding this document, please raise them as github issues. Only send comments by email if you are unable to raise issues on github (see links below). All comments are welcome.
To make it easier to track comments, please raise separate issues or emails for each comment, and point to the section you are commenting on using a URL for the dated version of the document.
This document was published by the Internationalization Working Group as a Working Draft.
GitHub Issues are preferred for discussion of this specification. Alternatively, you can send comments to our mailing list. Please send them topublic-i18n-indic@w3.org (archives).
Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by a group operating under theW3C Patent Policy. The group does not expect this document to become a W3C Recommendation.W3C maintains apublic list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes containsEssential Claim(s) must disclose the information in accordance withsection 6 of the W3C Patent Policy.
This document is governed by the1 March 2019 W3C Process Document.
Table of Contents
- 1. Introduction
- 2. Indic orthographic syllable boundaries
- 3. Text segmentation
- 4. Line breaking
- 5. Initial letter styling
- 5.1 Selecting initial letters
- 5.2 Typical drop initial usage in Indic scripts
- 5.3 Alignment of Initial letter of Indic scripts with hanging baseline
- 5.4 Scripts that don't have hanging baseline such as Kannada, Tamil, Telugu, Malayalam , Odia etc
- 5.5 Initial Letter box formatting in Indian languages
- 6. Letter Spacing
- 7. Vertical arrangements of characters
- 8. Collation
- A. Contributors
- B. Revision Log
- C. References
- C.1 Normative references
1. Introduction
1.1 About this document
This document describes the basic requirements for Indian Languages layout for display purpose. It discusses some of the major layout requirements in first letter pseudo-element, vertical arrangements of characters, letter spacing, text segmentation, line breaking rules in Indic languages.
The current document focuses on Devanagari, but there are plans to widen the scope to encompass additional Indian scripts as time goes on.
The minimal requirements presented in this document for Indian languages text layout will also be used in E-publishing and CSS standards. This documents covers major issues of e-content in Indian languages in order to create a standard format of text layout to address storage, rendering problems, vertical writing, letter spacing, line breaking etc.
It also describes a set of ABNF-based rules for valid segmentation of Indic orthographic syllables in order to get the proper display in browsers. Text segmentation[UAX29] and line breaking [UAX14] algorithms are considered in detail. Standards for CSS and digital publications will benefit from this document.
1.2 Indian language complexities
India has large linguistic diversity with 22 constitutionally recognized languages and 12 scripts.This document is currently focused largely on the Devanagari script. The expectation is that over time its scope will widen to cover additional major scripts from the list below.
The mapping between languages and scripts is complex. Multiple languages may have common scripts, while a language can be written in multiple scripts. Each language and script is unique in nature and cannot be easily replicated, even if they share common characteristics. The orthographic changes may also occur in some languages and adoption of new orthography is a gradual process, thus posing additional challenges.
Serial No. | Language | Script |
---|---|---|
1 | Hindi | Devanagari |
2 | Sanskrit | Devanagari |
3 | Marathi | Devanagari |
4 | Konkani | Devanagari |
5 | Nepali | Devanagari |
6 | Maithili | Devanagari |
7 | Sindhi | Devanagari, Perso-Arabic |
8 | Bodo | Devanagari |
9 | Dogri | Devanagari |
10 | Bengali | Bengali |
11 | Assamese | Bengali |
12 | Manipuri | Bengali, Meetei (Mayak) |
13 | Gujarati | Gujarati |
14 | Kannada | Kannada |
15 | Malayalam | Malayalam |
16 | Odia | Odia |
17 | Punjabi | Gurmukhi |
18 | Tamil | Tamil |
19 | Telugu | Telugu |
20 | Urdu | Perso-Arabic |
21 | Santhali | Ol-Chiki, Devanagari |
22 | Kashmiri | Devanagari, Perso-Arabic |
The scripts of South Asia share so many common features that a side-by-side comparison of a few will often reveal structural similarities, even in modern letter forms. They are all abugidas in which most symbols stand for a consonant with an inherent vowel.The North Indian branch of scripts was, like Brahmi itself, mainly used to write Indo-European languages such as Pali and Sanskrit, and eventually the Hindi, Bengali, and Gujarati language, though it was also the source for scripts for non-Indo-European languages such as Tibetan, Mongolian, and Lepcha, as well as many South-East Asian scripts. The South Indian scripts are also derived from Brahmi and, therefore, share many similarities in structural characteristics. For more details visit [South-Asian-Scripts].
Figure 1 shows the evolution of Indian scripts over a period of time from Brahmi script.
Figure 1 Development of Indian Scripts
For more details visit [Evolution-of-Indic-Scripts]
1.3 Basic components of Indian languages
1.3.1 Unicode & CLDR
Unicode is the Universal character encoding standard, used for representing text for information processing. Unicode encodes all of the individual characters used for all the written languages of the world. The standards provide information about the character and their use.
Common Locale Data Repository is the largest standard repository of locale data in the world. It is managed by the Unicode Consortium. It provides locale data in an XML format for use in computer applications. It facilitates locale-related information sharing among applications regardless of their domains. Its goal is to provide basic linguistic information for diverse “locales” in an open, interoperable form.
This data is usable for localizing applications.
Some examples of the information that CLDR gathers for languages and territories are:
- Date formats
- Time Zones
- Number formats
- Currency and its formats
- Measurement Systems
- Collation (Sort order) Specification: Sorting, Searching and Matching
- Translations of names for language, territory, script, time zones, currencies
- Script and exemplar characters used by a language
- Calendaring rules, Formats and important dates.
Note
Reference URL: [CLDR]
1.3.2 Unicode Normalization
Unicode normalization [UAX15] is a form of text normalization that transforms equivalent sequences of characters into the same representation. Unicode normalization is important in Unicode text processing applications, because it affects the semantics of comparing, searching, and sorting Unicode sequences
When a unique representation is required , a normalized form of Unicode text can be used to eliminate unwanted distinctions. The key part of normalization is to provide a unique canonical order for visually non distinct sequences of combining characters.
1.3.2.1 Canonical & Compatible Equivalence
Unicode contains numerous characters to maintain compatibility with existing standards, some of which are functionally equivalent to other characters or sequences of characters. Because of this, Unicode defines some code point sequences as equivalent. Unicode provides two notions of equivalence: canonical and compatible.
Canonical equivalence is a form of equivalence that preserves visually and functionally equivalent characters.
Figure 2 shows the canonical equivalence:
Figure 2 Canonical Equivalence
1.3.3 Unicode Code charts – Devanagari & Devanagari Extended
The following Unicode Character Code chart is per the Unicode Standard:
Figure 3 Unicode Devanagari and Devanagari extended Code Chart
Note
The latest version of Unicode online code charts are available at [Code-Charts] . The charts cover all character content reference of the 12 scripts of Indian languages. These files contains an excerpt from the character code tables and list of character names for the latest version of Unicode Standard.
2. Indic orthographic syllable boundaries
2.1 Need for ABNF valid segmentation
ABNF Valid Segmentation based Indic orthographic syllable definition is provided here for correct and standardized representation of Indian languages layout. This will address various issues mentioned in the following sections.
This definition will be useful in order to get the uniform display of Indic layout in the browsers, applications, Digital publishing etc.
2.2 ABNF based definition of Indic orthographic syllable
V[m] |{CH}C[v][m]|CH
The linguistic definition of Indic orthographic syllable has been mapped to ABNF (Augmented Backus–Naur Form) for the purpose of text segmentation, line breaking , drop letter, letter spacing in horizontal text and vertical text representation. The definition has been elaborated , using examples from various Indic scripts in the table below.
The definition is a combination of 3 rules :
Rule 1 : V[m]
Rule 2 : {CH}C[v][m]
Rule 3 : CH (This rule is applicable only at the end of the word)
V(upper case) is independent vowel
m is modifier (Anusvara/Visarga/Chandrabindu)
C is a consonant with inherent vowel which may or may not include a single nukta
v (lower case) is any dependent vowel or vowel sign (mātrā)
H is halant / virama
| is a rule separator
[ ] - The enclosed items is optional under this bracket
{} - The enclosed item/items occurs zero or repeated multiple times
2.3 Various example use cases of ABNF based Indic orthographic syllable definition for Indian languages
Rule 1 : V[m]
V (Vowel) is a syllable | V+ Modifier is a syllable | |
---|---|---|
Hindi | अ, ई, उ | अं, उँ, आः |
Kannada | ಅ, ಇ | ಅಂ , ಅಃ |
Tamil | அ, ஆ, இ | NA |
Telugu | అ, ఇ, | అం , ఆః |
Malayalam | അ, ഇ, ഉ | അം, അഃ |
Bengali | অ , ই , ঋ | উঃ , এঁ, আঁ |
Nepali | अ, आ, इ, उ | अँ, अं, उः |
Manipuri language of Bengali script | অ, ই, উ | ওঁ, অং (হোয়) |
Kashmiri language of Devanagari script | अ , ऑ ,ऒ ,ऎ | अँ |
Maithili | अ, ई, उ | अं, उँ, आः |
Dogri | अ, ई, उ | अं |
Odia | ଅ, ଈ, ଉ | ଅଂ, ଉଁ, ଆଃ |
Punjabi | ਅ, ਆ, ਇ | ਇੰ, ਉਂ |
Sanskrit (Excluding Vedic Extensions) | अ, ई, उ | अं, उँ, आः |
Marathi | अ, ई, ऐ | अं, उँ, आः |
Assamese | অ , ই , ঈ | অঁ , অং, আঁ , ইঃ |
Santhali language of Devanagari script | अ, ई, उ | अं, उँ, आः |
Gujarati | અ, ઇ, ઈ | અં, અઃ |
Konkani | अ, ई, उ | अं |
Bodo | आ , ओ , ए , उ | ऐं , ऒं |
Sindhi language of Devanagari script | अ , ऊ , ई , ऐ | ओं , एं , उं |
Rule 2 : {CH}C[v][m]
Consonant is a syllable | Zero or more Consonant(Nukta *) + Virama sequences followed by consonant (+Nukta*)is a syllable | Zero or more consonant+ (Nukta*)+ virāma sequences followed by a consonant (+Nukta*) followed by a vowel sign is a syllable | zero or more consonant+ (Nukta*)+ virāma sequences followed by a consonant (+Nukta*) followed by modifier is a syllable | zero or more consonant+ (Nukta*)+ virāma sequences followed by a consonant (+Nukta*) followed by a vowel sign and modifier is a syllable | |
---|---|---|---|---|---|
Hindi | र, क, ज, ल, म | प्प, क्ख,च्त, ज्ज्व, त्क्ल, त्स्न , र्त्स्न्य, फ़्क | र्ता, र्त्स्न्या, फ़्जी, क्या, स्थि | तः,स्तं, स्त्रँ, स्तः, फ़्ज़ँ | र्त्स्न्या: त्स्न्युं, त्स्न्युँ, फ़्ज़ें,हि |
Kannada | ರ, ಕ, ಜ, ಲ, ಮ | ಪ್ಪ, ಕ್ಖ,ಚ್ತ, ಜ್ಜ್ವ, ತ್ಕ್ಲ, ರ್ತ, ರ್ತ್ಸ, ರ್ತ್ಸ್ನ | ರ್ತಾ, ರ್ತ್ಸ್ನ್ಯಾ , ಖ್ವಾ | ತಃ, ಸ್ತಂ | ರ್ತ್ಸ್ನ್ಯಾಃ , ತ್ಸ್ನ್ಯುಂ |
Tamil | க, ச, ங | க்ஷ | ஶ்ரீ , ஸ்ரீ , ரா | NA | NA |
Telugu | ర, క, జ, ల | ప్ప, క్ఖ, చ్త,జ్జ్వ , ర్త్స్న , ర్త్స్న్య | ర్తా, ర్త్స్న్యా , ఖ్ఖి | తః, స్తం | క్కిం , ఖ్ఖిం , గ్గిం |
Malayalam | ര, ക, ജ, ല, മ | പ്പ, ജ്ജ്വ, ത്സ, ക്ത | ക്ഷി, ത്തി, ത്സാ, ജ്ഞി , മ്മീ | നഃ, മഃ | ക്ലി , ത്തിം |
Bengali | ক, ঙ, ঘ, ছ | ক্ক, ষ্ট, ষ্ণ, থ্র | ণ্যে, ন্ত্রে , গ্নে , গ্নী , ন্ত্রী | NA | স্যাঁ, ট্যাঁ, খ্রীঃ, ষ্টাং |
Nepali | क छ ड भ | क्क क्ख ज्ज्व | र्पे , स्ति | तः स्त्रं | त्स्न्युँ |
Manipuri language of Bengali script | ক, ল, ম, প | ন্দ, ক্ত , পৃ, র্জ্জ | র্তি, (পার্তি) , ঙ্থ্রৈ | ক্তং (খজিক্তং) | দাঃ, ন্দ্রাং, প্ত্রেং |
Kashmiri language of Devanagari script | र, क, ज, ल | त्य, थ्व, च्य | न्यॊ, र्ता प्रा, क्या , प्रॉ | स्तं | NA |
Maithili | र, क, ज | क्ख , न्ह, न्ध , फ़्क | र्ता, र्त्स्न्या, फ़्जी, क्या | तः,स्तं, स्त्रँ, स्तः | त्स्न्युं , त्स्न्युँ, फ़्ज़ें |
Dogri | क, ज,स ,ल | ग्ग, द्ध , क्क | फ्ही , म्मी , ड़ि , क्का | जं , सं | यें , च्चैं , रें |
Odia | କ, ଜ, ମ, ର, ଳ | କ୍କ, ଚ୍ଚ, ଟ୍ଟ, ଜ୍ଜ, ନ୍ନ , ଜ୍ଜ୍ୱ , ର୍ଣ୍ଣ, , ର୍ତ୍ସ | ର୍ତ୍ତା, ଜ୍ଞା, ଜ୍ଞୀ , ସ୍ଥି | ତଃ, ସ୍ତଂ, ସ୍ତଃ | ହିଂ |
Punjabi | ਕ, ਜ, ਧ,ਵ | ਪ੍ਰ, ਕ੍ਰ , ਸ੍ਵ | ਨ੍ਹਾ,ਕੌ,ਹੋ | ਧੰ, ਯੱ, ਨੰ | ਮਾਂ, ਪੁੱ, ਚਿੱ |
Sanskrit (Excluding Vedic Extensions) | ग,ड,प,र,ण | ल्म, त्य, ल्प | क्षे, र्था, यो , प्तो | तं ,न्तः, मः , प॑ , र॒ | षाः, ताः, स्यां , दी॑ , हि॒ |
Marathi | ल, ष, ळ | स्व, क्ष्ण | व्या, त्स्ना | कं, स्पं | त्क्रां,त्र्यां |
Assamese | ক , খ, ঘ | ন্ত্ৰ , ৰ্খ, ৰ্জ , ৰ্ট | ৰ্কে , ন্হা, ছ্ছা , ম্প্ৰ্দা | ৰ্নিং , ৰ্ণাং , ট্ৰাং , ৰ্কিং | NA |
Santhali language of Devanagari script | र, क, ज, ल, म | NA | र्ता, ड़ि | तः, कं , मः | ताः, रें |
Gujarati | ર, ક , લ, મ | ક્ક, દ્ય, સ્ત્ર , ર્જ્જ, ર્પ્ક્ક | ર્તા,ર્ત્સ્ન્યા, ક્યા | તઃ, સ્તઃ | ર્ત્સ્ન્યાઃ, હિં |
Konkani | ळ | य, स्प, ल्म, स्थ , ल्ल्य | ज्यु, त्मे, स्त्री, स्तू, भ्रू | स्कं, स्थं, न्हं, द्वं | व्हां, म्हों, ल्लें, र्दें |
Bodo | ब, फ, ख , ज | प्ता , ज्ज , ब्ला | ब्ला , यो , न्दो , न्थि | सं , रं , गं , न्थं | खां , दुं |
Sindhi language of Devanagari script | क, घ , ज , ग | क्ट , ग्घ , फ्ख , स्त्र , च्ग़ , न्ज | बि , लू , यि , क्षी | धं , धृं , षं | हिं , सौं , श्रिं |
* Nukta within a bracket is optional.Consonant may or may not include Nukta.
Rule 3 : CH
This rule is applicable only for those Indian languages where pure consonant appears at the end of the word.
Examples of Rule3 - Consonant + virama at the end of the word | |
---|---|
Hindi | NA |
Tamil | வணக்கம் , தமிழ் , எண்ணம், செயல் |
Kannada | ಬ್ಯಾಂಕ್ |
Telugu | క్ , జ్ , ఞ్ |
Malayalam | വാക്ക്, ചാക്ക് , നിനക്ക് |
Bengali | ত্ (হঠাৎ) , This rule would not be applicable if ৎ is declared as pure consonant. |
Nepali | छन्, हुन्, गर्दैनन्, गर्छस् |
Manipuri language of Bengali script | খ্বাঙজেৎ |
Kashmiri language of Devanagari script | NA |
Maithili | NA |
Dogri | राह् , ओह् |
Odia | NA |
Punjabi | NA |
Sanskrit (Excluding Vedic Extensions) | तेजस्, मरुत् , माम् |
Assamese | ত্ (হঠাৎ) , This rule would not be applicable if ৎ is declared as pure consonant. |
Santhali language of Devanagari script | NA |
Gujarati | આત્મસાત્ |
Konkani | NA |
Bodo | NA |
Sindhi language of Devanagari script | NA |
3. Text segmentation
A string of Unicode-encoded text often needs to be broken up into text elements programmatically. Common examples of text elements include what users think of as characters, words, lines (more precisely, where line breaks are allowed), and sentences. The precise determination of text elements may vary according to orthographic conventions for a given script or language. The goal of matching user perceptions cannot always be met exactly because the text alone does not always contain enough information to unambiguously decide boundaries. For example, the period (U+002E FULL STOP) is used ambiguously, sometimes for end-of-sentence purposes, sometimes for abbreviations, and sometimes for numbers. In most cases, however, programmatic text boundaries can match user perceptions quite closely, although sometimes the best that can be done is not to surprise the user. Word boundaries are used in a number of different contexts. The most familiar ones are selection (double-click mouse selection, or “move to next word” control-arrow keys), and “Whole Word Search” for search and replace. They are also used in database queries, to determine whether elements are within a certain number of words of one another . Grapheme cluster boundaries are important for collation, regular expressions, UI interactions (such as mouse selection, arrow key movement, backspacing), segmentation for vertical text, identification of boundaries for Initial-letter styling, and counting “character” positions within text. [UAX29]
3.1 Word Boundaries
Solution for word boundaries:
User-percieved characters boundaries should be based on tailored Grapheme Cluster Boundaries to conform Indic orthographic syllable definition
In case of Devanagari phrase separator । , U+0964 DEVANAGARI DANDA, (called purna viram in Hindi) and ॥ , U+0965 DEVANAGARI DOUBLE DANDA, (deergh viram in Hindi) used to mark end of the verse as in Sanskrit text, shlokas etc.),In some of the browsers ending word is selected with purna viram on double-click while in some browsers purna viram is selected as a separate.So the properties of purna viram and deergh viram should be same as the properties of FullStop or other punctuation marks so that new line should not begin with purna viram and deergh viram.
For others characters, the text segmentation should be done as Indic orthographic syllable.
3.2 Typographic units
Indic script behavior in initial letter styling is based on syllables, rather than individual letter forms.
The above Figure shows an example of a drop intial in Hindi. In the first word of the paragraph, स्कूल ('skūl'), the sequence of characters is stored in memory is as follows:
There are two syllables in this word: SA+VIRAMA+KA+UU and LA. Note, however, that there are three Unicode grapheme clusters here: SA+VIRAMA, KA+UU and LA.
Styling is done on the basis of the whole orthographic syllable, not the first character, nor even the first grapheme.
4. Line breaking
When inline-level content is laid out into lines, it is broken across line boxes. Such a break is called a line break. In most writing systems, in the absence of hyphenation a line break occurs only at word boundaries. Many writing systems use spaces or punctuation to explicitly separate words, and line break opportunities can be identified by these characters. Line breaking, also known as word wrapping, is the process of breaking a section of text into lines such that it will fit in the available width of a page, window or other display area.
4.1 Hyphenation
There are different cases of hyphenation, some of the cases are given below :
Case 1 : Hyphens are commonly used in Copulative compounds words in Hindi language. Hindi has both prefixes and suffixes which are joined to words with a hyphen.
नर-नारी, लाभ-हानि, माता-पिता, ऊंच-नीच
Case 2:Single word can breaks at the end of the line follow Indic orthographic syllable using hyphen.Following example shows correct representation of word आकर्षण and विज्ञापन using hyphen :
4.2 Guiding principles of Line breaking for Indian languages
In Indic writing system , it is preferred that line breaks at word boundaries ,if required following principles may be adhered :
Rule 1: New line cannot begin with following symbols/Punctuation marks. Also these should be retain with the associated text
Symbols | Character name | Unicode code-point |
---|---|---|
। | DEVANAGARI DANDA | U + 0964 |
॥ | DEVANAGARI DOUBLE DANDA | U + 0965 |
) | RIGHT PARENTHESIS | U + 0029 |
+ | PLUS SIGN | U + 002B |
* | ASTERISK | U + 002A |
- | HYPHENATIONPOINT-VISIBLE HYPHEN HYPHENATION-SOFT HYPHEN | U + 2027 U+ 00AD |
/ | SOLIDUS | U + 002F |
, | COMMA | U + 002C |
. | FULL STOP | U + 002E |
: | COLON | U + 003A |
; | SEMICOLON | U + 003B |
= | EQUALS SIGN | U + 003D |
> | GREATER-THAN SIGN | U + 003E |
] | RIGHT SQUARE BRACKET | U + 005D |
_ | LOW LINE | U + 005F |
| | VERTICAL LINE | U + 007C |
} | RIGHT CURLY BRACKET | U + 007D |
~ | TILDE | U + 007E |
% | PERCENT SIGN | U + 0025 |
Rule 2: The definition of Indic orthographic syllable may be used to break the line and a hyphen should be at the breaking point so that word can be read intuitively However the language specific morpho-phonemic rules and industry practices (from media, publishing and grammar books) could be used for hyphenation. U+ 00AD (soft hyphen) is used in some languages such as Tamil and Malayalam.
Rule 3: The hyphenated words can be broken at the hyphen e.g.:
- नर-नारी should be treated as:
- नर- on the first line and नारी on the next line
Rule 4: Expression with mathematical symbol should be treated as single unit so that at the end of the line expression should not breaks at operator level
Rule 5: Breaking should not be allowed at numerical values such as currency values, year etc. e.g.
“100.00” or “10,000”, nor in “12:59”
5. Initial letter styling
Drop initial is a typographic effect emphasizing the initial letter(s) of a block element with a presentation similar to a 'floated' element.
5.1 Selecting initial letters
Initial letters in Indic scripts must be selected on the basis of orthographic syllables, rather than individual letter forms (see an example at the end of § 3. Text segmentation). A detailed definition of Indic syllables can be found in § 2. Indic orthographic syllable boundaries. In Indian languages the size of the initial letter is determined by the number of the lines between the top line of the syllable and the lowest bit in the orthographic Indic syllable cluster where subjoined consonant and other diacritics appear.
5.2 Typical drop initial usage in Indic scripts
Most of the Indic drop initial letters in magazines and newspapers use 2 to 4 line drops. Some examples are shown below.
Figure 4 Examples of Indic Initial letters
The sunken and raised initial letter are not preferred in Indian languages. In the above examples , reference points on the drop cap must align precisely with reference points in the text. .In Indic scripts the top reference point is the hanging base line for those scripts that have one, and the mean/median line for those that don't, and the bottom alignment point is the text after-edge
Initial letter wrap property is not applicable for Indian languages. No contour-filling is required in Indian languages.
Alignment of the top line of the non-highlighted characters at the top of the thicker top line of the initial letter is common in India. In some examples the top lines of the initial letter and the following letters don't touch. This is due to variable technology/formats used by the publishers. It is preferred that both the top lines of Initial letter and neighbouring text should touch.
Here are some additional examples of initial highlighted letter and drop letter based on the Indic syllable definition.
The remainder of this section describes the detailed rules for placement and alignment of characters with initial letter styling relative to the adjacent text.
5.3 Alignment of Initial letter of Indic scripts with hanging baseline
Indian languages which use hanging baseline such as Hindi, Bengali, Gujarati, Marathi, Punjabi etc. The part from the hanging baseline and the ascent of the Initial letter may follow the following mechanism, where n = h/2:
Figure 5 Rule of Indic script with hanging baseline
In Indic scripts that have a hanging baseline, the top alignment point is the hanging baseline, and the bottom alignment point is the text-after-edge, and the hanging baselines of both the initial letter and first line of text should be aligned.
5.4 Scripts that don't have hanging baseline such as Kannada, Tamil, Telugu, Malayalam , Odia etc
Publishers in India commonly used the following rules for such scripts:
- The height of the initial letter is based on the Indic orthographic syllable described in § 2. Indic orthographic syllable boundaries.
- Ascent of the first non-highlighted line is equal to the median/mean line of the initial letter as shown below :
Based on above observations the general rule for South Indian languages Indian languages scripts will be :
- ¼ height of the total Drop Cap Height projected or ascended above the ascent of the first-line
- ¾ of the total Drop Cap Height occupied or descended from ascent of first line or X1 to descent of the last line or line XN.
5.5 Initial Letter box formatting in Indian languages
When initial letters are highlighted within a box, Indian publishers commonly use different heights for the boxes and sizes for the characters. It is proposed that the syllable within the box is centre-aligned with reference to the box parameters as shown in the figure below :
Figure 6 Examples of Indic initial letters within a box.
6. Letter Spacing
In styling issues like horizontal spacing, the spacing between characters like C E R T I F I C A T E, the space is given between the every character in case of English. But in case of Indian language, the space needs to be introduced after each syllable for correct representation.
Letter spacing in Indian Languages is used . In some of the languages like Bengali it is more prevalent . In Hindi , which is the largest speaking language in India the character spacing is sometimes used. Also it is used for decorative style of writing such as Newspaper Column , banner etc. Here is the example of the name plate of the Museum. The top bar is broken in letter spacing and the space letter is added between orthographic syllable.
Here is the some examples of letter spacing that based on definition :
- अं त र्रा ष्ट्री य क र ण
- स्वा ग त म्
- सु स ज्जि त
- स म्प्र ति Here is the example of the name plate of the Museum. The top bar is broken in letter spacing and the space letter is added between orthographic syllable.
7. Vertical arrangements of characters
In vertical arrangement of characters writing each character on a new line may not be suitable in Indian languages. The vertical arrangements of characters are sometimes used in Indian texts. In order to form correct arrangements, it is preferred to follow tailored grapheme cluster approach. Variations of vertical arrangement of the characters in Hindi is represent below :
7.1 Variations in vertical arrangements
Figure 8 Variations in vertical arrangements
The above example shows two variation of the word in order to differentiate the correct and wrong representation of the word. The segmentation of the vertical arrangements should follow the Indic syllabic definition.Given below the example 'स्वागतम्' that follows rule 2 and rule 3 of Indic orthographic syllable definition:
स्वा | CHCv- Rule 2 |
---|---|
ग | C - Rule 2 |
त | C - Rule 2 |
म् | CH - Rule 3 |
8. Collation
Collation is one of the most important features for Indic languages . It determines the order in which a given culture indexes its characters. This is best seen in a dictionary sorting order where for easy search words are sorted and arranged in a specific order. Within a given script, each allo-script may have a different sort-order. Thus in Hindi the conjunct glyph क्ष is sorted along with क , since the first letter of that conjunct is क and on a similar principle ज्ञ is sorted along with ज . The same is not the case with Marathi and Nepali which admit a different sort order.
Different scripts admit different sort orders and for all high end NLP applications. Sorting is a crucial feature to ensure that the applications index data as per the cultural perception of that community. In quite a few States, sort order is clearly defined by the statutory bodies of that state and hence it is crucial that such sort order be ascertained and introduced in the document .
The order(left to right) as given below is pertinent to sorting by a computer program and is compliant with CLDR as laid down by Unicode.
़ \u093C | ॐ \u0950 | ं \u0902 | ँ \u0901> | ः \u0903 | अ \u0905 |
---|---|---|---|---|---|
आ \u0906 | इ \u0907 | ई \u0908 | उ \u0909 | ऊ \u090A | ऋ \u090B |
ऌ \u090C | ऍ \u090D | ए \u090F | ऐ \u0910 | ऑ \u0911 | ओ \u0913 |
औ \u0914 | क \u0915 | ख \u0916 | ग \u0917 | घ \u0918 | ङ \u0919 |
च \u091A | छ \u091B | ज \u091C | झ \u091D | ञ \u091E | ट \u091F |
ठ \u0920 | ड \u0921 | ढ \u0922 | ण \u0923 | त \u0924 | थ \u0925 |
द \u0926 | ध \u0927 | न \u0928 | प \u092A | फ \u092B | ब \u092C |
भ \u092D | म \u092E | य \u092F | र \u0930 | ल \u0932 | ळ \u0933 |
व \u0935 | श \u0936 | ष \u0937 | स \u0938 | ह \u0939 | ऽ \u093D |
ा \u093E | ि \u093F | ी \u0940 | ु \u0941 | ू \u0942 | \U0943 |
\U0944 | \U0945 | े \u0947 | ै \u0948 | ॉ \u0949 | ो \u094B |
ौ \u094C | ् \u094D |
Following is the sort order of Consonant 'क'
क | कँ | कं | कः | का | कि | की | कु | कू | कृ | के | कॅ |
---|---|---|---|---|---|---|---|---|---|---|---|
कै | को | कॉ | कौ | क् | क़ |
A. Contributors
Serial No. | Name | Organization |
---|---|---|
1 | Swaran Lata | DeitY |
2 | Dr. Somnath Chandra | DeitY |
3 | Manoj Kumar Jain | DeitY |
4 | Gautam Sengupta | University of Hyderabad |
5 | Girish Nath Jha | JNU |
6 | Rajeev Sangal | IIT Varanasi |
7 | Dipti Misra Sharma | IIIT Hyderabad |
8 | R K Sharma | Thapar University |
9 | Rajat Mohanty | IIT Bombay |
10 | Venkatesh Choppella | IIIT Hyderabad |
11 | Soma Paul | IIIT Hyderabad |
12 | M D Kulkarni | C-DAC Pune |
13 | Panchanan Mohanty | University of Hyderabad |
14 | G. Uma Maheshwar Rao | University of Hyderabad |
15 | Dr. Bisembli P. Hemananda | University of Mysore |
16 | Dr. R. Chandrashekar | JNU |
17 | Dr. Elizabeth Sherly | IIITM-K |
18 | V K Bhadran | C-DAC |
19 | Sanjay Kumar Choudhury | C-DAC |
20 | Dr. Ghanashyam Nepal | University of North Bengal |
21 | Dr. Sarbajit Singh | Indian Institute of Information Technology, Manipur |
22 | Dr. Adil Amin Kak | University of Kashmir |
23 | Dr. Abhijit Dixit | JNU |
24 | Dr. Panchanan Mohanty | University of Hyderabad |
25 | Dr.Preeti Dubey | Central University of Jammu |
26 | Amba Kulkarni | University of Hyderabad |
27 | Smt. Mridismita Mitra | C-DAC |
28 | Smt. Pampa Bhattacharyya | C-DAC |
29 | Dr. Jyoti D. Pawar | DCST , Goa University |
30 | Ramdas Karmali | DCST , Goa University |
31 | Prafulla Basumatary | Gauhati University |
32 | Bhojraj Lekhwani | C-DAC |
33 | Sanat Hansda | Visva-Bharati University, Santiniketan, W.B |
B. Revision Log
- Various editorial and code tweaks.
- Added use cases of ABNF based Indic orthographic syllable definition for various languages and scripts besides Hindi/Devanagari.
- Unicode chart images updated.
Recent and older changes can be found in the github commit log.
C. References
C.1 Normative references
[CLDR]
Unicode CLDR. URL: http://cldr.unicode.org
[Code-Charts]
Unicode Code Charts. URL: http://www.unicode.org/charts/
[Evolution-of-Indic-Scripts]
Indic Scripts. URL: http://www.ciillibrary.org/Sites/Photography/PhotographyHome.html
[South-Asian-Scripts]
Unicode Technical note#10 : South Asian Scripts. URL: http://www.unicode.org/notes/tn10/
[UAX14]
Unicode Line Breaking Algorithm. URL: http://www.unicode.org/reports/tr14/
[UAX15]
Unicode Normalization Forms. Ken Whistler. Unicode Consortium. 24 February 2020. Unicode Standard Annex #15. URL: https://www.unicode.org/reports/tr15/tr15-50.html
[UAX29]
Grapheme Cluster boundaries. URL: http://www.unicode.org/reports/tr29/