DOCSLIB.ORG

ISO/IEC JTC1/SC22/WG20 N537 En

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
ISO/IEC JTC1/SC22/WG20 N537 En ISO/IEC JTC1/SC22/WG20 N537 en Date: 5 November 1997 ISO ORGANIZATION INTERNATIONALE DE NORMALISATION INTERNATIONAL ORGANIZATION FOR STANDARDIZATION МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ CEI (IEC) COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE INTERNATIONAL ELECTROTECHNICAL COMMISSION МЕЖДУНАРОДНАЯ ЗЛЕКТРОТЕХНИЧЕСКАЯ КОМИССИЯ Title: ISO/IEC FCD 14651 - International String Ordering - Method for comparing Character Strings and Description of the Common Template Tailorable Ordering Reference: SC22/WG20 N 527 (Disposition of comments on CD ballot) Source: Alain LaBonté, project editor Project: JTC1.22.30.02.02 Date: 1997-11-05 Status: To be sent for FCD ballot processing ISO/IEC CD 14651 Title ISO/IEC CD 14651 - International String Ordering - Method for comparing Character Strings and Description of the Common Template Tailorable Ordering [ISO/CEI CD 14651 - Classement international de chaînes de caractères - Méthode de comparaison de chaînes de caractères et description du modèle commun d’ordre de classement] Status: Final Committee Document Date: 1997-11-05 Project: 22.30.02.02 Editor: Alain LaBonté Gouvernement du Québec Secrétariat du Conseil du trésor Service de la prospective 875, Grande-Allée Est, 4C Québec, QC G1R 5R8 Canada GUIDE SHARE Europe SCHINDLER Information AG CH-6030 Ebikon (Bern) Switzerland Email: [email protected] 2 ISO/IEC CD 14651 Table of Contents: FOREWORD ...........................................................................................................................................4 INTRODUCTION.....................................................................................................................................4 1 SCOPE.................................................................................................................................................6 2 NORMATIVE REFERENCES ...............................................................................................................7 3 DEFINITIONS.......................................................................................................................................7 4 SYMBOLS AND ABBREVIATIONS ...................................................................................................10 5 REQUIREMENTS...............................................................................................................................10 5.1 Prehandling phase (external to the comparison operation API)........................................................................ 11 5.1.1 Prehandling of the symbolic table data..................................................................................................................... 11 5.1.2 Prehandling of character strings provided to the comparison operation API .............................................................. 11 5.2 Comparison operation API.............................................................................................................................. 12 5.2.1.1 Procedure 1 - Compare two character strings (COMPCAR)....................................................................................................................... 13 5.2.1.2 Procedure 2 - Compare two prefabricated bit strings (COMPBIN) ............................................................................................................ 15 5.2.1.3 Procedure 3 - Convert a character string to a comparable bit string (CARABIN)...................................................................................... 17 5.3 Multilevel key building..................................................................................................................................... 19 5.4 Table formation .............................................................................................................................................. 19 5.5 Common Template table (table 1)................................................................................................................... 19 6. CONFORMANCE ..............................................................................................................................19 7. DATA SPECIFICATION ....................................................................................................................21 7.1 Data specification........................................................................................................................................... 21 7.2 Tailoring Mechanism ...................................................................................................................................... 21 Example 1 of tailoring:..................................................................................................................................................... 21 Example 2 of tailoring:..................................................................................................................................................... 21 Example 3 of tailoring:..................................................................................................................................................... 22 NORMATIVE ANNEXES .......................................................................................................................23 Annex 1 (normative) International Common Template Table (Table 1).................................................................. 23 Annex 2 (normative) Benchmark..........................................................................................................................104 INFORMATIVE ANNEXES.................................................................................................................. 106 Annex A (informative) Tutorial on solutions brought by this standard to problems of lexical ordering ...................106 Annex B (informative) Prehandling and Posthandling..........................................................................................111 Description of the prehandling phase.............................................................................................................................. 111 Description of the Posthandling Phase............................................................................................................................ 112 Annex C (informative) Multilevel key building.....................................................................................................113 Preliminary considerations ............................................................................................................................................. 113 Assumptions ............................................................................................................................................................................................................113 Table sections and processing properties ................................................................................................................................................................113 Key composition ............................................................................................................................................................ 114 Formation of subkey level 1 through m minus 1 (level i; m=4 in the Common Template) ..................................................................................114 Formation of subkey level m (m=4 in the Common Template table)....................................................................................................................115 Formation of subkey level 5....................................................................................................................................................................................116 Posthandling ............................................................................................................................................................................................................116 Annex D (informative) - Principles of the comparison API ....................................................................................117 Annex E (informative) User needs calling for this standard..................................................................................118 3 ISO/IEC CD 14651 FOREWORD ISO (International Standards Organization) and IEC (International Electrotechnical Commission) form the specialized bodies for world-wide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees. These technical committees are established by the respective organization to deal with particular fields of mutual interest. In liaison with ISO and IEC, other international organizations, governmental and non-governmental, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee known as ISO/IEC JTC1. Draft International Standards adopted by the joint technical committee are circulated to the national bodies for voting. Publication as an international standard requires approval by at least 75% of the national bodies that cast a vote. The ISO/IEC 14651 International Standard has been prepared by the Joint Technical Committee ISO/IEC JTC1, Information Technology. INTRODUCTION This International standard provides a method for ordering text data worldwide, and provides a common template table whose tailoring eases adaptation of a specific script while retaining
Load more

