DOCSLIB.ORG

Information, Characters, Unicode Information – Characters

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Information, Characters, Unicode Information – Characters Information, Characters, Unicode Information { Characters In modern computing, natural-language text is very important information. (\Number-crunching" is less important.) Characters of text are represented in several different ways and a known character encoding is necessary to exchange text information. For many years an important encoding standard for characters has been US ASCII{a 7-bit encoding. Since 7 does not divide 32, the ubiquitous word size of computers, 8-bit encodings are more common. Very common is ISO 8859-1 aka \Latin-1," and other 8-bit encodings of characters sets for languages other than English. Currently, a very large multi-lingual character repertoire known as Unicode is gaining importance. US ASCII (7-bit), or bottom half of Latin1 NUL SOH STX ETX EOT ENQ ACK BEL BS HT LF VT FF CR SS SI DLE DC1 DC2 DC3 DC4 NAK SYN ETP CAN EM SUB ESC FS GS RS US !"# $ %&'()*+,-./ 0123456789:;<=>? @ABCDEFGHIJKLMNO PQRSTUVWXYZ[\]^_ `abcdefghijklmno pqrstuvwxyz{|}~ DEL Control Characters Notice that the first twos rows are filled with so-called control characters. This characters have no printable representation. Except for various standards for indicating lines of text, these characters have no use today. So, nearly one-quarter of the space available for representing characters is wasted. Of course, the space character does not have a printable representation (no ink is used to print a space), but it is extremely useful. Some US-ASCII Characters Each character has a unique bit pattern used to represent it (and a Unicode name as we shall see later). binary oct dec char Unicode 0000 1001 0011 9 HT U+0009 horizontal tabulation 0010 0000 0040 32 U+0020 space 0010 1110 0056 46 . U+002E full stop 0010 1111 0057 47 / U+002F solidus 0011 0000 0060 48 0 U+0030 digit zero 0011 0001 0061 49 1 U+0031 digit one Top half of Latin-1 With 8 bits 256 characters can be encoded. Latin-1 is twice as big as US-ASCII. The extra characters allow languages like Spanish and German to be written in Latin-1. XXX XXX BPH NBH IND NEL SSA ESA HTS HTJ VTS PLD PLU RI SS2 SS3 DCS PU1 PU2 SST CCH MS SPA EPA SOS XXX SCI CSI ST OSC PM APC ¡ ¢ £ ¤ ¥ ¦ § ¨ © ª « : SHY ® ¯ ° ± 2 3 ´ µ ¶ · ¸ 1 º » ¼ ½ ¾ ¿ A` A´ A^ A~ A¨ A˚ Æ C¸ E` E´ E^ E¨ I` I´ I^ I¨ Ð N~ O` O´ O^ O~ O¨ × Ø U` U´ U^ U¨ Y´ Þ ß `a ´a ^a ~a ¨a ˚a æ ¸c `e ´e ^e ¨e `ı ´ı ^ı ¨ı đ ~n `o ´o ^o ~o ¨o ÷ ø `u ´u ^u ¨u ´y þ ¨y Some Characters Here are some of the characters in Latin-1 not used in writing English. binary oct dec Unicode 1100 0011 0303 195 A~ U+00C3 latin capital letter a with tilde 1101 0111 0327 215 × U+00D7 multiplication sign 1101 1111 0337 223 ß U+00DF latin small letter sharp s 1110 1101 0355 237 ´ı U+00ED latin small letter i with acute 1111 1110 0376 254 þ U+00FE latin small letter thorn An 8-bit character set is a convenient size and so US ASCII is for the most part replaced by Latin-1 which supports some European languages. Microsoft's CP1252 is somewhat similar. The new ISO 8859-15 (Latin-9) nicknamed Latin-0 updates Latin-1 by replacing eight infrequently used characters ¤¦¨´¼½¾. with left-out French letters (¨y,œ) and Finnish and Lithuanian letters (ˇs,ˇz),and placing the Euro sign e in the cell 0xA4 of the former (unspecified) currency sign ¤. ¤ U+00A4 currency sign ! e U+20AC euro sign ¦ U+00A6 broken bar ! Sˇ U+0160 latin capital letter s with caron ¨ U+00A8 diaeresis ! ˇs U+0161 latin small letter s with caron ´ U+00B4 acute accent ! Zˇ U+017D latin capital letter z with caron ¸ U+00B8 cedilla ! ˇz U+017E latin small letter z with caron ¼ U+00BC vulgar frac 1 quarter ! Œ U+0152 latin capital ligature oe ½ U+00BD vulgar fraction 1 half ! œ U+0153 latin small ligature oe ¾ U+00BE vulgar frac 3 quarters! Y¨ U+0178 latin capital letter y with diaeresis Top half of Latin-0 XXX XXX BPH NBH IND NEL SSA ESA HTS HTJ VTS PLD PLU RI SS2 SS3 DCS PU1 PU2 SST CCH MS SPA EPA SOS XXX SCI CSI ST OSC PM APC ¡ ¢ £ e ¥ Sˇ § ˇs © ª « : SHY ® ¯ ° ± 2 3 Zˇ µ ¶ · ˇz 1 º » Œœ Y¨¿ A` A´ A^ A~ A¨ A˚ Æ C¸ E` E´ E^ E¨ I` I´ I^ I¨ Ð N~ O` O´ O^ O~ O¨ × Ø U` U´ U^ U¨ Y´ Þ ß `a ´a ^a ~a ¨a ˚a æ ¸c `e ´e ^e ¨e `ı ´ı ^ı ¨ı đ ~n `o ´o ^o ~o ¨o ÷ ø `u ´u ^u ¨u ´y þ ¨y Differences in Character Encodings binary oct dec hex MacR 1252 Latin1 Latin0 0111 0011 0163 115 0x73 s s s s 1000 0000 0200 128 0x80 A¨ e XXX XXX 1000 0101 0205 135 0x85 O¨ ::: NEL NEL 1000 1010 0212 138 0x8A ¨a Sˇ VTS VTS 1010 0100 0244 164 0xA4 § ¤ ¤ e 1010 0110 0246 166 0xA6 ¶ ¦ ¦ Sˇ 1011 0110 0266 182 0xB6 @ ¶¶¶ 1101 1011 0333 219 0xDB e U^ U^ U^ 1110 0100 0344 228 0xE4 ‰ ¨a ¨a ¨a 1111 0011 0363 243 0xF3 U^ ´o ´o ´o Standards help insure that the bit patterns are understood the same way. But the applicable standard must be clearly known. Java Makes It Easy Indicate to the Scanner class which character encoding is to be expected, and Java will interpret the bytes correctly. This is because Java uses Unicode internally which is a superset of all commonly used character set encodings. Scanner s = new Scanner (System.in,"LATIN-1"); Scanner s = new Scanner (System.in,"Cp1252"); Without a specified character encoding, the computer's default encoding is used. Scanner s = new Scanner (System.in); A program with such a scanner may behave differently on different computers, leading to confusion. TIP All the input in lab will be US-ASCII, so please use the two argument form of the Scanner class at all times. Scanner s = new Scanner (System.in,"US-ASCII"); A bad bit pattern in the input (there won't be one) would result in a Unicode character for \bad character" { 0xFFFD replacement character { in your input. The behavior of the programs for the exercises in lab is never defined on any \bad" input whatsoever The program may do anything at all including loop or result in a runtime error. In particular the program does not have to detect \bad" input or report it. What Do Characters Mean? Some characters, like the tab, have no fixed meaning, even though it has an agreed upon code point. Tabs are interpreted differently by different applications leading to confusion. Six invisible or white-space characters are legal in a Java program. No other control characters are legal in a Java program. A Java program is permitted to end with the \substitute" character. binary oct dec Latin1 Unicode 0000 1001 0011 9 HT U+0009 horizontal tabulation 0000 1010 0012 10 LF U+000A line feed 0000 1100 0014 12 FF U+000C form feed 0000 1101 0015 13 CR U+000D carriage return 0001 1010 0032 26 SUB U+001A substitute 0010 0000 0040 32 U+0020 space There is no advantage to using a horizontal tabulation or a substitute character in a Java program. But there is a risk of breaking some application that uses Java source code for input (pretty-printers, text beautifiers, metric tools, etc.) Newlines indications are necessary for formatting programs, and Java permits all three of the common newline conventions: the line feed character (common in Unix applications), the carriage return (Mac applications), and the carriage return character followed by the line feed (Microsoft applications). MacOS CR "\r" Unix LF "\n" Windows CR,LF "\r\n" Other newline markers are much less common. Next-line (NEL x85) is used to mark end-of-line on some IBM mainframes. Unicode has its own approach to indicating a new line: Unicode U+2028 line separator The method readLine() of the Java class BufferedReader tolerates MacOS, Unix or Window (but not Unicode) new-line indications. The Java JVM initializes the new-line indication according to the platform it is running. This value is available through system properties: System.getProperty("line.separator"). The method format in class Formatter recognizes %n in format strings as the value of the line separator. // Use Unicode line separator character System.setProperty("line.separator","\u2028"); System.out.format("A line.%n"); Newline From Wikipedia: In computing a newline, also known as a line break or end-of-line (EOL) marker, is a special character or sequence of characters signifying the end of a line of text. There is also some confusion whether newlines terminate or separate lines. If a newline is considered a separator, there will be no newline after the last line of a file. The general convention on most systems is to add a newline even after the last line, i.e. to treat newline as a line terminator. Some programs have problems processing the last line of a file if it is not newline terminated. Newline Please consider the newline mark a line terminator. The number of newline marks in a file is the number of lines in the file. You can lose points on tests through this type of miscommunication. Unicode Versions version date scripts characters bits 1.0 Oct 1991 24 7,161 12.81 2.0 Jul 1996 24 38,950 15.25 3.0 Sep 1999 38 49,249 15.59 4.0 Apr 2003 52 96,447 16.56 5.0 Jul 2006 64 99,098 16.60 6.0 Oct 2010 93 109,449 16.74 7.0 Jun 2014 123 113,021 16.79 8.0 Jun 2015 123 120,737 16.88 9.0 Jun 2016 135 128,237 16.97 10.0 Jun 2017 139 136,690 17.06 11.0 Jun 2018 146 137,374 17.07 Here characters mean the number of encoded characters: graphic characters, format characters plus control characters.
Load more

Recommended publications
  • ST.36 Page: 3.36.1
    HANDBOOK ON INDUSTRIAL PROPERTY INFORMATION AND DOCUMENTATION Ref.: Standards – ST.36 page: 3.36.1 STANDARD ST.36 Version 1.2 RECOMMENDATION FOR THE PROCESSING OF PATENT INFORMATION USING XML (EXTENSIBLE MARKUP LANGUAGE) Revision adopted by ST.36 Task Force of the Standards and Documentation Working Group (SDWG) on November 23, 2007 TABLE OF CONTENTS INTRODUCTION ............................................................................................................................................................ 2 DEFINITIONS ................................................................................................................................................................. 3 SCOPE OF THE STANDARD ........................................................................................................................................ 3 REQUIREMENTS OF THE STANDARD........................................................................................................................ 4 General ......................................................................................................................................................................... 4 Characters .................................................................................................................................................................... 5 Naming international common elements....................................................................................................................... 6 Naming office-specific elements
    [Show full text]
  • International Standard Iso/Iec 10646
    This is a preview - click here to buy the full publication INTERNATIONAL ISO/IEC STANDARD 10646 Sixth edition 2020-12 Information technology — Universal coded character set (UCS) Technologies de l'information — Jeu universel de caractères codés (JUC) Reference number ISO/IEC 10646:2020(E) © ISO/IEC 2020 This is a preview - click here to buy the full publication ISO/IEC 10646:2020 (E) CONTENTS 1 Scope ..................................................................................................................................................1 2 Normative references .........................................................................................................................1 3 Terms and definitions .........................................................................................................................2 4 Conformance ......................................................................................................................................8 4.1 General ....................................................................................................................................8 4.2 Conformance of information interchange .................................................................................8 4.3 Conformance of devices............................................................................................................8 5 Electronic data attachments ...............................................................................................................9 6 General structure
    [Show full text]
  • Package Mathfont V. 1.6 User Guide Conrad Kosowsky December 2019 [email protected]
    Package mathfont v. 1.6 User Guide Conrad Kosowsky December 2019 [email protected] For easy, off-the-shelf use, type the following in your docu- ment preamble and compile using X LE ATEX or LuaLATEX: \usepackage[hfont namei]{mathfont} Abstract The mathfont package provides a flexible interface for changing the font of math- mode characters. The package allows the user to specify a default unicode font for each of six basic classes of Latin and Greek characters, and it provides additional support for unicode math and alphanumeric symbols, including punctuation. Crucially, mathfont is compatible with both X LE ATEX and LuaLATEX, and it provides several font-loading commands that allow the user to change fonts locally or for individual characters within math mode. Handling fonts in TEX and LATEX is a notoriously difficult task. Donald Knuth origi- nally designed TEX to support fonts created with Metafont, and while subsequent versions of TEX extended this functionality to postscript fonts, Plain TEX's font-loading capabilities remain limited. Many, if not most, LATEX users are unfamiliar with the fd files that must be used in font declaration, and the minutiae of TEX's \font primitive can be esoteric and confusing. LATEX 2"'s New Font Selection System (nfss) implemented a straightforward syn- tax for loading and managing fonts, but LATEX macros overlaying a TEX core face the same versatility issues as Plain TEX itself. Fonts in math mode present a double challenge: after loading a font either in Plain TEX or through the nfss, defining math symbols can be unin- tuitive for users who are unfamiliar with TEX's \mathcode primitive.
    [Show full text]
  • L2/20-246 Teeth and Bellies: a Proposed Model for Encoding Book Pahlavi
    L2/20-246 Teeth and bellies: a proposed model for encoding Book Pahlavi Roozbeh Pournader (WhatsApp) September 7, 2020 Background In Everson 2002, a proposal was made to encode a unified Avestan and Pahlavi script in the Unicode Standard. The proposal went through several iterations, eventually leading to a separate encoding of Avestan as proposed by Everson and Pournader 2007a, in which Pahlavi was considered non-unifiable with Avestan due to its cursive joining property. The non-cursive Inscriptional Pahlavi (Everson and Pournader 2007b) and the cursive Psalter Pahlavi (Everson and Pournader 2011) were later encoded too. But Book Pahlavi, despite several attempts (see the Book Pahlavi Topical Document list at https://unicode.org/L2/ topical/bookpahlavi/), remains unencoded. Everson 2002 is peculiar among earlier proposals by proposing six Pahlavi archigraphemes, including an ear, an elbow, and a belly. I remember from conversations with Michael Everson that he intended these to be used for cases when a scribe was just copying some text without understanding the underlying letters, considering the complexity of the script and the loss of some of its nuances to later scribes. They could also be used when modern scholars wanted to represent a manuscript as written, without needing to over-analyze potentially controversial readings. Meyers 2014 takes such a graphical model to an extreme, trying to encode pieces of the writing system, most of which have some correspondence to letters, but with occasional partial letters (e.g. PARTIAL SHIN and FINAL SADHE-PARTIAL PE). Unfortunately, their proposal rejects joining properties for Book Pahlavi and insists that “[t]he joining behaviour of the final stems of the characters in Book Pahlavi is more similar to cursive variants of Latin than to Arabic”.
    [Show full text]
  • Assessment of Options for Handling Full Unicode Character Encodings in MARC21 a Study for the Library of Congress
    1 Assessment of Options for Handling Full Unicode Character Encodings in MARC21 A Study for the Library of Congress Part 1: New Scripts Jack Cain Senior Consultant Trylus Computing, Toronto 1 Purpose This assessment intends to study the issues and make recommendations on the possible expansion of the character set repertoire for bibliographic records in MARC21 format. 1.1 “Encoding Scheme” vs. “Repertoire” An encoding scheme contains codes by which characters are represented in computer memory. These codes are organized according to a certain methodology called an encoding scheme. The list of all characters so encoded is referred to as the “repertoire” of characters in the given encoding schemes. For example, ASCII is one encoding scheme, perhaps the one best known to the average non-technical person in North America. “A”, “B”, & “C” are three characters in the repertoire of this encoding scheme. These three characters are assigned encodings 41, 42 & 43 in ASCII (expressed here in hexadecimal). 1.2 MARC8 "MARC8" is the term commonly used to refer both to the encoding scheme and its repertoire as used in MARC records up to 1998. The ‘8’ refers to the fact that, unlike Unicode which is a multi-byte per character code set, the MARC8 encoding scheme is principally made up of multiple one byte tables in which each character is encoded using a single 8 bit byte. (It also includes the EACC set which actually uses fixed length 3 bytes per character.) (For details on MARC8 and its specifications see: http://www.loc.gov/marc/.) MARC8 was introduced around 1968 and was initially limited to essentially Latin script only.
    [Show full text]
  • Kirja-Alan Onix
    KIRJA-ALAN ONIX SUOMALAINEN SOVELLUS Versio 3.0.2. Marraskuu 2012 Päivitetty huhtikuu 2015 Helsinki 2012 ISBN 978-952-10-8321-1 (PDF) Työryhmä: Mirja Anttila, Kansalliskirjasto Peter Bagge, Kustannusosakeyhtiö Otava Juha Hakala, Kansalliskirjasto Jari Heikkinen, Kansalliskirjasto Susanna Honkanen, Suomalainen Kirjakauppa Oy Maarit Huttunen, Kansalliskirjasto Karin von Koskull, Stockmann Oyj Abp, Akateeminen Kirjakauppa Tuomo Suominen, Sanoma Pro Oy Olli Tuuteri, BTJ Finland Oy Aija Vahtola, Kansalliskirjasto Eila Vainikka, Kuntaliitto Susanna Vestman, Kirjavälitys Oy Laura Vuorensola, Stockmann Oyj Abp, Akateeminen kirjakauppa Suomalainen ONIX-sovellus perustuu seuraaviin dokumentteihin: ONIX for Books Product Information Format Specification Release 3.0 revision 1, January 2012 ONIX for Books: Code Lists Issues 18–27 Alkuperäiset dokumentit ovat saatavilla osoitteessa http://www.editeur.org/ Kommentit formaattiin ja mahdolliset lisäkysymykset Suomen ONIX-keskukselle. http://www.onix.fi/ 1 Sisällys Suomalaisen sovelluksen esipuhe ........................................................................................................... 4 ONIX-viesti .............................................................................................................................................. 5 Viestin rakenne ................................................................................................................................... 5 P.1 Tuotetietueen viite ja tyyppi (Record reference number, type and source) .............................
    [Show full text]
  • How to Speak Emoji : a Guide to Decoding Digital Language Pdf, Epub, Ebook
    HOW TO SPEAK EMOJI : A GUIDE TO DECODING DIGITAL LANGUAGE PDF, EPUB, EBOOK National Geographic Kids | 176 pages | 05 Apr 2018 | HarperCollins Publishers | 9780007965014 | English | London, United Kingdom How to Speak Emoji : A Guide to Decoding Digital Language PDF Book Secondary Col 2. Primary Col 1. Emojis are everywhere on your phone and computer — from winky faces to frowns, cats to footballs. They might combine a certain face with a particular arrow and the skull emoji, and it means something specific to them. Get Updates. Using a winking face emoji might mean nothing to us, but our new text partner interprets it as flirty. And yet, once he Parenting in the digital age is no walk in the park, but keep this in mind: children and teens have long used secret languages and symbols. However, not all users gave a favourable response to emojis. Black musicians, particularly many hip-hop artists, have contributed greatly to the evolution of language over time. A collection of poems weaving together astrology, motherhood, music, and literary history. Here begins the new dawn in the evolution the language of love: emoji. She starts planning how they will knock down the wall between them to spend more time together. Irrespective of one's political standpoint, one thing was beyond dispute: this was a landmark verdict, one that deserved to be reported and analysed with intelligence - and without bias. Though somewhat If a guy likes you, he's going to make sure that any opportunity he has to see you, he will. Here and Now Here are 10 emoticons guys use only when they really like you! So why do they do it? The iOS 6 software.
    [Show full text]
  • Tai Lü / ᦺᦑᦟᦹᧉ Tai Lùe Romanization: KNAB 2012
    Institute of the Estonian Language KNAB: Place Names Database 2012-10-11 Tai Lü / ᦺᦑᦟᦹᧉ Tai Lùe romanization: KNAB 2012 I. Consonant characters 1 ᦀ ’a 13 ᦌ sa 25 ᦘ pha 37 ᦤ da A 2 ᦁ a 14 ᦍ ya 26 ᦙ ma 38 ᦥ ba A 3 ᦂ k’a 15 ᦎ t’a 27 ᦚ f’a 39 ᦦ kw’a 4 ᦃ kh’a 16 ᦏ th’a 28 ᦛ v’a 40 ᦧ khw’a 5 ᦄ ng’a 17 ᦐ n’a 29 ᦜ l’a 41 ᦨ kwa 6 ᦅ ka 18 ᦑ ta 30 ᦝ fa 42 ᦩ khwa A 7 ᦆ kha 19 ᦒ tha 31 ᦞ va 43 ᦪ sw’a A A 8 ᦇ nga 20 ᦓ na 32 ᦟ la 44 ᦫ swa 9 ᦈ ts’a 21 ᦔ p’a 33 ᦠ h’a 45 ᧞ lae A 10 ᦉ s’a 22 ᦕ ph’a 34 ᦡ d’a 46 ᧟ laew A 11 ᦊ y’a 23 ᦖ m’a 35 ᦢ b’a 12 ᦋ tsa 24 ᦗ pa 36 ᦣ ha A Syllable-final forms of these characters: ᧅ -k, ᧂ -ng, ᧃ -n, ᧄ -m, ᧁ -u, ᧆ -d, ᧇ -b. See also Note D to Table II. II. Vowel characters (ᦀ stands for any consonant character) C 1 ᦀ a 6 ᦀᦴ u 11 ᦀᦹ ue 16 ᦀᦽ oi A 2 ᦰ ( ) 7 ᦵᦀ e 12 ᦵᦀᦲ oe 17 ᦀᦾ awy 3 ᦀᦱ aa 8 ᦶᦀ ae 13 ᦺᦀ ai 18 ᦀᦿ uei 4 ᦀᦲ i 9 ᦷᦀ o 14 ᦀᦻ aai 19 ᦀᧀ oei B D 5 ᦀᦳ ŭ,u 10 ᦀᦸ aw 15 ᦀᦼ ui A Indicates vowel shortness in the following cases: ᦀᦲᦰ ĭ [i], ᦵᦀᦰ ĕ [e], ᦶᦀᦰ ăe [ ∎ ], ᦷᦀᦰ ŏ [o], ᦀᦸᦰ ăw [ ], ᦀᦹᦰ ŭe [ ɯ ], ᦵᦀᦲᦰ ŏe [ ].
    [Show full text]
  • Using Functions
    TIBCO WebFOCUS® Using Functions Release 8207 May 2021 DN4501670.0521 Copyright © 2021. TIBCO Software Inc. All Rights Reserved. Contents 1. How to Use This Manual ...................................................... 17 Available Languages .................................................................17 Operating Systems .................................................................. 17 2. Introducing Functions .........................................................19 Using Functions .....................................................................19 Types of Functions ...................................................................20 WebFOCUS-specific Functions.................................................... 22 Simplified Analytic Functions..................................................... 22 Simplified Character Functions....................................................23 Character Functions.............................................................25 Variable Length Character Functions...............................................28 Character Functions for DBCS Code Pages......................................... 29 Maintain-specific Character Functions..............................................30 Data Source and Decoding Functions..............................................31 Simplified Date and Date-Time Functions...........................................33 Date Functions................................................................. 33 Standard Date Functions..................................................
    [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]
  • CJKV Unified Ideographs Extension C
    22nd International Unicode Conference (IUC22) Unicode and the Web: Evolution or Revolution? September 9 - 13, 2002, San Jose, California http://www.unicode.org/iuc/iuc22/ CJKV Unified Ideographs Extension C Richard S. COOK Linguistics Department University of California, Berkeley [email protected] http://stedt.berkeley.edu/ 2002-09-18-10:31 INTRODUCTION This presentation is concerned with introducing the audience to some of the issues surrounding Ideographic Rapporteur Group (ISO/IEC JTC1/SC2/WG2/IRG) work on “CJK Unified Ideographs Extension C” (Ext C), including the following: (1) The IRG methodology constraining glyph submissions for Ext C1 (why more Han characters and which?) (2) The method of preparing glyph submissions for the Unicode Technical Committee (UTC) (3) IRG member submissions for Ext C1, introducing some of the submitted glyphs, the print sources for the glyph submissions (4) The IRG process of submission evaluation (5) The impact of submitted glyphs on the “Han Variant” problem (see Cook, IUC-19) (6) Plans for Ext C2 UTC submissions 22nd International Unicode Conference1 San Jose, California, September 2002 CJKV Unified Ideographs Extension C BACKGROUND As many people already know, The Unicode Standard 3.2 is the best thing ever to happen to the digitization of Chinese texts. The immense work done to produce the CJKV1 part of this standard, undertaken by the Ideographic Rapporteur Group (IRG)2, has pushed CJKV computing to higher levels than many had ever thought possible. With the IRG’s creation of “Extension B”, 42,711 new characters were added to The Unicode Standard, so that it now encodes a total of 70,207 unique “ideographs”.3 The issue is somewhat complicated by things such as “compatibility characters which are not actually compatibility characters”.
    [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]