Inside ASCII
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
End-Of-Line Hyphenation of Chemical Names (IUPAC Provisional
Pure Appl. Chem. 2020; aop IUPAC Recommendations Albert J. Dijkstra*, Karl-Heinz Hellwich, Richard M. Hartshorn, Jan Reedijk and Erik Szabó End-of-line hyphenation of chemical names (IUPAC Provisional Recommendations) https://doi.org/10.1515/pac-2019-1005 Received October 16, 2019; accepted January 21, 2020 Abstract: Chemical names and in particular systematic chemical names can be so long that, when a manu- script is printed, they have to be hyphenated/divided at the end of a line. Many systematic names already contain hyphens, but sometimes not in a suitable division position. In some cases, using these hyphens as end-of-line divisions can lead to illogical divisions in print, as can also happen when hyphens are added arbi- trarily without considering the ‘chemical’ context. The present document provides recommendations and guidelines for authors of chemical manuscripts, their publishers and editors, on where to divide chemical names at the end of a line and instructions on how to avoid these names being divided at illogical places as often suggested by desk dictionaries. Instead, readability and chemical sense should prevail when authors insert optional hyphens. Accordingly, the software used to convert electronic manuscripts to print can now be programmed to avoid illogical end-of-line hyphenation and thereby save the author much time and annoy- ance when proofreading. The recommendations also allow readers of the printed article to determine which end-of-line hyphens are an integral part of the name and should not be deleted when ‘undividing’ the name. These recommendations may also prove useful in languages other than English. -
ISO Basic Latin Alphabet
ISO basic Latin alphabet The ISO basic Latin alphabet is a Latin-script alphabet and consists of two sets of 26 letters, codified in[1] various national and international standards and used widely in international communication. The two sets contain the following 26 letters each:[1][2] ISO basic Latin alphabet Uppercase Latin A B C D E F G H I J K L M N O P Q R S T U V W X Y Z alphabet Lowercase Latin a b c d e f g h i j k l m n o p q r s t u v w x y z alphabet Contents History Terminology Name for Unicode block that contains all letters Names for the two subsets Names for the letters Timeline for encoding standards Timeline for widely used computer codes supporting the alphabet Representation Usage Alphabets containing the same set of letters Column numbering See also References History By the 1960s it became apparent to thecomputer and telecommunications industries in the First World that a non-proprietary method of encoding characters was needed. The International Organization for Standardization (ISO) encapsulated the Latin script in their (ISO/IEC 646) 7-bit character-encoding standard. To achieve widespread acceptance, this encapsulation was based on popular usage. The standard was based on the already published American Standard Code for Information Interchange, better known as ASCII, which included in the character set the 26 × 2 letters of the English alphabet. Later standards issued by the ISO, for example ISO/IEC 8859 (8-bit character encoding) and ISO/IEC 10646 (Unicode Latin), have continued to define the 26 × 2 letters of the English alphabet as the basic Latin script with extensions to handle other letters in other languages.[1] Terminology Name for Unicode block that contains all letters The Unicode block that contains the alphabet is called "C0 Controls and Basic Latin". -
The Stata Journal
The Stata Journal View metadata, citation and similar papers at core.ac.uk brought to you by CORE Editor Executive Editor provided by Research Papers in Economics H. Joseph Newton Nicholas J. Cox Department of Statistics Department of Geography Texas A & M University University of Durham College Station, Texas 77843 South Road 979-845-3142; FAX 979-845-3144 Durham City DH1 3LE UK [email protected] [email protected] Associate Editors Christopher Baum J. Scott Long Boston College Indiana University Rino Bellocco Thomas Lumley Karolinska Institutet University of Washington, Seattle David Clayton Roger Newson Cambridge Inst. for Medical Research King’s College, London Mario A. Cleves Marcello Pagano Univ. of Arkansas for Medical Sciences Harvard School of Public Health Charles Franklin Sophia Rabe-Hesketh University of Wisconsin, Madison University of California, Berkeley Joanne M. Garrett J. Patrick Royston University of North Carolina MRC Clinical Trials Unit, London Allan Gregory Philip Ryan Queen’s University University of Adelaide James Hardin Mark E. Schaffer University of South Carolina Heriot-Watt University, Edinburgh Stephen Jenkins Jeroen Weesie University of Essex Utrecht University Jens Lauritsen Jeffrey Wooldridge Odense University Hospital Michigan State University Stanley Lemeshow Ohio State University Stata Press Production Manager Lisa Gilmore Copyright Statement: The Stata Journal and the contents of the supporting files (programs, datasets, and help files) are copyright c by StataCorp LP. The contents of the supporting files (programs, datasets, and help files) may be copied or reproduced by any means whatsoever, in whole or in part, as long as any copy or reproduction includes attribution to both (1) the author and (2) the Stata Journal. -
Unicode and Code Page Support
Natural for Mainframes Unicode and Code Page Support Version 4.2.6 for Mainframes October 2009 This document applies to Natural Version 4.2.6 for Mainframes and to all subsequent releases. Specifications contained herein are subject to change and these changes will be reported in subsequent release notes or new editions. Copyright © Software AG 1979-2009. All rights reserved. The name Software AG, webMethods and all Software AG product names are either trademarks or registered trademarks of Software AG and/or Software AG USA, Inc. Other company and product names mentioned herein may be trademarks of their respective owners. Table of Contents 1 Unicode and Code Page Support .................................................................................... 1 2 Introduction ..................................................................................................................... 3 About Code Pages and Unicode ................................................................................ 4 About Unicode and Code Page Support in Natural .................................................. 5 ICU on Mainframe Platforms ..................................................................................... 6 3 Unicode and Code Page Support in the Natural Programming Language .................... 7 Natural Data Format U for Unicode-Based Data ....................................................... 8 Statements .................................................................................................................. 9 Logical -
SAS 9.3 UTF-8 Encoding Support and Related Issue Troubleshooting
SAS 9.3 UTF-8 Encoding Support and Related Issue Troubleshooting Jason (Jianduan) Liang SAS certified: Platform Administrator, Advanced Programmer for SAS 9 Agenda Introduction UTF-8 and other encodings SAS options for encoding and configuration Other Considerations for UTF-8 data Encoding issues troubleshooting techniques (tips) Introduction What is UTF-8? . A character encoding capable of encoding all possible characters Why UTF-8? . Dominant encoding of the www (86.5%) SAS system options for encoding . Encoding – instructs SAS how to read, process and store data . Locale - instructs SAS how to present or display currency, date and time, set timezone values UTF-8 and other Encodings ASSCII (American Standard Code for Information Interchange) . 7-bit . 128 - character set . Examples (code point-char-hex): 32-Space-20; 63-?-3F; 64-@-40; 65-A-41 UTF-8 and other Encodings ISO 8859-1 (Latin-1) for Western European languages Windows-1252 (Latin-1) for Western European languages . 8-bit (1 byte, 256 character set) . Identical to asscii for the first 128 chars . Extended ascii chars examples: . 155-£-A3; 161- ©-A9 . SAS option encoding value: wlatin1 (latin1) UTF-8 and other Encodings UTF-8 and other Encodings Problems . Only covers English and Western Europe languages, ISO-8859-2, …15 . Multiple encoding is required to support national languages . Same character encoded differently, same code point represents different chars Unicode . Unicode – assign a unique code/number to every possible character of all languages . Examples of unicode points: o U+0020 – Space U+0041 – A o U+00A9 - © U+C3BF - ÿ UTF-8 and other Encodings UTF-8 . -
The Not So Short Introduction to Latex2ε
The Not So Short Introduction to LATEX 2ε Or LATEX 2ε in 139 minutes by Tobias Oetiker Hubert Partl, Irene Hyna and Elisabeth Schlegl Version 4.20, May 31, 2006 ii Copyright ©1995-2005 Tobias Oetiker and Contributers. All rights reserved. This document is free; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This document is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this document; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. Thank you! Much of the material used in this introduction comes from an Austrian introduction to LATEX 2.09 written in German by: Hubert Partl <[email protected]> Zentraler Informatikdienst der Universität für Bodenkultur Wien Irene Hyna <[email protected]> Bundesministerium für Wissenschaft und Forschung Wien Elisabeth Schlegl <noemail> in Graz If you are interested in the German document, you can find a version updated for LATEX 2ε by Jörg Knappen at CTAN:/tex-archive/info/lshort/german iv Thank you! The following individuals helped with corrections, suggestions and material to improve this paper. They put in a big effort to help me get this document into its present shape. -
Basis Technology Unicode対応ライブラリ スペックシート 文字コード その他の名称 Adobe-Standard-Encoding A
Basis Technology Unicode対応ライブラリ スペックシート 文字コード その他の名称 Adobe-Standard-Encoding Adobe-Symbol-Encoding csHPPSMath Adobe-Zapf-Dingbats-Encoding csZapfDingbats Arabic ISO-8859-6, csISOLatinArabic, iso-ir-127, ECMA-114, ASMO-708 ASCII US-ASCII, ANSI_X3.4-1968, iso-ir-6, ANSI_X3.4-1986, ISO646-US, us, IBM367, csASCI big-endian ISO-10646-UCS-2, BigEndian, 68k, PowerPC, Mac, Macintosh Big5 csBig5, cn-big5, x-x-big5 Big5Plus Big5+, csBig5Plus BMP ISO-10646-UCS-2, BMPstring CCSID-1027 csCCSID1027, IBM1027 CCSID-1047 csCCSID1047, IBM1047 CCSID-290 csCCSID290, CCSID290, IBM290 CCSID-300 csCCSID300, CCSID300, IBM300 CCSID-930 csCCSID930, CCSID930, IBM930 CCSID-935 csCCSID935, CCSID935, IBM935 CCSID-937 csCCSID937, CCSID937, IBM937 CCSID-939 csCCSID939, CCSID939, IBM939 CCSID-942 csCCSID942, CCSID942, IBM942 ChineseAutoDetect csChineseAutoDetect: Candidate encodings: GB2312, Big5, GB18030, UTF32:UTF8, UCS2, UTF32 EUC-H, csCNS11643EUC, EUC-TW, TW-EUC, H-EUC, CNS-11643-1992, EUC-H-1992, csCNS11643-1992-EUC, EUC-TW-1992, CNS-11643 TW-EUC-1992, H-EUC-1992 CNS-11643-1986 EUC-H-1986, csCNS11643_1986_EUC, EUC-TW-1986, TW-EUC-1986, H-EUC-1986 CP10000 csCP10000, windows-10000 CP10001 csCP10001, windows-10001 CP10002 csCP10002, windows-10002 CP10003 csCP10003, windows-10003 CP10004 csCP10004, windows-10004 CP10005 csCP10005, windows-10005 CP10006 csCP10006, windows-10006 CP10007 csCP10007, windows-10007 CP10008 csCP10008, windows-10008 CP10010 csCP10010, windows-10010 CP10017 csCP10017, windows-10017 CP10029 csCP10029, windows-10029 CP10079 csCP10079, windows-10079 -
JS Character Encodings
JS � Character Encodings Anna Henningsen · @addaleax · she/her 1 It’s good to be back! 2 ??? https://travis-ci.org/node-ffi-napi/get-symbol-from-current-process-h/jobs/641550176 3 So … what’s a character encoding? People are good with text, computers are good with numbers Text List of characters “Encoding” List of bytes List of integers 4 So … what’s a character encoding? People are good with text, computers are good with numbers Hello [‘H’,’e’,’l’,’l’,’o’] 68 65 6c 6c 6f [72, 101, 108, 108, 111] 5 So … what’s a character encoding? People are good with text, computers are good with numbers 你好! [‘你’,’好’] ??? ??? 6 ASCII 0 0x00 <NUL> … … … 65 0x41 A 66 0x42 B 67 0x43 C … … … 97 0x61 a 98 0x62 b … … … 127 0x7F <DEL> 7 ASCII ● 7-bit ● Covers most English-language use cases ● … and that’s pretty much it 8 ISO-8859-*, Windows code pages ● Idea: Usually, transmission has 8 bit per byte available, so create ASCII-extending charsets for more languages ISO-8859-1 (Western) ISO-8859-5 (Cyrillic) Windows-1251 (Cyrillic) (aka Latin-1) … … … … 0xD0 Ð а Р 0xD1 Ñ б С 0xD2 Ò в Т … … … … 9 GBK ● Idea: Also extend ASCII, but use 2-byte for Chinese characters … … 0x41 A 0x42 B … … 0xC4 0xE3 你 0xC4 0xE4 匿 … … 10 https://xkcd.com/927/ 11 Unicode: Multiple encodings! 4d c3 bc 6c 6c (UTF-8) U+004D M “Müll” U+00FC ü 4d 00 fc 00 6c 00 6c 00 (UTF-16LE) U+006C l U+006C l 00 4d 00 fc 00 6c 00 6c (UTF-16BE) 12 Unicode ● New idea: Don’t create a gazillion charsets, and drop 1-byte/2-byte restriction ● Shared character set for multiple encodings: U+XXXX with 4 hex digits, e.g. -
CONTENTS 1. Introduction...1 2. RPL Principles
CONTENTS 1. Introduction...................................... 1 2. RPL Principles.................................... 2 2.1 Origins..................................... 2 2.2 Mathematical Control........................ 3 2.3 Formal Definitions ......................... 5 2.4 Execution................................... 6 2.4.1 EVAL............................... 8 2.4.2 Data Class Objects................. 9 2.4.3 Identifier Class Objects........... 9 2.4.4 Procedure Class Objects............ 10 2.4.5 Object Skipover and SEMI........... 10 2.4.6 RPL Pointers....................... 11 2.5 Memory Management........................... 11 2.6 User RPL and System RPL..................... 13 2.7 Programming in System RPL................... 14 2.8 Sample RPL Program.......................... 16 2.8.1 The Source File.................... 16 2.8.2 Compiling the Program.............. 18 3. Object Structures................................. 19 3.1 Object Types................................ 19 3.1.1 Identifier Object.................. 19 3.1.2 Temporary Identifier Object........ 19 3.1.3 ROM Pointer Object................. 20 3.1.4 Binary Integer Object.............. 20 3.1.5 Real Number Object................. 20 3.1.6 Extended Real Number Object........ 21 3.1.7 Complex Number Object.............. 22 3.1.8 Extended Complex Number Object............................. 22 3.1.9 Array Object....................... 23 3.1.10 Linked Array Object................ 23 3.1.11 Character String Object............ 25 3.1.12 Hex String Object.................. 25 3.1.13 Character Object................... 25 3.1.14 Unit Object........................ 26 3.1.15 Code Object........................ 26 3.1.16 Primitive Code Object.............. 27 3.1.17 Program Object..................... 27 3.1.18 List Object........................ 28 3.1.19 Symbolic Object.................... 28 3.1.20 Directory Object................... 29 3.1.21 Graphics Object.................... 29 3.2 Terminology and Abbreviations............... 30 4. -
Solaris Internationalization Guide for Developers
Solaris Internationalization Guide For Developers Sun Microsystems, Inc. 901 San Antonio Road Palo Alto, CA 94303-4900 U.S.A. Part No: 805-4123–10 October 1998 Copyright 1998 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, SunDocs, Java, the Java Coffee Cup logo, 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. SunOS, Solaris, X11, SPARC, UNIX, PostScript, OpenWindows, AnswerBook, SunExpress, SPARCprinter, JumpStart, Xlib 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. -
Unicode Unicode
You are at: ALA.org » PLA » Professional Tools » PLA Tech Notes » Unicode Unicode By Richard W. Boss Unicode is an international character-encoding standard designed to support the electronic exchange, processing, storage, and display of the written texts of all of the world’s languages and scripts, including scientific, mathematical, and technical symbols. Unicode is an encoding standard, not a software program or a font. The standard is independent of operating systems, programming languages, database management systems, and hardware platforms. Before Unicode, there were hundreds of different encoding schemes; no single one could contain enough characters. The European Union alone required several for its languages. The Importance of Unicode for Libraries While academic libraries have had holdings in a number of languages and scripts for many decades, public libraries—as the result of the increasingly diverse communities that they serve-- have begun to purchase books in a wide variety of languages and scripts. There is hardly a metropolitan area in North America that does not have immigrants from a score of countries. Even public libraries in small communities are serving an increasing number of people for whom English is not their primary language. Unicode is also important for resource sharing. Libraries need to be able to borrow or lend materials in a wide variety of languages and scripts on behalf of patrons who cannot find what they need in their own libraries. The ability to send and receive bibliographic information among Unicode-conforming libraries is a major breakthrough. Even libraries that have no interest in Unicode for themselves should appreciate the fact that vendors of integrated library systems and other information technologies that support Unicode are able to market their products globally, therefore, strengthening them financially and making it possible to maintain aggressive product development programs. -
Nuts 'N' Bolts: Legal-Writing Mechanics—Part I Gerald Lebovits
University of Ottawa Faculty of Law (Civil Law Section) From the SelectedWorks of Hon. Gerald Lebovits June, 2009 Nuts 'n' Bolts: Legal-Writing Mechanics—Part I Gerald Lebovits Available at: https://works.bepress.com/gerald_lebovits/158/ JUNE 2009 VOL. 81 | NO. 5 JournalNEW YORK STATE BAR ASSOCIATION Attorney Web Sites Ethical Issues Are Only the Beginning Also in this Issue From the “Code” to the by Adam R. Bialek, Paris A. Gunther “Rules” and Scott M. Smedresman “Cohabitation” Clauses After Graev Avoiding IRS Tax Disputes 2008 Insurance Law – Part II THE LEGAL WRITER BY GERALD LEBOVITS GERALD LEBOVITS is a judge at the New York City Civil Court, Housing Part, in Manhattan and an adjunct professor at St. John’s University School of Law. For their research help on Parts I and II of this column, he thanks Alexandra Standish, his court attorney, and St. John’s University law student Jamie Bunyan. Judge Lebovits’s e-mail address is [email protected]. Nuts ’n’ Bolts: Legal-Writing Mechanics — Part I riting mechanics refers to unless all the pieces fit. Making your feet from the car.” Tanbook and Redbook writing details: numbers, nuts ’n’ bolts fit just right will assure an example: “The top law students earned Wnumerals, and figures; typo- accessible, comprehensible, and con- 2, 4, and 11 awards, respectively.” graphic symbols; abbreviations; italics sistent document. Don’t start a sentence with a fig- and underlining; and capitalizations. ure.11 Incorrect: “2009 marks the one- No one right way best tightens 1. Numbers, Numerals, and Figures year anniversary of his admission legal-writing nuts ’n’ bolts, but differ- A number is an abstract mathematical to the New York bar.” Correct: “Two ent authorities try.