DOCSLIB.ORG

WG2 Meeting Unicode 2011 N4005 Agenda

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
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. 7. Liaison reports FYI 7.1. Unicode Consortium 7.2. IETF 7.3. SC22 7.4. W3C 7.5. SEI (N4086) 8. WG2 matters 2011-05-17 Draft Agenda – Meeting 58 Page 1 of 5 JTC 1/SC 2/WG 2/N4005-A 8.1. Potential ad hoc meetings: Hungarian Runic/Rovas, Duployan, Webdings and Wingdings 8.2. Proposed additions to Principles & Procedures (N4049) 8.3. Updated Principles & Procedures (N3902, N4052) 8.4. Roadmap snapshot (N4056) 8.5. Recommendation to explore agile working methods between WG2 meetings (N4061) 8.6. Concerns on revision processes of Unicode Technical Reports (N4092) 8.7. Notes on new directives regarding amendments (N4091) 8.8. Ballots disposition of comments 8.8.1. Draft disposition of comments – 3rd edition (N4023) 8.8.2. Draft disposition of comments – PDAM 1 – 3rd edition (N4024) 9. IRG status and reports 9.1. IRG Meeting 35 Resolutions (N4020) 9.2. Summary of IRG activities (N4021) 9.3. Comments on N4021 – IVD Registration (N4075, N4084) 10. Script contributions related to ballots 10.1. 3rd Edition 10.1.1. Notes on the naming of some characters proposed in the FCD of ISO/IEC 10646:2012 (N3984) 10.1.2. R. O. Korea's Response to Japan's question RE: Idu chars (N4008) 10.1.3. Comment on ISO/IEC 10646:2012 3rd edition – Request for U-Source (N4058) 10.2. PDAM 1 10.2.1. Proposal to Rename the Block Name for Sindhi (N3957, N3979) 10.2.2. Coptic Numbers 10.2.2.1. Request to Rename ‘Coptic Numbers’ to ‘Coptic Epact Numerals’ (N3958) 10.2.2.2. Final Proposal to Encode Coptic Epact Numbers (N3990) 10.2.3. Comments on Bassa Vah Comma in Amendment 1(N3991) 10.2.4. Discussion of Mro Dandas (N4011) 10.2.5. Windings/webdings addition proposal (N4022, N4085) 11. Script contributions not related to ballots 11.1. Carried forward from previous meeting: 11.1.1. Tolong Siki script (N3811) 11.1.2. Landa script family (N3768) 11.1.3. Pahawh Hmong script (N3667) 11.1.4. Old Yi script (N3288) 11.1.5. Nushu script (N3598, N3705, N3719) 11.1.6. Proposal for encoding the Mende script (N3863) 11.1.7. Towards an Encoding for the Tirhuta Script (N3765 (Maithili), N4035) 11.1.8. Preliminary proposal for encoding the Kpelle script (N3762) 11.1.9. Preliminary Proposal to encode the Gangga MalAyu Script (N3959) 11.1.10. Preliminary proposal for Ahom (N3928) 11.1.11. Introducing the Zou Script (N3864) 11.1.12. Preliminary Code Chart and Names List for the Pyu Script (N3874) 2011-05-17 Draft Agenda – Meeting 58 Page 2 of 5 JTC 1/SC 2/WG 2/N4005-A 11.1.13. A preliminary proposal for the Dhives Akuru script (N3848) 11.1.14. Balti Scripts 11.1.14.1. Preliminary proposals for the Balti scripts (N3842) 11.1.14.2. Preliminary Proposal to Encode the Balti ‘B’ Script (N4016) 11.1.15. Preliminary proposals for the Gondi scripts (N3841) 11.1.16. Obsolete Simplified Chinese characters (N3695, N3721) 11.1.17. Metrical Symbols 11.1.17.1. Proposal to add Metrical Symbols (N3913) 11.1.17.2. Revised proposal to encode Metrical Symbols and related characters (N4073/N4074) 11.1.17.3. Comments on N3913 Proposal to encode Metrical Symbols and related characters (N4047) 11.1.17.4. 11.1.18. Hentaigana characters (N3698, N4091) 11.1.19. Lithuanian dialectology (N3914, N4062, N4057, N4070, N4085) 11.1.20. Documenting a fallback glyph for Tifinagh Consonant Joiner (N4069) 11.1.21. Proposal to include Duployan Shorthands and Chinook script and Shorthand Format Controls in UCS (N3895, N3908, N3922, N3932, N3940, N4088) 11.2. Proposed additions to ISO/IEC 10646 (N3995) 11.2.1. Final Proposal to Encode the Khojki Script (N3883,N3978) 11.2.2. Proposal to encode the Typikon Symbols (N3971) 11.2.3. Proposal to Encode the Mark's Chapter Symbol (N3998) 11.2.4. Request to encode South Indian CANDRABINDU-s (N3964) 11.2.5. Proposal to add ARABIC MARK SIDEWAYS NOON GHUNNA (N3989) 11.2.6. Proposal to add ARABIC LETTER BEH WITH HAMZA ABOVE (N3988) 11.2.7. Proposal to add two kana characters (N3987, N4087) 11.2.8. Proposal to encode GREEK CAPITAL LETTER YOT (N3997) 11.2.9. Proposal for encoding the Elbasan script (N3985) 11.2.10. Proposal for encoding the Nabataean script (N3969) 11.2.11. Revised proposal for encoding the Linear A script (N3973) 11.2.12. Proposal to Encode the Letters GYAN and TRA for Limbu (N3975) 11.2.13. Proposal to Encode the Marwari Letter DDA for Devanagari (N3970) 11.2.14. Proposal to encode some outstanding early Cyrillic characters (N3974) 11.3. Proposals for Hungarian Runic/Szekely-Hungarian Rovas 11.3.1. Revised proposal for encoding the Szekely-Hungarian Rovas script (N4007, N4085) 11.3.2. Comments on encoding the Rovas Scripts (N4076) 11.3.3. Issues of encoding the Rovas scripts (N4080) 11.3.4. Proposal for encoding the Hungarian script (N3697, N4085) 11.3.5. Hungarian Native Writing Proposal (N3566) 11.3.6. Proposal for encoding generic punctuation used with the Hungarian Runic script (N3664) 11.3.7. Mapping between Hungarian Runic proposals in N3697 and N4007 (N4042) 11.3.8. Comparison of Hungarian Runic and Szekely-Hungarian Rovas proposals (N4064, N4085) 11.3.9. Notes on the Szekely-Hungarian Rovas script (N4055) 11.4. B. Other Rovas scripts 11.4.1. Encoding the Khazarian Rovas script (N3999) 11.4.2. Proposal for encoding the Carpathian Basin Rovas script (N4006) 2011-05-17 Draft Agenda – Meeting 58 Page 3 of 5 JTC 1/SC 2/WG 2/N4005-A 11.5. Soyombo script 11.5.1. Revised Preliminary Proposal to Encode the Soyombo Script (N4026) 11.5.2. Determining the Encoding Model for Soyombo Vowels (N3986) 11.6. Proposal to Encode the Pau Cin Hau Alphabet – replaces N3781, N3784 and N3865 and N3960 (N4017, N4057) 11.7. Introducing the Logographic Script of Pau Cin Hau (N3961) 11.8. Proposal to Encode the Jenticha Script (N3962 Preliminary, N4028 Latest) 11.9. Preliminary Proposal to Encode the Tikamuli Script (N3963) 11.10. Naxi Dongba Pictograph 11.10.1. Revised Proposal for Encoding Naxi Dongba Pictograph (preliminary N3935, Revised N4043) 11.10.2. USNB Comments on N3935 and N4043 “Revised Proposal for Encoding Naxi Dongba Pictograph” (N3965, N4060) 11.11. Preliminary proposal for encoding the Afaka script (N3972) 11.12. Preliminary proposal for encoding the Woleai script (N3977) 11.13. Proposal to encode a Subscript Solidus (N3980) 11.14. English Phonotypic Alphabet (EPA) 11.14.1. Revised Proposal to encode characters for the English Phonotypic Alphabet (EPA) (N3981) 11.14.2. Second Revised Proposal to encode characters for the English Phonotypic Alphabet (EPA) (N4079) 11.14.3. Comments on Revised Proposal (N3981) to encode characters for the English Phonotypic Alphabet (N4059) 11.14.4. 11.15. Proposal to encode three additional emoticons (N3982) 11.16. Revised Proposal to encode a punctuation mark “Double Hyphen” (N3983) 11.17. Comments on N3910 “Proposal for Encoding Chinese Chess Symbols” 11.17.1. ROK's - N3992 11.17.2. USNB - N3966 11.18. Proposal to add heraldic hatching characters (N4011) 11.19. Proposal to encode additional playing card characters (N4012) 11.20. Proposal to encode additional Runic characters (N4013, N4085) 11.21. Preliminary proposal for encoding the Tulu script (N4025) 11.22. Preliminary Proposal to Encode the Multani Script (N4027) 11.23. Second revised proposal for encoding the Manichaean (N4029, N4057) 11.24. Proposal for the addition of six Latin characters (N4030, N4085) 11.25. Proposal to encode the Marchen script (N4032) 11.26. Introducing the Magar AkkhA Script (N4036) 11.27. Introducing the Kirat Rai Script (N4037) 11.28. Preliminary Proposal to Encode the Prachalit Nepal Script (N4038) 11.29. Preliminary proposal for encoding the Caucasian Albanian (N4039) 11.30. Proposal for encoding the Psalter Pahlavi script (N4040) 11.31. Preliminary Proposal to Encode the Mongolian Square Script (N4041) 11.32. Proposal to Encode Special Scripts and Characters for Uighur language (N4067) 2011-05-17 Draft Agenda – Meeting 58 Page 4 of 5 JTC 1/SC 2/WG 2/N4005-A 11.33.
Load more

