DOCSLIB.ORG

Luatex Glyph Chart for Stix2math.Otf Some Background Information: Unicode Ranges

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

LuaTEX glyph chart for STIX2Math.otf Some background information: Unicode ranges OpenType fonts can contain additional symbols (glyphs) which represent characters that do not have an official Unicode encoding value. These unencoded characters (glyphs) are sometimes assigned to so-called “Private Use” Unicode values by software using the OpenType font: this behaviour is system/software dependent. Unicode sets aside three ranges of values for Private Use: • Basic Multilingual Plane: E000–F8FF (57,344–63,743) • Plane 15: F0000–FFFFD (983,040–1,048,573) • Plane 16: 100000–10FFFD (1,048,576–1,114,109) The STIX2Math.otf font has numerous unencoded characters which LuaTEX, via luaotfload, maps to Private Use Uni- code values. For further information on Private Use areas see https://en.wikipedia.org/wiki/Private_Use_Areas. Table of Unicode blocks for math characters The following table shows the names given to ranges (blocks) of mathematical characters encoded by Unicode, together with the range of Unicode values for each block and the number of characters encoded. Name of Unicode block Unicode range (decimal) Unicode range (hex) Number of symbols Mathematical Operators 8704–8959 2200–22FF 256 Supplemental Mathematical Operators 10,752–11,007 2A00–2AFF 256 Mathematical Alphanumeric Symbols 119,808–120,831 1D400–1D7FF 1024 Letterlike Symbols 8848–8527 2100–214F 80 Miscellaneous Mathematical Symbols-A 10,176–10,223 27C0–27EF 48 Miscellaneous Mathematical Symbols-B 10,624–10,751 2980–29FF 128 Miscellaneous Technical 8960–9215 2300–23FF 256 Geometric Shapes 9632–9727 25A0–25FF 96 Miscellaneous Symbols and Arrows 11,008–11,263 2B00–2BFF 256 Arrows 8592–8703 2190–21FF 112 Supplemental Arrows-A 10,224–10,239 27F0–27FF 16 Supplemental Arrows-B 10,496–10,623 2900–297F 128 Combining Diacritical Marks for Symbols 8400–8447 20D0–20FF 48 Arabic Mathematical Alphabetic Symbols 126,464–126,719 1EE00–1EEFF 256 Why LuaTEX only: a brief technical explanation This glyph chart is primarily intended for use with LuaTEX (LuaLATEX). It contains a complete listing of every glyph con- tained in the STIX2 font STIX2Math.otf—including characters (glyphs) that are not encoded within Unicode: so-called unencoded characters. When LuaTEX (via the luaotfload package) loads the STIX2Math.otf font it maps the unencoded characters (glyphs) to Unicode values within the Private Use ranges. To highlight this we have assigned three different colours to glyphs contained our chart for STIX2Math.otf: • Encoded characters: displayed in red • Private Use (Basic Multilingual Plane): E000–F8FF (57,344–63,743) • Private Use (Plane 15): F0000–FFFFD (983,040–1,048,573) Note: Many of the Unicode-encoded characters (glyphs), coloured red in this chart, may not belong to any of the Unicode blocks assigned to math characters but, instead, are encoded elsewhere within other Unicode blocks. For example, character (glyph) 9619 (▓) is named “DARK SHADE” and encoded as part of the Unicode range called “Block Elements” https: //en.wikipedia.org/wiki/Block_Elements. So, as you can see, STIX2Math.otf contains a wide range of encoded and unencoded characters (glyphs). Information for each glyph Each glyph is accompanied by the following information: • its Unicode value displayed in blue text (U=xxxx...). • its glyph identifier (GID=...) shown in black text. How can I access one of the glyphs shown in the chart? Because STIX2Math.otf is a math font you’ll need to put LuaTEX into math mode to access the glyphs. All you need to do is write $\mathrm{\charxxxx...}$ where xxxx... is that character’s (glyph’s) Unicode value—whether it is encoded or not. Here are some examples: Unicode value TEX code Glyph produced U=983339 $\mathrm{\char983339}$ ∜ U=934 $\mathrm{\char934}$ Φ U=9619 $\mathrm{\char9619}$ ▓ U=10717 $\mathrm{\char10717}$ ⧝ U=98316 $\mathrm{\char983168}$ } How was this chart created? This chart was produced using a “callback” feature of the luaotfload package: patch_font. Via this mechanism, it is possible to intercept, store and subsequently process the low-level data contained in the OpenType fonts loaded into LuaTEX. In outline, the code looks like the following snippet, where tfmdata contains the OpenType font data we wish to process/tabulate. \directlua { local dump_font = function (tfmdata) objstore[filenum]=tfmdata end luatexbase.add_to_callback( "luaotfload.patch_font", dump_font, "my_private_callbacks_dump_font" ) } Glyph chart for STIX2Math.otf Glyphs in this table are listed according to their Unicode value (in ascending order) and, for clarity, are displayed using a large point size. ! " # $ % U=32 U=33 U=34 U=35 U=36 U=37 GID=1 GID=1054 GID=1071 GID=1136 GID=1124 GID=1193 & ′ ( ) ∗ + U=38 U=39 U=40 U=41 U=42 U=43 GID=658 GID=1070 GID=1064 GID=1065 GID=1072 GID=1196 , − . / 0 1 U=44 U=45 U=46 U=47 U=48 U=49 GID=1048 GID=1075 GID=1052 GID=1060 GID=1137 GID=1138 2 3 4 5 6 7 U=50 U=51 U=52 U=53 U=54 U=55 GID=1139 GID=1140 GID=1141 GID=1142 GID=1143 GID=1144 8 9 ∶ ; < = U=56 U=57 U=58 U=59 U=60 U=61 GID=1145 GID=1146 GID=1051 GID=1049 GID=1203 GID=1202 > ? @ A B C U=62 U=63 U=64 U=65 U=66 U=67 GID=1204 GID=1056 GID=1116 GID=3 GID=4 GID=5 D E F G H I U=68 U=69 U=70 U=71 U=72 U=73 GID=6 GID=7 GID=8 GID=9 GID=10 GID=11 J K L M N O U=74 U=75 U=76 U=77 U=78 U=79 GID=12 GID=13 GID=14 GID=15 GID=16 GID=17 P Q R S T U U=80 U=81 U=82 U=83 U=84 U=85 GID=18 GID=19 GID=20 GID=21 GID=22 GID=23 V W X Y Z [ U=86 U=87 U=88 U=89 U=90 U=91 GID=24 GID=25 GID=26 GID=27 GID=28 GID=1066 \ ] ^ _ ‵ a U=92 U=93 U=94 U=95 U=96 U=97 GID=1061 GID=1067 GID=1108 GID=1111 GID=687 GID=255 b c d e f g U=98 U=99 U=100 U=101 U=102 U=103 GID=256 GID=257 GID=258 GID=259 GID=260 GID=261 h i j k l m U=104 U=105 U=106 U=107 U=108 U=109 GID=262 GID=263 GID=265 GID=266 GID=267 GID=268 n o p q r s U=110 U=111 U=112 U=113 U=114 U=115 GID=269 GID=270 GID=271 GID=272 GID=273 GID=274 t u v w x y U=116 U=117 U=118 U=119 U=120 U=121 GID=275 GID=276 GID=277 GID=278 GID=279 GID=280 z { | } ~ U=122 U=123 U=124 U=125 U=126 U=160 GID=281 GID=1068 GID=1062 GID=1069 GID=1109 GID=2 ¡ ¢ £ ¤ ¥ ¦ U=161 U=162 U=163 U=164 U=165 U=166 GID=1055 GID=1125 GID=1126 GID=1122 GID=1127 GID=1110 § ¨ © ª « ¬ U=167 U=168 U=169 U=170 U=171 U=172 GID=1099 GID=694 GID=1117 GID=1206 GID=1093 GID=1205 ­ ® ¯ ° ± 2 U=173 U=174 U=175 U=176 U=177 U=178 GID=1077 GID=1120 GID=695 GID=1208 GID=1199 GID=1149 3 ´ µ ¶ · ¸ U=179 U=180 U=181 U=182 U=183 U=184 GID=1150 GID=689 GID=1216 GID=1097 GID=1101 GID=702 1 1 3 1 º » 4 2 4 U=185 U=186 U=187 U=188 U=189 U=190 GID=1148 GID=1207 GID=1094 GID=1181 GID=1185 GID=1189 ¿ À Á Â Ã Ä U=191 U=192 U=193 U=194 U=195 U=196 GID=1057 GID=29 GID=30 GID=31 GID=37 GID=38 Å Æ Ç È É Ê U=197 U=198 U=199 U=200 U=201 U=202 GID=47 GID=53 GID=62 GID=71 GID=72 GID=73 Ë Ì Í Î Ï Ð U=203 U=204 U=205 U=206 U=207 U=208 GID=81 GID=107 GID=108 GID=109 GID=111 GID=252 Ñ Ò Ó Ô Õ Ö U=209 U=210 U=211 U=212 U=213 U=214 GID=139 GID=145 GID=146 GID=147 GID=153 GID=156 × Ø Ù Ú Û Ü U=215 U=216 U=217 U=218 U=219 U=220 GID=1200 GID=170 GID=201 GID=202 GID=203 GID=206 Ý Þ ß à á â U=221 U=222 U=223 U=224 U=225 U=226 GID=235 GID=253 GID=465 GID=282 GID=283 GID=284 ã ä å æ ç è U=227 U=228 U=229 U=230 U=231 U=232 GID=290 GID=291 GID=300 GID=307 GID=317 GID=329 é ê ë ì í î U=233 U=234 U=235 U=236 U=237 U=238 GID=330 GID=331 GID=339 GID=369 GID=370 GID=371 ï ð ñ ò ó ô U=239 U=240 U=241 U=242 U=243 U=244 GID=373 GID=620 GID=409 GID=416 GID=417 GID=418 õ ö ÷ ø ù ú U=245 U=246 U=247 U=248 U=249 U=250 GID=424 GID=427 GID=1201 GID=441 GID=477 GID=478 û ü ý þ ÿ Ā U=251 U=252 U=253 U=254 U=255 U=256 GID=479 GID=482 GID=514 GID=621 GID=517 GID=40 ā Ă ă Ą ą Ć U=257 U=258 U=259 U=260 U=261 U=262 GID=293 GID=41 GID=294 GID=52 GID=306 GID=58 ć Ĉ ĉ Ċ ċ Č U=263 U=264 U=265 U=266 U=267 U=268 GID=313 GID=59 GID=314 GID=61 GID=316 GID=60 č Ď ď Đ đ Ē U=269 U=270 U=271 U=272 U=273 U=274 GID=315 GID=64 GID=320 GID=70 GID=326 GID=82 ē Ĕ ĕ Ė ė Ę U=275 U=276 U=277 U=278 U=279 U=280 GID=340 GID=85 GID=343 GID=86 GID=344 GID=93 ę Ě ě Ĝ ĝ Ğ U=281 U=282 U=283 U=284 U=285 U=286 GID=351 GID=79 GID=337 GID=95 GID=354 GID=97 ğ Ġ ġ Ģ ģ Ĥ U=287 U=288 U=289 U=290 U=291 U=292 GID=356 GID=98 GID=357 GID=99 GID=358 GID=100 ĥ Ħ ħ Ĩ ĩ Ī U=293 U=294 U=295 U=296 U=297 U=298 GID=360 GID=106 GID=367 GID=110 GID=372 GID=113 ī Ĭ ĭ Į į İ U=299 U=300 U=301 U=302 U=303 U=304 GID=375 GID=114 GID=376 GID=119 GID=380 GID=115 횤 IJ ij Ĵ ĵ Ķ U=305 U=306 U=307 U=308 U=309 U=310 GID=382 GID=254 GID=646 GID=120 GID=384 GID=124 ķ ĸ Ĺ ĺ Ļ ļ U=311 U=312 U=313 U=314 U=315 U=316 GID=390 GID=392 GID=125 GID=393 GID=131 GID=399 Ľ ľ Ŀ ŀ Ł ł U=317 U=318 U=319 U=320 U=321 U=322 GID=126 GID=394 GID=132 GID=400 GID=133 GID=401 Ń ń Ņ ņ Ň ň U=323 U=324 U=325 U=326 U=327 U=328 GID=137 GID=407 GID=144 GID=414 GID=138 GID=408 ʼn Ŋ ŋ Ō ō Ŏ U=329 U=330 U=331 U=332 U=333 U=334 GID=415 GID=251 GID=580 GID=157 GID=428 GID=160 ŏ Ő ő Œ œ Ŕ U=335 U=336 U=337 U=338 U=339 U=340 GID=431 GID=162 GID=432 GID=172 GID=444 GID=175 ŕ Ŗ ŗ Ř ř Ś U=341 U=342 U=343 U=344 U=345 U=346 GID=448 GID=181 GID=454 GID=176 GID=449 GID=182 ś Ŝ ŝ Ş ş Š U=347 U=348 U=349 U=350 U=351 U=352 GID=455 GID=184 GID=457 GID=191 GID=464 GID=185 š Ţ ţ Ť ť Ŧ U=353 U=354 U=355 U=356 U=357 U=358 GID=458 GID=199 GID=473 GID=193 GID=466 GID=200 ŧ Ũ ũ Ū ū Ŭ U=359 U=360 U=361 U=362 U=363 U=364 GID=476 GID=204 GID=480 GID=207 GID=483 GID=209 ŭ Ů ů Ű ű Ų U=365 U=366 U=367 U=368 U=369 U=370 GID=485 GID=210 GID=486 GID=212 GID=488 GID=217 ų Ŵ ŵ Ŷ ŷ Ÿ U=371 U=372 U=373 U=374 U=375 U=376 GID=493 GID=228 GID=506 GID=236 GID=515 GID=238 Ź ź Ż ż Ž ž U=377 U=378 U=379 U=380 U=381 U=382 GID=242
Recommended publications
  • Assessment of Options for Handling Full Unicode Character Encodings in MARC21 a Study for the Library of Congress

    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.
  • The Unicode Standard 5.2 Code Charts

    The Unicode Standard 5.2 Code Charts

    Miscellaneous Technical Range: 2300–23FF The Unicode Standard, Version 5.2 This file contains an excerpt from the character code tables and list of character names for The Unicode Standard, Version 5.2. Characters in this chart that are new for The Unicode Standard, Version 5.2 are shown in conjunction with any existing characters. For ease of reference, the new characters have been highlighted in the chart grid and in the names list. This file will not be updated with errata, or when additional characters are assigned to the Unicode Standard. See http://www.unicode.org/errata/ for an up-to-date list of errata. See http://www.unicode.org/charts/ for access to a complete list of the latest character code charts. See http://www.unicode.org/charts/PDF/Unicode-5.2/ for charts showing only the characters added in Unicode 5.2. See http://www.unicode.org/Public/5.2.0/charts/ for a complete archived file of character code charts for Unicode 5.2. Disclaimer These charts are provided as the online reference to the character contents of the Unicode Standard, Version 5.2 but do not provide all the information needed to fully support individual scripts using the Unicode Standard. For a complete understanding of the use of the characters contained in this file, please consult the appropriate sections of The Unicode Standard, Version 5.2, online at http://www.unicode.org/versions/Unicode5.2.0/, as well as Unicode Standard Annexes #9, #11, #14, #15, #24, #29, #31, #34, #38, #41, #42, and #44, the other Unicode Technical Reports and Standards, and the Unicode Character Database, which are available online.
  • TS 126 234 V5.6.0 (2003-09) Technical Specification

    TS 126 234 V5.6.0 (2003-09) Technical Specification

    ETSI TS 126 234 V5.6.0 (2003-09) Technical Specification Universal Mobile Telecommunications System (UMTS); Transparent end-to-end streaming service; Protocols and codecs (3GPP TS 26.234 version 5.6.0 Release 5) 3GPP TS 26.234 version 5.6.0 Release 5 1 ETSI TS 126 234 V5.6.0 (2003-09) Reference RTS/TSGS-0426234v560 Keywords UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: [email protected] Copyright Notification No part may be reproduced except as authorized by written permission.
  • Frequently Asked Questions and Selected Resources on Cyrillic Multilingual Computing

    Frequently Asked Questions and Selected Resources on Cyrillic Multilingual Computing

    Frequently Asked Questions and Selected Resources on Cyrillic Multilingual Computing Kevin S. Hawkins SUMMARY. The persistence of multiple standards, both de jure and de facto, for handling text on the computer is perhaps the most perplexing problem facing those who wish to use a computer in more than one lan- guage, or even to provide access to data across more than one operating system and application platform. Using Cyrillic as an example, this ar- ticle attempts to answer questions commonly asked by non-expert computer users who wish to work in more than one language. [Article copies available for a fee from The Haworth Document Delivery Service: 1-800-HAWORTH. E-mail address: <[email protected]> Website: <http://www.HaworthPress.com> © 2005 by The Haworth Press, Inc. All rights reserved.] Kevin S. Hawkins, MS, is Electronic Publishing Librarian, Scholarly Publishing Office, University Library, University of Michigan. Address correspondence to: Kevin S. Hawkins, 300 Hatcher Graduate Library North, 920 North University Avenue, Ann Arbor, MI 48109-1205 USA (E-mail: kshawkin@ umich.edu). The author wishes to thank David Dubin and the other members of the GSLIS Re- search Writing Group at the University of Illinois at Urbana-Champaign for their com- prehensive advice, and Troy Williams, Benjamin Rifkin, Michael Brewer, David Dubin, Tatiana Poliakevitch, Irina Roskin, Peter Houtzagers, and Uladzimir Katkouski for their specific corrections and suggestions. [Haworth co-indexing entry note]: “Frequently Asked Questions and Selected Resources on Cyrillic Multilingual Computing.” Hawkins, Kevin S. Co-published simultaneously in Slavic & East European Infor- mation Resources (The Haworth Information Press, an imprint of The Haworth Press, Inc.) Vol.
  • Sample Chapter 3

    Sample Chapter 3

    108_GILLAM.ch03.fm Page 61 Monday, August 19, 2002 1:58 PM 3 Architecture: Not Just a Pile of Code Charts f you’re used to working with ASCII or other similar encodings designed I for European languages, you’ll find Unicode noticeably different from those other standards. You’ll also find that when you’re dealing with Unicode text, various assumptions you may have made in the past about how you deal with text don’t hold. If you’ve worked with encodings for other languages, at least some characteristics of Unicode will be familiar to you, but even then, some pieces of Unicode will be unfamiliar. Unicode is more than just a big pile of code charts. To be sure, it includes a big pile of code charts, but Unicode goes much further. It doesn’t just take a bunch of character forms and assign numbers to them; it adds a wealth of infor- mation on what those characters mean and how they are used. Unlike virtually all other character encoding standards, Unicode isn’t de- signed for the encoding of a single language or a family of closely related lan- guages. Rather, Unicode is designed for the encoding of all written languages. The current version doesn’t give you a way to encode all written languages (and in fact, this concept is such a slippery thing to define that it probably never will), but it does provide a way to encode an extremely wide variety of lan- guages. The languages vary tremendously in how they are written, so Unicode must be flexible enough to accommodate all of them.
  • UTR #25: Unicode and Mathematics

    UTR #25: Unicode and Mathematics

    UTR #25: Unicode and Mathematics http://www.unicode.org/reports/tr25/tr25-5.html Technical Reports Draft Unicode Technical Report #25 UNICODE SUPPORT FOR MATHEMATICS Version 1.0 Authors Barbara Beeton ([email protected]), Asmus Freytag ([email protected]), Murray Sargent III ([email protected]) Date 2002-05-08 This Version http://www.unicode.org/unicode/reports/tr25/tr25-5.html Previous Version http://www.unicode.org/unicode/reports/tr25/tr25-4.html Latest Version http://www.unicode.org/unicode/reports/tr25 Tracking Number 5 Summary Starting with version 3.2, Unicode includes virtually all of the standard characters used in mathematics. This set supports a variety of math applications on computers, including document presentation languages like TeX, math markup languages like MathML, computer algebra languages like OpenMath, internal representations of mathematics in systems like Mathematica and MathCAD, computer programs, and plain text. This technical report describes the Unicode mathematics character groups and gives some of their default math properties. Status This document has been approved by the Unicode Technical Committee for public review as a Draft Unicode Technical Report. Publication does not imply endorsement by the Unicode Consortium. This is a draft document which may be updated, replaced, or superseded by other documents at any time. This is not a stable document; it is inappropriate to cite this document as other than a work in progress. Please send comments to the authors. A list of current Unicode Technical Reports is found on http://www.unicode.org/unicode/reports/. For more information about versions of the Unicode Standard, see http://www.unicode.org/unicode/standard/versions/.
  • Letterlike Symbols Range: 2100–214F

    Letterlike Symbols Range: 2100–214F

    Letterlike Symbols Range: 2100–214F This file contains an excerpt from the character code tables and list of character names for The Unicode Standard, Version 14.0 This file may be changed at any time without notice to reflect errata or other updates to the Unicode Standard. See https://www.unicode.org/errata/ for an up-to-date list of errata. See https://www.unicode.org/charts/ for access to a complete list of the latest character code charts. See https://www.unicode.org/charts/PDF/Unicode-14.0/ for charts showing only the characters added in Unicode 14.0. See https://www.unicode.org/Public/14.0.0/charts/ for a complete archived file of character code charts for Unicode 14.0. Disclaimer These charts are provided as the online reference to the character contents of the Unicode Standard, Version 14.0 but do not provide all the information needed to fully support individual scripts using the Unicode Standard. For a complete understanding of the use of the characters contained in this file, please consult the appropriate sections of The Unicode Standard, Version 14.0, online at https://www.unicode.org/versions/Unicode14.0.0/, as well as Unicode Standard Annexes #9, #11, #14, #15, #24, #29, #31, #34, #38, #41, #42, #44, #45, and #50, the other Unicode Technical Reports and Standards, and the Unicode Character Database, which are available online. See https://www.unicode.org/ucd/ and https://www.unicode.org/reports/ A thorough understanding of the information contained in these additional sources is required for a successful implementation.
  • The Unicode Standard 5.1 Code Charts

    The Unicode Standard 5.1 Code Charts

    Letterlike Symbols Range: 2100–214F The Unicode Standard, Version 5.1 This file contains an excerpt from the character code tables and list of character names for The Unicode Standard, Version 5.1. Characters in this chart that are new for The Unicode Standard, Version 5.1 are shown in conjunction with any existing characters. For ease of reference, the new characters have been highlighted in the chart grid and in the names list. This file will not be updated with errata, or when additional characters are assigned to the Unicode Standard. See http://www.unicode.org/errata/ for an up-to-date list of errata. See http://www.unicode.org/charts/ for access to a complete list of the latest character code charts. See http://www.unicode.org/charts/PDF/Unicode-5.1/ for charts showing only the characters added in Unicode 5.1. See http://www.unicode.org/Public/5.1.0/charts/ for a complete archived file of character code charts for Unicode 5.1. Disclaimer These charts are provided as the online reference to the character contents of the Unicode Standard, Version 5.1 but do not provide all the information needed to fully support individual scripts using the Unicode Standard. For a complete understanding of the use of the characters contained in this file, please consult the appropriate sections of The Unicode Standard, Version 5.0 (ISBN 0-321-48091-0), online at http://www.unicode.org/versions/Unicode5.0.0/, as well as Unicode Standard Annexes #9, #11, #14, #15, #24, #29, #31, #34, #38, #41, #42, and #44, the other Unicode Technical Reports and Standards, and the Unicode Character Database, which are available online.
  • Character Properties 4

    Character Properties 4

    The Unicode® Standard Version 14.0 – Core Specification To learn about the latest version of the Unicode Standard, see https://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. © 2021 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 https://www.unicode.org/reporting.html. For information about the Unicode terms of use, please see https://www.unicode.org/copyright.html. The Unicode Standard / the Unicode Consortium; edited by the Unicode Consortium. — Version 14.0. Includes index. ISBN 978-1-936213-29-0 (https://www.unicode.org/versions/Unicode14.0.0/) 1.
  • Letterlike Symbols Number Forms

    Letterlike Symbols Number Forms

    ISO/IEC JTC1/SC2/WG2 N2392 Title: A Report of Korean Script ad hoc group meeting on Oct. 15, 2001 Participants: Kim Kyongsok (ROK), Mun Hwang Ryong, Park Dong Ki, Yang Song Jin, Yun Chang Hwa (four from D P R of Korea), Kobayashi (not present when the report was written) Source : Korean script ad hoc group. Date: 2001-10-16 References: WG2 N2374, WG2 N2376, WG2 N2390, WG2 N2243 1. D P R of Korea nominated Mr. YANG, Song Jin as a co-chair from D P R of Korea. 2. Adding a 6th column to CJK and CJK Ext. A tables of ISO/IEC 10646-1:2000 [WG2 N2376] - D P R of Korea proposed that they would prepare a sample output of one page so that IRG and WG2 can review it, on the condition that IRG Rapporteur, IRG Technical Editor and Contributing Editor provide D P R of Korea with current CJK fonts and related software used to produce the current CJK tables. When the sample output proves acceptable, DPRK would prepare CJK and CJK Ext. A tables. - Detailed milestones can be discussed at WG2. 3. Adding 70 symbols [WG2 N2374, WG2 N2390] 3.1 For the following 47 characters, no issues were raised and propose that they be added to BMP. Letterlike Symbols Proposed Shape Character Name UCS LIMITED LIABILITY SIGN U+214C # 004C 0054 0044 PARTNERSHIP SIGN U+214D # 0050 0054 0045 FACSIMILE SIGN U+214E # 0046 0041 0058 Number Forms Proposed Shape Character Name UCS VULGAR FRACTION ONE HALF WITH U+2151 HORIZONTAL BAR # 00BD VULGAR FRACTION ONE THIRD WITH U+2184 HORIZONTAL BAR # 2153 VULGAR FRACTION TWO THIRDS WITH U+2185 HORIZONTAL BAR # 2154 VULGAR FRACTION
  • I18n, M17n, Unicode, and All That

    I18n, M17n, Unicode, and All That

    I18N, M17N, UNICODE, AND ALL THAT Tim Bray General-Purpose Web Geek Sun Microsystems /[a-zA-Z]+/ This is probably a bug. The Problems We Have To Solve Identifying characters Storage Byte⇔character mapping Transfer Good string API Published in 1996; it has 74 major sections, most of which discuss whole families of writing systems. www.w3.org/TR/charmod Identifying Characters 1,1 17 “Planes”14,1 each with 64k code points: U+0000 – U+10FFFF BMP 12 Unicode Code Points 0 0000 1 0000 Basic Multilingual Plane 2 0000 Dead Languages & Math 3 0000 Han Characters 4 0000 5 0000 Non-BMP 6 0000 7 0000 99,024 characters defined in Unicode 5.0 “Astral” Planes 8 0000 9 0000 A 0000 B 0000 C 0000 D 0000 E 0000 Language F 0000 10 0000 Private Use T ags The Basic Multilingual Plane (BMP) U+0000 – U+FFFF 0000 Alphabets 1000 2000 3000 Punctuation 4000 Asian-language Support 5000 Han Characters 6000 7000 8000 9000 A000 Y B000 i Hangul C000 D000 E000 (*: Legacy-Compatibility junk)Surrogates F000 Private Use * Unicode Character Database 00C8;LATIN CAPITAL LETTER E WITH GRAVE;Lu;0;L;0045 0300;;;;N;LATIN CAPITAL LETTER E GRAVE;;;00E8; “Character #200 is LATIN CAPITAL LETTER E WITH GRAVE, a lower-case letter, combining class 0, renders L-to-R, can be composed by U+0045/U+0300, had a differentÈ name in Unicode 1, isn’t a number, lowercase is U+00E8.” www.unicode.org/Public/Unidata $ U+0024 DOLLAR SIGN Ž U+017D LATIN CAPITAL LETTER Z WITH CARON ® U+00AE REGISTERED SIGN ή U+03AE GREEK SMALL LETTER ETA WITH TONOS Ж U+0416 CYRILLIC CAPITAL LETTER ZHE א U+05D0 HEBREW LETTER
  • Unicode Characters in Proofpower Through Lualatex

    Unicode Characters in Proofpower Through Lualatex

    Unicode Characters in ProofPower through Lualatex Roger Bishop Jones Abstract This document serves to establish what characters render like in utf8 ProofPower documents prepared using lualatex. Created 2019 http://www.rbjones.com/rbjpub/pp/doc/t055.pdf © Roger Bishop Jones; Licenced under Gnu LGPL Contents 1 Prelude 2 2 Changes 2 2.1 Recent Changes .......................................... 2 2.2 Changes Under Consideration ................................... 2 2.3 Issues ............................................... 2 3 Introduction 3 4 Mathematical operators and symbols in Unicode 3 5 Dedicated blocks 3 5.1 Mathematical Operators block .................................. 3 5.2 Supplemental Mathematical Operators block ........................... 4 5.3 Mathematical Alphanumeric Symbols block ........................... 4 5.4 Letterlike Symbols block ..................................... 6 5.5 Miscellaneous Mathematical Symbols-A block .......................... 7 5.6 Miscellaneous Mathematical Symbols-B block .......................... 7 5.7 Miscellaneous Technical block .................................. 7 5.8 Geometric Shapes block ...................................... 8 5.9 Miscellaneous Symbols and Arrows block ............................. 9 5.10 Arrows block ........................................... 9 5.11 Supplemental Arrows-A block .................................. 10 5.12 Supplemental Arrows-B block ................................... 10 5.13 Combining Diacritical Marks for Symbols block ......................... 11 5.14