DOCSLIB.ORG

Specification Method for Cultural Conventions

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Reference number of working document: ISO/IEC JTC1/SC22/WG20 N690 Date: 1999-06-28 Reference number of document: ISO/IEC PDTR 14652 Committee identification: ISO/IEC JTC1/SC22 Secretariat: ANSI Information technology Ð Specification method for cultural conventions Technologies de l’information — Méthode de modélisation des conventions culturelles 1 Document type: International standard Document subtype: if applicable Document stage: (40) Enquiry Document language: E H:\IPS\SAMARIN\DISKETTE\BASICEN.DOT ISO Basic template Version 3.0 1997-02-03 ISO/IEC PDTR 14652:1999(E) © ISO/IEC 2 Contents Page 3 4 1 SCOPE 1 5 2 NORMATIVE REFERENCES 1 6 3 TERMS, DEFINITIONS AND NOTATIONS 2 7 4 FDCC-set 6 8 4.1 FDCC-set definition 6 9 4.2 LC_IDENTIFICATION 10 10 4.3 LC_CTYPE 11 11 4.4 LC_COLLATE 27 12 4.5 LC_MONETARY 42 13 4.6 LC_NUMERIC 46 14 4.7 LC_TIME 47 15 4.8 LC_MESSAGES 53 16 4.9 LC_PAPER 53 17 4.10 LC_NAME 55 18 4.11 LC_ADDRESS 57 19 4.12 LC_TELEPHONE 57 20 5 CHARMAP 58 21 6 REPERTOIREMAP 62 22 7 CONFORMANCE 89 23 Annex A (informative) DIFFERENCES FROM POSIX 90 24 Annex B (informative) RATIONALE 92 25 Annex C (informative) BNF GRAMMAR 106 26 Annex D (informative) INDEX 111 27 BIBLIOGRAPHY 114 ii © ISO/IEC ISO/IEC PDTR 14652:1999(E) 28 Foreword 29 30 ISO (the International Organization for Standardization) and IEC (the International 31 Electrotechnical Commission) form the specialized system for worldwide standardization. 32 National bodies that are members of ISO or IEC participate in the development of 33 International Standards through technical committees established by the respective 34 organization to deal with particular fields of technical activity. ISO and IEC technical 35 committees collaborate in fields of mutual interest. Other international organizations, 36 governmental and non-governmental, in liaison with ISO and IEC, also take part in the 37 work. In the field of information technology, ISO and IEC have established a joint 38 technical committee, ISO/IEC JTC 1. 39 40 The main task of a technical committee is to prepare International Standards but in 41 exceptional circumstances, the publication of a Technical Report of one of the following 42 types may be proposed: 43 44 - type 1, when the required support cannot be obtained for the publication of an 45 International Standard, despite repeated efforts; 46 47 - type 2, when the subject is still under technical development or where for any 48 other reason there is the future but not immediate possibility of an agreement on an 49 International Standard; 50 51 - type 3, when a technical committee has collected data of a different kind from 52 that which is normally published as an International Standard ("state of the art", for 53 example). 54 55 Technical Reports are drafted in accordance with the rules given in the ISO/IEC 56 Directives, Part 3. 57 58 Technical Reports of types 1 and 2 are subject to review within three years of publication, 59 to decide whether they can be transformed into International Standards. Technical Report 60 of type 3 do not necessarily have to be reviewed until the date they provide are considered 61 to be no longer valid or useful. 62 63 ISO/IEC TR 14652 is a Technical Report type 1, and it was prepared by Joint Technical 64 Committee ISO/IEC JTC 1, Information technology, Subcommittee 22, Programming 65 languages, their environments and system software interfaces. 66 67 The Annexes A, B, C and D of this Technical Report are for information only. iii ISO/IEC PDTR 14652:1999(E) © ISO/IEC 68 Introduction 69 70 This Technical Report defines a general mechanism to specify cultural conventions, and it 71 defines formats for a number of specific cultural conventions in the areas of character 72 classification and conversion, sorting, number formatting, monetary formatting, date 73 formatting, message display, paper formats, addressing of persons, postal address 74 formatting, telephone number handling, and a way to specify how much is covered and the 75 status of it. 76 77 There are a number of benefits coming from this standard: 78 79 Rigid specification Using this Technical Report, a user can rigidly specify a 80 number of the cultural conventions that apply to the 81 information technology environment of the user. 82 83 Cultural adaptability If an application has been designed and built in a 84 cultural neutral manner, the application may use the 85 specifications as data to its APIs, and thus the same 86 application may accommodate different users in a 87 culturally acceptable way to each of the users, without 88 change of the binary application. 89 90 Productivity This standard specifies those cultural conventions and 91 how to specify data for them. With those data an 92 application developer is relieved from getting the 93 different information to support all the cultural 94 environments for the expected customers of the product. 95 The application developer is thus ensured of culturally 96 correct behavior as specified by the customer, and 97 possibly more markets may be reached as customers may 98 have the possibility to provide the data themselves for 99 markets that were not targeted. 100 101 Uniform behaviour When a number of applications share one cultural 102 specification, which may be supplied from the user or a 103 built-in nature, their behaviour for cultural adaptation 104 become uniform. 105 106 The specification format is independent of platforms and specific encoding, and targeted to 107 be usable from a wide range of programming languages. 108 109 A number of cultural conventions, such as spelling, hyphenation rules and terminology, are 110 not specifiable with this standard, but the standard provides mechanisms to define new 111 categories and also new keywords within existing categories. An internationalized 112 application may take advantage of information provided with the FDCC-set (such as the 113 language) to provide further internationalized services to the user. 114 115 This Technical Report defines a format compatible with the one used in the International 116 String Ordering standard, ISO/IEC 14651. This Technical Report is backwards compatible 117 with the ISO/IEC 9945-2:1993 POSIX shell and utilities standard, particulary its clauses iv © ISO/IEC ISO/IEC PDTR 14652:1999(E) 118 2.4 and 2.5. The major extensions from that text are listed in annex A. This Technical 119 Report has enhanced functionality in a number of areas such as ISO/IEC 10646 support, 120 more classification of characters, transliteration, dual (multi) currency support, enhanced 121 date and time formatting, paper size identification, personal name writing, postal address 122 formatting, telephone number handling, and management of categories. There is enhanced 123 support for character sets including ISO/IEC 2022 handling and an enhanced method to 124 separate the specification of cultural conventions from an actual encoding via a description 125 of the character repertoire employed. A standard set of values for all the categories has 126 been defined covering the repertoire of ISO/IEC 10646-1. 127 v TECHNICAL REPORT © ISO/IEC ISO/IEC PDTR 14652:1999(E) 128 Information technology Ð Specification method for cultural 129 conventions 130 131 1 SCOPE 132 133 This Technical Report specifies a description format for the specification of cultural 134 conventions, a description format for character sets, and a description format for binding 135 character names to ISO/IEC 10646, plus a set of default values for some of these items. 136 137 The specification is upward compatible with POSIX locale specifications - a locale 138 conformant to POSIX specifications will also be conformant to the specifications in this 139 Standard, while the reverse condition will not hold. The descriptions are intended to be 140 coded in text files to be used via Application Programming Interfaces, that are expected to 141 be developed for a number of programming languages. 142 143 2 NORMATIVE REFERENCES 144 145 The following normative documents contain provisions which, through reference in this 146 text, constitute provisions of this Technical Report. For dated references, subsequent 147 amendments to, or revisions of, any of these publications do not apply. However, parties 148 to agreements based on this Technical Report are encouraged to investigate the possibility 149 of applying the most recent editions of the normative documents indicated below. For 150 undated references, the latest edition of the normative document referred to applies. 151 Members of ISO and IEC maintain registers of currently valid Technical Reports. 152 153 ISO 639 (all parts), Codes for the representation of names of languages. 154 155 ISO/IEC 2022, Information technology - Character code structure and extension tech- 156 niques. 157 158 ISO 3166 (all parts), Codes for the representation of names of countries and their 159 subdivisions. 160 161 ISO 4217, Codes for the representation of currencies and funds. 162 163 ISO 8601, Data elements and interchange formats - Information interchange - Represen- 164 tation of dates and times. 165 166 ISO/IEC 9945-2:1993, Information technology - Portable Operating System Interface 167 (POSIX) - Part 2: Shell and Utilities. 168 169 ISO/IEC 10646-1:1993, Information technology - Universal Multiple-Octet Coded Cha- 170 racter Set (UCS) - Part 1: Architecture and Basic Multilingual Plane (including Cor.1 and 171 AMD 1-9). 172 173 ISO/IEC 14651, Information technology - International string ordering - Method for 174 comparing character strings and description of a default tailorable ordering. 175 176 ISO/IEC 15897:1999, Information technology - Procedures for registration of cultural 177 conventions. 1 ISO/IEC PDTR 14652:1999(E) © ISO/IEC 178 179 3 TERMS, DEFINITIONS AND NOTATIONS 180 181 3.1 Terms and definitions 182 183 For the purposes of this Technical Report, the terms and definitions given in the following 184 apply.
Recommended publications
  • Teemtalk® 5.0 for Windows CE & Xpe User's Guide

    Teemtalk® 5.0 for Windows CE & Xpe User's Guide

    TeemTalk® 5.0 for Windows CE & XPe User's Guide USA Neoware, Inc. 3200 Horizon Drive King of Prussia, PA 19406 Tel: +1-610-277-8300 Fax: +1-610-771-4200 Email: [email protected] UK Neoware UK Ltd The Stables, Cosgrove Milton Keynes MK19 7JJ Tel: +44 (0) 1908 267111 Fax: +44 (0) 1908 267112 Email: [email protected] TeemTalk Software Support Telephone: +1-610-277-8300 Web: http://www.neoware.com/support/ Software Version 5.0.1 October 2004 Neoware UK Ltd, The Stables, Cosgrove, Milton Keynes, MK19 7JJ Tel: +44 (0) 1908 267111 Fax: +44 (0) 1908 267112 TeemTalk © 1988-2004 Neoware UK Ltd, All Rights Reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/) This product includes cryptographic software written by Eric Young ([email protected]) The material in this manual is for information purposes only and is subject to change without notice. Neoware UK Ltd accepts no responsibility for any errors contained herein. Trademarks TeemTalk is a registered trademark of Neoware UK Ltd. ADDS Viewpoint A2 is a trademark of Applied Digital Data Systems Inc. AIX is a registered trademark of International Business Machines Corporation. D100, D200 and D410 are trademarks of Data General. Dataspeed is a registered trademark of AT&T. DEC, VT52, VT100, VT131, VT220, VT300, VT320 and VT340 are registered trademarks of Digital Equipment Corporation. Hazeltine is a trademark of Esprit Systems, Inc. HP700/92, HP700/94, HP700/96, HP2392A and HP2622A are trademarks of Hewlett Packard Company. IBM is a registered trademark of International Business Machines Corporation.
  • IBM Db2 High Performance Unload for Z/OS User's Guide

    IBM Db2 High Performance Unload for Z/OS User's Guide

    5.1 IBM Db2 High Performance Unload for z/OS User's Guide IBM SC19-3777-03 Note: Before using this information and the product it supports, read the "Notices" topic at the end of this information. Subsequent editions of this PDF will not be delivered in IBM Publications Center. Always download the latest edition from the Db2 Tools Product Documentation page. This edition applies to Version 5 Release 1 of Db2 High Performance Unload for z/OS (product number 5655-AA1) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM® Corporation 1999, 2021; Copyright Infotel 1999, 2021. All Rights Reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. © Copyright International Business Machines Corporation . US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this information......................................................................................... vii Chapter 1. Db2 High Performance Unload overview................................................ 1 What does Db2 HPU do?..............................................................................................................................1 Db2 HPU benefits.........................................................................................................................................1 Db2 HPU process and components.............................................................................................................2
  • Technical Reference Manual for the Standardization of Geographical Names United Nations Group of Experts on Geographical Names

    Technical Reference Manual for the Standardization of Geographical Names United Nations Group of Experts on Geographical Names

    ST/ESA/STAT/SER.M/87 Department of Economic and Social Affairs Statistics Division Technical reference manual for the standardization of geographical names United Nations Group of Experts on Geographical Names United Nations New York, 2007 The Department of Economic and Social Affairs of the United Nations Secretariat is a vital interface between global policies in the economic, social and environmental spheres and national action. The Department works in three main interlinked areas: (i) it compiles, generates and analyses a wide range of economic, social and environmental data and information on which Member States of the United Nations draw to review common problems and to take stock of policy options; (ii) it facilitates the negotiations of Member States in many intergovernmental bodies on joint courses of action to address ongoing or emerging global challenges; and (iii) it advises interested Governments on the ways and means of translating policy frameworks developed in United Nations conferences and summits into programmes at the country level and, through technical assistance, helps build national capacities. NOTE The designations employed and the presentation of material in the present publication do not imply the expression of any opinion whatsoever on the part of the Secretariat of the United Nations concerning the legal status of any country, territory, city or area or of its authorities, or concerning the delimitation of its frontiers or boundaries. The term “country” as used in the text of this publication also refers, as appropriate, to territories or areas. Symbols of United Nations documents are composed of capital letters combined with figures. ST/ESA/STAT/SER.M/87 UNITED NATIONS PUBLICATION Sales No.
  • Combining Diacritical Marks Range: 0300–036F the Unicode Standard

    Combining Diacritical Marks Range: 0300–036F the Unicode Standard

    Combining Diacritical Marks Range: 0300–036F The Unicode Standard, Version 4.0 This file contains an excerpt from the character code tables and list of character names for The Unicode Standard, Version 4.0. Characters in this chart that are new for The Unicode Standard, Version 4.0 are shown in conjunction with any existing characters. For ease of reference, the new characters have been highlighted in the chart grid and in the names list. This file will not be updated with errata, or when additional characters are assigned to the Unicode Standard. See http://www.unicode.org/charts for access to a complete list of the latest character charts. Disclaimer These charts are provided as the on-line reference to the character contents of the Unicode Standard, Version 4.0 but do not provide all the information needed to fully support individual scripts using the Unicode Standard. For a complete understanding of the use of the characters contained in this excerpt file, please consult the appropriate sections of The Unicode Standard, Version 4.0 (ISBN 0-321-18578-1), as well as Unicode Standard Annexes #9, #11, #14, #15, #24 and #29, the other Unicode Technical Reports and the Unicode Character Database, which are available on-line. See http://www.unicode.org/Public/UNIDATA/UCD.html and http://www.unicode.org/unicode/reports A thorough understanding of the information contained in these additional sources is required for a successful implementation. Fonts The shapes of the reference glyphs used in these code charts are not prescriptive. Considerable variation is to be expected in actual fonts.
  • Regular Expressions in Jlex to Define a Token in Jlex, the User to Associates a Regular Expression with Commands Coded in Java

    Regular Expressions in Jlex to Define a Token in Jlex, the User to Associates a Regular Expression with Commands Coded in Java

    Regular Expressions in JLex To define a token in JLex, the user to associates a regular expression with commands coded in Java. When input characters that match a regular expression are read, the corresponding Java code is executed. As a user of JLex you don’t need to tell it how to match tokens; you need only say what you want done when a particular token is matched. Tokens like white space are deleted simply by having their associated command not return anything. Scanning continues until a command with a return in it is executed. The simplest form of regular expression is a single string that matches exactly itself. © CS 536 Spring 2005 109 For example, if {return new Token(sym.If);} If you wish, you can quote the string representing the reserved word ("if"), but since the string contains no delimiters or operators, quoting it is unnecessary. For a regular expression operator, like +, quoting is necessary: "+" {return new Token(sym.Plus);} © CS 536 Spring 2005 110 Character Classes Our specification of the reserved word if, as shown earlier, is incomplete. We don’t (yet) handle upper or mixed- case. To extend our definition, we’ll use a very useful feature of Lex and JLex— character classes. Characters often naturally fall into classes, with all characters in a class treated identically in a token definition. In our definition of identifiers all letters form a class since any of them can be used to form an identifier. Similarly, in a number, any of the ten digit characters can be used. © CS 536 Spring 2005 111 Character classes are delimited by [ and ]; individual characters are listed without any quotation or separators.
  • Agricultural Soil Carbon Credits: Making Sense of Protocols for Carbon Sequestration and Net Greenhouse Gas Removals

    Agricultural Soil Carbon Credits: Making Sense of Protocols for Carbon Sequestration and Net Greenhouse Gas Removals

    Agricultural Soil Carbon Credits: Making sense of protocols for carbon sequestration and net greenhouse gas removals NATURAL CLIMATE SOLUTIONS About this report This synthesis is for federal and state We contacted each carbon registry and policymakers looking to shape public marketplace to ensure that details investments in climate mitigation presented in this report and through agricultural soil carbon credits, accompanying appendix are accurate. protocol developers, project developers This report does not address carbon and aggregators, buyers of credits and accounting outside of published others interested in learning about the protocols meant to generate verified landscape of soil carbon and net carbon credits. greenhouse gas measurement, reporting While not a focus of the report, we and verification protocols. We use the remain concerned that any end-use of term MRV broadly to encompass the carbon credits as an offset, without range of quantification activities, robust local pollution regulations, will structural considerations and perpetuate the historic and ongoing requirements intended to ensure the negative impacts of carbon trading on integrity of quantified credits. disadvantaged communities and Black, This report is based on careful review Indigenous and other communities of and synthesis of publicly available soil color. Carbon markets have enormous organic carbon MRV protocols published potential to incentivize and reward by nonprofit carbon registries and by climate progress, but markets must be private carbon crediting marketplaces. paired with a strong regulatory backing. Acknowledgements This report was supported through a gift Conservation Cropping Protocol; Miguel to Environmental Defense Fund from the Taboada who provided feedback on the High Meadows Foundation for post- FAO GSOC protocol; Radhika Moolgavkar doctoral fellowships and through the at Nori; Robin Rather, Jim Blackburn, Bezos Earth Fund.
  • Chapter 4 Formatting Text Copyright

    Chapter 4 Formatting Text Copyright

    Writer 6.0 Guide Chapter 4 Formatting Text Copyright This document is Copyright © 2018 by the LibreOffice Documentation Team. Contributors are listed below. You may distribute it and/or modify it under the terms of either the GNU General Public License (http://www.gnu.org/licenses/gpl.html), version 3 or later, or the Creative Commons Attribution License (http://creativecommons.org/licenses/by/4.0/), version 4.0 or later. All trademarks within this guide belong to their legitimate owners. Contributors Jean Hollis Weber Bruce Byfield Gillian Pollack Acknowledgments This chapter is updated from previous versions in the LibreOffice Writer Guide. Contributors to earlier versions are: Jean Hollis Weber John A. Smith Hazel Russman John M. Długosz Ron Faile Jr. Figure 4 is from Bruce Byfield’s Designing with LibreOffice. This chapter is adapted from part of Chapter 3 of the OpenOffice.org 3.3 Writer Guide. The contributors to that chapter are: Jean Hollis Weber Agnes Belzunce Daniel Carrera Laurent Duperval Katharina Greif Peter Hillier-Brook Michael Kotsarinis Peter Kupfer Iain Roberts Gary Schnabl Barbara M. Tobias Michele Zarri Sharon Whiston Feedback Please direct any comments or suggestions about this document to the Documentation Team’s mailing list: [email protected] Note Everything you send to a mailing list, including your email address and any other personal information that is written in the message, is publicly archived and cannot be deleted. Publication date and software version Published July 2018. Based on LibreOffice 6.0. Note for macOS users Some keystrokes and menu items are different on macOS from those used in Windows and Linux.
  • The Not So Short Introduction to Latex2ε

    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.
  • Database Globalization Support Guide

    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.
  • AVR244 AVR UART As ANSI Terminal Interface

    AVR244 AVR UART As ANSI Terminal Interface

    AVR244: AVR UART as ANSI Terminal Interface Features 8-bit • Make use of standard terminal software as user interface to your application. • Enables use of a PC keyboard as input and ascii graphic to display status and control Microcontroller information. • Drivers for ANSI/VT100 Terminal Control included. • Interactive menu interface included. Application Note Introduction This application note describes some basic routines to interface the AVR to a terminal window using the UART (hardware or software). The routines use a subset of the ANSI Color Standard to position the cursor and choose text modes and colors. Rou- tines for simple menu handling are also implemented. The routines can be used to implement a human interface through an ordinary termi- nal window, using interactive menus and selections. This is particularly useful for debugging and diagnostics purposes. The routines can be used as a basic interface for implementing more complex terminal user interfaces. To better understand the code, an introduction to ‘escape sequences’ is given below. Escape Sequences The special terminal functions mentioned (e.g. text modes and colors) are selected using ANSI escape sequences. The AVR sends these sequences to the connected terminal, which in turn executes the associated commands. The escape sequences are strings of bytes starting with an escape character (ASCII code 27) followed by a left bracket ('['). The rest of the string decides the specific operation. For instance, the command '1m' selects bold text, and the full escape sequence thus becomes 'ESC[1m'. There must be no spaces between the characters, and the com- mands are case sensitive. The various operations used in this application note are described below.
  • 5892 Cisco Category: Standards Track August 2010 ISSN: 2070-1721

    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.
  • Czech and Slovak Typesetting Rules

    Czech and Slovak Typesetting Rules

    Czech and Slovak Typesetting Rules Tomáš Hála Mendel University in Brno, CZ BachoTEX 2019 Czech and Slovak Typesetting Rules Selected sources − ON 88 2503:1974 − Pop, Flégr and Pop: Sazba I [Typesetting I], 1989 (textbook) − ČSN 01 6910:2007 and older − ČSN 01 6910:2011 − STN 01 6910:2011 − Pravidla českého pravopisu [Rules of Czech Ortography], 1987, − Pravidla českého pravopisu [Rules of Czech Ortography], 1993 − Pravidlá slovenského pravopisu [Rules of Slovak Ortography], 1993, 2000 2 Czech and Slovak Typesetting Rules Spaces intersentence spacing interword space non-breaking interword space thin space 3 Czech and Slovak Typesetting Rules Spaces between sentences intersentence spacing % Czech, Slovak \frenchspacing % English (American) \nonfrenchspacing 4 Czech and Slovak Typesetting Rules Spaces between sentences intersentence spacing % ConTeXt \installlanguage [\s!en] [\c!spacing=\v!broad, ... \installlanguage [\s!cs] [\c!spacing=\v!packed, ... 5 Czech and Slovak Typesetting Rules Dashes: punctuation usage en-dash XOR em-dash en-dash v em-dash: designer’s opinion dashes v spaces: semanticising usage 6 Czech and Slovak Typesetting Rules Dashes: punctuation usage dashes must not open the new line \def\ip{\pdash} % Czech, Slovak \def\pdash{~-- } 7 Czech and Slovak Typesetting Rules Dashes: interval usage Czech and Slovak ∘ 35–45 %, 5–8 C English ∘ ∘ 35%–45%, 5 C–15 C, 70–72 percent %Czech and Slovak \def\idash{\discretionary{\char32až}{}{--}} \def\az{\idash} %English \def\idash{\discretionary{\char32to}{}{--}} 8 Czech and Slovak Typesetting