Recommended publications
  • 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.
    [Show full text]
  • 5892 Cisco Category: Standards Track August 2010 ISSN: 2070-1721
    Internet Engineering Task Force (IETF) P. Faltstrom, Ed. Request for Comments: 5892 Cisco Category: Standards Track August 2010 ISSN: 2070-1721 The Unicode Code Points and Internationalized Domain Names for Applications (IDNA) Abstract This document specifies rules for deciding whether a code point, considered in isolation or in context, is a candidate for inclusion in an Internationalized Domain Name (IDN). It is part of the specification of Internationalizing Domain Names in Applications 2008 (IDNA2008). Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5892. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
    [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]
  • Kyrillische Schrift Für Den Computer
    Hanna-Chris Gast Kyrillische Schrift für den Computer Benennung der Buchstaben, Vergleich der Transkriptionen in Bibliotheken und Standesämtern, Auflistung der Unicodes sowie Tastaturbelegung für Windows XP Inhalt Seite Vorwort ................................................................................................................................................ 2 1 Kyrillische Schriftzeichen mit Benennung................................................................................... 3 1.1 Die Buchstaben im Russischen mit Schreibschrift und Aussprache.................................. 3 1.2 Kyrillische Schriftzeichen anderer slawischer Sprachen.................................................... 9 1.3 Veraltete kyrillische Schriftzeichen .................................................................................... 10 1.4 Die gebräuchlichen Sonderzeichen ..................................................................................... 11 2 Transliterationen und Transkriptionen (Umschriften) .......................................................... 13 2.1 Begriffe zum Thema Transkription/Transliteration/Umschrift ...................................... 13 2.2 Normen und Vorschriften für Bibliotheken und Standesämter....................................... 15 2.3 Tabellarische Übersicht der Umschriften aus dem Russischen ....................................... 21 2.4 Transliterationen veralteter kyrillischer Buchstaben ....................................................... 25 2.5 Transliterationen bei anderen slawischen
    [Show full text]
  • AIX Globalization
    AIX Version 7.1 AIX globalization IBM Note Before using this information and the product it supports, read the information in “Notices” on page 233 . This edition applies to AIX Version 7.1 and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2010, 2018. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this document............................................................................................vii Highlighting.................................................................................................................................................vii Case-sensitivity in AIX................................................................................................................................vii ISO 9000.....................................................................................................................................................vii AIX globalization...................................................................................................1 What's new...................................................................................................................................................1 Separation of messages from programs..................................................................................................... 1 Conversion between code sets.............................................................................................................
    [Show full text]
  • List of Approved Special Characters
    List of Approved Special Characters The following list represents the Graduate Division's approved character list for display of dissertation titles in the Hooding Booklet. Please note these characters will not display when your dissertation is published on ProQuest's site. To insert a special character, simply hold the ALT key on your keyboard and enter in the corresponding code. This is only for entering in a special character for your title or your name. The abstract section has different requirements. See abstract for more details. Special Character Alt+ Description 0032 Space ! 0033 Exclamation mark '" 0034 Double quotes (or speech marks) # 0035 Number $ 0036 Dollar % 0037 Procenttecken & 0038 Ampersand '' 0039 Single quote ( 0040 Open parenthesis (or open bracket) ) 0041 Close parenthesis (or close bracket) * 0042 Asterisk + 0043 Plus , 0044 Comma ‐ 0045 Hyphen . 0046 Period, dot or full stop / 0047 Slash or divide 0 0048 Zero 1 0049 One 2 0050 Two 3 0051 Three 4 0052 Four 5 0053 Five 6 0054 Six 7 0055 Seven 8 0056 Eight 9 0057 Nine : 0058 Colon ; 0059 Semicolon < 0060 Less than (or open angled bracket) = 0061 Equals > 0062 Greater than (or close angled bracket) ? 0063 Question mark @ 0064 At symbol A 0065 Uppercase A B 0066 Uppercase B C 0067 Uppercase C D 0068 Uppercase D E 0069 Uppercase E List of Approved Special Characters F 0070 Uppercase F G 0071 Uppercase G H 0072 Uppercase H I 0073 Uppercase I J 0074 Uppercase J K 0075 Uppercase K L 0076 Uppercase L M 0077 Uppercase M N 0078 Uppercase N O 0079 Uppercase O P 0080 Uppercase
    [Show full text]
  • Characters for Classical Latin
    Characters for Classical Latin David J. Perry version 13, 2 July 2020 Introduction The purpose of this document is to identify all characters of interest to those who work with Classical Latin, no matter how rare. Epigraphers will want many of these, but I want to collect any character that is needed in any context. Those that are already available in Unicode will be so identified; those that may be available can be debated; and those that are clearly absent and should be proposed can be proposed; and those that are so rare as to be unencodable will be known. If you have any suggestions for additional characters or reactions to the suggestions made here, please email me at [email protected] . No matter how rare, let’s get all possible characters on this list. Version 6 of this document has been updated to reflect the many characters of interest to Latinists encoded as of Unicode version 13.0. Characters are indicated by their Unicode value, a hexadecimal number, and their name printed IN SMALL CAPITALS. Unicode values may be preceded by U+ to set them off from surrounding text. Combining diacritics are printed over a dotted cir- cle ◌ to show that they are intended to be used over a base character. For more basic information about Unicode, see the website of The Unicode Consortium, http://www.unicode.org/ or my book cited below. Please note that abbreviations constructed with lines above or through existing let- ters are not considered separate characters except in unusual circumstances, nor are the space-saving ligatures found in Latin inscriptions unless they have a unique grammatical or phonemic function (which they normally don’t).
    [Show full text]
  • CEN WORKSHOP Agreementfinal Draft for CWA/MES:1998
    CEN WORKSHOP AGREEMENTFinal draft for CWA/MES:1998 1998-11-18 English version Information technology – Multilingual European Subsets in ISO/IEC 10646-1 Technologies de l’information – Informationstechnologie – Jeux partiels européens multilingues Mehrsprachige europäische Untermengen dans l’ISO/CEI 10646-1 in ISO/IEC 10646-1 This CEN Workshop Agreement has been drafted and approved by a Workshop of representatives of interested parties, whose names and affiliations can be obtained from the CEN/ISSS Secretariat. The formal process followed by the Workshop in the development of this Workshop Agreement has been endorsed by the National Members of CEN, but neither the National Members of CEN nor the CEN Central Secretariat can be held accountable for the technical content of this CEN Workshop Agreement or for possible conflicts with standards or legislation. This CEN Workshop Agreement can in no way be held as being an official standard developed by CEN and its Members. This CEN Workshop Agreement is publicly available, as a reference document, from the CEN Members National Standard Bodies. CEN Members are the National Standards Bodies of Austria, Belgium, the Czech Republic, Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Luxembourg, the Netherlands, Norway, Portugal, Spain, Sweden, Switzerland and the United Kingdom. CEN EUROPEAN COMMITTEE FOR STANDARDIZATION COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG Central Secretariat: rue de Stassart 36, B-1050 Brussels © CEN 1998 All rights of exploitation in any form and by any means reserved worldwide for CEN national Members Ref.No. CWA/MES:1998 E Information technology – Page 2 Multilingual European Subsets in ISO/IEC 10646-1 Final Draft for CWA/MES:1998 Contents Foreword 3 Introduction 4 1.
    [Show full text]
  • 1 Symbols (2286)
    1 Symbols (2286) USV Symbol Macro(s) Description 0009 \textHT <control> 000A \textLF <control> 000D \textCR <control> 0022 ” \textquotedbl QUOTATION MARK 0023 # \texthash NUMBER SIGN \textnumbersign 0024 $ \textdollar DOLLAR SIGN 0025 % \textpercent PERCENT SIGN 0026 & \textampersand AMPERSAND 0027 ’ \textquotesingle APOSTROPHE 0028 ( \textparenleft LEFT PARENTHESIS 0029 ) \textparenright RIGHT PARENTHESIS 002A * \textasteriskcentered ASTERISK 002B + \textMVPlus PLUS SIGN 002C , \textMVComma COMMA 002D - \textMVMinus HYPHEN-MINUS 002E . \textMVPeriod FULL STOP 002F / \textMVDivision SOLIDUS 0030 0 \textMVZero DIGIT ZERO 0031 1 \textMVOne DIGIT ONE 0032 2 \textMVTwo DIGIT TWO 0033 3 \textMVThree DIGIT THREE 0034 4 \textMVFour DIGIT FOUR 0035 5 \textMVFive DIGIT FIVE 0036 6 \textMVSix DIGIT SIX 0037 7 \textMVSeven DIGIT SEVEN 0038 8 \textMVEight DIGIT EIGHT 0039 9 \textMVNine DIGIT NINE 003C < \textless LESS-THAN SIGN 003D = \textequals EQUALS SIGN 003E > \textgreater GREATER-THAN SIGN 0040 @ \textMVAt COMMERCIAL AT 005C \ \textbackslash REVERSE SOLIDUS 005E ^ \textasciicircum CIRCUMFLEX ACCENT 005F _ \textunderscore LOW LINE 0060 ‘ \textasciigrave GRAVE ACCENT 0067 g \textg LATIN SMALL LETTER G 007B { \textbraceleft LEFT CURLY BRACKET 007C | \textbar VERTICAL LINE 007D } \textbraceright RIGHT CURLY BRACKET 007E ~ \textasciitilde TILDE 00A0 \nobreakspace NO-BREAK SPACE 00A1 ¡ \textexclamdown INVERTED EXCLAMATION MARK 00A2 ¢ \textcent CENT SIGN 00A3 £ \textsterling POUND SIGN 00A4 ¤ \textcurrency CURRENCY SIGN 00A5 ¥ \textyen YEN SIGN 00A6
    [Show full text]
  • Psftx-Centos-8.2/Pancyrillic.F16.Psfu Linux Console Font Codechart
    psftx-centos-8.2/pancyrillic.f16.psfu Linux console font codechart Glyphs 0x000 to 0x0FF 0 1 2 3 4 5 6 7 8 9 A B C D E F 0x00_ 0x01_ 0x02_ 0x03_ 0x04_ 0x05_ 0x06_ 0x07_ 0x08_ 0x09_ 0x0A_ 0x0B_ 0x0C_ 0x0D_ 0x0E_ 0x0F_ Page 1 Glyphs 0x100 to 0x1FF 0 1 2 3 4 5 6 7 8 9 A B C D E F 0x10_ 0x11_ 0x12_ 0x13_ 0x14_ 0x15_ 0x16_ 0x17_ 0x18_ 0x19_ 0x1A_ 0x1B_ 0x1C_ 0x1D_ 0x1E_ 0x1F_ Page 2 Font information 0x018 U+2191 UPWARDS ARROW Filename: psftx-centos-8.2/pancyrillic.f16.psfu 0x019 U+2193 DOWNWARDS ARROW PSF version: 1 0x01A U+2192 RIGHTWARDS ARROW Glyph size: 8 × 16 pixels Glyph count: 512 0x01B U+2190 LEFTWARDS ARROW Unicode font: Yes (mapping table present) 0x01C U+2039 SINGLE LEFT-POINTING ANGLE QUOTATION MARK Unicode mappings 0x01D U+2040 CHARACTER TIE 0x000 U+FFFD REPLACEMENT CHARACTER 0x01E U+25B2 BLACK UP-POINTING 0x001 U+2022 BULLET TRIANGLE 0x01F U+25BC BLACK DOWN-POINTING 0x002 U+25C6 BLACK DIAMOND, TRIANGLE U+2666 BLACK DIAMOND SUIT 0x020 U+0020 SPACE 0x003 U+2320 TOP HALF INTEGRAL 0x021 U+0021 EXCLAMATION MARK 0x004 U+2321 BOTTOM HALF INTEGRAL 0x022 U+0022 QUOTATION MARK 0x005 U+2013 EN DASH 0x023 U+0023 NUMBER SIGN 0x006 U+2014 EM DASH 0x024 U+0024 DOLLAR SIGN 0x007 U+2026 HORIZONTAL ELLIPSIS 0x025 U+0025 PERCENT SIGN 0x008 U+201A SINGLE LOW-9 QUOTATION MARK 0x026 U+0026 AMPERSAND 0x009 U+201E DOUBLE LOW-9 0x027 U+0027 APOSTROPHE QUOTATION MARK 0x00A U+2018 LEFT SINGLE QUOTATION 0x028 U+0028 LEFT PARENTHESIS MARK 0x029 U+0029 RIGHT PARENTHESIS 0x00B U+2019 RIGHT SINGLE QUOTATION MARK 0x02A U+002A ASTERISK 0x00C U+201C LEFT DOUBLE
    [Show full text]
  • Section 18.1, Han
    The Unicode® Standard Version 13.0 – Core Specification To learn about the latest version of the Unicode Standard, see http://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. © 2020 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 http://www.unicode.org/reporting.html. For information about the Unicode terms of use, please see http://www.unicode.org/copyright.html. The Unicode Standard / the Unicode Consortium; edited by the Unicode Consortium. — Version 13.0. Includes index. ISBN 978-1-936213-26-9 (http://www.unicode.org/versions/Unicode13.0.0/) 1.
    [Show full text]
  • Natural Functions Natural Functions
    Natural Functions Natural Functions Natural Functions This document describes various Software AG Natural functions whose names start with SAG and which were implemented as so-called User-Defined Functions; see User-Defined Functions in the Programming Guide. These Natural functions are delivered in the library SYSTEM on system file FNAT. Sample function calls are provided in the library SYSEXPG. URL Encoding Base64 Encoding URL Encoding Interfacing Natural applications with HTTP requests often requires that the URI (Uniform Resource Identifiers) is URL-encoded. The REQUEST DOCUMENT statement needs such a URL to access a document. URL-Encoding (or Percent-Encoding) is a mechanism to replace some special characters in parts of a URL. Only characters of the US-ASCII character set can be used to form a URL. Some characters of the US-ASCII character set have a special meaning when used in a URL - they are classified as "reserved" control characters, which structure the URL string into different semantic subcomponents. The quasi standard concerning the generic syntax of an URL is laid down in RFC3986, a document composed by the Internet community. It describes under which conditions the URL-Encoding is needed. This includes the representation of characters which are not inside the US-ASCII character set (for example, Euro sign), and it describes the use of reserved characters. Reserved characters are: ? = & # ! $ % ’ ( ) * + , / : ; @ [ ] Non reserved characters are: A-Z a-z 0-9 - _ . ~ A URL may only consist of reserved and non-reserved characters, other characters are not permitted. If other byte values are needed (which do not correspond to any of the reserved and non-reserved characters) or if reserved characters are used as data (which should not have a special semantic meaning in the URL context), they need to be translated into the "%-encoding" form - a percent sign, immediately followed by the two-digit hexadecimal representation of the code point, due to the Windows-1252 encoding scheme.
    [Show full text]