DOCSLIB.ORG

Assamese-Alphabets.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Assamese-Alphabets.Pdf pronounced as p by Hokkaido Ainu hence no word in tone to r. beginning with b is there in Rev. Dr. Batchelor's Ainu T, t : is pronounced as t in the English words, type or tin. In dictionary. But one word "betsu" meaning river or stream composition t often becomes d. in Ainu is often found in use of other writers or books. Q,q : Thus p and b is pronounced in Ainu not like p and b in V,v} are not used in writing Ainu English but somewhat midway. X,x C, c : is used mostly in combination with h as ch with S, s : is pronounced as in English pronounciation of ch as in church or chop. A sound similar Y,y : is pronounced as in English, yes. to ch, ts is reportedly used by Ainus of Tokapchi and W,w :is pronounced as the sound w in the English word, what. Sakhalin, eg tsup-sun, tsey-house. D,d : like t is never used in the beginning of a sentence, but t Now a brief introduction of the Assamese language. The often becomes d in composition. Assamese is the eastern-most language of the Indo-European F,f : is same as English f but softer and is used only with u language affiliates. It is spoken mostly in the Assam state of following it. the Indian Union. Assamese has fairly large number of literary G,g : has the sound of g in the word, good. No sentence works from ancient to modern times. It is one of the language commences with this letter but k often becomes g in recognised and listed in the 8th Schedule of Indian Constitution composition. Contrary to the view expressed by many scholars, Assamese is H,h : has the sound of h in the word house not a Sanskrit originated language. Rather it has evolved from J, j : as such does not occur in Ainu but chi and cha are its own origin in common with all other Indo-European sometimes pronounced like j. languages. Due to the process of Hinduisation and migration K,k : has the sound of k as in the English word keep. The k is from North India it was later influenced very much by import sometimes pronounced like the Greek alphabet x (chi) of Sanskrit words into its vocabulary. The Assamese language L, l : does not occur in Ainu tongue but in some place r sounds shows striking similarity in vocabulary with many of the Kaffir like l, the tone being nearer to r than to l. Ainus pronounce languages of Afghanistan and Pakistan, Persian and many of all words with l by r. Rev. Dr. Batchelor gives the example the European Indo-European languages. A feature absent in most of the word look which will be pronounced rook by the other Indo-Aryan languages of India. The Assamese is Ainu. surrounded all around by Tibeto-Burman sub-group of Sino- M,m : Tibetan language group and an Austric language block and these &} are pronounced as in English have imparted limited influence on its vocabulary and structure. N,n The Ainu affinity of the Assamese will add a new chapter in P, p : also has the same sound as in English though as mentioned the study of the Assamese language.The Assamese language earlier it is sometimes changed into b. has its own alphabets which is similar to the Bengali and Kaithi R, r : is pronounced some what between r and l, but being nearer alphabets of Maithili language of Bihar, West Bengal and Bihar 5 6 are two states of the Indian Union. The Assamese alphabets Application of vowels also exhibits some degree of similarity in forms to the Tibetan The alphabets given above for Assamese vowels are only used script. generally at the beginning of a word. When subjoined to a A brief description of the Assamese alphabets. consonant they take these forms Assamese vowels ’, â -- not expressed —, ang ’ are never used as the , â (â as in all) ’±, a -- ± –, ah } beginning of a word. ’±, a (a as in father) ˝◊√√, i --- ø Their forms do not ˝◊√√, i ÷, i -- œ change into other ÷, (i as in pin) i} ¤, a, e -- Œ symbols. ά◊, u ‹ ∆ (u as in put, oo as in poor, soot) , ai -- ÿ, u } ά◊, u -- ≈ Ÿ‘¬, ri (ri as in rishi, a sage) ÿ, u -- ” ¤, e, a (e as in met, men, a as in hat, cat) ›, o -- Œ ± ‹, ai (dipthong ai as in going) fi, ou -- Œ à ›, o (sound peculiar to Assamese not exactly the English 'o' as Ÿ‘¬, ri -- ‘ in whole, dole, etc.) fi, ou (dipthong ou as in bow but longer, o pronounced as in However sometimes vowels are used after consonant unchanged hoe, doe with u following it ) as for example —, âng (âng as in ong of long) ˜˝◊√√ mâi -- I –, ah ( as in ah) Ó¬˝◊√√ tâi -- you ŒÓ¬›“ teo -- he Assamese consonants Consonant vowel combined forms fl¡ ‡ · ‚ „√√ , kâ , khâ , gâ , ghâ , ngâ Some combination of consonant with vowels are written by ‰¬, sâ Â√, sâ Ê√, zâ Á¡, zhâ ¤û√√, nyâ different forms of letters. Ȭ, tâ ͬ, thâ ά, dâ Ϭ, dhâ Ì√√, nâ Ó¬, tâ Ô, thâ √, dâ Ò, dhâ Ú√√, nâ 1 râ + ≈ u=1n∏ ru ¬Û, pâ Ù¬, phâ ¬ı, bâ ˆ¬, bhâ ˜√√, mâ 1 râ + ” u=1+ ru ˚, jâ ˚˛, yâ 1, râ ˘, lâ ª√√, wâ ˝√√ hâ + ≈ u=U hu ˙, xâ ¯∏, xâ ¸, xâ ˝√√, hâ é¬√√, khyâ · gâ + ≈ u=& gu », tâ άˇ, râ Ϭˇ, rhâ ˙ xâ + ≈ u=q xu 7 8 are two states of the Indian Union. The Assamese alphabets Application of vowels also exhibits some degree of similarity in forms to the Tibetan The alphabets given above for Assamese vowels are only used script. generally at the beginning of a word. When subjoined to a A brief description of the Assamese alphabets. consonant they take these forms Assamese vowels ’, â -- not expressed —, ang ’ are never used as the , â (â as in all) ’±, a -- ± –, ah } beginning of a word. ’±, a (a as in father) ˝◊√√, i --- ø Their forms do not ˝◊√√, i ÷, i -- œ change into other ÷, (i as in pin) i} ¤, a, e -- Œ symbols. ά◊, u ‹ ∆ (u as in put, oo as in poor, soot) , ai -- ÿ, u } ά◊, u -- ≈ Ÿ‘¬, ri (ri as in rishi, a sage) ÿ, u -- ” ¤, e, a (e as in met, men, a as in hat, cat) ›, o -- Œ ± ‹, ai (dipthong ai as in going) fi, ou -- Œ à ›, o (sound peculiar to Assamese not exactly the English 'o' as Ÿ‘¬, ri -- ‘ in whole, dole, etc.) fi, ou (dipthong ou as in bow but longer, o pronounced as in However sometimes vowels are used after consonant unchanged hoe, doe with u following it ) as for example —, âng (âng as in ong of long) ˜˝◊√√ mâi -- I –, ah ( as in ah) Ó¬˝◊√√ tâi -- you ŒÓ¬›“ teo -- he Assamese consonants Consonant vowel combined forms fl¡ ‡ · ‚ „√√ , kâ , khâ , gâ , ghâ , ngâ Some combination of consonant with vowels are written by ‰¬, sâ Â√, sâ Ê√, zâ Á¡, zhâ ¤û√√, nyâ different forms of letters. Ȭ, tâ ͬ, thâ ά, dâ Ϭ, dhâ Ì√√, nâ Ó¬, tâ Ô, thâ √, dâ Ò, dhâ Ú√√, nâ 1 râ + ≈ u=1n∏ ru ¬Û, pâ Ù¬, phâ ¬ı, bâ ˆ¬, bhâ ˜√√, mâ 1 râ + ” u=1+ ru ˚, jâ ˚˛, yâ 1, râ ˘, lâ ª√√, wâ ˝√√ hâ + ≈ u=U hu ˙, xâ ¯∏, xâ ¸, xâ ˝√√, hâ é¬√√, khyâ · gâ + ≈ u=& gu », tâ άˇ, râ Ϭˇ, rhâ ˙ xâ + ≈ u=q xu 7 8 Compound Consonants eg. Two consonants are sometimes joined together to give a fl¡ kâ + ˚˛ yâ = fl¡… kyâ combined sound. Ê√ jâ + ˚˛ yâ = Ê√… jyâ Compound consonant where the two forms are preserved eg. 1 râ used after a consonant takes the form }} eg. fl¡ kâ + ˘ lâ = flv¡ klâ fl¡ kâ + 1 râ = Sê krâ „√√ ngâ + fl¡ kâ = Ç ngkâ Ó¬ tâ + 1 râ = S trâ „√√ ngâ + · gâ = e nggâ ˆ¬ bhâ + 1 râ = w bhrâ ˜√√ mâ + ¬Û pâ = •Û mpâ ˆ¬ bhâ + 1 râ + ≈ u=wn∏ bhru ˜√√ mâ + ˜ mâ = •ú mmâ ˙ xâ + 1 râ = | shrâ ¯∏√√ xâ + Ȭ tâ = ©Ü shtâ ˙ xâ + 1 râ + ≈ u=|n∏ shru √ 1 ^ Compound consonants where the form changes into a different dâ + râ = drâ alphabet. √ dâ + 1 râ + ≈ u=^n dru „√√ ngâ + fl¡ kâ = Ç ngkâ 1 râ used before a consonant denoted by a « sign over the cosonant „√√ ngâ + · gâ = e nggâ eg Ó¬ 1 fl¡ Ó¬fl«¡ ¤û nyâ + ‰¬ sâ = = ngchâ tâ + râ + kâ = târkâ Ì nâ + ά dâ = G ndâ A symbol “ called chandra-bindu (moon and dot) is used above Ú√√ nâ + Ô thâ = Lö nthâ a consonant to give a nasal intonation. In English transliteration, Ú“ ¸∏√√ xâ + Ô thâ = ¶ö sthâ a dot is used above the letter in this book eg = nâ Ú∏√√ nâ + Ò dhâ = g ndhâ Hasanta tâ » ¯∏√√ xâ + Ì nâ = ¯û shnâ Ȭ∏√√ Ȭ A This alphabet is never used at the beginning of a word, but tâ + tâ = ttâ always after an alphabet. Ó¬√ Ó¬ M√√ tâ + tâ = ttâ When a consonant is not to be expressed fully ie. the ’ â sound √ Ò X dâ + dhâ = ddhâ with it, it is marked with ƒ sign. fl¡ kâ + Ó¬ tâ = Mê√ ktâ eg Ê√√ jâ + ¤û nyâ = : gyâ ¬ı bâ + Ó¬ tâ + ˘ lâ = ¬ıÓ¬˘ bâtâlâ ·√ gâ + Ò dhâ = * gdhâ ¬ı tâ + Ó¬ râ + ˘ƒ la = ¬ıÓ¬˘ƒ bâtâl ˝√√ hâ + ˜ mâ = p¡ hmâ A ’ sign is used along with a letter to give 'o' sound to a word ˚˛ yâ joined after a consonant is written by the … sign, and it eg.
Load more

