DOCSLIB.ORG

Unicode Reference Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Start Oracle® Documaker Unicode Reference Guide 12.5.0 Part number: E73730-01 April 2016 Copyright Copyright © 2009, 2016, Oracle and/or its affiliates. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software-- Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. Oracle, JD Edwards, and PeopleSoft are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. THIRD PARTY SOFTWARE NOTICES This product includes software developed by Apache Software Foundation (http://www.apache.org/). THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Copyright © 2000-2009 The Apache Software Foundation. All rights reserved. Apache Commons Math Copyright 2001-2008 The Apache Software Foundation This product includes software translated from the odex Fortran routine developed by E. Hairer and G. Wanner and distributed under the following license: Copyright (c) 2004, Ernst Hairer Apache License Version 2.0, January 2004 (http://www.apache.org/licenses/LICENSE-2.0) THIS SOFTWARE IS PROVIDED "AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE VISIGOTH SOFTWARE SOCIETY OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Apache Commons Codec Copyright 2002-2009 The Apache Software Foundation Copyright (C) 2002 Kevin Atkinson ([email protected]) Apache Commons Pool Copyright 2001-2011 The Apache Software Foundation Apache Jakarta Commons Lang Copyright 2001-2007 The Apache Software Foundation Apache Jakarta Commons FileUpload Copyright 2002-2006 The Apache Software Foundation Apache Commons CLI Copyright 2001-2009 The Apache Software Foundation Apache Commons Collections Copyright 2001-2008 The Apache Software Foundation Apache Commons Logging Copyright 2003-2013 The Apache Software Foundation Barcode4J Copyright 2002-2010 Jeremias Märki Copyright 2005-2006 Dietmar Bürkle Portions of this software were contributed under section 5 of the Apache License. Contributors are listed under: (http://barcode4j.sourceforge.net/contributors.html) Copyright 2002-2010 The Apache Software Foundation This product includes software distributed via the Berkeley Software Distribution (BSD) and licensed for binary distribution under the Generic BSD license. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Copyright © 2009, Berkeley Software Distribution (BSD) This product includes software developed by the JDOM Project (http://www.jdom.org/). THIS SOFTWARE IS PROVIDED "AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin. All rights reserved. This product includes software developed by the Massachusetts Institute of Technology (MIT). THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Copyright © 2009 MIT This product includes software developed by Jean-loup Gailly and Mark Adler. This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Copyright (c) 1995-2005 Jean-loup Gailly and Mark Adler This software is based in part on the work of the Independent JPEG Group (http://www.ijg.org/). This product includes software developed by the Dojo Foundation (http://dojotoolkit.org). THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
Recommended publications
  • Typing Vietnamese on Window

    Typing Vietnamese on Window

    TYPING VIETNAMESE WITH UNICODE FONT It is recommended that you use a Vietnamese keyboard or keyboard driver for the task. Despite its name, it is not hardware: it is a small program that sits in your OS and converts your keystrokes into Vietnamese characters. Unikey. Its advantages are: It's free. It's just a download away: for NT/2000/XP, for 95/98/MEor for Linux. Installation is simple: just unzip it and it is ready to go. It sits on the taskbar. This makes it easy to switch between "English" mode and "Vietnamese" mode: just click on the icon on the taskbar. The user interface actually provides for English speakers, which makes it easier to understand. Setup 1. When you start up Unikey, you see the following dialogue: What does it all mean? Fortunately, you can find out what is happening by clicking on the "Mở rộng" button. "Mở rộng" means expand, and that's what you need to do. Uncheck the checkbox with "Vietnamese interface”. The whole interface will turn into English: I recommend you always set the "Character Set" to Unicode - always. A character set is basically how characters like "ư" and "a" are represented as numbers that computers can handle. The Microsoft Office programs are set to handle Unicode by default. Unicode is an international standard, so you can't go much wrong with it. The "Input method" is what keystrokes will form a character like "ư". I prefer TELEX, but I will give instructions for using Unikey with VNI as well. See the next section for instructions.
  • Download Free Chinese Fonts for Mac

    Download Free Chinese Fonts for Mac

    1 / 4 Download Free Chinese Fonts For Mac ttc and Songti ttc and include TC fonts Hiragino Sans GB ~ Beginning with OS X 10.. 01[?]KaiTi楷体GB18030simkai ttfv5 01[?]FangSong_GB2312仿宋_GB2312GB2312SIMFANG.. [NEED MORE DETAILS HERE] [DISCUSSION OF WEB FONTS AND CSS3]Arphic [文鼎]Taiwan.. If you want to use this font for both simplified and traditional Chinese, then use Font Book to deactivate BiauKai and activate DFKai-SB instead.. ttf file and select install MacOS X (10 3 or later)Double-click on the ttf file and select install.. West is an IRG participant as a member of the UK delegation, so he is well-informed and up-to-date on the progress of their work, and his fonts reflect that knowledge. In addition, the Microsoft Office XP Proofing Tools (and Chinese editions) include the font Simsun (Founder Extended) [SURSONG.. A long time vendor of Chinese OEM fonts, in 2006 Monotype's new owners [Monotype Imaging] also acquired China Type Design [中國字體設計] in Hong Kong.. For the character sets and weights for each, see the Fonts section for your OS: 10.. If you have downloaded a font that is saved in Free Chinese Fonts Free Chinese Font is all about Chinese fonts that are free to download! This site aims to help you download high quality Chinese fonts in.. FamilyFile nameCharsetOS 910 310 410 510 610 710 810 1010 11PingFang SC PingFang HK PingFang TCPingFang.. Font files had to be converted between Windows and Macintosh Regardless, all TrueType fonts contain 'cmap' tables that map its glyphs to various encodings. chinese fonts chinese fonts, chinese fonts generator, chinese fonts download, chinese fonts copy and paste, chinese fonts google docs, chinese fonts dafont, chinese fonts adobe, chinese fonts in microsoft word, chinese fonts word, chinese fonts calligraphy Arial Unicode MS ~ Beginning with OS X 10 5, Apple includes this basic Monotype Unicode font from Microsoft Office [Arial Unicode.
  • 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.
  • UTC L2/15-257 2015-11-02 Universal Multiple-Octet Coded Character Set International Organization for Standardization Organisation Internationale De Normalisation

    UTC L2/15-257 2015-11-02 Universal Multiple-Octet Coded Character Set International Organization for Standardization Organisation Internationale De Normalisation

    ISO/IEC JTC1/SC2/WG2 N4xxx UTC L2/15-257 2015-11-02 Universal Multiple-Octet Coded Character Set International Organization for Standardization Organisation Internationale de Normalisation Doc Type: Working Group Document Title: Proposal to Disunify Khamti Letters from Myanmar (Revision 3) Source: Martin Hosken Status: Individual contribution Action: For consideration by UTC and WG2 Date: 2015-11-02 Executive Summary This proposal is to disunify the Khamti and Aiton and Phake style Myanmar consonants (those with the dots) into their own letters as part of the Myanmar script block, and thus create a new Myanmar Extended block to hold them in. The effect is to add 16 characters. In addition the representative glyphs for Khamti specific letters in the Myanmar Extended block are adjusted to have the Khamti style. Introduction In the encoding of Khamti, Aiton and Phake, the decision was made to unify the dotted characters with their undotted forms. The differences were considered stylistic: Burmese Style Khamti Style က က Most Khamti, Aiton and Phake users living in Burma are also fluent in Burmese and Shan, and use those languages, as well as their own language, on a computer. In a plain text context (such as is most commonly used, including Facebook, SMS, email) where these languages are being used, the Burmese style of characters gets used exclusively. This is because it makes even less sense to view Burmese using Khamti style1 characters than to view Khamti using the dotless Burmese style. This has the effect of users rarely seeing their language written in an appropriate style.
  • Unicode Support in the Solaris Operating Environment

    Unicode Support in the Solaris Operating Environment

    Unicode Support in the Solaris Operating Environment Sun Microsystems, Inc. 901 San Antonio Road Palo Alto, CA 94303-4900 U.S.A. Part Number 806-5584 May 2000 Copyright 2000 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303-4900 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and SunTM Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
  • Extending TEX for Unicode

    Extending TEX for Unicode

    Extending TEXforUnicode Richard J. Kinch 6994 Pebble Beach Ct Lake Worth FL 33467 USA Telephone (561) 966-8400 FAX (561) 966-0962 [email protected] URL: http://styx.ios.com/~kinch Abstract TEX began its “childhood” with 7-bit-encoded fonts, and has entered adolescence with 8-bit encodings such as the Cork standard. Adulthood will require TEX to embrace 16-bit encoding standards such as Unicode. Omega has debuted as a well-designed extension of the TEX formatter to accommodate Unicode, but much new work remains to extend the fonts and DVI translation that make up the bulk of a complete TEX implementation. Far more than simply doubling the width of some variables, such an extension implies a massive reorganization of many components of TEX. We describe the many areas of development needed to bring TEX fully into multi-byte encoding. To describe and illustrate these areas, we introduce the r TrueTEX Unicode edition, which implements many of the extensions using the Windows Graphics Device Interface and TrueType scalable font technology. Integrating TEXandUnicode especially to a commercial product in an inter- national marketplace. You cannot use T X for long without discovering E • With access to Unicode fonts, the natural that character encoding is a big, messy issue in every ability of T X to process the large character sets implementation. The promise of Unicode, a 16-bit E of the Asian continent will be realized. Methods character-encoding standard [15, 14], is to clean up such as the Han unification will be accessible. the mess and simplify the issues.
  • Using Unicode Skywire Software, L.L.C

    Using Unicode Skywire Software, L.L.C

    Start Using Unicode Skywire Software, L.L.C. Phone: (U. S.) 972.377.1110 3000 Internet Boulevard (EMEA) +44 (0) 1372 366 200 Suite 200 FAX: (U. S.) 972.377.1109 Notice Frisco, Texas 75034 (EMEA) +44 (0) 1372 366 201 www.skywiresoftware.com Support: (U. S.) 866.4SKYWIRE (EMEA) +44 (0) 1372 366 222 [email protected] PUBLICATION COPYRIGHT NOTICE Copyright © 2008 Skywire Software, L.L.C. All rights reserved. Printed in the United States of America. This publication contains proprietary information which is the property of Skywire Software or its subsidiaries. This publication may also be protected under the copyright and trade secret laws of other countries. TRADEMARKS Skywire® is a registered trademark of Skywire Software, L.L.C. Docucorp®, its products (Docucreate™, Documaker™, Docupresentment™, Docusave®, Documanage™, Poweroffice®, Docutoolbox™, and Transall™) , and its logo are trademarks or registered trademarks of Skywire Software or its subsidiaries. The Docucorp product modules (Commcommander™, Docuflex®, Documerge®, Docugraph™, Docusolve®, Docuword™, Dynacomp®, DWSD™, DBL™, Freeform®, Grafxcommander™, Imagecreate™, I.R.I.S. ™, MARS/NT™, Powermapping™, Printcommander®, Rulecommander™, Shuttle™, VLAM®, Virtual Library Access Method™, Template Technology™, and X/HP™ are trademarks of Skywire Software or its subsidiaries. Skywire Software (or its subsidiaries) and Mynd Corporation are joint owners of the DAP™ and Document Automation Platform™ product trademarks. Docuflex is based in part on the work of Jean-loup Gailly and Mark Adler. Docuflex is based in part on the work of Sam Leffler and Silicon Graphic, Inc. Copyright © 1988-1997 Sam Leffler. Copyright © 1991-1997 Silicon Graphics, Inc. Docuflex is based in part on the work of the Independent JPEG Group.
  • Junicode, V. 0.6.5

    Junicode, V. 0.6.5

    Junicode, v. 0.6.5 Table of Contents What is Junicode?...............................................................................................................2 GNU General Public License..............................................................................................3 How the GNU General Public License Applies to Junicode..............................................11 How to install Junicode.....................................................................................................12 1. Microsoft Windows..................................................................................................12 2. Macintosh OS X.......................................................................................................12 3. Linux.......................................................................................................................12 Reading the Code Charts..................................................................................................12 Basic Latin (0000-007F)....................................................................................................14 Latin 1 Supplement (0080-00FF)......................................................................................15 Latin Extended A (0100-017F).........................................................................................16 Latin Extended B (0180-024F).........................................................................................17 IPA Extensions (0250-02AF)............................................................................................18
  • Introduction� � 1/9

    Introduction 1/9

    Jehol Diary: Introduction 1/9 Introduction 1. Editions This Yŏrhailgi ( 熱河日記 lit.Jehol Diary) editions comparisonis intendedtogaina standardcritical edition.The editions usedfor this aim can be divided intotwocatego ries. The ‘primary editions’ are important objects of studies in textual criticism. The most representative editions are selectedfrom the eachof all the three groups,whichare defined by Professor Kim Myŏngho ( 金明昊 http://skku.ac.kr/) in his published doc- toral dissertation(Kim 1990 see ‘References’ below ).The descriptions for the primary edi- tions below alsostem from it (pp.2843).Andthe ‘secondary editions’ are modernones, whichare basedonthe primaryeditions. The abbreviations for eacheditionconsisting of one capital letter like (C) or ( N) are givenbelow.Romanletters like (C) refer tothe ‘primary andsecondary editions’ and the ‘Korean translations’, whereas italic letters like (N) refer to ‘other editions men tionedinreferences andusedpartly for this comparison’.And (X) refers towhat I de- cide for or what I correct.Except these abbreviations capital letters are never usedfor searching convenience,eventhoughitviolatesEnglishorthography. 1.1. Primary editions 1. (C) Ch’ungnam Univ. edition ( 忠南大本/忠南大所藏筆寫本 ‘no year specification’ means ‘sine anno’): It is presumedtobe the closest editiontothe autograph andbe- longstothe “manuscriptgroup”( 草稿本系列).[pdf:http://clins.cnu.ac.kr/ ( 史.地理 類119)] 2. (K) Kwangmunhoe edition ( 光文會本/崔南善編新活字本 1911): The best-edited edition( 善本)inthemanuscriptgroup.[image:http://nl.go.kr/( 燕岩外集, 古0411/ 古25112530)] 3. (P) Pak Yŏngch’ŏl edition ( 朴榮喆本/朴榮喆編新活字本 1932): The best-edited editioninthe “modifiededitions group A” ( 改作A本系列).It seems tobe baseddi- rectly onthe standardor definitive edition( 定本). It is alsothe most circulatededi- tion.[html: http://minchu.or.kr/ ( 韓國文集叢刊 252); image: http://nl.go.kr/ ( 燕巖 集, 한古朝46가1145); book: http://staatsbibliothekberlin.de/ ( 北京圖書館出版社 1996,5A43946)] 4.
  • Unicode Latin and IPA Characters Version 0.41, February 17, 2011 / by Pim Rietbroek

    Unicode Latin and IPA Characters Version 0.41, February 17, 2011 / by Pim Rietbroek

    Alphabetic List of Unicode Latin and IPA Characters Version 0.41, February 17, 2011 / By Pim Rietbroek Instruments for Authors 1) Purpose of this document With the implementation of Unicode on practically every computer sold today we have gained access to a huge character set, which is also robust in that it transfers very well across computer programs and platforms. But finding a way to input a specific character carrying an accent or a diacritic, ḥ for instance, is sometimes not so easy. The character charts found on the Unicode website are for the most part not arranged alphabetically. And computer manufacturers have at the moment of this writing not supplied a generic input method or keyboard file that gives easy access to all Latin and IPA characters which are to be found in the Unicode Standard. In the absence of such solutions I have compiled an alphabetic list of Latin and IPA characters encoded in the Unicode Standard with their corresponding hexadecimal code point value (hexadecimal – or ‘base-16’ – numbers run from 0 to 9 and then up from A to F). 2) Accents and Diacritics: ‘Precomposed’ versus ‘Decomposed’ In the previous paragraph the word ‘character’ was used loosely to mean both a single letter like a and an accented letter like á. Without going into the details of the Unicode Standard it is important to note that while many accented letters are encoded as separate so-called ‘precomposed’ characters (like á) they are just as validly encoded in an analytic way (‘decomposed’) as ‘base letter plus combining diacritic(s)’, like a plus ◌́ (the latter character being ‘combining acute accent’, Unicode hexadecimal 0301; the dotted circle is only displayed here to show that the accent will be combined with the previous character).
  • Unicode for Linguists

    Unicode for Linguists

    Unicode for Linguists Kevin Scannell INNET Summer School Gniezno, Poland 4 September 2013 Encoding basics ● Encoding: a mapping characters ↔ numbers ● Computers are good at storing numbers! ● Encodings don't care how chars are input ● Also not concerned with how they're displayed ● No fonts, formatting, boldface, etc. – just text! ● “Modularity”; three independent layers ● Confusion in part b/c it was not always so ● (keyboards and fonts bundled together) Fonts ● Again, correctly-encoded text stands on its own ● Sure, fonts let you to render text on the screen ● But you have good wide-coverage fonts already ● There are some exceptions of course: ● I I I I I I I I I I I I I I I I ● And some fonts are buggy... ● Especially stacked diacritics, ligatures The Joy of Text ● Unicode encodes “plain text” (and no more) ● Plain text is portable across platforms ● Plain text is long-lived ● Plain text is the ultimate “open” format ● Plain text is indexed by Google, “discoverable” ● No proprietary tools needed to manipulate text ● Plain text is easily viewable, editable ● Allows you to bring powerful Unix tools to bear ● Even marked-up text like XML counts! Encodings: Some History ● ASCII (1963); A-Za-z, 0-9, etc., map to 0-127 ● EBCDIC (1964); mapping to 0-255 (w/ gaps) ● ISO 8859 series (1987-); 0-255, extend ASCII ● Big5 (1984); traditional Chinese ● Shift JIS; Japanese ● GB2312/18030; simplified Chinese ● Literally hundreds of others ● Why was this so terrible? Alphabet soup IBM1124, CP424, ISO_10367-BOX, ECMA-128, ISO8859-1, KOI-7, CSIBM1137,
  • Unihan Disambiguation Through Font Technology

    Unihan Disambiguation Through Font Technology

    Unicode Disambiguation Through Font Technology (Dirk Meyer) bc Unihan Disambiguation Through Font Technology Dirk Meyer CJKV Type Development Adobe Systems Incorporated 15th International Unicode Conference San Jose, CA, August/September 1999 15th International Unicode Conference 1 San Jose, CA, August/September 1999 Unicode Disambiguation Through Font Technology (Dirk Meyer) bc Overview • Short history of Unicode ’s CJK portion • Unihan ambiguity – the result of Han Unification • Fonts can help to solve the problem • Implementation: CID-keyed font • Implementation: OpenType (OTF) font • Summary Q&A 15th International Unicode Conference San Jose, CA, August/September 1999 “Unihan disambiguation” Through Font Technology The purpose of this presentation is to show how different font technologies (CID-keyed Font Technology, OpenType, etc.) can be applied to help resolving what is commonly called the “Unihan ambiguity problem.” The process of Han Unification can be considered to be one of the major “historical” achievements among the efforts to create Unicode. But developers are facing the problem of how to “disambiguate” the characters of the Basic Multilingual Plane’s (BMP) Unihan portion in the context of cross-locale Unicode fonts. In order to represent the Chinese characters of different Asian locales in a culturally adequate and typographically correct way with the help of Unicode, additional glyphs must be available in a font which shall be used across locale borders. Preliminary research shows that in such a “multi- locale” or “Pan-CJK” font, roughly 50 percent of the CJK characters need more than one glyph representation, depending on the typeface. Different approaches exist to make the additional glyphs available in fonts and how applications can get access to them.