DOCSLIB.ORG

A Guide to Developing Fonts for Indian Languages

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Guide to Developing Fonts for Indian Languages A Guide To Indian Language Font Development Elaborate, Illustrated font development guideline document for scripts of India by font designers, developers, language experts. Editor Santhosh Thottingal Contributors Balasankar C Behdad Esfahbod Hrishikesh Kartik Mistry Kavya Manohar Rahimanuddin Shaik Rajeesh Nambiar Ryan Kaldari Vasudev Kamath March 31, 2014 https://github.com/IndicFontbook/Fontbook Dedicated to all font designers Contents 1 Introduction 1 1.1 Objectives of document ................... 2 1.2 Target Audience for this document ............ 2 1.3 Scope ............................. 2 1.4 How to use this document ................. 3 1.5 Notes on Collaboration ................... 3 2 General Concepts 5 2.1 Script ............................. 5 2.2 Complex script ....................... 5 2.3 Glyph ............................ 6 2.4 Ligatures ........................... 7 2.5 Cluster/Syllable ...................... 8 2.6 Akhand ........................... 8 2.7 Ra Forms .......................... 8 2.8 Split Matra ......................... 8 2.9 Reordering ......................... 9 2.10 Zero Width Joiner ..................... 9 2.11 Zero Width Non Joiner .................. 9 2.12 Stacking ........................... 9 3 Open font format 11 3.1 Introduction ......................... 11 3.2 GPOS ............................. 11 3.3 GSUB ............................. 11 3.4 GDEF ............................. 11 3.5 Shaping Engine ....................... 11 3.6 Shape Glyph sequence ................... 12 3.7 Position Glyph sequence .................. 12 iii 3.8 Reference fonts ....................... 12 3.9 Reference Rendering Engine ................ 12 4 Bengali 13 4.1 Introduction ......................... 13 4.2 Reference fonts ....................... 13 4.2.1 Lohit Bengali .................... 13 4.2.2 History ........................ 13 5 Devanagari 15 5.1 Introduction ......................... 15 5.2 Reference fonts ....................... 15 5.2.1 Lohit Devanagari .................. 15 5.2.2 History ........................ 16 6 Gujarati 17 6.1 Introduction ......................... 17 6.2 Reference fonts ....................... 17 6.2.1 Lohit Gujarati .................... 17 6.2.2 History ........................ 18 7 Kannada 19 8 Malayalam 21 8.1 Introduction ......................... 21 8.2 Orthography variation ................... 22 8.3 Reference fonts ....................... 23 8.3.1 Meera Font ..................... 23 8.3.2 Lohit Malayalam Font ............... 24 8.3.3 History ........................ 24 8.4 Technical details ....................... 25 8.4.1 Opentype Script Tags - mlym and mlm2 .... 25 8.4.2 Reordering ..................... 25 8.4.3 Vowel signs and combining marks ........ 25 8.4.4 Samvruthokaram .................. 28 8.4.5 Conjunct Signs for , , .............. 30 8.4.6 Reph ......................... 30 8.4.7 Dot Reph ....................... 31 8.4.8 Chillus ........................ 32 8.4.9 Stacking ....................... 33 8.4.10 Font metrics ..................... 34 8.4.11 Positioning rules .................. 34 8.4.12 ZWNJ and ZWJ Signs ............... 34 8.4.13 Prebase substitutions ................ 34 8.4.14 Akhand forms .................... 34 8.4.15 Below base forms .................. 34 8.4.16 Below base substitutions .............. 34 8.4.17 Half forms ...................... 34 8.4.18 Postbase forms ................... 34 8.4.19 Latin glyphs and punctuations .......... 34 8.4.20 Kerning ....................... 34 8.4.21 Shape references .................. 34 8.4.22 Left and right bearings ............... 34 8.4.23 Italic variant ..................... 34 8.4.24 Bold variant ..................... 34 8.5 Design ............................ 34 8.5.1 Number of glyphs ................. 34 8.5.2 Guidelines ...................... 35 9 Odiya 39 10 Panjabi 41 11 Tamil 43 12 Telugu 45 12.1 Introduction ......................... 45 13 Glossary 47 14 References 51 15 Appendices 53 1 Introduction "I can't go to a restaurant and order food because I keep looking at the fonts on the menu.-Donald Knuth" One of the integral building blocks for providing multilingual sup- port for digital content are fonts. In current times, OpenType fonts are the choice. With the increasing need for supporting languages beyond the Latin script, the TrueType font specification was extended to include elements for the more elaborate writing systems that exist. This effort was jointly undertaken in the 1990s by Microsoft and Adobe. The outcome of this effort was the OpenType Specification - a succes- sor to the TrueType font specification. Fonts for Indic languages had traditionally been created for the print- ing industry. The TrueType specification provided the baseline for the digital fonts that were largely used in desktop publishing. These fonts however suffered from inconsistencies arising from technical shortcomings like non-uniform character codes. These shortcomings made the fonts highly unreliable for digital content and their use across platforms. The problems with character codes were largely alleviated with the gradual standardization through modification and adoption of Unicode character codes. The OpenType Specification additionally extended the styling and behavior for the typography. The availability of the specification eased the process of creating Indic language fonts with consistent typographic behavior as per the script's requirement. However, disconnects between the styling and techni- 1 cal implementation hampered the font creation process. Several well- stylized fonts were upgraded to the new specification through com- plicated adjustments, which at times compromised on their aesthetic quality. On the other hand, the technical adoption of the specification details was a comparatively new know-how for the font designers. To strike a balance, an initiative was undertaken by the a group of font developers and designers to document the knowledge acquired from the hands own experience for the benefit of upcoming develop- ers and designers in this field. The outcome of the project will be an elaborate, illustrated guideline for font designers. A chapter will be dedicated to each of the Indic scripts - Bengali, Devanagari, Gujarati, Kannada, Malayalam, Odia, Punjabi, Tamil and Telugu. The guidelines will outline the technical representation of the canonical aspects of these complex scripts. This is especially important when designing for complex scripts where the shape or positioning of a character depends on its relation to other characters. This project is open for participation and contributors can commit directly on the project repository. 1.1 Objectives of document 1.2 Target Audience for this document 1.3 Scope • This document covers only languages and scripts recognized in India. • This document covers all complex OFF features required for Indian scripts. • This document is based on the current expertise of community members working in this area. • This document is from the typography perspective for each script and many not be linguistically correct. • This document does not cover design or calligraphy style aspects but covers only technical aspects. • This document is based on Unicode 6.2 and ISO/IEC 14496- 22:2009 (Second Edition) "Open Font Format" standard. • This document is not a tutorial on font design or development and does not teach typography. 1.4 How to use this document Elaborate, Illustrated font design guideline document for Indic fonts by font designers, developers, language experts. - designer freedom to adapt 1.5 Notes on Collaboration 2 General Concepts 2.1 Script At least one set of defined base elements or symbols, is a requirement for all writing systems. these symbols are individually termed as characters and collectively called a script. simply the set of the sym- bols required to represent a writing system is called a script. a script may in turn be used to represent more than one languages. Latin, Devanagari and Arabic are examples of scripts. English, French, Ger- man, and Latin are all languages written using the Latin script. 2.2 Complex script Complex script is a writing system in which the shape or positioning of a character depends on its relation to other characters. What makes it complex? * Bi-directional: text is written right-to-left (For exam- The Devanagari ddhrya-ligature, as displayed in the ple: Arabic, Hebrew) and left-to-right JanaSanskritSans font. (For example: Devanagari) * Context sensitive shaping and ligatures: Character may change shape depending upon position. 5 * Ordering: In Gujarati, Ki is where 'i' is place before 'K'. //FIXME What is a complex script? What makes it complex, some examples, screenshots 2-3 paragraph + images How it differs from simple scripts like Latin Character 2.3 Glyph A glyph is an element of writing. It can be a single character or a group of characters. Visually, if you see one or more characters form a single visual unit, it is called a glyph. In typography, it is "the specific shape, design, or representation of a character". 1 It is a particular graphical representation, in a particular typeface, of an element of written language, which could be a grapheme, or part of a grapheme, or sometimes several graphemes in combination. To illustrate this concept, a set glyphs inside a Latin font (Fig. 2.1) and a Malayalam font (Fig. 2.2) as seen in fontforge is given below. Figure 2.1: Glyphs inside Roboto font 1Ilene Strizver. "Confusing (and Frequently Misused) Type Terminology, Part 1". fonts.com. Monotype
Load more

