This Document Serves As a Summary of the UC Berkeley Script Encoding Initiative's Recent Activities. Proposals Recently Submit

Total Page:16

File Type:pdf, Size:1020Kb

This Document Serves As a Summary of the UC Berkeley Script Encoding Initiative's Recent Activities. Proposals Recently Submit L2/11‐049 TO: Unicode Technical Committee FROM: Deborah Anderson, Project Leader, Script Encoding Initiative, UC Berkeley DATE: 3 February 2011 RE: Liaison Report from UC Berkeley (Script Encoding Initiative) This document serves as a summary of the UC Berkeley Script Encoding Initiative’s recent activities. Proposals recently submitted to the UTC that have involved SEI assistance include: Afaka (Everson) [preliminary] Elbasan (Everson and Elsie) Khojki (Pandey) Khudawadi (Pandey) Linear A (Everson and Younger) [revised] Nabataean (Everson) Woleai (Everson) [preliminary] Webdings/Wingdings Ongoing work continues on the following: Anatolian Hieroglyphs (Everson) Balti (Pandey) Dhives Akuru (Pandey) Gangga Malayu (Pandey) Gondi (Pandey) Hungarian Kpelle (Everson and Riley) Landa (Pandey) Loma (Everson) Mahajani (Pandey) Maithili (Pandey) Manichaean (Everson and Durkin‐Meisterernst) Mende (Everson) Modi (Pandey) Nepali script (Pandey) Old Albanian alphabets Pahawh Hmong (Everson) Pau Cin Hau Alphabet and Pau Cin Hau Logographs (Pandey) Rañjana (Everson) Siyaq (and related symbols) (Pandey) Soyombo (Pandey) Tani Lipi (Pandey) Tolong Siki (Pandey) Warang Citi (Everson) Xawtaa Dorboljin (Mongolian Horizontal Square script) (Pandey) Zou (Pandey) Proposals for unencoded Greek papyrological signs, as well as for various Byzantine Greek and Sumero‐Akkadian characters are being discussed. A proposal for the Palaeohispanic script is also underway. Deborah Anderson is encouraging additional participation from Egyptologists for future work on Ptolemaic signs. She has received funding from the National Endowment for the Humanities and support from Google to cover work through 2011. .
Recommended publications
  • Resource, Valuable Archive on Social and Economic History in Western India
    H-Asia Resource, Valuable archive on social and economic history in Western India Discussion published by Sumit Guha on Friday, September 2, 2016 Note on a valuable new resource: Haribhakti Collection Department of History, Faculty of Arts The Maharaja Sayajirao University of Baroda, Vadodara, Gujarat-INDIA Foundation: 1949 Eighteenth Century Baroda in Gujarat has not only evidenced the emergence of political potentates in Gaekwads but also the pecuniary mainstays amongst citizens. The foremost were the Haribhaktis’[i]; who are remembered for business success in areas such as money-lending/indigenous banking, coin- changing, traders in private capacity and banking; formation of Gaekwad’s State financial policy- which stimulated rural resources and commercial economy that benefitted in the making of urban Gujarat during the 18th and 19th centuries; and as philanthropists in individual capability. The business acumen and continuous support to Gaekwad fetched honours and titles like Nagar‘ Seth’ and ‘Raj Ratan' ‘Raj Mitra’ ‘Chiranjiva’&c to them by rulers and citizens. Their firm building in Vadodara dates back to last quarter of 19th century; and its location is near Mandvi darwaza in Ghadiali pol popularly known as Haribhakti ni Haveli “…made up of red and yellow wood and …stands as grandeur of 200 years past”. This family as state bankers were Kamvisadars, traders and Nagarseths of Gaekwad`s of Baroda. Their multifunctional role is apparent as we have more than 1000bahis/ account books and around 10,000 loose sheets of correspondence and statements;kundlis, astrological charts, receipts of transactions related to religious donations, grants for educational and health infrastructure, greetings, invitations, admiration and condolence letters etc.
    [Show full text]
  • Cuneiform and Hieroglyphs 11
    The Unicode® Standard Version 13.0 – Core Specification To learn about the latest version of the Unicode Standard, see http://www.unicode.org/versions/latest/. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trade- mark claim, the designations have been printed with initial capital letters or in all capitals. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc., in the United States and other countries. The authors and publisher have taken care in the preparation of this specification, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The Unicode Character Database and other files are provided as-is by Unicode, Inc. No claims are made as to fitness for any particular purpose. No warranties of any kind are expressed or implied. The recipient agrees to determine applicability of information provided. © 2020 Unicode, Inc. All rights reserved. This publication is protected by copyright, and permission must be obtained from the publisher prior to any prohibited reproduction. For information regarding permissions, inquire at http://www.unicode.org/reporting.html. For information about the Unicode terms of use, please see http://www.unicode.org/copyright.html. The Unicode Standard / the Unicode Consortium; edited by the Unicode Consortium. — Version 13.0. Includes index. ISBN 978-1-936213-26-9 (http://www.unicode.org/versions/Unicode13.0.0/) 1.
    [Show full text]
  • A Translation of the Malia Altar Stone
    MATEC Web of Conferences 125, 05018 (2017) DOI: 10.1051/ matecconf/201712505018 CSCC 2017 A Translation of the Malia Altar Stone Peter Z. Revesz1,a 1 Department of Computer Science, University of Nebraska-Lincoln, Lincoln, NE, 68588, USA Abstract. This paper presents a translation of the Malia Altar Stone inscription (CHIC 328), which is one of the longest known Cretan Hieroglyph inscriptions. The translation uses a synoptic transliteration to several scripts that are related to the Malia Altar Stone script. The synoptic transliteration strengthens the derived phonetic values and allows avoiding certain errors that would result from reliance on just a single transliteration. The synoptic transliteration is similar to a multiple alignment of related genomes in bioinformatics in order to derive the genetic sequence of a putative common ancestor of all the aligned genomes. 1 Introduction symbols. These attempts so far were not successful in deciphering the later two scripts. Cretan Hieroglyph is a writing system that existed in Using ideas and methods from bioinformatics, eastern Crete c. 2100 – 1700 BC [13, 14, 25]. The full Revesz [20] analyzed the evolutionary relationships decipherment of Cretan Hieroglyphs requires a consistent within the Cretan script family, which includes the translation of all known Cretan Hieroglyph texts not just following scripts: Cretan Hieroglyph, Linear A, Linear B the translation of some examples. In particular, many [6], Cypriot, Greek, Phoenician, South Arabic, Old authors have suggested translations for the Phaistos Disk, Hungarian [9, 10], which is also called rovásírás in the most famous and longest Cretan Hieroglyph Hungarian and also written sometimes as Rovas in inscription, but in general they were unable to show that English language publications, and Tifinagh.
    [Show full text]
  • Bryn Mawr Classical Review 2017.08.38
    Bryn Mawr Classical Review 2017.08.38 http://bmcr.brynmawr.edu/2017/2017-08-38 BMCR 2017.08.38 on the BMCR blog Bryn Mawr Classical Review 2017.08.38 Paola Cotticelli-Kurras, Alfredo Rizza (ed.), Variation within and among Writing Systems: Concepts and Methods in the Analysis of Ancient Written Documents. LautSchriftSprache / ScriptandSound. Wiesbaden: Dr. Ludwig Reichert Verlag, 2017. Pp. 384. ISBN 9783954901456. €98.00. Reviewed by Anna P. Judson, Gonville & Caius College, University of Cambridge ([email protected]) Table of Contents [Authors and titles are listed at the end of the review.] This book is the first of a new series, ‘LautSchriftSprache / ScriptandSound’, focusing on the field of graphemics (the study of writing systems), in particular historical graphemics. As the traditional view of writing as (merely) a way of representing speech has given way to a more nuanced understanding of writing as a different, rather than secondary, means of communication,1 graphemics has become an increasingly popular field; it is also necessarily an interdisciplinary field, since it incorporates the study not only of written texts’ linguistic features, but also broader aspects such as their visual features, material supports, and contexts of production and reading. A series dedicated to the study of graphemics across multiple academic disciplines is therefore a very welcome development. This first volume presents twenty-one papers from the third ‘LautSchriftSprache’ conference, held in Verona in 2013. In their introduction, the editors stress that the aim is to present studies of writing systems with as wide a scope as possible in terms of location, chronology, writing support, cultural context, and function.
    [Show full text]
  • Internationalization in Ruby 2.4
    Internationalization in Ruby 2.4 http://www.sw.it.aoyama.ac.jp/2016/pub/IUC40-Ruby2.4/ 40th Internationalization and Unicode Conference Santa Clara, California, U.S.A., November 3, 2016 Martin J. DÜRST [email protected] Aoyama Gakuin University © 2016 Martin J. Dürst, Aoyama Gakuin University Abstract Ruby is a purely object-oriented scripting language which is easy to learn for beginners and highly appreciated by experts for its productivity and depth. This presentation discusses the progress of adding internationalization functionality to Ruby for the version 2.4 release expected towards the end of 2016. One focus of the talk will be the currently ongoing implementation of locale-aware case conversion. Since Ruby 1.9, Ruby has a pervasive if somewhat unique framework for character encoding, allowing different applications to choose different internationalization models. In practice, Ruby is most often and most conveniently used with UTF-8. Support for internationalization facilities beyond character encoding has been available via various external libraries. As a result, applications may use conflicting and confusing ways to invoke internationalization functionality. To use case conversion as an example, up to version 2.3, Ruby comes with built-in methods for upcasing and downcasing strings, but these only work on ASCII. Our implementation extends this to the whole Unicode range for version 2.4, and efficiently reuses data already available for case-sensitive matching in regular expressions. We study the interface of internationalization functions/methods in a wide range of programming languages and Ruby libraries. Based on this study, we propose to extend the current built-in Ruby methods, e.g.
    [Show full text]
  • Final Proposal for Encoding the Warang Citi Script in the SMP of The
    JTC1/SC2/WG2 N4259 L2/12-118 2012-04-19 Universal Multiple-Octet Coded Character Set International Organization for Standardization Organisation Internationale de Normalisation Международная организация по стандартизации Doc Type: Working Group Document Title: Final proposal for encoding the Warang Citi script in the SMP of the UCS Source: UC Berkeley Script Encoding Initiative (Universal Scripts Project) Author: Michael Everson Status: Liaison Contribution Action: For consideration by JTC1/SC2/WG2 and UTC Replaces: N1958 (1999-01-29), N3411 (2008-04-08), N3668 (2009-08-05) Date: 2012-04-19 1. Introduction. The Warang Citi script is used to write the Ho language. Ho is a North Munda language, which family, together with the Mon-Khmer languages, makes up Austro-Asiatic. Warang Citi was devised by charismatic community leader Lako Bodra as part of a comprehensive cultural program, and was offered as an improvement over scripts used by Christian missionary linguists. Ho people live in the Indian states of Orissa and Jharkand. In Jharkand, they are found in Ranchi, Chaibasa and Jamshedpur, and in villages like Pardsa, Jaldhar, Tekasi, Tilupada, Baduri, Purtydigua, Roladih, Tupu Dana, Jetia, Dumbisai, Harira, Gitilpi, Karlajuri, Sarliburu, Narsana, Gidibas Kokcho, Lupungutu, Pandaveer, Jhinkapani, Kondwa. According to the SIL Ethnologue, there are 1,026,000 speakers of Ho. There are at present two publications in the script: a magazine Ho Sanagam (‘meeting’ from Hindi saṅgam), which comes out yearly and Kolhan Sakam, which comes out biweekly. Today, the Ho community can be characterized as still a primarily oral community, with an emergent literary tradition. Many Ho do not write their language in any form.
    [Show full text]
  • ONIX for Books Codelists Issue 40
    ONIX for Books Codelists Issue 40 23 January 2018 DOI: 10.4400/akjh All ONIX standards and documentation – including this document – are copyright materials, made available free of charge for general use. A full license agreement (DOI: 10.4400/nwgj) that governs their use is available on the EDItEUR website. All ONIX users should note that this is the fourth issue of the ONIX codelists that does not include support for codelists used only with ONIX version 2.1. Of course, ONIX 2.1 remains fully usable, using Issue 36 of the codelists or earlier. Issue 36 continues to be available via the archive section of the EDItEUR website (http://www.editeur.org/15/Archived-Previous-Releases). These codelists are also available within a multilingual online browser at https://ns.editeur.org/onix. Codelists are revised quarterly. Go to latest Issue Layout of codelists This document contains ONIX for Books codelists Issue 40, intended primarily for use with ONIX 3.0. The codelists are arranged in a single table for reference and printing. They may also be used as controlled vocabularies, independent of ONIX. This document does not differentiate explicitly between codelists for ONIX 3.0 and those that are used with earlier releases, but lists used only with earlier releases have been removed. For details of which code list to use with which data element in each version of ONIX, please consult the main Specification for the appropriate release. Occasionally, a handful of codes within a particular list are defined as either deprecated, or not valid for use in a particular version of ONIX or with a particular data element.
    [Show full text]
  • UTC L2/16‐037 FROM: Deborah Anderson, Ken Whistler
    TO: UTC L2/16‐037 FROM: Deborah Anderson, Ken Whistler, Rick McGowan, Roozbeh Pournader, Andrew Glass, and Laurentiu Iancu SUBJECT: Recommendations to UTC #146 January 2016 on Script Proposals DATE: 22 January 2016 The recommendations below are based on documents available to the members of this group at the time they met, January 19, 2016. EUROPE 1. Latin Document: L2/15‐327 Proposal to add Medievalist punctuation characters – Everson Discussion: We reviewed this document, which requested 21 characters. Many of the proposed characters require more detailed analysis, specifically providing examples that show contrasts in manuscripts, in old transcriptions, and how the marks are represented in text today. Specific comments raised in the discussion: • §1 Introduction. In the list of the proposed characters on pages 1 and 2, include dotted guide‐ lines, which show the placement of the characters in relation to the baseline, mid‐line, and top line, and solid lines separating individual table cells. • §2.2.3. Punctus versus. The text suggests that two glyphs for the same character are being proposed: PUNCTUS VERSUS MARK and LOW PUNCTUS VERSUS MARK. • §2.4 Distinctiones. “Note too that ჻ is the Georgian paragraph separator; no ‘generic’ punctuation mark for that has been encoded.” Is this a request to unify the Latin ჻ with U+10FB Georgian Paragraph Separator? If so, it can be added to ScriptExtensions.txt. • §4 Linebreaking. The assignment of SY as the LB property for DOTTED SOLIDUS should be reviewed by the UTC, since the SY class currently has only one member and it would be prudent to be cautious about adding another member to SY.
    [Show full text]
  • Name Hierarchy Methods Enums and Flags
    Pango::Gravity(3pm) User Contributed Perl Documentation Pango::Gravity(3pm) NAME Pango::Gravity − represents the orientation of glyphs in a segment of text HIERARCHY Glib::Enum +−−−−Pango::Gravity METHODS gravity = Pango::Gravity::get_for_matrix ($matrix) • $matrix (Pango::Matrix) gravity = Pango::Gravity::get_for_script ($script, $base_gravity, $hint) • $script (Pango::Script) • $base_gravity (Pango::Gravity) • $hint (Pango::GravityHint) boolean = Pango::Gravity::is_vertical ($gravity) • $gravity (Pango::Gravity) double = Pango::Gravity::to_rotation ($gravity) • $gravity (Pango::Gravity) ENUMS AND FLAGS enum Pango::Gravity • ’south’ / ’PANGO_GRAVITY_SOUTH’ • ’east’ / ’PANGO_GRAVITY_EAST’ • ’north’ / ’PANGO_GRAVITY_NORTH’ • ’west’ / ’PANGO_GRAVITY_WEST’ • ’auto’ / ’PANGO_GRAVITY_AUTO’ enum Pango::GravityHint • ’natural’ / ’PANGO_GRAVITY_HINT_NATURAL’ • ’strong’ / ’PANGO_GRAVITY_HINT_STRONG’ • ’line’ / ’PANGO_GRAVITY_HINT_LINE’ enum Pango::Script • ’invalid−code’ / ’PANGO_SCRIPT_INVALID_CODE’ • ’common’ / ’PANGO_SCRIPT_COMMON’ • ’inherited’ / ’PANGO_SCRIPT_INHERITED’ • ’arabic’ / ’PANGO_SCRIPT_ARABIC’ • ’armenian’ / ’PANGO_SCRIPT_ARMENIAN’ • ’bengali’ / ’PANGO_SCRIPT_BENGALI’ • ’bopomofo’ / ’PANGO_SCRIPT_BOPOMOFO’ • ’cherokee’ / ’PANGO_SCRIPT_CHEROKEE’ • ’coptic’ / ’PANGO_SCRIPT_COPTIC’ • ’cyrillic’ / ’PANGO_SCRIPT_CYRILLIC’ • ’deseret’ / ’PANGO_SCRIPT_DESERET’ • ’devanagari’ / ’PANGO_SCRIPT_DEVANAGARI’ • ’ethiopic’ / ’PANGO_SCRIPT_ETHIOPIC’ • ’georgian’ / ’PANGO_SCRIPT_GEORGIAN’ perl v5.28.0 2018-10-29 1 Pango::Gravity(3pm) User Contributed
    [Show full text]
  • Writing in Anatolia: the Origins of the Anatolian Hieroglyphs and the Introductions of the Cuneiform Script 1
    Altoriental. Forsch., Akademie Verlag, 39 (2012) 2, 287–315 Willemijn Waal Writing in Anatolia: The Origins of the Anatolian Hieroglyphs and the Introductions of the Cuneiform Script 1 Abstract This article argues that the Anatolian hieroglyphic script, which is generally thought to have been an invention of the second half of the second millennium BCE, has its origins already in the late third/early second millennium BCE. The argument that Anatolian hieroglyphs are much older than hitherto assumed is based on a wide array of evidence, such as (signs on) seals and textual data from both Ana- tolia and the Aegean. These data imply that Anatolian hieroglyphs, like virtually any other writing system, started out as a simple pictographic script used for basic economic and administrative records and over time developed into a full-fledged writing system, rather than being ‘invented’ in the Hittite Period. It is demonstrated that the enigmatic is.urtum-documents found in Old Assyrian texts refer to documents written in Ana- tolian hieroglyphs, similar to the gisˇ.hur/US. URTUM/gulzattar documents in the Hittite Period.These docu- ments, which have not been preserved because they were written on the perishable material wood, contained those types of texts that are conspicuously absent from the Old Assyrian and Hittite Periods. Since the Anatolians already had a script of their own, the cuneiform script never became firmly rooted within Anatolian society, and its usage was restricted to certain domains. This would explain why the cuneiform script was introduced (and subsequently abandoned) twice in Bronze Age Anatolia, whereas the Anatolian hieroglyphs continued to be used well into the first millennium BCE.
    [Show full text]
  • Unicode Character Properties
    Unicode character properties Document #: P1628R0 Date: 2019-06-17 Project: Programming Language C++ Audience: SG-16, LEWG Reply-to: Corentin Jabot <[email protected]> 1 Abstract We propose an API to query the properties of Unicode characters as specified by the Unicode Standard and several Unicode Technical Reports. 2 Motivation This API can be used as a foundation for various Unicode algorithms and Unicode facilities such as Unicode-aware regular expressions. Being able to query the properties of Unicode characters is important for any application hoping to correctly handle any textual content, including compilers and parsers, text editors, graphical applications, databases, messaging applications, etc. static_assert(uni::cp_script('C') == uni::script::latin); static_assert(uni::cp_block(U'[ ') == uni::block::misc_pictographs); static_assert(!uni::cp_is<uni::property::xid_start>('1')); static_assert(uni::cp_is<uni::property::xid_continue>('1')); static_assert(uni::cp_age(U'[ ') == uni::version::v10_0); static_assert(uni::cp_is<uni::property::alphabetic>(U'ß')); static_assert(uni::cp_category(U'∩') == uni::category::sm); static_assert(uni::cp_is<uni::category::lowercase_letter>('a')); static_assert(uni::cp_is<uni::category::letter>('a')); 3 Design Consideration 3.1 constexpr An important design decision of this proposal is that it is fully constexpr. Notably, the presented design allows an implementation to only link the Unicode tables that are actually used by a program. This can reduce considerably the size requirements of an Unicode-aware executable as most applications often depend on a small subset of the Unicode properties. While the complete 1 Unicode database has a substantial memory footprint, developers should not pay for the table they don’t use. It also ensures that developers can enforce a specific version of the Unicode Database at compile time and get a consistent and predictable run-time behavior.
    [Show full text]
  • The Anatolian Subgroup of Indo-European in the Light of the “Minor” Languages
    The Anatolian Subgroup of Indo-European in the Light of the “Minor” Languages H. Craig Melchert Carrboro NC Almost immediately following Bedřich Hrozný’s successful identification of Hittite as an Indo-European language, there was an early recognition that Hittite (Nesite) was not the only Indo-European language in Anatolia. Forrer (1919) already identified Luvian and Palaic as distinct languages among Hattusha texts, and Cuneiform Luvian was recognized as closely related to Hittite by Hrozný (1920: 35–39 & 55) and Forrer (1922: 215–223, correcting 1919: 1035). Forrer (1922: 241–247) tentatively added Palaic as also related. The affiliation of the language of the “Hittite hieroglyphs” was established by the early 1930s: see Forrer 1932: 59 and passim, Meriggi 1932: 10 and 42–57, and Hrozný 1933: 77–XX). Lycian and Lydian were shown to be Indo-European with special affinity with Hittite-Luvian-Palaic by Meriggi (1936a, 1936b), though this was not universally acknowledged. The concept of an “Anatolian” subgroup of Indo-European was thus existent before the Second World War, even if that label would not become standard for many decades. However, the full impact of the “minor” Anatolian languages on the history of Hittite and its relationship to the rest of Indo-European was long delayed. Handbooks on the historical grammar of Hittite published from the 1930s to the 1970s largely explicated Hittite directly from some model of Proto-Indo- European, treating the other languages very selectively or in appendices: see e.g. Sturtevant 1933, Sturtevant-Hahn 1951, Kronasser 1956 and 1966, and Oettinger 1979. Hittite still played an outsized role in the more comprehensive treatment of 2 Kammenhuber 1969.
    [Show full text]