Recommended publications
  • An Animated Avatar to Interpret Signwriting Transcription
    An Animated Avatar to Interpret SignWriting Transcription Yosra Bouzid Mohamed Jemni Research Laboratory of Technologies of Information and Research Laboratory of Technologies of Information and Communication & Electrical Engineering (LaTICE) Communication & Electrical Engineering (LaTICE) ESSTT, University of Tunis ESSTT, University of Tunis [email protected] [email protected] Abstract—People with hearing disability often face multiple To address this issue, different methods and technologies barriers when attempting to interact with hearing society. geared towards deaf communication have been suggested over The lower proficiency in reading, writing and understanding the the last decades. For instance, the use of sign language spoken language may be one of the most important reasons. interpreters is one of the most common ways to ensure a Certainly, if there were a commonly accepted notation system for successful communication between deaf and hearing persons in sign languages, signed information could be provided in written direct interaction. But according to a WFD survey in 2009, 13 form, but such a system does not exist yet. SignWriting seems at countries out of 93 do not have any sign language interpreters, present the best solution to the problem of SL representation as it and in many of those countries where there are interpreters, was intended as a practical writing system for everyday there are serious problems in finding qualified candidates. communication, but requires mastery of a set of conventions The digital technologies, particularly video and avatar-based different from those of the other transcriptions systems to become a proficient reader or writer. To provide additional systems, contribute, in turn, in bridging the communication support for deaf signers to learn and use such notation, we gap.
    [Show full text]
  • 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. .
    [Show full text]
  • A Human-Editable Sign Language Representation for Software Editing—And a Writing System?
    A human-editable Sign Language representation for software editing—and a writing system? Michael Filhol [email protected] LIMSI, CNRS, Université Paris Saclay Orsay, France Abstract To equip SL with software properly, we need an input system to rep- resent and manipulate signed contents in the same way that every day software allows to process written text. Refuting the claim that video is good enough a medium to serve the purpose, we propose to build a repres- entation that is: editable, queryable, synthesisable and user-friendly—we define those terms upfront. The issue being functionally and conceptually linked to that of writing, we study existing writing systems, namely those in use for vocal languages, those designed and proposed for SLs, and more spontaneous ways in which SL users put their language in writing. Ob- serving each paradigm in turn, we move on to propose a new approach to satisfy our goals of integration in software. We finally open the prospect of our proposition being used outside of this restricted scope, as a writing system in itself, and compare its properties to the other writing systems presented. 1 Motivation and goals The main motivation here is to equip Sign Language (SL) with software and foster implementation as available tools for SL are paradoxically limited in such digital times. For example, translation assisting software would help respond arXiv:1811.01786v1 [cs.CL] 5 Nov 2018 to the high demand for accessible content and information. But equivalent text-to-text software relies on source and target written forms to work, whereas similar SL support seems impossible without major revision of the typical user interface.
    [Show full text]
  • ISO/IEC JTC1/SC2/WG2 N 4823 Date: 2017-05-24
    ISO/IEC JTC1/SC2/WG2 N 4823 Date: 2017-05-24 ISO/IEC JTC1/SC2/WG2 Coded Character Set Secretariat: Japan (JISC) Doc. Type: Disposition of comments Title: Disposition of comments on PDAM1.2 to ISO/IEC 10646 5th edition Source: Michel Suignard (project editor) Project: JTC1 02.10646.00.01.00.05 Status: For review by WG2 Date: 2017-05-24 Distribution: WG2 Reference: SC2 N4518 Medium: Paper, PDF file Comments were received from the following members: China, Ireland, Japan, Mongolia, UK, and USA. The following document is the disposition of those comments. The disposition is organized per country. Note – With some minor exceptions, the full content of the ballot comments has been included in this document to facilitate the reading. The dispositions are inserted in between these comments and are marked in Underlined Bold Serif text, with explanatory text in italicized serif. As a result of this disposition, a new PDAM1.3 ballot will be initiated. It is expected to be the last PDAM ballot for Amendment 1 before a DAM ballot is initiated. Page 1 Following these dispositions, the following changes were done to the Amendment repertoire: Xiangqi game symbols 30 characters removed (U+1F270..U+1F28D) from the Enclose Ideographic Supplement block (U+1F200..U+1F2FF) and replaced by 14 characters (U+1FA60..U+1FA6D) in a new block: Chess Symbols (U+1FA00..U+1FA6F) with names and code points as follows: 1FA60 RED XIANGQI GENERAL 1FA61 RED XIANGQI MANDARIN 1FA62 RED XIANGQI ELEPHANT 1FA63 RED XIANGQI HORSE 1FA64 RED XIANGQI CHARIOT 1FA65 RED XIANGQI CANNON 1FA66 RED XIANGQI SOLDIER 1FA67 BLACK XIANGQI GENERAL 1FA68 BLACK XIANGQI MANDARIN 1FA69 BLACK XIANGQI ELEPHANT 1FA6A BLACK XIANGQI HORSE 1FA6B BLACK XIANGQI CHARIOT 1FA6C BLACK XIANGQI CANNON 1FA6D BLACK XIANGQI SOLDIER Small Historic Kana The characters proposed at 1B127..1B12F are removed from this amendment.
    [Show full text]
  • Greek Alphabet ( ) Ελληνικ¿ Γρ¿Μματα
    Greek alphabet and pronunciation 9/27/05 12:01 AM Writing systems: abjads | alphabets | syllabic alphabets | syllabaries | complex scripts undeciphered scripts | alternative scripts | your con-scripts | A-Z index Greek alphabet (ελληνικ¿ γρ¿μματα) Origin The Greek alphabet has been in continuous use for the past 2,750 years or so since about 750 BC. It was developed from the Canaanite/Phoenician alphabet and the order and names of the letters are derived from Phoenician. The original Canaanite meanings of the letter names was lost when the alphabet was adapted for Greek. For example, alpha comes for the Canaanite aleph (ox) and beta from beth (house). At first, there were a number of different versions of the alphabet used in various different Greek cities. These local alphabets, known as epichoric, can be divided into three groups: green, blue and red. The blue group developed into the modern Greek alphabet, while the red group developed into the Etruscan alphabet, other alphabets of ancient Italy and eventually the Latin alphabet. By the early 4th century BC, the epichoric alphabets were replaced by the eastern Ionic alphabet. The capital letters of the modern Greek alphabet are almost identical to those of the Ionic alphabet. The minuscule or lower case letters first appeared sometime after 800 AD and developed from the Byzantine minuscule script, which developed from cursive writing. Notable features Originally written horizontal lines either from right to left or alternating from right to left and left to right (boustophedon). Around 500 BC the direction of writing changed to horizontal lines running from left to right.
    [Show full text]
  • Expanding Information Access Through Data-Driven Design
    ©Copyright 2018 Danielle Bragg Expanding Information Access through Data-Driven Design Danielle Bragg A dissertation submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy University of Washington 2018 Reading Committee: Richard Ladner, Chair Alan Borning Katharina Reinecke Program Authorized to Offer Degree: Computer Science & Engineering University of Washington Abstract Expanding Information Access through Data-Driven Design Danielle Bragg Chair of the Supervisory Committee: Professor Richard Ladner Computer Science & Engineering Computer scientists have made progress on many problems in information access: curating large datasets, developing machine learning and computer vision, building extensive networks, and designing powerful interfaces and graphics. However, we sometimes fail to fully leverage these modern techniques, especially when building systems inclusive of people with disabilities (who total a billion worldwide [168], and nearly one in five in the U.S. [26]). For example, visual graphics and small text may exclude people with visual impairments, and text-based resources like search engines and text editors may not fully support people using unwritten sign languages. In this dissertation, I argue that if we are willing to break with traditional modes of information access, we can leverage modern computing and design techniques from computer graphics, crowdsourcing, topic modeling, and participatory design to greatly improve and enrich access. This dissertation demonstrates this potential
    [Show full text]
  • Complete Issue
    _____________________________________________________________ Volume 8 October 1993 Number 2 _____________________________________________________________ Editor Editorial Assistants John Miles Foley Dave Henderson Elizabeth P. McNulty Catherine S. Quick Slavica Publishers, Inc. For a complete catalog of books from Slavica, with prices and ordering information, write to: Slavica Publishers, Inc. P.O. Box 14388 Columbus, Ohio 43214 ISSN: 0883-5365 Each contribution copyright (c) 1993 by its author. All rights reserved. The editor and the publisher assume no responsibility for statements of fact or opinion by the authors. Oral Tradition seeks to provide a comparative and interdisciplinary focus for studies in oral literature and related fields by publishing research and scholarship on the creation, transmission, and interpretation of all forms of oral traditional expression. As well as essays treating certifiably oral traditions, OT presents investigations of the relationships between oral and written traditions, as well as brief accounts of important fieldwork, a Symposium section (in which scholars may reply at some length to prior essays), review articles, occasional transcriptions and translations of oral texts, a digest of work in progress, and a regular column for notices of conferences and other matters of interest. In addition, occasional issues will include an ongoing annotated bibliography of relevant research and the annual Albert Lord and Milman Parry Lectures on Oral Tradition. OT welcomes contributions on all oral literatures, on all literatures directly influenced by oral traditions, and on non-literary oral traditions. Submissions must follow the list-of reference format (style sheet available on request) and must be accompanied by a stamped, self-addressed envelope for return or for mailing of proofs; all quotations of primary materials must be made in the original language(s) with following English translations.
    [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]
  • Signwriting Symbols to Students
    JTC1/SC2/WG2 N4342 L2/12-321 2012-10-14 Universal Multiple-Octet Coded Character Set International Organization for Standardization Organisation Internationale de Normalisation Международная организация по стандартизации Doc Type: Working Group Document Title: Proposal for encoding Sutton SignWriting in the UCS Source: Michael Everson, Martin Hosken, Stephen Slevinski, and Valerie Sutton Status: Individual Contribution Action: For consideration by JTC1/SC2/WG2 and UTC Date: 2012-10-14 Replaces: N4015 1. Introduction. SignWriting is a script developed in 1974 by Valerie Sutton, the inventor of Sutton Movement Writing, who two years earlier had developed DanceWriting. SignWriting is a featural script, its glyphs being visually iconic as well as in their spatial arrangement in text, which represents a sort of snapshot of any given sign. SignWriting is currently being used to write the following Sign Languages: American Sign Language (in USA, English-speaking Canada) Japanese Sign Language Arabian Sign Languages Malawi Sign Language Australian Sign Language Malaysian Sign Language Bolivian Sign Language Maltese Sign Language Brazilian Sign Language Mexican Sign Language British Sign Language Nepalese Sign Language Catalan Sign Language New Zealand Sign Language Colombian Sign Language Nicaraguan Sign Language Czech Sign Language Norwegian Sign Language Danish Sign Language Peruvian Sign Language Dutch Sign Language Philippines Sign Language Ethiopian Sign Language Polish Sign Language Finnish Sign Language Portugese Sign Language Flemish Sign Language Québec Sign Language French-Belgian Sign Language South African Sign Language French Sign Language Spanish Sign Language German Sign Language Swedish Sign Language Greek Sign Language Swiss Sign Language Irish Sign Language Taiwanese Sign Language Italian Sign Language Tunisian Sign Language A variety of literature exists in SignWriting.
    [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]
  • A Cross-Linguistic Guide to Signwriting ® a Phonetic Approach
    A Cross-Linguistic ® Guide to SignWriting A phonetic approach Stephen Parkhurst Dianne Parkhurst A Cross-Linguistic Guide to SignWriting ®: A phonetic approach ©2008 Stephen Parkhurst Revision 2010 For use at SIL-UND courses during the summer of 2010. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, transmitted or utilized in any form or by any means, electronic, mechanical, photocopying, recorded or otherwise, without permission from the authors. Stephen and Dianne Parkhurst E-mail: [email protected] A note from the authors SignWriting®, also known as Sutton Movement Writing for Sign Language, was invented by Valerie Sutton in 1974. Over the years the system has changed significantly and has gradually grown in acceptance and popularity in more than 30 countries. While there are other writing systems and notation systems for writing signed languages, we have not found any system that is as useful for writing accurately any sign or movement (including all non-manual movements and expressions) with relative ease and speed. It is also the only writing system that we have tried that is possible to read faster than one can physically produce the signs (outpacing even photos and line drawings in ease and speed of reading). We have taken much of the material for this manual from a course we developed for teaching SignWriting (SW) to Deaf adults in Spain. That course in Spain focused on teaching the symbols of SW that are used in Spanish Sign Language (or LSE, for Lengua de Signos Española) with a heavy focus on reading.
    [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]