DOCSLIB.ORG

Amendment No. 2 to Registry Agreement

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Amendment No. 2 to Registry Agreement Amendment No. 2 to Registry Agreement The Internet Corporation for Assigned Names and Numbers and Association Relative à la Télévision Européenne G.E.I.E. agree, effective as of _______________________________ (“Amendment No. 2 Effective Date”), that the modification set forth below is made to the 11 December 2014 .arte Registry Agreement between the parties (“Agreement”). The parties hereby agree to amend Exhibit A by deleting the following subsection in its entirety. 3.3. Registry Operator may offer registration of IDNs in the following languages/scripts (IDN Tables and IDN Registration Rules will be published by the Registry Operator as specified in the ICANN IDN Implementation Guidelines): 3.3.1. Latin Script The parties hereby further agree to amend Exhibit A by replacing the deleted subsection above with new text as a new subsection 3.3. 3.3. Registry Operator may offer registration of IDNs in the following languages/scripts (IDN Tables and IDN Registration Rules will be published by the Registry Operator as specified in the ICANN IDN Implementation Guidelines): 3.3.1. Arabic script 3.3.2. Armenian script 3.3.3. Avestan script 3.3.4. Azerbaijani language 3.3.5. Balinese script 3.3.6. Bamum script 3.3.7. Batak script 3.3.8. Belarusian language 3.3.9. Bengali script 3.3.10. Bopomofo script 3.3.11. Brahmi script 3.3.12. Buginese script 3.3.13. Buhid script 3.3.14. Bulgarian language 3.3.15. Canadian Aboriginal script 3.3.16. Carian script 3.3.17. Cham script 3.3.18. Cherokee script 3.3.19. Chinese language 3.3.20. Coptic script 3.3.21. Croatian language 3.3.22. Cuneiform script 3.3.23. Cyrillic script 3.3.24. Devanagari script 3.3.25. Egyptian Hieroglyphs script 3.3.26. Ethiopic script 3.3.27. French language 3.3.28. Georgian script 3.3.29. Glagolitic script 3.3.30. Greek script 3.3.31. Greek, Modern language 3.3.32. Gujarati script 3.3.33. Gurmukhi script 3.3.34. Han script 3.3.35. Hangul script 3.3.36. Hanunoo script 3.3.37. Hebrew script 3.3.38. Hiragana script 3.3.39. Imperial Aramaic script 3.3.40. Inscriptional Pahlavi script 3.3.41. Inscriptional Parthian script 3.3.42. Japanese language 3.3.43. Javanese script 3.3.44. Kaithi script 3.3.45. Kannada script 3.3.46. Katakana script 3.3.47. Kayah Li script 3.3.48. Kharoshthi script 3.3.49. Khmer script 3.3.50. Korean language 3.3.51. Kurdish language 3.3.52. Lao script 3.3.53. Latin script 3.3.54. Lepcha script 3.3.55. Limbu script 3.3.56. Lisu script 3.3.57. Lycian script 3.3.58. Lydian script 3.3.59. Macedonian language 3.3.60. Malayalam script 3.3.61. Mandaic script 3.3.62. Meitei Mayek script 3.3.63. Moldavian language 3.3.64. Mongolian script 3.3.65. Myanmar script 3.3.66. New Tai Lue script 3.3.67. Nko script 3.3.68. Ogham script 3.3.69. Ol Chiki script 3.3.70. Old Persian script 3.3.71. Old South Arabian script 3.3.72. Old Turkic script 3.3.73. Oriya script 3.3.74. Phags Pa script 3.3.75. Phoenician script 3.3.76. Polish language 3.3.77. Rejang script 3.3.78. Runic script 3.3.79. Russian language 3.3.80. Samaritan script 3.3.81. Saurashtra script 3.3.82. Serbian language 3.3.83. Sinhala script 3.3.84. Spanish language 3.3.85. Sundanese script 3.3.86. Swedish language 3.3.87. Syloti Nagri script 3.3.88. Syriac script 3.3.89. Tagalog script 3.3.90. Tagbanwa script 3.3.91. Tai Le script 3.3.92. Tai Tham script 3.3.93. Tai Viet script 3.3.94. Tamil script 3.3.95. Telugu script 3.3.96. Thaana script 3.3.97. Thai script 3.3.98. Tibetan script 3.3.99. Tifinagh script 3.3.100. Ukrainian language 3.3.101. Vai script 3.3.102. Yi script The parties agree that, except as set forth in this Amendment, the current terms and conditions of the Agreement will remain in full force and effect. All capitalized terms not defined will have the meaning given to them in the Agreement. ACCEPTED AND AGREED: INTERNET CORPORATION FOR ASSIGNED NAMES AND NUMBERS By: _____________________________ Akram Atallah President, Global Domains Division ASSOCIATION RELATIVE À LA TÉLÉVISION EUROPÉENNE G.E.I.E. By: _____________________________ Peter Boudgoust President By: _____________________________ Anne Durupty Vice President .
Load more