Recommended publications
  • On the Origin of the Indian Brahma Alphabet
    - ON THE <)|{I<; IN <>F TIIK INDIAN BRAHMA ALPHABET GEORG BtfHLKi; SECOND REVISED EDITION OF INDIAN STUDIES, NO III. TOGETHER WITH TWO APPENDICES ON THE OKU; IN OF THE KHAROSTHI ALPHABET AND OF THK SO-CALLED LETTER-NUMERALS OF THE BRAHMI. WITH TIIKKK PLATES. STRASSBUKi-. K A K 1. I. 1 1M I: \ I I; 1898. I'lintccl liy Adolf Ilcil/.haiisi'ii, Vicniiii. Preface to the Second Edition. .As the few separate copies of the Indian Studies No. Ill, struck off in 1895, were sold very soon and rather numerous requests for additional ones were addressed both to me and to the bookseller of the Imperial Academy, Messrs. Carl Gerold's Sohn, I asked the Academy for permission to issue a second edition, which Mr. Karl J. Trlibner had consented to publish. My petition was readily granted. In addition Messrs, von Holder, the publishers of the Wiener Zeitschrift fur die Kunde des Morgenlandes, kindly allowed me to reprint my article on the origin of the Kharosthi, which had appeared in vol. IX of that Journal and is now given in Appendix I. To these two sections I have added, in Appendix II, a brief review of the arguments for Dr. Burnell's hypothesis, which derives the so-called letter- numerals or numerical symbols of the Brahma alphabet from the ancient Egyptian numeral signs, together with a third com- parative table, in order to include in this volume all those points, which require fuller discussion, and in order to make it a serviceable companion to the palaeography of the Grund- riss.
    [Show full text]
  • 5892 Cisco Category: Standards Track August 2010 ISSN: 2070-1721
    Internet Engineering Task Force (IETF) P. Faltstrom, Ed. Request for Comments: 5892 Cisco Category: Standards Track August 2010 ISSN: 2070-1721 The Unicode Code Points and Internationalized Domain Names for Applications (IDNA) Abstract This document specifies rules for deciding whether a code point, considered in isolation or in context, is a candidate for inclusion in an Internationalized Domain Name (IDN). It is part of the specification of Internationalizing Domain Names in Applications 2008 (IDNA2008). Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5892. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
    [Show full text]
  • ISO/IEC International Standard 10646-1
    ISO/IEC 10646:2003/Amd.6:2009(E) Information technology — Universal Multiple-Octet Coded Character Set (UCS) — AMENDMENT 6: Bamum, Javanese, Lisu, Meetei Mayek, Samaritan, and other characters Page 2, Clause 3, Normative references Click on this highlighted text to access the reference file. Update the reference to the Unicode Bidirectional Algo- NOTE 5 – The content is also available as a separate view- rithm and the Unicode Normalization Forms as follows: able file in the same file directory as this document. The file is named: “CJKU_SR.txt”. Unicode Standard Annex, UAX#9, The Unicode Bidi- rectional Algorithm: Page 25, Clause 29, Named UCS Sequence http://www.unicode.org/reports/tr9/tr9-21.html. Identifiers Unicode Standard Annex, UAX#15, Unicode Normali- Insert the additional 290 sequence identifiers zation Forms: http://www.unicode.org/reports/tr15/tr15-31.html. <0B95, 0BCD> TAMIL CONSONANT K <0B99, 0BCD> TAMIL CONSONANT NG Page 14, Sub-clause 20.3, Format characters <0B9A, 0BCD> TAMIL CONSONANT C <0B9E, 0BCD> TAMIL CONSONANT NY Insert the following entry in the list of formats charac- <0B9F, 0BCD> TAMIL CONSONANT TT ters: <0BA3, 0BCD> TAMIL CONSONANT NN <0BA4, 0BCD> TAMIL CONSONANT T 110BD KAITHI NUMBER SIGN <0BA8, 0BCD> TAMIL CONSONANT N <0BAA, 0BCD> TAMIL CONSONANT P Page 20, Sub-clause 26.1, Hangul syllable <0BAE, 0BCD> TAMIL CONSONANT M composition method <0BAF, 0BCD> TAMIL CONSONANT Y <0BB0, 0BCD> TAMIL CONSONANT R <0BB2, 0BCD> TAMIL CONSONANT L Insert the following note after Note 2. <0BB5, 0BCD> TAMIL CONSONANT V NOTE 3 – Hangul text can be represented in several differ- <0BB4, 0BCD> TAMIL CONSONANT LLL ent ways in this standard.
    [Show full text]
  • (RSEP) Request October 16, 2017 Registry Operator INFIBEAM INCORPORATION LIMITED 9Th Floor
    Registry Services Evaluation Policy (RSEP) Request October 16, 2017 Registry Operator INFIBEAM INCORPORATION LIMITED 9th Floor, A-Wing Gopal Palace, NehruNagar Ahmedabad, Gujarat 380015 Request Details Case Number: 00874461 This service request should be used to submit a Registry Services Evaluation Policy (RSEP) request. An RSEP is required to add, modify or remove Registry Services for a TLD. More information about the process is available at https://www.icann.org/resources/pages/rsep-2014- 02-19-en Complete the information requested below. All answers marked with a red asterisk are required. Click the Save button to save your work and click the Submit button to submit to ICANN. PROPOSED SERVICE 1. Name of Proposed Service Removal of IDN Languages for .OOO 2. Technical description of Proposed Service. If additional information needs to be considered, attach one PDF file Infibeam Incorporation Limited (“infibeam”) the Registry Operator for the .OOO TLD, intends to change its Registry Service Provider for the .OOO TLD to CentralNic Limited. Accordingly, Infibeam seeks to remove the following IDN languages from Exhibit A of the .OOO New gTLD Registry Agreement: - Armenian script - Avestan script - Azerbaijani language - Balinese script - Bamum script - Batak script - Belarusian language - Bengali script - Bopomofo script - Brahmi script - Buginese script - Buhid script - Bulgarian language - Canadian Aboriginal script - Carian script - Cham script - Cherokee script - Coptic script - Croatian language - Cuneiform script - Devanagari script
    [Show full text]
  • A Case Study in Improving Neural Machine Translation Between Low-Resource Languages
    NMT word transduction mechanisms for LRL Learning cross-lingual phonological and orthagraphic adaptations: a case study in improving neural machine translation between low-resource languages Saurav Jha1, Akhilesh Sudhakar2, and Anil Kumar Singh2 1 MNNIT Allahabad, Prayagraj, India 2 IIT (BHU), Varanasi, India Abstract Out-of-vocabulary (OOV) words can pose serious challenges for machine translation (MT) tasks, and in particular, for low-resource Keywords: Neural language (LRL) pairs, i.e., language pairs for which few or no par- machine allel corpora exist. Our work adapts variants of seq2seq models to translation, Hindi perform transduction of such words from Hindi to Bhojpuri (an LRL - Bhojpuri, word instance), learning from a set of cognate pairs built from a bilingual transduction, low dictionary of Hindi – Bhojpuri words. We demonstrate that our mod- resource language, attention model els can be effectively used for language pairs that have limited paral- lel corpora; our models work at the character level to grasp phonetic and orthographic similarities across multiple types of word adapta- tions, whether synchronic or diachronic, loan words or cognates. We describe the training aspects of several character level NMT systems that we adapted to this task and characterize their typical errors. Our method improves BLEU score by 6.3 on the Hindi-to-Bhojpuri trans- lation task. Further, we show that such transductions can generalize well to other languages by applying it successfully to Hindi – Bangla cognate pairs. Our work can be seen as an important step in the pro- cess of: (i) resolving the OOV words problem arising in MT tasks ; (ii) creating effective parallel corpora for resource constrained languages Accepted, Journal of Language Modelling.
    [Show full text]
  • General Historical and Analytical / Writing Systems: Recent Script
    9 Writing systems Edited by Elena Bashir 9,1. Introduction By Elena Bashir The relations between spoken language and the visual symbols (graphemes) used to represent it are complex. Orthographies can be thought of as situated on a con- tinuum from “deep” — systems in which there is not a one-to-one correspondence between the sounds of the language and its graphemes — to “shallow” — systems in which the relationship between sounds and graphemes is regular and trans- parent (see Roberts & Joyce 2012 for a recent discussion). In orthographies for Indo-Aryan and Iranian languages based on the Arabic script and writing system, the retention of historical spellings for words of Arabic or Persian origin increases the orthographic depth of these systems. Decisions on how to write a language always carry historical, cultural, and political meaning. Debates about orthography usually focus on such issues rather than on linguistic analysis; this can be seen in Pakistan, for example, in discussions regarding orthography for Kalasha, Wakhi, or Balti, and in Afghanistan regarding Wakhi or Pashai. Questions of orthography are intertwined with language ideology, language planning activities, and goals like literacy or standardization. Woolard 1998, Brandt 2014, and Sebba 2007 are valuable treatments of such issues. In Section 9.2, Stefan Baums discusses the historical development and general characteristics of the (non Perso-Arabic) writing systems used for South Asian languages, and his Section 9.3 deals with recent research on alphasyllabic writing systems, script-related literacy and language-learning studies, representation of South Asian languages in Unicode, and recent debates about the Indus Valley inscriptions.
    [Show full text]
  • Proposal to Encode the Kaithi Script in ISO/IEC 10646
    Proposal to Encode the Kaithi Script in ISO/IEC 10646 Anshuman Pandey University of Michigan Ann Arbor, Michigan, U.S.A. [email protected] December 13, 2007 Contents Proposal Summary Form i 1 Introduction 1 1.1 Description ..................................... ...... 1 1.2 Justification for Encoding . ........... 1 1.3 Acknowledgments ................................. ...... 2 1.4 ProposalHistory ................................. ....... 2 2 Characters Proposed 3 2.1 CharactersNotProposed . ......... 4 2.2 Basis for Character Shapes . .......... 4 3 Technical Features 8 3.1 Name ............................................ 8 3.2 Classification ................................... ....... 8 3.3 Allocation...................................... ...... 8 3.4 EncodingModel................................... ...... 8 3.5 CharacterProperties. .......... 8 3.6 Collation ....................................... ..... 11 3.7 Typology of Characters . ......... 11 4 Background 13 4.1 Origins ......................................... 13 4.2 Name ............................................ 13 4.3 Definitions...................................... ...... 13 4.4 Languages Written in the Script . ........... 14 4.5 Standardization and Growth . .......... 16 4.6 Decline ......................................... 16 4.7 Usage ........................................... 17 5 Orthography 23 5.1 Distinguishing Features . ........... 23 5.2 Vowels.......................................... 23 5.3 Consonants ...................................... ..... 23 5.4 Nasalization...................................
    [Show full text]
  • Magahi and Magadh: Language and People
    G.J.I.S.S.,Vol.3(2):52-59 (March-April, 2014) ISSN: 2319-8834 MAGAHI AND MAGADH: LANGUAGE AND PEOPLE Lata Atreya1 , Smriti Singh2, & Rajesh Kumar3 1Department of Humanities and Social Sciences, Indian Institute of Technology Patna, Bihar, India 2Department of Humanities and Social Sciences, Indian Institute of Technology Patna, Bihar, India 3Department of Humanities and Social Sciences, Indian Institute of Technology Madras, Tamil Nadu, India Abstract Magahi is an Indo-Aryan language, spoken in Eastern part of India. It is genealogically related to Magadhi Apbhransha, once having the status of rajbhasha, during the reign of Emperor Ashoka. The paper outlines the Magahi language in historical context along with its present status. The paper is also a small endeavor to capture the history of Magadh. The paper discusses that once a history of Magadh constituted the history of India. The paper also attempts to discuss the people and culture of present Magadh. Keywords: Magahi, Magadhi Apbhransha, Emperor Ashoka. 1 Introduction The history of ancient India is predominated by the history of Magadh. Magadh was once an empire which expanded almost till present day Indian peninsula excluding Southern India. Presently the name ‘Magadh’ is confined to Magadh pramandal of Bihar state of India. The prominent language spoken in Magadh pramandal and its neighboring areas is Magahi. This paper talks about Magahi as a language, its history, geography, script and its classification. The paper is also a small endeavor towards the study of the history of ancient Magadh. The association of history of Magadh with the history and culture of ancient India is outlined.
    [Show full text]
  • The Fontspec Package Font Selection for X LE ATEX and Lualatex
    The fontspec package Font selection for X LE ATEX and LuaLATEX WILL ROBERTSON With contributions by Khaled Hosny, Philipp Gesang, Joseph Wright, and others. http://wspr.io/fontspec/ 2020/02/21 v2.7i Contents I Getting started 5 1 History 5 2 Introduction 5 2.1 Acknowledgements ............................... 5 3 Package loading and options 6 3.1 Font encodings .................................. 6 3.2 Maths fonts adjustments ............................ 6 3.3 Configuration .................................. 6 3.4 Warnings ..................................... 6 4 Interaction with LATEX 2ε and other packages 7 4.1 Commands for old-style and lining numbers ................. 7 4.2 Italic small caps ................................. 7 4.3 Emphasis and nested emphasis ......................... 7 4.4 Strong emphasis ................................. 7 II General font selection 8 1 Main commands 8 2 Font selection 9 2.1 By font name ................................... 9 2.2 By file name ................................... 10 2.3 By custom file name using a .fontspec file . 11 2.4 Querying whether a font ‘exists’ ........................ 12 1 3 Commands to select font families 13 4 Commands to select single font faces 13 4.1 More control over font shape selection ..................... 14 4.2 Specifically choosing the NFSS family ...................... 15 4.3 Choosing additional NFSS font faces ....................... 16 4.4 Math(s) fonts ................................... 17 5 Miscellaneous font selecting details 18 III Selecting font features 19 1 Default settings 19 2 Working with the currently selected features 20 2.1 Priority of feature selection ........................... 21 3 Different features for different font shapes 21 4 Selecting fonts from TrueType Collections (TTC files) 23 5 Different features for different font sizes 23 6 Font independent options 24 6.1 Colour .....................................
    [Show full text]
  • Proposal to Encode the Kaithi Script in ISO/IEC 10646
    ISO/IEC JTC1/SC2/WG2 N3389 L2/07-418 2007-12-13 Proposal to Encode the Kaithi Script in ISO/IEC 10646 Anshuman Pandey University of Michigan Ann Arbor, Michigan, U.S.A. [email protected] December 13, 2007 Contents Proposal Summary Form i 1 Introduction 1 1.1 Description ..................................... ...... 1 1.2 Justification for Encoding . ........... 2 1.3 Acknowledgments ................................. ...... 2 1.4 ProposalHistory ................................. ....... 2 2 Characters Proposed 3 2.1 CharactersNotProposed . ......... 4 2.2 Basis for Character Shapes . .......... 4 3 Technical Features 8 3.1 Name ............................................ 8 3.2 Classification ................................... ....... 8 3.3 Allocation...................................... ...... 8 3.4 EncodingModel................................... ...... 8 3.5 CharacterProperties. .......... 8 3.6 Collation ....................................... ..... 11 3.7 Typology of Characters . ......... 11 4 Background 13 4.1 Origins ......................................... 13 4.2 NameoftheScript ................................. ...... 13 4.3 Functional Definitions of ‘Kaithi’ . ............. 13 4.4 Languages Written in the Script . ........... 14 4.5 Standardization and Growth . .......... 15 4.6 Decline ......................................... 16 4.7 Usage ........................................... 17 5 Orthography 23 5.1 Distinguishing Features . ........... 23 5.2 Vowels.......................................... 23 5.3 Consonants .....................................
    [Show full text]
  • Overview and Rationale
    Integration Panel: Maximal Starting Repertoire — MSR-5 Overview and Rationale REVISION – APRIL 06, 2021 – PUBLIC COMMENT Table of Contents 1 Overview 3 2 Maximal Starting Repertoire (MSR-5) 3 2.1 Files 3 2.1.1 Overview 3 2.1.2 Normative Definition 4 2.1.3 HTML Presentation 4 2.1.4 Code Charts 4 2.2 Determining the Contents of the MSR 5 2.3 Process of Deciding the MSR 6 3 Scripts 8 3.1 Comprehensiveness and Staging 8 3.2 What Defines a Related Script? 9 3.3 Separable Scripts 9 3.4 Deferred Scripts 9 3.5 Historical and Obsolete Scripts 9 3.6 Selecting Scripts and Code Points for the MSR 10 3.7 Scripts Appropriate for Use in Identifiers 10 3.8 Modern Use Scripts 11 3.8.1 Common and Inherited 12 3.8.2 Scripts included in MSR-1 12 3.8.3 Scripts added in MSR-2 12 3.8.4 Scripts added in MSR-3 through MSR-5 13 3.8.5 Modern Scripts Ineligible for the Root Zone 13 3.9 Scripts for Possible Future MSRs 13 3.10 Scripts Identified in UAX#31 as Not Suitable for identifiers 14 4 Exclusions of Individual Code Points or Ranges 16 4.1 Historic and Phonetic Extensions to Modern Scripts 16 4.2 Code Points That Pose Special Risks 17 4.3 Code Points with Strong Justification to Exclude 17 4.4 Code Points That May or May Not be Excludable from the Root Zone LGR 17 4.5 Non-spacing Combining Marks 18 Integration Panel: Maximal Starting Repertoire — MSR-3 Overview and Rationale 5 Discussion of Particular Code Points 20 5.1 Digits and Hyphen 20 5.2 CONTEXT O Code Points 21 5.3 CONTEXT J Code Points 21 5.4 Code Points Restricted for Identifiers 21 5.5 Compatibility
    [Show full text]
  • On the History of Origin of Kaithi and Many Other Indian Scripts
    ON THE HISTORY OF ORIGIN OF KAITHI AND MANY OTHER INDIAN SCRIPTS BY ANAND M. SHARAN PROFESSOR MECHANICAL ENGINEERING MEMORIAL UNIVERSITY OF NEWFOUNDLAND, ST JOHN’S, NEWFOUNDLAND, CANADA A1B 3X5 E-MAIL: asharan@ mun.ca AND BHAIRAB L. DAS PROJECT OFFICER BIHAR LEGISLATIVE COUNCIL PATNA, BIHAR, INDIA 800015 E-MAIL: [email protected] AUG. 7, 2014 1 ABSTRACT This work deals with history of Kaithi and other important Indian scripts. It shows the reason why many scripts came about between 6th to 9th century and then evolution of these scripts into Devanagari. The work shows that for ordinary people’s interest, Kaithi, Modhi, Mahajani etc were in use rather than Devanagari even in the Hindi speaking states of India. Devanagari was used for Sanskrit and other formal and scriptural purposes since many of these Kutil derived scripts could not be used to express precisely the Sanskrit literature which the old brahmi was used for. 2 1. INTRODUCTION Indian Civilization is old as can be seen from the remains of the Indus- Harappa civilizations which go back to 3500 BC. One finds various seals and other artifacts from this civilization which extended over vast territories greater than any other ones in ancient world. The cities were well developed and also, had drainage system not found anywhere else in those years. This civilization had a script called the Indus Script whose decipherment has remained elusive even though many have claimed to have deciphered it but so far – no test has been established to check the decipherments. One of the claimants is Kalyanaraman; he uses the rebus method to decode [1].
    [Show full text]