A Character Sets and Collating Sequences

Total Page:16

File Type:pdf, Size:1020Kb

A Character Sets and Collating Sequences Character Sets and Collating Sequences ______________ A-l A CHARACTER SETS AND COLLATING SEQUENCES A.I Processor-Dependent Character Sets Default character type: The character set of the default character type contains at least all characters of the Fortran character set. In addition to the Fortran character set, a Fortran processor may support other representable cha­ racters, which may appear only in character literal constants, in character string edit descriptors, in comments, and in formatted records. The processor character set may contain control characters. Nondefault character type: If a Fortran processor supports in addition to the default character type one or more nondefault character types, the cha­ racters of such a nondefault character type may appear only in character literal constants of that type or in formatted records. In the last case, the types of the datum in the record and of the corresponding input/output list item must agree. One character in the character set of a nondefault character type is designated as the blank character; this blank character of the non default character type may be used as the padding character for formatted input. Collating sequence Each processor-dependent character set has its own collating sequence. The first character has position 0, the second has position 1, and so on. The ICHAR intrinsic function returns for a given character the position of this character in the processor-dependent collating sequence. For example, the function refe­ rence ICHAR(,X') returns the integer value 231 if the Fortran processor uses the EBCDIC character set. And conversely, the CHAR intrinsic function retu~ns for a given nonnegative integer value the character that corresponds to this given po- ~ sition in the processor-dependent collating sequence. For example, CHAR(231) returns the character 'X' if the EBCDIC character set is used. A.2 ASCII Character Set The ASCII character set is a standard character set. The International Fortran Standard refers to ISO/IEC 646:1991. With regard to letters, digits, and special characters of the Fortran character set, ISO/IEC 646:1991 and ANSI X3.4-1986, which is the US national vers;on of the ISO /IEC standard, are identical. An ASCII character is encoded by 7 bits. Therefore, a standard ASCII character set contains a total number of 128 characters. The first 32 characters (hex 00 to hex IF) of the ASCII character set are control characters and graphic characters. Nearly all other characters (hex 20 to hex 7E) are printable characters. A-2 _____________ Character Sets and Collating Sequences b7 0 0 1 1 b6 0 0 1 1 0 0 1 1 0 0 011 011 b5 01 1 01 1 1 1 Bits Control Symbols, Upper-case Lower-case b4 b3 b2 b1 Characters Digits Letters Letters 0 16 32 48 G4 80 9G 112 0 0 0 0 NUL DLE SP 0 @ P 0 o 10 20 20 40 30 GO 40 100 50 120 GO 140 70 P 1GO 1 17 33 49 G5 81 97 113 0 0 0 1 SOH DC1 ! 1 A Q a q 1 1 11 21 21 41 31 G1 41 101 51 121 G1 141 71 1G1 2 18 34 50 GG 82 98 114 0 0 1 0 STX DC2 " 2 B R b r 2 2 12 22 22 42 32 G2 42 102 52 122 G2 142 72 162 3 19 35 51 G7 83 99 115 0 0 1 1 ETX DC3 # 3 C S c S 3 3 13 23 23 43 33 G3 43 103 53 123 G3 143 73 IG3 4 20 3G 52 G8 84 100 11G 0 1 0 0 EOT DC4 $ 4 D T d t 4 4 14 24 24 44 34 G4 44 104 54 124 G4 144 74 1G4 5 21 37 53 G9 85 101 117 0 1 0 1 ENQ NAK % 5 E U e u 5 [) 15 25 25 45 35 G5 45 105 55 125 G5 145 75 1135 0 22 38 54 70 80 102 118 0 1 1 0 ACK SYN & 6 F V f v 0 o 10 20 20 40 3G 00 40 100 56 120 00 140 70 160 7 23 39 , [)5 71 87 103 119 0 1 1 1 BEL ETB 7 G W W 7 7 17 27 27 47 37 07 47 107 57 127 07 9 147 77 107 8 24 40 50 72 88 104 120 1 0 0 0 BS CAN ( 8 H X h x 8 10 18 30 28 50 38 70 48 110 58 130 08 150 78 170 D 25 41 57 73 89 105 121 1 0 0 1 HT EM ) 9 1 Y i 9 11 19 31 29 51 39 71 49 111 59 131 09 151 79 Y 171 10 20 42 58 74 90 100 122 1 0 1 0 LF SUB * J Z j Z A 12 1A 32 2A 52 3A 72 4A 112 5A 132 GA 152 7A 172 11 27 43 59 75 91 107 123 1 0 1 1 VT ESC , K [ k { B 13 18 33 2B + 53 38 73 4B 113 58 133 OB 153 7B 173 12 28 44 00 7G D2 108 124 1 1 0 0 FF FS , L I C 14 1C 34 2C 54 3C < 74 4C 114 5C \ 134 OC 154 7C I 174 13 20 45 01 77 93 100 125 1 1 0 1 CR GS - M ] m } D 15 1D 35 2D 55 3D = 75 4D 115 5D 135 OD 155 7D 175 14 30 4G G2 78 94 110 120 1 1 1 0 SO RS > N A n rv E 10 IE 30 2E 50 3E 7G 4E 110 5E 130 OE 150 7E 170 15 31 47 03 79 95 111 127 1 1 1 1 SI US / ? 0 0 DEL F 17 IF 37 2F 57 3F 77 4F 117 5F - 137 GF Hi7 7F 177 The IACHAR intrinsic function returns for a given character the position of this character in the ASCII collating sequence; IACHAR('X') returns the integer value 88. And the ACHAR intrinsic function returns for a given nonnegative integer value the character that corresponds to this given value in the ASCII collating sequence; ACHAR(88) returns the character 'X'. The intrinsic functions LGE, LGT, LLE, and LLT perform lexical comparisons of character strings on the basis of the ASCII collating sequence. Models for Numbers ___________________ B-1 B MODELS FOR NUMBERS The bit manipulation intrinsic subprograms, the numeric manipulation intrinsic functions, and the inquiry intrinsic functions are defined in terms of models for the representation of each kind of integer, real, or double precision real data implemented by the processor. These models are used to describe the charac­ teristics and the behaviour of the corresponding number sets of a particular type. A model has parameters which are chosen by the Fortran processor such that the model best fits the hardware. Note that these models do not dictate to the Fortran processor how it has to implement numbers and how they should behave, but the internal representation and the behaviour of the actually implemented numbers are described in terms of these (abstract) models. B.1 Models for Integers The models for integer data i are defined by: q i = s x l: Wk x r k - 1 k=l with Value Description s +1 or -1 sign r integer > 1 base q integer > 0 max. number of digits Wk each an integer with 0 ::; Wk < r digit The parameters r and q ~etermine the set of value~ of the integer model numbers. ~ Example: For model z = s X l:~~l Wk X 2k- 1 IS q = 31 and r = 2. ~ B.2 Models for Reals The models for real data x are defined by: B-2 ____________________ Models for Numbers with Value Description 8 +1 or -1 sign b integer > 1 base P integer> 1 max. number of digits fk each an integer with 0 S ik < b, digit but h > 0 e integer with emin S e S emax exponent The parameters b, p, emin, and emax determine the set of values of the (real) floating point model numbers. Example: For model x = {O e (/ ,,24 f -k) 8 X 2 x 1 2 + L..Jk=2 k X 2 ,-126 S e S 127 is b = 2, p = 24, emin = -126, and emax = 127. B.3 Models for Bit Manipulation Bit manipulations are performed on integer data. Therefore, a bit is defined as a binary digit w at position k of a nonnegative integer datum. The models for these integers are defined by: 5-1 j = :L Wk X 2k k=O with Value Description 8 integer > 0 maximal number of digits Wk each either 0 or 1 digit, bit The parameter 8 determines the set of values. Example: For model j = L~;O Wk X 2k is 8 = 32. It defines a model for integer data with 32 bits. The models for bit manipulation define that the integer datum is a sequence of 8 bits, which are numbered from the right to the left beginning with 0 for the rightmost bit and ending with (8 - 1) for the leftmost bit. These models apply only to the intrinsic subprograms for bit manipulation and bit inquiry. For all other purposes, the "normal" models for integer data must be used. Decremental Language Features _________________ (-1 C DECREMENTALFEATURES C.l Deleted Language Features The following deleted language features are not included in the normative part of the standard document but in its informative appendix.
Recommended publications
  • INTERSKILL MAINFRAME QUARTERLY December 2011
    INTERSKILL MAINFRAME QUARTERLY December 2011 Retaining Data Center Skills Inside This Issue and Knowledge Retaining Data Center Skills and Knowledge 1 Interskill Releases - December 2011 2 By Greg Hamlyn Vendor Briefs 3 This the final chapter of this four part series that briefly Taking Care of Storage 4 explains the data center skills crisis and the pros and cons of Learning Spotlight – Managing Projects 5 implementing a coaching or mentoring program. In this installment we will look at some of the steps to Tech-Head Knowledge Test – Utilizing ISPF 5 implementing a program such as this into your data center. OPINION: The Case for a Fresh Technical If you missed these earlier installments, click the links Opinion 6 below. TECHNICAL: Lost in Translation Part 1 - EBCDIC Code Pages 7 Part 1 – The Data Center Skills Crisis MAINFRAME – Weird and Unusual! 10 Part 2 – How Can I Prevent Skills Loss in My Data Center? Part 3 – Barriers to Implementing a Coaching or Mentoring Program should consider is the GROW model - Determine whether an external consultant should be Part Four – Implementing a Successful Coaching used (include pros and cons) - Create a basic timeline of the project or Mentoring Program - Identify how you will measure the effectiveness of the project The success of any project comes down to its planning. If - Provide some basic steps describing the coaching you already believe that your data center can benefit from and mentoring activities skills and knowledge transfer and that coaching and - Next phase if the pilot program is deemed successful mentoring will assist with this, then outlining a solid (i.e.
    [Show full text]
  • IPDS Technical Reference 1
    IPDS Technical Reference 1 TABLE OF CONTENTS Manuals for the IPDS card.................................................................................................................................4 Notice..................................................................................................................................................................5 Important.........................................................................................................................................................5 How to Read This Manual................................................................................................................................. 6 Symbols...........................................................................................................................................................6 About This Book..................................................................................................................................................7 Audience.........................................................................................................................................................7 Terminology.................................................................................................................................................... 7 About IPDS.......................................................................................................................................................... 8 Capabilities of IPDS............................................................................................................................................9
    [Show full text]
  • 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".
    [Show full text]
  • 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
    [Show full text]
  • Iso/Iec 8632-4:1999(E)
    This is a preview - click here to buy the full publication INTERNATIONAL ISO/IEC STANDARD 8632-4 Second edition 1999-12-01 Information technology — Computer graphics — Metafile for the storage and transfer of picture description information — Part 4: Clear text encoding Technologies de l'information — Infographie — Métafichier de stockage et de transfert des informations de description d'images — Partie 4: Codage en clair des textes Reference number ISO/IEC 8632-4:1999(E) © ISO/IEC 1999 ISO/IEC 8632-4:1999(E) This is a preview - click here to buy the full publication PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. © ISO/IEC 1999 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body in the country of the requester.
    [Show full text]
  • Database Globalization Support Guide
    Oracle® Database Database Globalization Support Guide 19c E96349-05 May 2021 Oracle Database Database Globalization Support Guide, 19c E96349-05 Copyright © 2007, 2021, Oracle and/or its affiliates. Primary Author: Rajesh Bhatiya Contributors: Dan Chiba, Winson Chu, Claire Ho, Gary Hua, Simon Law, Geoff Lee, Peter Linsley, Qianrong Ma, Keni Matsuda, Meghna Mehta, Valarie Moore, Cathy Shea, Shige Takeda, Linus Tanaka, Makoto Tozawa, Barry Trute, Ying Wu, Peter Wallack, Chao Wang, Huaqing Wang, Sergiusz Wolicki, Simon Wong, Michael Yau, Jianping Yang, Qin Yu, Tim Yu, Weiran Zhang, Yan Zhu This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S.
    [Show full text]
  • 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
    [Show full text]
  • IBM Data Conversion Under Websphere MQ
    IBM WebSphere MQ Data Conversion Under WebSphere MQ Table of Contents .................................................................................................................................................... 3 .................................................................................................................................................... 3 Int roduction............................................................................................................................... 4 Ac ronyms and terms used in Data Conversion........................................................................ 5 T he Pieces in the Data Conversion Puzzle............................................................................... 7 Coded Character Set Identifier (CCSID)........................................................................................ 7 Encoding .............................................................................................................................................. 7 What Gets Converted, and How............................................................................................... 9 The Message Descriptor.................................................................................................................... 9 The User portion of the message..................................................................................................... 10 Common Procedures when doing the MQPUT................................................................. 10 The message
    [Show full text]
  • Making the Most of Your Mainframe Data: from EBCDIC to ASCII
    Making the Most of Your Mainframe Data: From EBCDIC to ASCII Syncsort | Making the Most of Your Mainframe Data: From EBCDIC to ASCII Introduction Providing access to mainframe data in systems across your organization is unfortunately not as simple as a one-to-one database duplication. Mainframe data represents one of the most complex data formats found in enterprise systems, and as a result, many teams struggle with data integration projects for this crucial asset and fail to extract the maximum value from their mainframe data. Organizations that implement a data integration strategy that encompasses mainframe data see significant benefits. To make the most of your mainframe data and realize its full potential, it is vital that you take into consideration the human and technical challenges that can occur. By avoiding common pitfalls, you’ll be on the road to unlocking your mainframe data and receiving what is most important to your organization – maximum business value. Syncsort | Making the Most of Your Mainframe Data: From EBCDIC to ASCII 02 Mainframe Data is Still the Bedrock of your Business Despite the growth of next-wave technologies, mainframes will continue to play an essential role in many businesses. Mainframes have no peer when it comes to the volume of transactions they can handle. In fact, estimates are that 2.5 billion transactions are run per day, per mainframe across the world, and analysts estimate that more than 70% of Fortune 500 companies use mainframes at the core of their most valuable business systems. Mainframes contain the vital data that organizations run on, and in turn, they power initiatives that help move a business forward, such as machine learning, AI, and predictive analytics.
    [Show full text]
  • Onetouch 4.0 Sanned Documents
    TO: MSPM Distribution FROM: J. H. Saltzer SUBJECT: 88.3.02 DATE: 02/05/68 This revision of BB.3.02 is because 1. The ASCII standard character set has been approved. References are altered accordingly. 2. The latest proposed ASCII standard card code has been revised slightly. Since the Multics standard card code matches the ASCII standard wherever convenient# 88.3.02 is changed. Codes for the grave accent# left and right brace, and tilde are affected. 3. One misprint has been corrected; the code for capita 1 11 S" is changed. MULTICS SYSTEM-PROGRAMMERS' MANUAL SECTION BB.3.02 PAGE 1 Published: 02/05/68; (Supersedes: BB.3.02; 03/30/67; BC.2.06; 11/10/66) Identification Multics standard card punch codes and Relation between ASCII and EBCDIC J • H • Sa 1 tze r Purpose This section defines standard card punch codes to be used in representing ASCII characters for use with Multics. Since the card punch codes are based on the punch codes defined for the IBM EBCDIC standard, automatically a correspondence between the EBCDIC and ASCII character sets is also defined. Note The Multics standard card punch codes described in this section are DQ! identical to the currently proposed ASCII punched card code. The proposed ASCII standard code is not supported by any currently available punched card equipment; until such support exists it is not a practical standard for Multics work. The Multics standard card punch code described here is based on widely available card handling equipment used with IBM System/360 computers. The six characters for which the Multics standard card code differs with the ASCII card code are noted in the table below.
    [Show full text]
  • LG Programmer’S Reference Manual
    LG Programmer’s Reference Manual Line Matrix Series Printers Trademark Acknowledgements ANSI is a registered trademark of American National Standards Institute, Inc. Code V is a trademark of Quality Micro Systems. Chatillon is a trademark of John Chatillon & Sons, Inc. Ethernet is a trademark of Xerox Corporation. IBM is a registered trademark of International Business Machines Corporation. IGP is a registered trademark of Printronix, LLC. Intelligent Printer Data Stream and IPDS are trademarks of International Business Machines Corporation. LinePrinter Plus is a registered trademark of Printronix, LLC. MS-DOS is a registered trademark of Microsoft Corporation. PC-DOS is a trademark of International Business Machines Corporation. PGL is a registered trademark of Printronix, LLC. PrintNet is a registered trademark of Printronix, LLC. Printronix is a registered trademark of Printronix, LLC. PSA is a trademark of Printronix, LLC. QMS is a registered trademark of Quality Micro Systems. RibbonMinder is a trademark of Printronix, LLC. Torx is a registered trademark of Camcar/Textron Inc. Utica is a registered trademark of Cooper Power Tools. Printronix, LLC. makes no representations or warranties of any kind regarding this material, including, but not limited to, implied warranties of merchantability and fitness for a particular purpose. Printronix, LLC. shall not be held responsible for errors contained herein or any omissions from this material or for any damages, whether direct, indirect, incidental or consequential, in connection with the furnishing, distribution, performance or use of this material. The information in this manual is subject to change without notice. This document contains proprietary information protected by copyright. No part of this document may be reproduced, copied, translated or incorporated in any other material in any form or by any means, whether manual, graphic, electronic, mechanical or otherwise, without the prior written consent of Printronix, LLC.
    [Show full text]
  • Iso/Iec Jtc 1/Sc 2/ Wg 2 N ___Ncits-L2-98
    Unicode support in EBCDIC based systems ISO/IEC JTC 1/SC 2/ WG 2 N _______ NCITS-L2-98-257REV 1998-09-01 Title: EBCDIC-Friendly UCS Transformation Format -- UTF-8-EBCDIC Source: US, Unicode Consortium and V.S. UMAmaheswaran, IBM National Language Technical Centre, Toronto Status: For information and comment Distribution: WG2 and UTC Abstract: This paper defines the EBCDIC-Friendly Universal Multiple-Octet Coded Character Set (UCS) Transformation Format (TF) -- UTF-8-EBCDIC. This transform converts data encoded using UCS (as defined in ISO/IEC 10646 and the Unicode Standard defined by the Unicode Consortium) to and from an encoding form compatible with IBM's Extended Binary Coded Decimal Interchange Code (EBCDIC). This revised document incorporates the suggestions made by Unicode Technical Committee Meeting No. 77, on 31 July 98, and several editoiral changes. It is also being presented at the Internationalization and Unicode Conference no. 13, in San Jose, on 11 September 98. It has been accepted by the UTC as the basis for a Unicode Technical Report and is being distributed to SC 2/WG 2 for information and comments at this time. 13th International Unicode Conference 1 San Jose, CA, September 1998 Unicode support in EBCDIC based systems 1 Background UCS Transformation Format UTF-8 (defined in Amendment No. 2 to ISO/IEC 10646-1) is a transform for UCS data that preserves the subset of 128 ISO-646-IRV (ASCII) characters of UCS as single octets in the range X'00' to X'7F', with all the remaining UCS values converted to multiple-octet sequences containing only octets greater than X'7F'.
    [Show full text]