Recommended publications
  • 5892 Cisco Category: Standards Track August 2010 ISSN: 2070-1721
    Internet Engineering Task Force (IETF) P. Faltstrom, Ed. Request for Comments: 5892 Cisco Category: Standards Track August 2010 ISSN: 2070-1721 The Unicode Code Points and Internationalized Domain Names for Applications (IDNA) Abstract This document specifies rules for deciding whether a code point, considered in isolation or in context, is a candidate for inclusion in an Internationalized Domain Name (IDN). It is part of the specification of Internationalizing Domain Names in Applications 2008 (IDNA2008). Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5892. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
    [Show full text]
  • 2903 Date: 2005-08-22
    ISO/IEC JTC 1/SC 2/WG 2 N2903 DATE: 2005-08-22 ISO/IEC JTC 1/SC 2/WG 2 Universal Multiple-Octet Coded Character Set (UCS) - ISO/IEC 10646 Secretariat: ANSI DOC TYPE: Meeting Minutes TITLE: Unconfirmed minutes of WG 2 meeting 46 Jinyan Hotel, Xiamen, Fujian Province, China; 2005-01-24/28 SOURCE: V.S. Umamaheswaran, Recording Secretary, and Mike Ksar, Convener PROJECT: JTC 1.02.18 – ISO/IEC 10646 STATUS: SC 2/WG 2 participants are requested to review the attached unconfirmed minutes, act on appropriate noted action items, and to send any comments or corrections to the convener as soon as possible but no later than 2005-09-05. ACTION ID: ACT DUE DATE: 2005-09-05 DISTRIBUTION: SC 2/WG 2 members and Liaison organizations MEDIUM: Acrobat PDF file NO. OF PAGES: 67 (including cover sheet) Mike Ksar Convener – ISO/IEC/JTC 1/SC 2/WG 2 Microsoft Corporation Phone: +1 425 707-6973 One Microsoft Way Fax: +1 425 936-7329 Bldg 24/2217 email: [email protected] Redmond, WA 98052-6399 or [email protected] Unconfirmed Meeting Minutes ISO/IEC JTC1/SC2/WG2 Meeting 46 Page 1 of 67 N2903 Jinyan Hotel, Xiamen, Fujian Province, China; 2005-01-24/28 2005-08-22 ISO International Organization for Standardization Organisation Internationale de Normalisation ISO/IEC JTC 1/SC 2/WG 2 Universal Multiple-Octet Coded Character Set (UCS) ISO/IEC JTC 1/SC 2/WG 2 N2903 Date: 2005-08-22 Title: Unconfirmed minutes of WG 2 meeting 46 Jinyan Hotel, Xiamen, Fujian Province, China; 2005-01-24/28 Source: V.S.
    [Show full text]
  • Action Items from N2903 15 Action Items All Action Items Recorded in the Minutes of the Previous Meetings from M25 to M42 Have Been Either Completed Or Dropped
    ISO/IEC JTC 1/SC 2/WG 2 N2903A DATE: 2005-08-22 Extract of Section 15 - Action Items from N2903 15 Action items All action items recorded in the minutes of the previous meetings from M25 to M42 have been either completed or dropped. Status of outstanding action items from earlier meetings M43 to M44, and new action items from the latest meeting M45, are listed in the tables that follow. a. Meeting 25, 1994-04-18/22, Antalya, Turkey (document N1033) b. Meeting 26, 1994-10-10/14,San Francisco, CA, USA (document N1117) c. Meeting 27, 1995-04-03/07, Geneva, Switzerland (document N1203) d. Meeting 28, 1995-06-22/26, Helsinki, Finland (document N 1253) e. Meeting 29, 1995-11-06/10, Tokyo, Japan (document N1303) f. Meeting 30, 1996-04-22/26, Copenhagen, Denmark (document N1353) g. Meeting 31, 1996-08-12/16, Québec City, Canada (document N1453) h. Meeting 32, 1997-01-20/24, Singapore (document N1503) i. Meeting 33, 1997-06-30/07-04, Heraklion, Crete, Greece (document N1603) j. Meeting 34, 1998-03-16/20, Redmond, WA, USA (document N1703) k. Meeting 35, 1998-09-21/25, London, UK (document N1903) l. Meeting 36, 1999-03-09/15, Fukuoka, Japan (document N2003) m. Meeting 37, 1999-09-17/21, Copenhagen, Denmark (document N2103) n. Meeting 38, 2000-07-18/21, Beijing, China (document N2203) o. Meeting 39, 2000-10-08/11, Vouliagmeni, Athens, Greece (document N2253) p. Meeting 40, 2001-04-02/05, Mountain View, CA, USA (document N2353), and q. Meeting 41, 2001-10-15/18, Singapore (document 2403) r.
    [Show full text]
  • Ancient Scripts
    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]
  • The University of Chicago Oriental Institute Seminars Number 2
    oi.uchicago.edu i THE UNIVERSITY OF CHICAGO ORIENTAL INSTITUTE SEMINARS NUMBER 2 Series Editors Leslie Schramer and Thomas G. Urban oi.uchicago.edu ii oi.uchicago.edu iii MARGINS OF WRITING, ORIGINS OF CULTURES edited by SETH L. SANDERS with contributions by Seth L. Sanders, John Kelly, Gonzalo Rubio, Jacco Dieleman, Jerrold Cooper, Christopher Woods, Annick Payne, William Schniedewind, Michael Silverstein, Piotr Michalowski, Paul-Alain Beaulieu, Theo van den Hout, Paul Zimansky, Sheldon Pollock, and Peter Machinist THE ORIENTAL INSTITUTE OF THE UNIVERSITY OF CHICAGO ORIENTAL INSTITUTE SEMINARS • NUMBER 2 CHICAGO • ILLINOIS oi.uchicago.edu iv Library of Congress Control Number: 2005938897 ISBN: 1-885923-39-2 ©2006 by The University of Chicago. All rights reserved. Published 2006. Printed in the United States of America. The Oriental Institute, Chicago Co-managing Editors Thomas A. Holland and Thomas G. Urban Series Editors’ Acknowledgments The assistance of Katie L. Johnson is acknowledged in the production of this volume. Front Cover Illustration A teacher holding class in a village on the Island of Argo, Sudan. January 1907. Photograph by James Henry Breasted. Oriental Institute photograph P B924 Printed by McNaughton & Gunn, Saline, Michigan The paper used in this publication meets the minimum requirements of American National Standard for Infor- mation Services — Permanence of Paper for Printed Library Materials, ANSI Z39.48-1984. oi.uchicago.edu v TABLE OF CONTENTS ACKNOWLEDGMENTS .................................................................................................................
    [Show full text]
  • L2/03-253 From: Daniel Kai Date: 2003-08-13 02:29:21 -0700 To: [email protected] Subject: Lepcha, Limbu, Syloti, Saurashtra, Tai Le and Bugis Proposals
    L2/03-253 From: Daniel Kai Date: 2003-08-13 02:29:21 -0700 To: [email protected] Subject: Lepcha, Limbu, Syloti, Saurashtra, Tai Le and Bugis Proposals Rick McGowan has asked that I email you briefly stating how I was able to implement support the above scripts based on various existing proposals and technical reports. All of our implementations are targeted for a Macintosh running OS X 10.2.x. Rick has additional documentation for each of these scripts that he is welcome to share with the committee. Lepcha We have successfully implemented the Lepcha script based on the Proposal for the UCS (author: Michael Everson) and the code points indicated in the roadmap. There are some changes that we suggest (justification for these suggestions can be found in the documentation mentioned above): 1. The letter LEPCHA CONSONANT SIGN B should be renamed to LEPCHA CONSONANT SIGN P. 2. The letter LEPCHA CONSONANT SIGN KANG should be removed. 3. Inclusion of unique punctuation marks. Limbu We have successfully implemented the Limbu script as portrayed in the Limbu code block in Unicode 4.0. We have one comment: 1. There are two glyphs that should be supported [directly] Ð they are the only two conjuncts that typically occur in the written language. Syloti We have created a viable implementation of the Syloti Nagri script based on the following documents: Proposal to WG2 for Encoding Syloti Nagri Script in the BMP DATE: 2003-06-12 Revised Proposal for Encoding Syloti Nagri Script in the BMP DATE 2003-05-10 and additional information specific to the script found in: Documentation in support of proposal for encoding Syloti Nagri in the BMP DATE: 2002-11-01 We raise the following issues (with full realization that they have already been discussed in depth) that do not impact the viability of the proposal directly.
    [Show full text]
  • Amendment No. 2 to Registry Agreement
    Amendment No. 2 to Registry Agreement The Internet Corporation for Assigned Names and Numbers and Infibeam Incorporation Limited agree, effective as of _______________________________ (“Amendment No. 2 Effective Date”), that the modification set forth in this amendment No. 2 (the “Amendment”) is made to the 09 January 2014 .OOO Registry Agreement between the parties, as amended (the “Agreement”). The parties hereby agree to amend Exhibit A of the Agreement by deleting section 5.3 in its entirety: [OLD TEXT] “5.3 Registry Operator may offer registration of IDNs in the following languages/scripts (IDN Tables and IDN Registration Rules will be published by the Registry Operator as specified in the ICANN IDN Implementation Guidelines): 5.3.1. Arabic script 5.3.2. Armenian script 5.3.3. Avestan script 5.3.4. Azerbaijani language 5.3.5. Balinese script 5.3.6. Bamum script 5.3.7. Batak script 5.3.8. Belarusian language 5.3.9. Bengali script 5.3.10. Bopomofo script 5.3.11. Brahmi script 5.3.12. Buginese script 5.3.13. Buhid script 5.3.14. Bulgarian language 5.3.15. Canadian Aboriginal script 5.3.16. Carian script 5.3.17. Cham script 5.3.18. Cherokee script 5.3.19. Chinese language 5.3.20. Coptic script 5.3.21. Croatian language 5.3.22. Cuneiform script 5.3.23. Cyrillic script 5.3.24. Devanagari script 5.3.25. Egyptian Hieroglyphs script 5.3.26. Ethiopic script 5.3.27. French language 5.3.28. Georgian script 5.3.29. Glagolitic script 5.3.30.
    [Show full text]
  • Preliminary Proposal to Encode the Book Pahlavi Script in the Unicode Standard
    UTC Document Register L2/13-141R Preliminary proposal to encode the Book Pahlavi script in the Unicode Standard Roozbeh Pournader, Google Inc. July 24, 2013 1. Background This is a proposal to encode the Book Pahlavi script in the Unicode Standard. Book Pahlavi was last proposed in the “Preliminary proposal to encode the Book Pahlavi script in the BMP of the UCS” (L2/07-234 = JTC1/SC2/WG2 N3294). Here is a short summary of the major differences in the character repertoire between that document and this proposal: • Characters only proposed here: an alternate form of d and a second alternate form of l (see section 7), one atomic symbol and two atomic ligatures (section 8), combining dot below (sections 3 and 6); • Characters proposed in L2/07-234 but not proposed here: ABBREVIATION TAA (representable as a character sequence, section 9), three archigraphemes (ambiguity, implementability, and multiple representation concerns, section 5), combining three dots below (no evidence of usage found), KASHIDA (unified with TATWEEL, sections 9 and 10), numbers (more information needed, section 10). 2. Introduction Book Pahlavi was the most important script used in writing the Middle Persian language.1 It probably started to be commonly used near the end of the Sassanian era (sixth century CE), evolving from the non-cursive Inscriptional Pahlavi. While the term “Book Pahlavi” refers to the script mostly surviving in books, Book Pahlavi has also been used in inscriptions, coins, pottery, and seals. Together with the alphabetic and phonetic Avestan script, the Book Pahlavi abjad is of religious importance to the Zoroastrian community, as most of their surviving religious texts have been written in one or both of the scripts.
    [Show full text]
  • (RSEP) Request October 16, 2017 Registry Operator INFIBEAM INCORPORATION LIMITED 9Th Floor
    Registry Services Evaluation Policy (RSEP) Request October 16, 2017 Registry Operator INFIBEAM INCORPORATION LIMITED 9th Floor, A-Wing Gopal Palace, NehruNagar Ahmedabad, Gujarat 380015 Request Details Case Number: 00874461 This service request should be used to submit a Registry Services Evaluation Policy (RSEP) request. An RSEP is required to add, modify or remove Registry Services for a TLD. More information about the process is available at https://www.icann.org/resources/pages/rsep-2014- 02-19-en Complete the information requested below. All answers marked with a red asterisk are required. Click the Save button to save your work and click the Submit button to submit to ICANN. PROPOSED SERVICE 1. Name of Proposed Service Removal of IDN Languages for .OOO 2. Technical description of Proposed Service. If additional information needs to be considered, attach one PDF file Infibeam Incorporation Limited (“infibeam”) the Registry Operator for the .OOO TLD, intends to change its Registry Service Provider for the .OOO TLD to CentralNic Limited. Accordingly, Infibeam seeks to remove the following IDN languages from Exhibit A of the .OOO New gTLD Registry Agreement: - Armenian script - Avestan script - Azerbaijani language - Balinese script - Bamum script - Batak script - Belarusian language - Bengali script - Bopomofo script - Brahmi script - Buginese script - Buhid script - Bulgarian language - Canadian Aboriginal script - Carian script - Cham script - Cherokee script - Coptic script - Croatian language - Cuneiform script - Devanagari script
    [Show full text]
  • Book Pahlavi
    ISO/IEC JTC1/SC2/WG2 N3294 L2/07-234 2007-07-30 Universal Multiple-Octet Coded Character Set International Organization for Standardization Organisation Internationale de Normalisation Международная организация по стандартизации Doc Type: Working Group Document Title: Preliminary proposal to encode the Book Pahlavi script in the BMP of the UCS Source: Michael Everson, Roozbeh Pournader, and Desmond Durkin-Meisterernst Status: Individual Contribution Action: For consideration by JTC1/SC2/WG2 and UTC Replaces: N2556 Date: 2007-07-30 1. Introduction. “Pahlavi” is a term used in two senses. As a term for language, it means Zoroastrian or Sasanian Middle Persian. As a term for writing systems. the word is used to describe the scripts used to write religious and secular Sasanian Middle Persian and closely similar material, such as epigraphic Parthian and Middle Persian. Three “Pahlavi” scripts are distinguished: Inscriptional Pahlavi, Psalter Pahlavi, and Book Pahlavi. All of these derive from Imperial Aramic. Book Pahlavi is an alphabetic script with an incomplete representation of vowels. The original Imperial Aramaic script’s development is marked by a progressive loss of differentiation of many letters. Thus the Imperial Aramaic letters Ö WAW, ç NUN, è AYIN, and ì RESH coalesced into one simple vertical stroke, in Book Pahlavi written Ñ. (In Inscriptional Pahlavi only Ö WAW, ç NUN, and ì RESH coalesce into •.) The Imperial Aramaic letters Ä ALEPH and á HET coalesced into Book Pahlavi Ä; the Imperial Aramaic letters Ç GIMEL, É DALETH, and â YODH coalesced into Book Pahlavi Ç; and (less importantly) the Imperial Aramaic letters å MEM and í QOPH coalesced into Book Pahlavi ä.
    [Show full text]
  • General Historical and Analytical / Writing Systems: Recent Script
    9 Writing systems Edited by Elena Bashir 9,1. Introduction By Elena Bashir The relations between spoken language and the visual symbols (graphemes) used to represent it are complex. Orthographies can be thought of as situated on a con- tinuum from “deep” — systems in which there is not a one-to-one correspondence between the sounds of the language and its graphemes — to “shallow” — systems in which the relationship between sounds and graphemes is regular and trans- parent (see Roberts & Joyce 2012 for a recent discussion). In orthographies for Indo-Aryan and Iranian languages based on the Arabic script and writing system, the retention of historical spellings for words of Arabic or Persian origin increases the orthographic depth of these systems. Decisions on how to write a language always carry historical, cultural, and political meaning. Debates about orthography usually focus on such issues rather than on linguistic analysis; this can be seen in Pakistan, for example, in discussions regarding orthography for Kalasha, Wakhi, or Balti, and in Afghanistan regarding Wakhi or Pashai. Questions of orthography are intertwined with language ideology, language planning activities, and goals like literacy or standardization. Woolard 1998, Brandt 2014, and Sebba 2007 are valuable treatments of such issues. In Section 9.2, Stefan Baums discusses the historical development and general characteristics of the (non Perso-Arabic) writing systems used for South Asian languages, and his Section 9.3 deals with recent research on alphasyllabic writing systems, script-related literacy and language-learning studies, representation of South Asian languages in Unicode, and recent debates about the Indus Valley inscriptions.
    [Show full text]
  • 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.
    [Show full text]