Unibook Document
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
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. . -
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. -
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. -
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 -
Chapter 6, Writing Systems and Punctuation
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. -
Deborah Anderson, Script Encoding Initiative, UC Berkeley Title: SEI Liaison Report Date: July 20, 2018
L2/18-239 To: UTC From: Deborah Anderson, Script Encoding Initiative, UC Berkeley Title: SEI Liaison Report Date: July 20, 2018 This document provides a summary of the UC Berkeley Script Encoding Initiative’s recent activities. Proposals/documents Proposals or documents currently submitted to the UTC (or WG2) that have involved SEI include: • Yezidi o Preliminary proposal for encoding the Yezidi script (L2/18-238) (Karaca et al.) • Reports and Feedback o Recommendations to UTC #156 (L2/18-241) (Anderson et al.) o Feedback on pushpika (L2/18-232) (Anderson) o Feedback on LATIN LETTER THORN WITH DIAGONAL STROKE (L2/18-242) o Brief Report from London meeting of Egyptologists, June 2018 (L2/18-237) (Anderson) o WG2 . Brief IR Report from WG2 Meeting #67 (L2/18-240) (Anderson) . Khitan Small Script Ad Hoc Report (London) (L2/18-213) (Anderson) . Emoji Ad Hoc Report (London, UK) (N5003) (Anderson) . Comments on WG2 #67 (June 2018) documents (L2/18-210 =N4977) (Anderson et al.) On the following proposals, Anderson acted as a supervisor (with Rick McGowan), with funding provided by the Unicode Adopt-a-Character program: o Proposal to encode the Chorasmian script in Unicode (L2/18-164r2) (Pandey) Script Proposals in Progress The following scripts have received SEI support in the past and are either in a preliminary stage, or are almost ready for approval, but require more information. The asterisk (*) before a script indicates that a 2018 proposal has been written and submitted to the UTC. • Afáka (Everson) [N4292=L2/12-228] • Bagam (Everson) [N4293=L2/12-229] • Balti ‘A’ and 'B' (Pandey) [N3842=L2/10-231, N4016=L2/11-103] • Bhujinmol (Pandey) [L2/14-283] • Book Pahlavi (Everson, Pournader, Durkin-Meisternernst) [N3294=L2/07-234] [later proposal by Pournader L2/13-141] (Future proposal planned by A. -
Kamloops Chinúk Wawa, Chinuk Pipa, and the Vitality of Pidgins
Kamloops Chinúk Wawa, Chinuk pipa, and the vitality of pidgins by David Douglas Robertson B.A., Columbia University, 1988 A Dissertation Submitted in Partial Fulfillment of the Requirements for the Degree of DOCTOR OF PHILOSOPHY in the Department of Linguistics © David Douglas Robertson, 2011 University of Victoria All rights reserved. This dissertation may not be reproduced in whole or in part, by photocopying or other means, without the permission of the author. ii Kamloops Chinúk Wawa, Chinuk pipa, and the vitality of pidgins by David Douglas Robertson B.A., Columbia University, 1988 Supervisory Committee Dr. Ewa Czaykowska-Higgins, Supervisor (Department of Linguistics, University of Victoria) Dr. Sarah Grey Thomason, Departmental Member (Department of Linguistics, University of Victoria; University of Michigan) Dr. Wendy Wickwire, Outside Member (Department of History, University of Victoria) iii Supervisory Committee Dr. Ewa Czaykowska-Higgins, Supervisor (Department of Linguistics, University of Victoria) Dr. Sarah Grey Thomason, Departmental Member (Department of Linguistics, University of Victoria; University of Michigan) Dr. Wendy Wickwire, Outside Member (Department of History, University of Victoria) Abstract This dissertation presents the first full grammatical description of unprompted (spontaneous) speech in pidgin Chinook Jargon [synonyms Chinúk Wawa, Chinook]. The data come from a dialect I term ‘Kamloops Chinúk Wawa’, used in southern interior British Columbia circa 1900. I also present the first historical study and structural analysis of the shorthand-based ‘Chinuk pipa ’ alphabet in which Kamloops Chinúk Wawa was written, primarily by Salish people. This study is made possible by the discovery of several hundred such texts, which I have transliterated and analyzed. The Basic Linguistic Theory-inspired (cf. -
Unifoundry.Com GNU Unifont Glyphs
Unifoundry.com GNU Unifont Glyphs Home GNU Unifont Archive Unicode Utilities Unicode Tutorial Hangul Fonts Unifont 9.0 Chart Fontforge Poll Downloads GNU Unifont is part of the GNU Project. This page contains the latest release of GNU Unifont, with glyphs for every printable code point in the Unicode 9.0 Basic Multilingual Plane (BMP). The BMP occupies the first 65,536 code points of the Unicode space, denoted as U+0000..U+FFFF. There is also growing coverage of the Supplemental Multilingual Plane (SMP), in the range U+010000..U+01FFFF, and of Michael Everson's ConScript Unicode Registry (CSUR). These font files are licensed under the GNU General Public License, either Version 2 or (at your option) a later version, with the exception that embedding the font in a document does not in itself constitute a violation of the GNU GPL. The full terms of the license are in LICENSE.txt. The standard font build — with and without Michael Everson's ConScript Unicode Registry (CSUR) Private Use Area (PUA) glyphs. Download in your favorite format: TrueType: The Standard Unifont TTF Download: unifont-9.0.01.ttf (12 Mbytes) Glyphs above the Unicode Basic Multilingual Plane: unifont_upper-9.0.01.ttf (1 Mbyte) Unicode Basic Multilingual Plane with CSUR PUA Glyphs: unifont_csur-9.0.01.ttf (12 Mbytes) Glyphs above the Unicode Basic Multilingual Plane with CSUR PUA Glyphs: unifont_upper_csur-9.0.01.ttf (1 Mbyte) PCF: unifont-9.0.01.pcf.gz (1 Mbyte) BDF: unifont-9.0.01.bdf.gz (1 Mbyte) Specialized versions — built by request: SBIT: Special version at the request -
Paths Into Script Formation in the Ancient Mediterranean Edited by Silvia Ferrara and Miguel Valério
STUDI MICENEI ED EGEO-ANATOLICI NUOVA SERIE SUPPLEMENTO 1 Paths into Script Formation in the Ancient Mediterranean edited by Silvia Ferrara and Miguel Valério Edizioni Quasar STUDI MICENEI ED EGEO-ANATOLICI NUOVA SERIE SUPPLEMENTO 1 è una pubblicazione del Consiglio Nazionale delle Ricerche, Roma ISBN 978-88-7140-898-9 Direttore / Editor-in-chief Anna D’Agata (CNR, Roma) Undertaken with the assistance of Institute for Aegean Prehistory (INSTAP), Philadelphia * Printed with the support of Gerda Henkel Stiftung, Düsseldorf * The editors are grateful to Judith Weingarten for revising the English of the original manuscript Immagine di copertina / Cover illustration Writing Travels the Sea, drawing by Miguel Valério based on signs from the Cretan Hieroglyphic, Byblos and Anatolian Hieroglyphic scripts Stampa e distribuzione / Printing and distribution Edizioni Quasar di Severino Tognon s.r.l. Via Ajaccio 41-43 – 00198 Roma tel. +39 0685358444, fax +39 0685833591 email: [email protected] www.edizioniquasar.it © 2018 CNR - Consiglio Nazionale delle Ricerche Autorizzazione Tribunale di Roma nr. 288/2014 del 31.12.2014 SOMMARIO Anna Lucia D’Agata Preface 7 Silvia Ferrara, Miguel Valério Introduction 9 Image-Bound Scripts at the Inception of Writing 1. Roeland P.-J.E. Decorte The Origins of Bronze Age Aegean Writing: Linear A, Cretan Hieroglyphic and a New Proposed Pathway of Script Formation 13 2. Mark Weeden Hieroglyphic Writing on Old Hittite Seals and Sealings? Towards a Material Basis for Further Research 51 Adaptations: Between Pictorialism and Schematism 3. Juan Pablo Vita, José Ángel Zamora The Byblos Script 75 4. Miguel Valério Cypro-Minoan: An Aegean-derived Syllabary on Cyprus (and Elsewhere) 103 5. -
WG2 Meeting Unicode 2011 N4005 Agenda
ISO/IEC JTC 1/SC 2/WG 2 N4005-A Date: 2011-06-03 mikeksar ! 6/3/11 9:41 AM Deleted: 2 Draft Agenda– Meeting # 58 Topic (Document No.) Proposed Outcome 1. Opening and roll call (N4001) Update WG2 Distribution List 2. Approval of the agenda (N4005-A) Approved agenda 3. Approval of minutes of meeting 57 (N3903) Approved Minutes 4. Review action items from previous meeting (N3903-AI) Updated Action Item List 5. JTC1 and ITTF matters: FYI 5.1. Results of voting on ISO/IEC 10646 2nd Edition (N3993) 5.2. Publication of ISO/IEC 10646 – 2nd Edition; includes AMD 8 6. SC2 matters: FYI 6.1. SC2 Program of Work FYI 6.2. Calling Notice and Draft Agenda for the 17th Plenary Meeting of ISO/IEC JTC1/SC 2 to be held in Helsinki, Finland, 2011-06-10 (N3994) 6.3. Draft WG2 report to SC2 (N4045) FYI 6.4. Submittals to ITTF – 2nd Edition (N3993) FYI 6.5. Ballot results Prepare Disposition of Comments 6.5.1. 3rd Edition (N4014.zip) – Text (N3967.zip) 6.5.2. PDAM1 – 3rd Edition (N4009.zip) – Text (N3968.zip) 6.6. JTC1 SC35: Comments on ISO/IEC JTC1/SC35 N1579 Proposal to incorporate symbols of ISO/IEC 9995-7:2009 and Amendment 1 into the UCS [=ISO/IEC JTC1/SC2/WG2 N3897] (N3996) (N4085) 6.7. Draft Technical Report Cultural and Linguistic Interoperability – Definitions and relationship between symbols, icons, animated icons, pictograms, characters and glyphs (N3927) 6.8. Proposal to encode missing Latin small capital and modifier letters (N4068, N4085) 6.9. -
Arbeitshilfe Schriftcodes Nach ISO 15924
Arbeitsstelle für Standardisierung (AfS) Projekt RDA 5. Februar 2014 Arbeitshilfe Schriftcodes nach ISO 15924 Blau unterlegte deutsche Bezeichnungen benötigen ggf. Überarbeitung - 5.2.2014 Code N° English Name Nom français Deutscher Name Date Afak 439 Afaka afaka Afaka-Schrift 2010-12-21 Aghb 239 Caucasian Albanian aghbanien Alwanische Schrift 2012-10-16 Arab 160 Arabic arabe Arabische Schrift 2004-05-01 Armi 124 Imperial Aramaic araméen impérial Reichsaramäische Schrift 2009-06-01 Armn 230 Armenian arménien Armenische Schrift 2004-05-01 Avst 134 Avestan avestique Avestische Schrift 2009-06-01 Bali 360 Balinese balinais Balinesische Schrift 2006-10-10 Bamu 435 Bamum bamoum Bamun-Schrift 2009-06-01 Bass 259 Bassa Vah bassa Bassa-Schrift 2010-03-26 Batk 365 Batak batik Batak-Schrift 2010-07-23 Beng 325 Bengali bengalî Bengalische Schrift 2004-05-01 Blis 550 Blissymbols symboles Bliss Bliss-Symbol 2004-05-01 Bopo 285 Bopomofo bopomofo Zhuyin Fuhao 2004-05-01 Brah 300 Brahmi brahma Brahmi-Schrift 2010-07-23 Arbeitshilfe AH-003 1 | 7 Code N° English Name Nom français Deutscher Name Date Brai 570 Braille braille Brailleschrift 2004-05-01 Bugi 367 Buginese bouguis Lontara-Schrift 2006-06-21 Buhd 372 Buhid bouhide Buid-Schrift 2004-05-01 Cakm 349 Chakma chakma Chakma-Schrift 2012-02-06 Unified Canadian Aboriginal Vereinheitlichte Silbenzeichen Cans 440 syllabaire autochtone canadien unifié 2004-05-29 Syllabics kanadischer Ureinwohner Cari 201 Carian carien Karische Schrift 2007-07-02 Cham 358 Cham cham (čam, tcham) Cham-Schrift 2009-11-11 Cher -
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