Creation of Digital Libraries in Indian Languages Using Unicode
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
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. -
A New Research Resource for Optical Recognition of Embossed and Hand-Punched Hindi Devanagari Braille Characters: Bharati Braille Bank
I.J. Image, Graphics and Signal Processing, 2015, 6, 19-28 Published Online May 2015 in MECS (http://www.mecs-press.org/) DOI: 10.5815/ijigsp.2015.06.03 A New Research Resource for Optical Recognition of Embossed and Hand-Punched Hindi Devanagari Braille Characters: Bharati Braille Bank Shreekanth.T Research Scholar, JSS Research Foundation, Mysore, India. Email: [email protected] V.Udayashankara Professor, Department of IT, SJCE, Mysore, India. Email: [email protected] Abstract—To develop a Braille recognition system, it is required to have the stored images of Braille sheets. This I. INTRODUCTION paper describes a method and also the challenges of Braille is a language for the blind to read and write building the corpora for Hindi Devanagari Braille. A few through the sense of touch. Braille is formatted to a Braille databases and commercial software's are standard size by Frenchman Louis Braille in 1825.Braille obtainable for English and Arabic Braille languages, but is a system of raised dots arranged in cells. Any none for Indian Braille which is popularly known as Bharathi Braille. However, the size and scope of the combination of one to six dots may be raised within each English and Arabic Braille language databases are cell and the number and position of the raised dots within a cell convey to the reader the letter, word, number, or limited. Researchers frequently develop and self-evaluate symbol the cell exemplifies. There are 64 possible their algorithm based on the same private data set and combinations of raised dots within a single cell. -
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. -
The Fontspec Package Font Selection for XƎLATEX and Lualatex
The fontspec package Font selection for XƎLATEX and LuaLATEX Will Robertson and Khaled Hosny [email protected] 2013/05/12 v2.3b Contents 7.5 Different features for dif- ferent font sizes . 14 1 History 3 8 Font independent options 15 2 Introduction 3 8.1 Colour . 15 2.1 About this manual . 3 8.2 Scale . 16 2.2 Acknowledgements . 3 8.3 Interword space . 17 8.4 Post-punctuation space . 17 3 Package loading and options 4 8.5 The hyphenation character 18 3.1 Maths fonts adjustments . 4 8.6 Optical font sizes . 18 3.2 Configuration . 5 3.3 Warnings .......... 5 II OpenType 19 I General font selection 5 9 Introduction 19 9.1 How to select font features 19 4 Font selection 5 4.1 By font name . 5 10 Complete listing of OpenType 4.2 By file name . 6 font features 20 10.1 Ligatures . 20 5 Default font families 7 10.2 Letters . 20 6 New commands to select font 10.3 Numbers . 21 families 7 10.4 Contextuals . 22 6.1 More control over font 10.5 Vertical Position . 22 shape selection . 8 10.6 Fractions . 24 6.2 Math(s) fonts . 10 10.7 Stylistic Set variations . 25 6.3 Miscellaneous font select- 10.8 Character Variants . 25 ing details . 11 10.9 Alternates . 25 10.10 Style . 27 7 Selecting font features 11 10.11 Diacritics . 29 7.1 Default settings . 11 10.12 Kerning . 29 7.2 Changing the currently se- 10.13 Font transformations . 30 lected features . -
Proposal to Encode 0C34 TELUGU LETTER LLLA
Proposal to encode 0C34 TELUGU LETTER LLLA Shriramana Sharma, Suresh Kolichala, Nagarjuna Venna, Vinodh Rajan jamadagni, suresh.kolichala, vnagarjuna and vinodh.vinodh: *-at-gmail.com 2012Jan-17 §1. Character to be encoded 0C34 TELUGU LETTER LLLA §2. Background LLLA is the Unicode term for the native form in South Indian scripts of the voiced retroflex approximant. It is an ill-informed notion that it is limited or unique to one particular language or script. Such written forms are already known to exist in Tamil, Malayalam and Kannada and characters for the same are already encoded in Unicode. Evidence for the native presence of corresponding written forms of LLLA in other South Indian scripts, which may or may not be identical to characters already encoded, is forthcoming. This document provides evidence for Telugu LLLA identical to Kannada LLLA and requests its encoding. Similar evidence is to be expected for other South Indian scripts in future as well. §3. Attestation Currently the Telugu script does not use LLLA. However historic usage before the 10th century is undeniably attested. When the literary Telugu language was effectively standardized by the time of the Mahābhārata of Nannayya in the 11th century, this letter had disappeared from use. It is clear that this disappeared from the Telugu language long before it disappeared from Kannada. However, it was definitely used as part of the Telugu script and language and is considered a Telugu character by Telugu epigraphist scholars. Even though the pre-10th-century Telugu writing had much (more) in common with the Kannada writing of those days and is perhaps better analysed as a single proto-Telugu Kannada script, and hence the older written form would not be a part of the modern Telugu 1 script currently encoded in the block 0C00-0C7F, the modern written form used when transcribing the older form is most definitely a part of the modern Telugu script and hence should be encoded as part of it. -
2013 Cover Page M1
iSTEP 2013: Development and Assessment of Assistive Technology for a School for the Blind in India Madeleine Clute, Madelyn Gioffre, Poornima Kaniarasu, Aditya Kodkany, Vivek Nair, Shree Lakshmi Rao, Aveed Sheikh, Avia Weinstein, Ermine A. Teves, M. Beatrice Dias, M. Bernardine Dias CMU-RI-TR-16-30 The Robotics Institute Carnegie Mellon University Pittsburgh, Pennsylvania 15213 June 2016 Copyright © 2016 TechBridgeWorld at Carnegie Mellon University Development and Assessment of Assistive Technology for a School for the Blind in India Madeleine Clute, Madelyn Gioffre, Poornima Kaniarasu, Aditya Kodkany, Vivek Nair, Shree Lakshmi Rao, Aveed Sheikh, Avia Weinstein, Ermine A. Teves, M. Beatrice Dias, M. Bernardine Dias 1 Acknowledgements We extend sincere and heartfelt gratitude to our partner, the Mathru Educational Trust for the Blind for mentoring and advising us throughout the duration of the iSTEP research internship. The authors would especially like to thank Ms. Muktha for giving us the opportunity to work with the Mathru School for the Blind. To all the students, teaching and non-teaching staff for their cooperation in working with us and providing us with a wealth of information that has assisted us in completing this research. In addition, we would also like to acknowledge Carnegie Mellon University for providing the academic infrastructure necessary to make our work possible. Abstract Assistive devices for the visually impaired are often prohibitively expensive for potential users in developing communities. This report describes field research aimed at developing and assessing assistive technology that is economically accessible and relevant to this population of visually impaired individuals. The work discussed was completed at the Mathru School for the Blind as part of the iSTEP internship program, which is organized by CMU’s TechBridgeWorld research group. -
Karnataka State Branch #36, 100 Feet Road, Veerabhadra Nagar, B.S.K
NFB Regd. No. 4866 NATIONAL FEDERATION OF THE BLIND (Affiliated to World Blind Union) Karnataka State Branch #36, 100 Feet Road, Veerabhadra Nagar, B.S.K. 3rd Stage,Bangalore-85 Souvenir 10th Anniversary 4th January 2015 Email : [email protected] Phone No. : 26728845 Mobile : 9880537783, 8197900171 Fax : 26729479 1 NFB Published by : National Federation of the Blind © Copyright : National Federation of the Blind Chief Editor : Goutham Agarwal General Secretary NFB, Karnataka Editor : Prasanna Udipikar HoD of English VVN Degree College, Bangalore Printed at : Omkar Offset Printers Nm. 3/4, 1st Main Road, New Tharagupet, Bangalore - 560 002 Telefax : + 91 080 2670 8186 / 87, 2670 9026 E-mail : [email protected] Website : www.omkaroffset.com 2 NFB Contents l NFB - a movement for rights of PWD’s l Voice of the Blind - NFB (Karnataka) l A Decade of Success at Glance l Brief Life Sketch of Louis Braille l What Is Braille Script? l Government Assistance for the Visually Impaired l Employment Schemes l Social Security Benefits l Causes and Types of Blindness l Prevention of Blindness l Higher Education is no Longer a Challenge for Women With Disability l Schools For Visually Challenged Children l Schemes of National Scholarship for students with disability l Some legal and functional definitions of Disability l Population of Visual Disability in India o o o 3 NFB Contact Us Sl. Name & Address Email ID. No. 1. NFB Karnataka principal office [email protected] #36, 100 Feet Road, Veerabhadra Nagar, B.S.K. 3rd Stage, Bangalore-560085 Ph: 080-26728845 Fax: 080-26729479 Mob: 9916368800 2 National Federation of the Blind (India) [email protected] National office New Delhi Plot No.21, Sector –VI, M.B.Road, Pushpavihar, New Delhi-110 017 Ph: 91-11-29564198 3 National Federation of the Blind Braille [email protected] cum talking library & Assistive Devices of Aids & appliances supply service Mob: 8197900171 4 NFB for 3% reserving for the disabled. -
Proposal for the Encoding of Brāhmī in Plane 1 of ISO/IEC 10646
ISO/IEC JTC 1/SC 2/WG 2 PROPOSAL SUMMARY FORM TO ACCOMPANY SUBMISSIONS FOR ADDITIONS TO THE REPERTOIRE OF ISO/IEC 106461 Please fill all the sections A, B and C below. (Please read Principles and Procedures Document for guidelines and details before filling this form.) See http://www.dkuug.dk/JTC1/SC2/WG2/docs/summaryform.html for latest Form. See http://www.dkuug.dk/JTC1/SC2/WG2/docs/principles.html for latest Principles and Procedures document. See http://www.dkuug.dk/JTC1/SC2/WG2/docs/roadmaps.html for latest roadmaps. A. Administrative 1. Title: Proposal for the Encoding of Brāhmī in Plane 1 of ISO/IEC 10646. 2. Requesters' names: Stefan Baums, Andrew Glass. 3. Requester type (Member body/Liaison/Individual contribution): Individual contribution. 4. Submission date: DRAFT 27 July 2003. 5. Requester's reference (if applicable): N/A. 6. This is a complete proposal. B. Technical - General 1. This proposal is for a new script (set of characters). Proposed name of script: Brāhmī. 2. Number of characters in proposal: 120. 3. Proposed category (see section II, Character Categories): C. 4. Proposed Level of Implementation (1, 2 or 3) (see clause 14, ISO/IEC 10646-1: 2000): 3. Is a rationale provided for the choice? Yes. If Yes, reference: Combining marks are used. 5. Is a repertoire including character names provided? Yes. a. If Yes, are the names in accordance with the 'character naming guidelines in Annex L of ISO/IEC 10646-1: 2000? Yes. b. Are the character shapes attached in a legible form suitable for review? Yes. -
Root Based Stemmer for Telugu Script
International Journal of Engineering and Advanced Technology (IJEAT) ISSN: 2249 – 8958, Volume-8 Issue-6, August 2019 Root Based Stemmer for Telugu Script Narla Swapna Abstract: In this paper, a new stemmer has been proposed The process of stemming is, reducing the inflected or named as “Root based stemmer”. This stemmer is strictly based resultant words to their base words. In general, a stem is a on Dravidian script. Stemming can be used to pick up the written word form. The stem need not be the same to the effectiveness of information retrieval. In proposed Root based morphological root of the word, it is usually enough that stemming technique, each and every token is compared against correlated words map to the identical stem, even if this stem with all the words of a valid root words dictionary until a match is found. Then extract the matched string or substring from a token is not in itself a valid root. In Text classification, stemming and identified as valid root. The present work is aimed to build tries to cut off details like exact form of a word and produce dictionary based stemmer to extract valid root words for Indian word bases as features. In 1960s, the stemming algorithms languages especially for Telugu and compare the results with have been developed in the department of computer science. existing stemmers. While replicating a document, the choice of the suitable Keywords: stemming, Information retrieval, Telugu documentary unit is the first step. A documentary unit consists of set of words extracted from the sentences. The I. -
(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 -
World Braille Usage, Third Edition
World Braille Usage Third Edition Perkins International Council on English Braille National Library Service for the Blind and Physically Handicapped Library of Congress UNESCO Washington, D.C. 2013 Published by Perkins 175 North Beacon Street Watertown, MA, 02472, USA International Council on English Braille c/o CNIB 1929 Bayview Avenue Toronto, Ontario Canada M4G 3E8 and National Library Service for the Blind and Physically Handicapped, Library of Congress, Washington, D.C., USA Copyright © 1954, 1990 by UNESCO. Used by permission 2013. Printed in the United States by the National Library Service for the Blind and Physically Handicapped, Library of Congress, 2013 Library of Congress Cataloging-in-Publication Data World braille usage. — Third edition. page cm Includes index. ISBN 978-0-8444-9564-4 1. Braille. 2. Blind—Printing and writing systems. I. Perkins School for the Blind. II. International Council on English Braille. III. Library of Congress. National Library Service for the Blind and Physically Handicapped. HV1669.W67 2013 411--dc23 2013013833 Contents Foreword to the Third Edition .................................................................................................. viii Acknowledgements .................................................................................................................... x The International Phonetic Alphabet .......................................................................................... xi References ............................................................................................................................ -
Proposal on Handling Reph in Gurmukhi and Telugu Scripts 1
Proposal on Handling Reph in Gurmukhi and Telugu Scripts Nagarjuna Venna August 1, 2006 1 Introduction Chapter 9 of the Unicode standard [1] describes the representational model for encoding Indic scripts. Devanagari is described in Section 9.1; the principles of Indic scripts are covered in some detail in the introduction to Devanagari. The descriptions of the remaining Indic scripts were abbreviated highlighting any dierences from Devanagari where appropriate. Some of the problems in this description were claried by Public Review Issue #37 [2] which focused on consistent handling of Zero Width Joiner (ZWJ) in Indic scripts. That proposal put forth a set of rules for handling ZWJ and ZWNJ that are applicable across all Indic scripts. The formation of Reph is dened in Section 9.1, Rules for Rendering, R2 of [1]. Reph is dened as a nonspacing combining mark glyph form of U+0930 DEVANAGARI LETTER RA positioned above or attached to the upper part of a base glyph form. Basically, Reph is formed when a RA which has the inherent vowel killed by the virama begins a syllable. Not all scripts have Reph; if the script in question has a Reph form, the sequence <RA, VIRAMA, C> is rendered with Reph on C. Also, for Devanagari, the sequence <RA, VIRAMA, ZWJ, ...> is always rendered as eyelash-RA instead of Reph. Devanagari, Bengali, Gujarati, Oriya, and Kannada are listed in [1] and [2] as scripts that have a Reph form. Gurmukhi, Tamil, and Telugu are listed as scripts that do not have a Reph form. Malayalam is described as a script that has Reph in the traditional orthography but not in modern usage.