DOCSLIB.ORG

Conference at a Glance

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Conference at a Glance Conference At A Glance | Home | Session Descriptions | Speakers' Bios | Register | Hotel | | Become A Sponsor | Become An Exhibitor | Advisory Committee | Program Committee | Monday, October 18, 2010 TUTORIALS Track 1 Track 2 Track 3 An Introduction to Writing Internationalization: Internationalization Morning Systems & Unicode An Introduction, Part in Database Drivers I: Character for Your Applications Encodings and SESSION 1 Unicode 09:00 – Richard Ishida Sumit Sarkar Internationalization Addison Phillips i18n Product 10:30 Lead Globalization Specialist W3C Architect Lab126 (Amazon) 10:30 - 10:45 Morning Refreshments An Introduction to Writing Internationalization: What's that Morning Systems & Unicode (Cont’d.) An Introduction, Part Gobbledygook in the II: Enabling URL? Software SESSION 2 Richard Ishida 10:45 – Addison Phillips Ram Viswanadha 12:30 Internationalization Globalization Internationalization Lead Architect Architect W3C Lab126 Yahoo! (Amazon) 12:30 - 13:30 Lunch Unicode - A Grand Tour Web Building Multilingual Afternoon Internationalization - Websites in Drupal Standards and Best and Joomla Practices SESSION 1 Craig R. Cummings Jim DeLaHunt 13:30 – Michael G McKenna Tex Texin Principal 15:30 Internationalization Xen Master Jim DeLaHunt & Architects XenCraft\ Associates Yahoo! Inc. 15:30 – 15:45 Afternoon Refreshments Unicode - A Grand Tour Developing World Using ICU Workshop Afternoon (cont'd.) Ready Applications for Smart Devices SESSION 2 Craig Rublee John Emmons 15:45 – Sr. Globalization Senior Software 17:45 Architect Engineer Adobe Systems, IBM Inc. 18:00-19:00 Welcome Reception Tuesday, October 19, 2010 09:00 - 9:15 Welcome & Opening Remarks 09:15 – 10:00 KEYNOTE PRESENTATION - Universal Access to All Knowledge Depends on Unicode Brewster Kahle, Digital Librarian 10:00 - 20:00 EXHIBIT AREA OPEN 10:00 – 10:30 Morning Refreshments in Exhibit Area Track 1 Track 2 Track 3 PRESENTATIONS I18N Platforms Language Processing Improving the Internationalization The Power of "Plain Text" & 10:30 – 11:20 Global Gateway: with PHP the Importance of Established and Meaningful Content Emerging Trends SESSION 1 in Multilingual Ken Lunde Navigation Senior Computer Kirti Velankar Scientist John_Yunker Yahoo Inc. Adobe. President Byte Level Research Global Ready Making Javascript Multilingual Unstructured 11:30 – 12:20 Assessment Tool Multilingual Text Analytics SESSION 2 Michael McKenna Rusmin Dirgantoro Internationalization Nebojša Ciric Chief Engineer Architect, Yahoo! Software Aeontera, Inc. Inc. Engineer, Google, Inc. Jungshik Shin Software Engineer, Google, Inc. 12:30 - 13:30 Lunch Track 1 Track 2 Track 3 PRESENTATIONS I18N Platforms Language Processing Machine New Name Writing in Public 13:30 – 14:20 Translation as a Internationalization Registers for Multi-country Problem of Functionality in the Use Unstructured Adobe Flash SESSION 3 Data platform Erkki I. Kolehmainen Mihai Nita Kotoistus and Oy Andy Bell Globalization KREST Sales and welocalize Architect Consulting Services Ltd Adobe Systems, Inc. Global by Design: Globalization for Proper Name 14:30 – 15:20 Systematic Flash/Flex Transcription/Transliteration Approach to I18N Enterprise with ICUTransforms Testing Applications SESSION 4 Sascha Brawer Google Inc Loïc Dufresne Michael Martin Jansche de Virel Bridgers Google Inc Localization Sr. Software Hiroshi Takenaka Strategist, Engineer, Google Inc Intel Globalization, Yui Terashima Corporation SAS Institute Google Inc 15:20 – 16:00 Afternoon Refreshments in Exhibit Area Track 1 Track 2 Track 3 PRESENTATIONS I18N Platforms Language Processing ICU Update Korean Hangul: Statistical Language 16:00 – 16:50 from Sejong the Detection in Web Pages Great's Hunmin Jeongeum to SESSION 5 Yoshito Richard Sites Unicode 5.2 Umaoka Google, Inc. Software Engineer, IBM Markus Michael S. Scherer Kaplan Unicode Program Software Manager, Engineer, Microsoft Google Inc. Extending ICU How To Achieve Dialect Detection 17:00 – 17:50 with New World(-Ready) Features Domination In Silverlight 4 SESSION 6 Khaled Hafez Savithri Jasti Guy Smith-Ferrier Google, Inc. Senior Engineer, Internationalization Yahoo Inc. Consultant, Capella Kirti Velankar Software Ltd. Senior Engineer, Yahoo Inc. 18:00 - 20:00 Conference Reception in Exhibit Area Wednesday, October 20, 2010 Track 1 Track 2 Track 3 PRESENTATIONS L10N Technology Platforms Language Processing Alert: New Internationalizing Script Encoding 09:00 – 09:50 Internationalized Twitter Initiative, UC Domain Names (IDNs) Berkeley are coming! (Click to see all SESSION 7 abstracs) Deborah Anderson Mark Davis Matt Sanford Researcher, Dept. of Sr. Tech Manager of Linguistics, UC Berkeley Internationalization International Architect, Team, Google Inc. Twitter, Inc. University of California, Santa Cruz Unicode and CLDR outside of Industry: News from Academic and Non-Profit Projects IRIs Beyond the Chrome Unicode and CLDR 10:00 – 10:50 Napkin: A Survey of Internationalization outside of Industry: Internationalized News from Academic Resource Identifier and Non-Profit SESSION 8 Issues and Projects (Cont'd.) Implementation Jungshik Shin The Rosetta Project - Martin J. Dürst Software Wiki of All Human Professor, Engineer, Language Aoyama Gakuin Google, Inc. University Nebojša Ciric Laura Welcher Addison Phillips Software Ph.D. Globalization Engineer, Architect, Lab126 Google, Inc. Locales for African Languages - the ANLoc AfriGen Experience Martin Benjamin Executive Director, Kamusi Project International 10:50 - 11:10 Morning Refreshments Unicode Fonts for the Windows 7 Tashkeel -- A library 11:10 – 12:00 Desktop, the Mobile for automatically and the Web adding diacritics to undiacritized Arabic SESSION 9 text Michael S. Kaplan Adil Allawi Program Manager Technical Company, Mohamed Eldawy Director, Microsoft Software Diwan Software Engineer, Google, Inc. Mohamed Taha Software Engineer, Google, Inc. 12:00 - 13:00 Lunch Track 3 Track 1 Track 2 PRESENTATIONS Language Processing L10N Technology Platforms (Cont'd) Deploying the CLDR International Features Extending Bidi 13:00 – 13:50 Common Locale Data of the iPhone OS Support on the Web Repository SESSION 10 Deborah Richard Ishida Steven Loomis Goldsmith Internationalization Software Engineer, Senior Software Lead, W3C IBM Engineer Aharon Lanin Mark Davis Apple, Inc. Software Engineer, Sr. Google, Inc. Internationalization Architect, Google Inc. CLDR 1.8 - Meeting Emoji in Unicode 6.0: Tailoring the Unicode 14:00 – 14:50 the Challenges of From Proposal to Bidi Algorithm Africa Deployment SESSION 11 Murray Sargent John Emmons Markus Scherer III Globalization Unicode Software Partner Software Architect, Engineer, Google Design Engineer, IBM Inc. Microsoft Katsuhiko Momoi Ayman Aldahleh Staff Test Engineer Software & I18n Consultant, Development Google Inc. Engineers, Yasuo Kida Microsoft Apple, Inc. Mark Davis Sr. Internationalization Architect, Google Inc. 14:50 – 15:10 Afternoon Refreshments Track 3 Track 1 Track 2 PRESENTATIONS Language Processing L10N Technology Platforms (Cont'd) Solving Problems with Designing Global Web A Beginner's Guide to 15:10 – 16:00 Locale/Language Service APIs Indic Scripts Identification SESSION 12 Yoshito Umaoka Norbert Lindenberg Christopher J. Software Engineer, Internationalization Chapman IBM Architect, Yahoo! Principal Mark Davis Inc. Engineer Sr. Monotype Internationalization Imaging Inc. Architect, Google Inc. Address and Phone Design Considerations The Past, Present, 16:10 – 17:00 Number for Chinese and Future of Tamil Internationalization - eCommerce Web Sites in Unicode Standards, SESSION 13 Technologies and Best Practices Tex Texin Xen Master, Michael Kaplan Shaopeng Jia XenCraft Program Software Manager Engineer, Company, Google Microsoft Clint Yang Software Engineer, Google Lara Rennie Software Engineer, Google Program is subject to change. Object Management Group®, (OMG®) organizes the Internationalization and Unicode Conferences around the world under an exclusive license granted by the Unicode Consortium. Personal information provided to OMG via this website is subject to OMG’s Privacy Policy. All responsibility for conference finances and operations is borne by OMG. The independent conference board provides technical review of the program and papers. All inquiries regarding the Internationalization and Unicode Conferences should be addressed to [email protected]. Copyright @ 2016 Object Management Group. All rights reserved..
Load more

Recommended publications
  • Unicode/IDN Security Mark Davis President, Unicode Consortium Chief SW Globalization Arch., IBM the Unicode Consortium
    Unicode/IDN Security Mark Davis President, Unicode Consortium Chief SW Globalization Arch., IBM The Unicode Consortium Software globalization standards: define properties and behavior for every character in every script Unicode Standard: a unique code for every character Common Locale Data Repository: LDML format plus repository for required locale data Collation, line breaking, regex, charset mapping, … Used by every major modern operating system, browser, office software, email client,… Core of XML, HTML, Java, C#, C (with ICU), Javascript, … Security ~ Identity System A X = x System B X ≠ x IDN You get an email about your paypal.com account, click on the link… You carefully examine your browser's address box to make sure that it is actually going to http://paypal.com/ … But actually it is going to a spoof site: “paypal.com” with the Cyrillic letter “p”. You (System A) think that they are the same DNS (System B) thinks they are different Examples: Letters Cross-Script p in Latin vs p in Cyrillic In-Script Sequences rn may appear at display sizes like m ! + ा typically looks identical to # so̷s looks like søs Rendering Support ä with two umlauts may look the same as ä with one el is actually e + l Examples: Numbers Western 0 1 2 3 4 5 6 7 8 9 Bengali ৺৺৺৺৺৺৺৺৺৺ Oriya ୱୱୱୱୱୱୱୱୱୱ Thus ৺ୱ = 42 Syntax Spoofing http://example.org/1234/not.mydomain.com http://example.org/1234/not.mydomain.com / = fraction-slash Also possible without Unicode: http://example.org--long-and-obscure-list-of- characters.mydomain.com UTR
    [Show full text]
  • Network Working Group D. Goldsmith Request for Comments: 1641 M
    Network Working Group D. Goldsmith Request for Comments: 1641 M. Davis Category: Experimental Taligent, Inc. July 1994 Using Unicode with MIME Status of this Memo This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Abstract The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993(E) jointly define a 16 bit character set (hereafter referred to as Unicode) which encompasses most of the world's writing systems. However, Internet mail (STD 11, RFC 822) currently supports only 7- bit US ASCII as a character set. MIME (RFC 1521 and RFC 1522) extends Internet mail to support different media types and character sets, and thus could support Unicode in mail messages. MIME neither defines Unicode as a permitted character set nor specifies how it would be encoded, although it does provide for the registration of additional character sets over time. This document specifies the usage of Unicode within MIME. Motivation Since Unicode is starting to see widespread commercial adoption, users will want a way to transmit information in this character set in mail messages and other Internet media. Since MIME was expressly designed to allow such extensions and is on the standards track for the Internet, it is the most appropriate means for encoding Unicode. RFC 1521 and RFC 1522 do not define Unicode as an allowed character set, but allow registration of additional character sets. In addition to allowing use of Unicode within MIME bodies, another goal is to specify a way of using Unicode that allows text which consists largely, but not entirely, of US-ASCII characters to be represented in a way that can be read by mail clients who do not understand Unicode.
    [Show full text]
  • Unicode Compression: Does Size Really Matter? TR CS-2002-11
    Unicode Compression: Does Size Really Matter? TR CS-2002-11 Steve Atkin IBM Globalization Center of Competency International Business Machines Austin, Texas USA 78758 [email protected] Ryan Stansifer Department of Computer Sciences Florida Institute of Technology Melbourne, Florida USA 32901 [email protected] July 2003 Abstract The Unicode standard provides several algorithms, techniques, and strategies for assigning, transmitting, and compressing Unicode characters. These techniques allow Unicode data to be represented in a concise format in several contexts. In this paper we examine several techniques and strategies for compressing Unicode data using the programs gzip and bzip. Unicode compression algorithms known as SCSU and BOCU are also examined. As far as size is concerned, algorithms designed specifically for Unicode may not be necessary. 1 Introduction Characters these days are more than one 8-bit byte. Hence, many are concerned about the space text files use, even in an age of cheap storage. Will storing and transmitting Unicode [18] take a lot more space? In this paper we ask how compression affects Unicode and how Unicode affects compression. 1 Unicode is used to encode natural-language text as opposed to programs or binary data. Just what is natural-language text? The question seems simple, yet there are complications. In the information age we are accustomed to discretization of all kinds: music with, for instance, MP3; and pictures with, for instance, JPG. Also, a vast amount of text is stored and transmitted digitally. Yet discretizing text is not generally considered much of a problem. This may be because the En- glish language, western society, and computer technology all evolved relatively smoothly together.
    [Show full text]
  • New Emoji Requests from Twitter Users: When, Where, Why, and What We Can Do About Them
    1 New Emoji Requests from Twitter Users: When, Where, Why, and What We Can Do About Them YUNHE FENG, University of Tennessee, Knoxville, USA ZHENG LU, University of Tennessee, Knoxville, USA WENJUN ZHOU, University of Tennessee, Knoxville, USA ZHIBO WANG, Wuhan University, China QING CAO∗, University of Tennessee, Knoxville, USA As emojis become prevalent in personal communications, people are always looking for new, interesting emojis to express emotions, show attitudes, or simply visualize texts. In this study, we collected more than thirty million tweets mentioning the word “emoji” in a one-year period to study emoji requests on Twitter. First, we filtered out bot-generated tweets and extracted emoji requests from the raw tweets using a comprehensive list of linguistic patterns. To our surprise, some extant emojis, such as fire and hijab , were still frequently requested by many users. A large number of non-existing emojis were also requested, which were classified into one of eight emoji categories by Unicode Standard. We then examined patterns of new emoji requests by exploring their time, location, and context. Eagerness and frustration of not having these emojis were evidenced by our sentiment analysis, and we summarize users’ advocacy channels. Focusing on typical patterns of co-mentioned emojis, we also identified expressions of equity, diversity, and fairness issues due to unreleased but expected emojis, and summarized the significance of new emojis on society. Finally, time- continuity sensitive strategies at multiple time granularity levels were proposed to rank petitioned emojis by the eagerness, and a real-time monitoring system to track new emoji requests is implemented.
    [Show full text]
  • Emojis and the Law
    Washington Law Review Volume 93 Number 3 10-1-2018 Emojis and the Law Eric Goldman Follow this and additional works at: https://digitalcommons.law.uw.edu/wlr Part of the Computer Law Commons Recommended Citation Eric Goldman, Emojis and the Law, 93 Wash. L. Rev. 1227 (2018). Available at: https://digitalcommons.law.uw.edu/wlr/vol93/iss3/4 This Article is brought to you for free and open access by the Law Reviews and Journals at UW Law Digital Commons. It has been accepted for inclusion in Washington Law Review by an authorized editor of UW Law Digital Commons. For more information, please contact [email protected]. 08 - Goldman.docx (Do Not Delete) 10/10/2018 5:46 PM EMOJIS AND THE LAW By Eric Goldman* Abstract: Emojis are an increasingly important way we express ourselves. Though emojis may be cute and fun, their usage can lead to misunderstandings with significant legal stakes— such as whether someone should be obligated by contract, liable for sexual harassment, or sent to jail. Our legal system has substantial experience interpreting new forms of content, so it should be equipped to handle emojis. Nevertheless, some special attributes of emojis create extra interpretative challenges. This Article identifies those attributes and proposes how courts should handle them. One particularly troublesome interpretative challenge arises from the different ways platforms depict emojis that are nominally standardized through the Unicode Consortium. These differences can unexpectedly create misunderstandings. The diversity of emoji depictions is not technologically required, nor does it necessarily benefit users. Instead, it likely reflects platforms’ concerns about intellectual property protection for emojis, which forces them to introduce unnecessary variations that create avoidable confusion.
    [Show full text]
  • UTS #10: Unicode Collation Algorithm
    UTS #10: Unicode Collation Algorithm http://www.unicode.org/reports/tr10/tr10-17.html Technical Reports Proposed Update Unicode Technical Standard #10 UNICODE COLLATION ALGORITHM Version 5.1.0 (draft 2) Authors Mark Davis ([email protected]), Ken Whistler ([email protected]) Date 2007-10-09 This Version http://www.unicode.org/reports/tr10/tr10-17.html Previous http://www.unicode.org/reports/tr10/tr10-16.html Version Latest Version http://www.unicode.org/reports/tr10/ Revision 17 Summary This report provides the specification of the Unicode Collation Algorithm, which provides a specification for how to compare two Unicode strings while remaining conformant to the requirements of The Unicode Standard. The UCA also supplies the Default Unicode Collation Element Table (DUCET) as the data specifying the default collation order for all Unicode characters. Status This is a draft document which may be updated, replaced, or superseded by other documents at any time. Publication does not imply endorsement by the Unicode Consortium. This is not a stable document; it is inappropriate to cite this document as other than a work in progress. A Unicode Technical Standard (UTS) is an independent specification. Conformance to the Unicode Standard does not imply conformance to any UTS. Please submit corrigenda and other comments with the online reporting form [Feedback]. Related information that is useful in understanding this document is found in the References. For the latest version of the Unicode Standard see [Unicode]. For a list of current Unicode Technical Reports see [Reports]. For more information about versions of the Unicode Standard, see [Versions].
    [Show full text]
  • Program - Session Descriptions
    Program - Session Descriptions Monday, October 18, 2010 09:00-12:30 MORNING TUTORIALS Presenter: Track 1: An Introduction to Writing Systems & Unicode Richard Ishida The tutorial will provide you with a good understanding of the many unique Hotel cut-off: Internationalization characteristics of non-Latin writing systems, and illustrate the problems involved in 09/26/2010 Lead, implementing such scripts in products. It does not provide detailed coding advice, but W3C does provide the essential background information you need to understand the Venue: fundamental issues related to Unicode deployment, across a wide range of scripts. It has also proved to be an excellent orientation for newcomers to the conference, providing Hyatt Regency the background needed to assist understanding of the other talks! The tutorial goes Hotel beyond encoding issues to discuss characteristics related to input of ideographs, Santa Clara, CA combining characters, context-dependent shape variation, text direction, vowel signs, USA ligatures, punctuation, wrapping and editing, font issues, sorting and indexing, keyboards, and more. The concepts are introduced through the use of examples from Chinese, Japanese, Korean, Arabic, Hebrew, Thai, Hindi/Tamil, Russian and Greek. While the tutorial is perfectly accessible to beginners, it has also attracted very good reviews from people at an intermediate and advanced level, due to the breadth of scripts discussed. No prior knowledge is needed. Presenter: Track 2: Internationalization: An Introduction, Part I: Characters and Character Encodings Addison Phillips Globalization What is internationalization? What do developers, product managers, or quality engineers Architect need to know about it? How does a software development organization incorporate Lab126 (Amazon) internationalization into the design, implementation, and delivery of an application? This tutorial track provides an introduction to the topics of internationalization, localization and globalization.
    [Show full text]
  • 3629 Alis Technologies STD: 63 November 2003 Obsoletes: 2279 Category: Standards Track
    Network Working Group F. Yergeau Request for Comments: 3629 Alis Technologies STD: 63 November 2003 Obsoletes: 2279 Category: Standards Track UTF-8, a transformation format of ISO 10646 Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2003). All Rights Reserved. Abstract ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo. UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo obsoletes and replaces RFC 2279. Table of Contents 1. Introduction . 2 2. Notational conventions . 3 3. UTF-8 definition . 4 4. Syntax of UTF-8 Byte Sequences . 5 5. Versions of the standards . 6 6. Byte order mark (BOM) . 6 7. Examples . 8 8. MIME registration . 9 9. IANA Considerations . 10 10. Security Considerations . 10 11. Acknowledgements . 11 12. Changes from RFC 2279 . 11 13. Normative References . 12 Yergeau Standards Track [Page 1] RFC 3629 UTF-8 November 2003 14.
    [Show full text]
  • The Unicode Standard, Version 3.0, Issued by the Unicode Consor- Tium and Published by Addison-Wesley
    The Unicode Standard Version 3.0 The Unicode Consortium ADDISON–WESLEY An Imprint of Addison Wesley Longman, Inc. Reading, Massachusetts · Harlow, England · Menlo Park, California Berkeley, California · Don Mills, Ontario · Sydney Bonn · Amsterdam · Tokyo · Mexico City 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 Addison-Wesley was aware of a trademark claim, the designations have been printed in initial capital letters. However, not all words in initial capital letters are trademark designations. The authors and publisher have taken care in preparation of this book, 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. If these files have been purchased on computer-readable media, the sole remedy for any claim will be exchange of defective media within ninety days of receipt. Dai Kan-Wa Jiten used as the source of reference Kanji codes was written by Tetsuji Morohashi and published by Taishukan Shoten. ISBN 0-201-61633-5 Copyright © 1991-2000 by Unicode, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or other- wise, without the prior written permission of the publisher or Unicode, Inc.
    [Show full text]
  • Unicode Technical Committee Liaison Statement To
    Subject: Re: Unicode Technical Committee Liaison Statement to IETF on iab-idn-nextsteps From: Mark Davis <[email protected]> Date: Friday, 24 Feb 2006 01.52.32 GMT+02:00 To: [email protected], CC:[email protected], [email protected], "[email protected]" <[email protected]> The Unicode Technical Committee has reviewed the document http://www.iab.org/documents/drafts/draft-iab-idn-nextsteps-02.txt. The UTC strongly supports many of the goals of the document, including especially improving the security of IDNs, and updating the version of Unicode used in NamePrep and StringPrep (since the old version of Unicode they require excludes or hampers many languages). There are, however, a number of areas of concern. As a general issue, we'd urge closer cooperation between the IAB and the Unicode consortium on the document, so that the character encoding and software internationalization issues can be reviewed by experts in the field, and accurately represented in the document. The chief area of concern is section 4.3. 4.3. Combining Characters and Character Components One thing that increases IDNA complexity and the need for normalization is that combining characters are permitted. Without them, complexity might be reduced enough to permit more easy transitions to new versions. The community should consider whether combining characters should be prohibited entirely from IDNs. A consequence of this, of course, is that each new language or script would require that all of its characters have Unicode assignments to specific, precomposed, code points, a model that the Unicode Consortium has rejected for Roman-based scripts.
    [Show full text]
  • RFC 2152 UTF-7 May 1997
    Network Working Group D. Goldsmith Request for Comments: 2152 Apple Computer, Inc. Obsoletes: RFC 1642 M. Davis Category: Informational Taligent, Inc. May 1997 UTF-7 A Mail-Safe Transformation Format of Unicode Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Abstract The Unicode Standard, version 2.0, and ISO/IEC 10646-1:1993(E) (as amended) jointly define a character set (hereafter referred to as Unicode) which encompasses most of the world’s writing systems. However, Internet mail (STD 11, RFC 822) currently supports only 7- bit US ASCII as a character set. MIME (RFC 2045 through 2049) extends Internet mail to support different media types and character sets, and thus could support Unicode in mail messages. MIME neither defines Unicode as a permitted character set nor specifies how it would be encoded, although it does provide for the registration of additional character sets over time. This document describes a transformation format of Unicode that contains only 7-bit ASCII octets and is intended to be readable by humans in the limiting case that the document consists of characters from the US-ASCII repertoire. It also specifies how this transformation format is used in the context of MIME and RFC 1641, "Using Unicode with MIME". Motivation Although other transformation formats of Unicode exist and could conceivably be used in this context (most notably UTF-8, also known as UTF-2 or UTF-FSS), they suffer the disadvantage that they use octets in the range decimal 128 through 255 to encode Unicode characters outside the US-ASCII range.
    [Show full text]
  • Naming Text Encodings to Demystify Them
    Naming Text Encodings to Demystify Them Document #: P1885R6 Date: 2021-08-14 Programming Language C++ Audience: LEWG Reply-to: Corentin Jabot <[email protected]> Peter Brett <[email protected]> If you can’t name it, you probably don’t know what it is If you don’t know what it is, you don’t know what it isn’t Tony Van Eerd Target C++23 Abstract For historical reasons, all text encodings mentioned in the standard are derived from a locale object, which does not necessarily match the reality of how programs and systems interact. This model works poorly with modern understanding of text, ie the Unicode model separates encoding from locales which are purely rules for formatting and text transformations but do not affect which characters are represented by a sequence of code units. Moreover, the standard does not provide a way to query which encodings are expected or used by the environment, leading to guesswork and unavoidable UB. This paper introduces the notions of literal encoding, environment encoding, and a way to query them. Examples Listing the encoding #include <text_encoding> #include <iostream> void print(const std::text_encoding & c) { std::cout << c.name() << " (iana mib: " << c.mib() << ")\n" << "Aliases:\n"; 1 for(auto && a : c.aliases()) { std::cout << '\t' << a << '\n'; } } int main() { std::cout << "Literal Encoding: "; print(std::text_encoding::literal()); std::cout << "Wide Literal Encoding: "; print(std::text_encoding::wide_literal()); std::cout << "environment Encoding: "; print(std::text_encoding::environment());
    [Show full text]