Recommended publications
  • 75 Characters Maximum
    Kannada Script LGR Proposal Introduction, Current Analysis and Next Steps Dr. U.B. Pavanaja NBGP F2F Meeting, Colombo 14 December 2017 | 1 Agenda 1 2 3 Introduction to Repertoire Analysis Within Script Kannada Script Variants 4 5 6 Cross-Script WLE Rules Current Status and Variants Next Steps for Completion | 2 Introduction to Kannada Script Population – there are about 60 million speakers of Kannada language which uses Kannada script. Geographical area - Kannada is spoken predominantly by the people of Karnataka State of India. It is also spoken by significant linguistic minorities in the states of Andhra Pradesh, Telangana, Tamil Nadu, Maharashtra, Kerala, Goa and abroad Languages written in Kannada script – Kannada, Tulu, Kodava (Coorgi), Konkani, Havyaka, Sanketi, Beary (byaari), Arebaase, Koraga | 3 Classification of Characters Swaras (vowels) Letter ಅ ಆ ಇ ಈ ಉ ಊ ಋ ಎ ಏ ಐ ಒ ಓ ಔ Vowel sign/ N/Aಾ ಾ ಾ ಾ ಾ ಾ ಾ ಾ ಾ ಾ ಾ ಾ matra Yogavahas In Kannada, all consonants Anusvara ಅಂ (vyanjanas) when written as ಕ (ka), ಖ (kha), ಗ (ga), etc. actually have a built-in vowel sign (matra) Visarga ಅಃ of vowel ಅ (a) in them. | 4 Classification of Characters Vargeeya vyanjana (structured consonants) voiceless voiceless aspirate voiced voiced aspirate nasal Velars ಕ ಖ ಗ ಘ ಙ Palatals ಚ ಛ ಜ ಝ ಞ Retroflex ಟ ಠ ಡ ಢ ಣ Dentals ತ ಥ ದ ಧ ನ Labials ಪ ಫ ಬ ಭ ಮ Avargeeya vyanjana (unstructured consonants) ಯ ರ ಱ (obsolete) ಲ ವ ಶ ಷ ಸ ಹ ಳ ೞ (obsolete) | 5 Repertoire Included-1 Sr. Unicode Glyph Character Name Unicode Indic Ref Widespread No. Code General Syllabic use ? Point Category Category [Yes/No] 1 0C82 ಂ KANNADA SIGN ANUSVARA Mc Anusvara Yes 2 0C83 ಂ KANNADA SIGN VISARGA Mc Visarga Yes 3 0C85 ಅ KANNADA LETTER A Lo Vowel Yes 4 0C86 ಆ KANNADA LETTER AA Lo Vowel Yes 5 0C87 ಇ KANNADA LETTER I Lo Vowel Yes 6 0C88 ಈ KANNADA LETTER II Lo Vowel Yes 7 0C89 ಉ KANNADA LETTER U Lo Vowel Yes 8 0C8A ಊ KANNADA LETTER UU Lo Vowel Yes KANNADA LETTER VOCALIC 9 0C8B ಋ R Lo Vowel Yes 10 0C8E ಎ KANNADA LETTER E Lo Vowel Yes | 6 Repertoire Included-2 Sr.
    [Show full text]
  • Uniform Rendering of XML Encoded Mathematical Content with Opentype Fonts
    i \eutypon24-25" | 2011/1/21 | 8:58 | page 11 | #15 i i i Εὔτυπon, τεῦχος 24-25 — >Okt¸brioc/October 2010 11 Uniform Rendering of XML Encoded Mathematical Content with OpenType Fonts Apostolos Syropoulos 366, 28th October Str. GR-671 00 Xanthi Greece E-mail: asyropoulos at yahoo dot com The new OpenType MATH font table contains important information that can be used to correctly and uniformly render mathematical con- tent (e.g., mathematical formulae, equations, etc.). Until now, all sys- tems in order to render XML encoded mathematical content employed some standard algorithms together with some standard sets of TrueType and/or Type 1 fonts, which contained the necessary glyphs. Unfortu- nately, this approach does not produce uniform results because certain parameters (e.g., the thickness of the fraction line, the scale factor of superscripts/subscripts, etc.) are system-dependant, that is, their exact values will depend on the particular setup of a given system. Fortunately, the new OpenType MATH table can be used to remedy this situation. In particular, by extending renderers so as to be able to render mathemat- ical contents with user-specified fonts, the result will be uniform across systems and platforms. In other words, the proposed technology would allow mathematical content to be rendered the same way ordinary text is rendered across platforms and systems. 1 Introduction The OpenType font format is a new cross-platform font file format developed jointly by Adobe and Microsoft. OpenType fonts may contain glyphs with ei- ther cubic B´eziersplines (used in PostScript fonts) or with quadratic B´ezier splines (used in TrueType fonts).
    [Show full text]
  • The Unicode Cookbook for Linguists: Managing Writing Systems Using Orthography Profiles
    Zurich Open Repository and Archive University of Zurich Main Library Strickhofstrasse 39 CH-8057 Zurich www.zora.uzh.ch Year: 2017 The Unicode Cookbook for Linguists: Managing writing systems using orthography profiles Moran, Steven ; Cysouw, Michael DOI: https://doi.org/10.5281/zenodo.290662 Posted at the Zurich Open Repository and Archive, University of Zurich ZORA URL: https://doi.org/10.5167/uzh-135400 Monograph The following work is licensed under a Creative Commons: Attribution 4.0 International (CC BY 4.0) License. Originally published at: Moran, Steven; Cysouw, Michael (2017). The Unicode Cookbook for Linguists: Managing writing systems using orthography profiles. CERN Data Centre: Zenodo. DOI: https://doi.org/10.5281/zenodo.290662 The Unicode Cookbook for Linguists Managing writing systems using orthography profiles Steven Moran & Michael Cysouw Change dedication in localmetadata.tex Preface This text is meant as a practical guide for linguists, and programmers, whowork with data in multilingual computational environments. We introduce the basic concepts needed to understand how writing systems and character encodings function, and how they work together. The intersection of the Unicode Standard and the International Phonetic Al- phabet is often not met without frustration by users. Nevertheless, thetwo standards have provided language researchers with a consistent computational architecture needed to process, publish and analyze data from many different languages. We bring to light common, but not always transparent, pitfalls that researchers face when working with Unicode and IPA. Our research uses quantitative methods to compare languages and uncover and clarify their phylogenetic relations. However, the majority of lexical data available from the world’s languages is in author- or document-specific orthogra- phies.
    [Show full text]
  • Assessment of Options for Handling Full Unicode Character Encodings in MARC21 a Study for the Library of Congress
    1 Assessment of Options for Handling Full Unicode Character Encodings in MARC21 A Study for the Library of Congress Part 1: New Scripts Jack Cain Senior Consultant Trylus Computing, Toronto 1 Purpose This assessment intends to study the issues and make recommendations on the possible expansion of the character set repertoire for bibliographic records in MARC21 format. 1.1 “Encoding Scheme” vs. “Repertoire” An encoding scheme contains codes by which characters are represented in computer memory. These codes are organized according to a certain methodology called an encoding scheme. The list of all characters so encoded is referred to as the “repertoire” of characters in the given encoding schemes. For example, ASCII is one encoding scheme, perhaps the one best known to the average non-technical person in North America. “A”, “B”, & “C” are three characters in the repertoire of this encoding scheme. These three characters are assigned encodings 41, 42 & 43 in ASCII (expressed here in hexadecimal). 1.2 MARC8 "MARC8" is the term commonly used to refer both to the encoding scheme and its repertoire as used in MARC records up to 1998. The ‘8’ refers to the fact that, unlike Unicode which is a multi-byte per character code set, the MARC8 encoding scheme is principally made up of multiple one byte tables in which each character is encoded using a single 8 bit byte. (It also includes the EACC set which actually uses fixed length 3 bytes per character.) (For details on MARC8 and its specifications see: http://www.loc.gov/marc/.) MARC8 was introduced around 1968 and was initially limited to essentially Latin script only.
    [Show full text]
  • Handwriting Recognition in Indian Regional Scripts: a Survey of Offline Techniques
    1 Handwriting Recognition in Indian Regional Scripts: A Survey of Offline Techniques UMAPADA PAL, Indian Statistical Institute RAMACHANDRAN JAYADEVAN, Pune Institute of Computer Technology NABIN SHARMA, Indian Statistical Institute Offline handwriting recognition in Indian regional scripts is an interesting area of research as almost 460 million people in India use regional scripts. The nine major Indian regional scripts are Bangla (for Bengali and Assamese languages), Gujarati, Kannada, Malayalam, Oriya, Gurumukhi (for Punjabi lan- guage), Tamil, Telugu, and Nastaliq (for Urdu language). A state-of-the-art survey about the techniques available in the area of offline handwriting recognition (OHR) in Indian regional scripts will be of a great aid to the researchers in the subcontinent and hence a sincere attempt is made in this article to discuss the advancements reported in this regard during the last few decades. The survey is organized into different sections. A brief introduction is given initially about automatic recognition of handwriting and official re- gional scripts in India. The nine regional scripts are then categorized into four subgroups based on their similarity and evolution information. The first group contains Bangla, Oriya, Gujarati and Gurumukhi scripts. The second group contains Kannada and Telugu scripts and the third group contains Tamil and Malayalam scripts. The fourth group contains only Nastaliq script (Perso-Arabic script for Urdu), which is not an Indo-Aryan script. Various feature extraction and classification techniques associated with the offline handwriting recognition of the regional scripts are discussed in this survey. As it is important to identify the script before the recognition step, a section is dedicated to handwritten script identification techniques.
    [Show full text]
  • Optical Character Recognition - a Combined ANN/HMM Approach
    Optical Character Recognition - A Combined ANN/HMM Approach Dissertation submitted to the Department of Computer Science Technical University of Kaiserslautern for the fulfillment of the requirements for the doctoral degree Doctor of Engineering (Dr.-Ing.) by Sheikh Faisal Rashid Dean: Prof. Dr. Klaus Schneider Thesis supervisors: Prof. Dr. Thomas Breuel, TU Kaiserslautern Prof. Dr. Andreas Dengel, TU Kaiserslautern Chair of supervisory committee: Prof. Dr. Karsten Berns, TU Kaiserslautern Kaiserslautern, 11 July, 2014 D 386 Abstract Optical character recognition (OCR) of machine printed text is ubiquitously considered as a solved problem. However, error free OCR of degraded (broken and merged) and noisy text is still challenging for modern OCR systems. OCR of degraded text with high accuracy is very important due to many applications in business, industry and large scale document digitization projects. This thesis presents a new OCR method for degraded text recognition by introducing a combined ANN/HMM OCR approach. The approach provides significantly better performance in comparison with state-of-the-art HMM based OCR methods and existing open source OCR systems. In addition, the thesis introduces novel applications of ANNs and HMMs for document image preprocessing and recognition of low resolution text. Furthermore, the thesis provides psychophysical experiments to determine the effect of letter permutation in visual word recognition of Latin and Cursive script languages. HMMs and ANNs are widely employed pattern recognition paradigms and have been used in numerous pattern classification problems. This work presents a simple and novel method for combining the HMMs and ANNs in application to segmentation free OCR of degraded text. HMMs and ANNs are powerful pattern recognition strategies and their combination is interesting to improve current state-of-the-art research in OCR.
    [Show full text]
  • Opentype Postscript Fonts with Unusual Units-Per-Em Values
    Luigi Scarso VOORJAAR 2010 73 OpenType PostScript fonts with unusual units-per-em values Abstract Symbola is an example of OpenType font with TrueType OpenType fonts with Postscript outline are usually defined outlines which has been designed to match the style of in a dimensionless workspace of 1000×1000 units per em Computer Modern font. (upm). Adobe Reader exhibits a strange behaviour with pdf documents that embed an OpenType PostScript font with A brief note about bitmap fonts: among others, Adobe unusual upm: this paper describes a solution implemented has published a “Glyph Bitmap Distribution Format by LuaTEX that resolves this problem. (BDF)” [2] and with fontforge it’s easy to convert a bdf font into an opentype one without outlines. A fairly Keywords complete bdf font is http://unifoundry.com/unifont-5.1 LuaTeX, ConTeXt Mark IV, OpenType, FontMatrix. .20080820.bdf.gz: this Vle can be converted to an Open- type format unifontmedium.otf with fontforge and it Introduction can inspected with showttf, a C program from [3]. Here is an example of glyph U+26A5 MALE AND FEMALE Opentype is a font format that encompasses three kinds SIGN: of widely used fonts: 1. outline fonts with cubic Bézier curves, sometimes Glyph 9887 ( uni26A5) starts at 492 length=17 referred to CFF fonts or PostScript fonts; height=12 width=8 sbX=4 sbY=10 advance=16 2. outline fonts with quadratic Bézier curve, sometimes Bit aligned referred to TrueType fonts; .....*** 3. bitmap fonts. ......** .....*.* Nowadays in digital typography an outline font is almost ..***... the only choice and no longer there is a relevant diUer- .*...*.
    [Show full text]
  • CM-Super: Automatic Creation of Efficient Type 1 Fonts from Metafont
    CM-Super: Automatic creation of efficient Type 1 fonts from METAFONT fonts Vladimir Volovich Voronezh State University Moskovsky prosp. 109/1, kv. 75, Voronezh 304077 Russia [email protected] Abstract In this article I describe making the CM-Super fonts: Type 1 fonts converted from METAFONT sources of various Computer Modern font families. The fonts contain a large number of glyphs covering writing in dozens of languages (Latin-based, Cyrillic-based, etc.) and provide outline replacements for the original METAFONT fonts. The CM-Super fonts were produced by tracing the high resolution bitmaps generated by METAFONT with the help of TEXtrace, optimizing and hinting the fonts with FontLab, and applying cleanups and optimizations with Perl scripts. 1 The idea behind the CM-Super fonts There exist free Type 1 versions of the original CM The Computer Modern (CM) fonts are the default fonts, provided by Blue Sky Research, Elsevier Sci- ence, IBM Corporation, the Society for Industrial and most commonly used text fonts with TEX. Orig- inally, CM fonts contained only basic Latin letters, and Applied Mathematics (SIAM), Springer-Verlag, and thus covered only the English language. There Y&Y and the American Mathematical Society, but are however a number of Computer Modern look- until not long ago there were no free Type 1 versions alike METAFONT fonts developed which cover other of other “CM look-alike” fonts available, which lim- languages and scripts. Just to name a few: ited their usage in PDF and PostScript target docu- ment formats. The CM-Super fonts were developed • EC and TC fonts, developed by J¨orgKnappen, to cover this gap.
    [Show full text]
  • License Agreement
    TAGARNO MOVE, FHD PRESTIGE/TREND/UNO License Agreement Version 2021.08.19 Table of Contents Table of Contents License Agreement ................................................................................................................................................ 4 Open Source & 3rd-party Licenses, MOVE ............................................................................................................ 4 Open Source & 3rd-party Licenses, PRESTIGE/TREND/UNO ................................................................................. 4 atk ...................................................................................................................................................................... 5 base-files ............................................................................................................................................................ 5 base-passwd ...................................................................................................................................................... 5 BSP (Board Support Package) ............................................................................................................................ 5 busybox.............................................................................................................................................................. 5 bzip2 .................................................................................................................................................................
    [Show full text]
  • Updated Proposal to Encode Tulu-Tigalari Script in Unicode
    Updated proposal to encode Tulu-Tigalari script in Unicode Vaishnavi Murthy Kodipady Yerkadithaya [ [email protected] ] Vinodh Rajan [ [email protected] ] 04/03/2021 Document History & Background Documents : (This document replaces L2/17-378) L2/11-120R Preliminary proposal for encoding the Tulu script in the SMP of the UCS – Michael Everson L2/16-241 Preliminary proposal to encode Tigalari script – Vaishnavi Murthy K Y L2/16-342 Recommendations to UTC #149 November 2016 on Script Proposals – Deborah Anderson, Ken Whistler, Roozbeh Pournader, Andrew Glass and Laurentiu Iancu L2/17-182 Comments on encoding the Tigalari script – Srinidhi and Sridatta L2/18-175 Replies to Script Ad Hoc Recommendations (L2/16-342) and Comments (L2/17-182) on Tigalari proposal (L2/16-241) – Vaishnavi Murthy K Y L2/17-378 Preliminary proposal to encode Tigalari script – Vaishnavi Murthy K Y, Vinodh Rajan L2/17-411 Letter in support of preliminary proposal to encode Tigalari – Guru Prasad (Has withdrawn support. This letter needs to be disregarded.) L2/17-422 Letter to Vaishnavi Murthy in support of Tigalari encoding proposal – A. V. Nagasampige L2/18-039 Recommendations to UTC #154 January 2018 on Script Proposals – Deborah Anderson, Ken Whistler, Roozbeh Pournader, Lisa Moore, Liang Hai, and Richard Cook PROPOSAL TO ENCODE TIGALARI SCRIPT IN UNICODE 2 A note on recent updates : −−−Tigalari Script is renamed Tulu-Tigalari script. The reason for the same is discussed under section 1.1 (pp. 4-5) of this paper & elaborately in the supplementary paper Tulu Language and Tulu-Tigalari script (pp. 5-13). −−−This proposal attempts to harmonize the use of the Tulu-Tigalari script for Tulu, Sanskrit and Kannada languages for archival use.
    [Show full text]
  • Proposal for a Kannada Script Root Zone Label Generation Ruleset (LGR)
    Proposal for a Kannada Script Root Zone Label Generation Ruleset (LGR) Proposal for a Kannada Script Root Zone Label Generation Ruleset (LGR) LGR Version: 3.0 Date: 2019-03-06 Document version: 2.6 Authors: Neo-Brahmi Generation Panel [NBGP] 1. General Information/ Overview/ Abstract The purpose of this document is to give an overview of the proposed Kannada LGR in the XML format and the rationale behind the design decisions taken. It includes a discussion of relevant features of the script, the communities or languages using it, the process and methodology used and information on the contributors. The formal specification of the LGR can be found in the accompanying XML document: proposal-kannada-lgr-06mar19-en.xml Labels for testing can be found in the accompanying text document: kannada-test-labels-06mar19-en.txt 2. Script for which the LGR is Proposed ISO 15924 Code: Knda ISO 15924 N°: 345 ISO 15924 English Name: Kannada Latin transliteration of the native script name: Native name of the script: ಕನ#ಡ Maximal Starting Repertoire (MSR) version: MSR-4 Some languages using the script and their ISO 639-3 codes: Kannada (kan), Tulu (tcy), Beary, Konkani (kok), Havyaka, Kodava (kfa) 1 Proposal for a Kannada Script Root Zone Label Generation Ruleset (LGR) 3. Background on Script and Principal Languages Using It 3.1 Kannada language Kannada is one of the scheduled languages of India. It is spoken predominantly by the people of Karnataka State of India. It is one of the major languages among the Dravidian languages. Kannada is also spoken by significant linguistic minorities in the states of Andhra Pradesh, Telangana, Tamil Nadu, Maharashtra, Kerala, Goa and abroad.
    [Show full text]
  • PDF Copy of My Gsoc Proposal
    GSoC Proposal for Haiku Add Haiku Support for new Harfbuzz library ● Full name: Deepanshu Goyal ​ ● Timezone: +0530 ​ ● Email address: [email protected] ​ ● IRC username (freenode.net): digib0y ​ ● Trac username (dev.haiku-os.org): digib0y ​ ● Trac ticket(s) containing patches for Haiku/ Pull requests: ○ https://github.com/haiku/website/pull/26 ○ https://github.com/haiku/website/pull/41 ○ https://github.com/haikuports/haikuports/pull/1204 ○ https://github.com/HaikuArchives/ArtPaint/pull/54 We also had technical discussions over few issues in ArtPaint which you can checkout: https://github.com/HaikuArchives/ArtPaint/issues , I have also commented few lines of code in one the ​ issues which you might be interested in! Apart from these I have submitted a patch to Haiku however most of the work on the patch was already done by a previous contributor . https://dev.haiku-os.org/attachment/ticket/11518/0001-Implemented-BFont-Blocks-added-build-featur e-for-fon.patch ● GitHub (or other public) repository: https://github.com/digib0y/ ​ ● Will you treat Google Summer of Code as full time employment? ​ ​ Yes, I do understand that Google Summer of Code is a full time virtual internship and I have no other commitment to any other internship, job, and exams. ● How many hours per week will you work? I will work for 40-50 hours a week, with give work update on every alternate day to the assigned mentor.. ● List all obligations (and their dates) that may take time away from GSoC (a second job, vacations, classes, ...): One day per week will be an off day, most probably weekend only if the goals for the week has been completed.
    [Show full text]