DOCSLIB.ORG

TTF) Glyphs: X³-Bézier Splines Adobe (Microsoft)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
TTF) Glyphs: X³-Bézier Splines Adobe (Microsoft) • Xavier Dupré über seine neue Schriftsippe FF Yoga „Der Körper eines Buchstabens ist mit dem eines Menschens vergleichbar — und beide interessieren mich brennend.“ Text + Interview: Jürgen Siebert Foto: Matthieu Spohn (PhotoAlto) Illustrationen: FSI & FontShop Schriften: FF Yoga/ FF Yoga Sans Spannung »› Balance «‹ Elastizität »› as aktuelle Design made in Germany-Ma- D gazin ist aus einer brandneuen Schrift gesetzt, die erst in wenigen Tagen auf den Markt kommt: FF Yoga, von Xavier Dupré. Yoga ist eine Schriftsippe, bestehend aus einer Sans und Serif. Während vergleichba- re Konzepte meist mit einer fertigen Serif- Familie beginnen, aus der eine Sans abge- leitet wird (z. B. FF Scala, FF Quadraat, …), entwickelte Dupré beide Varianten parallel. Warum diese Vorgehensweise für ihn bes- ser funktioniert und wieso das Endergebnis anders wird, erklärte Xavier Dupré im Dmig- Exklusivinterview. Ramburgefonstiväl Ramburgefonstivl FF Yoga Sans Regular FF Yoga Regular Ramburgefonstivüñ Ramburgefonstivrä FF Yoga Sans Italic FF Yoga Italic Ramburgefonstivx Ramburgefonstiw FF Yoga Sans Bold FF Yoga Bold Ramburgefonstivkä Ramburgefonstivö FF Yoga Sans Bold Italic FF Yoga Bold Italic Wann und mit welcher Intention hast Q: Planst du Erweiterungen für die Sippe? Q: du die Schrift Yoga entworfen? A: Ja. Meine ursprüngliche Idee war die Ent- Meine Arbeit an Yoga begann vor rund wicklung eines Schriftsystems für alle Anfor- A: zwei Jahren mit dem Ziel, eine nüch- derungen. Ich habe bereits mit dem Entwerfen terne und vielseitige Schriftfamilie zu entwer- optischer Größenvarianten für die Yoga Serif fen, die Originalität und Balance verbindet. Sie begonnen und mit Display-Fassungen der Spannung »› sollte noch besser für Mengentexte geeignet Yoga Sans. Aber ich brauche noch Zeit. Außer- sein als meine Malaga, jedoch gleichermaßen dem arbeite ich parallel an zu vielen anderen ausdrucksstark, dank kräftiger Serifen und Schriftfamilien. raffiniertem Kontrast. Q: Warum hast du die Schrift Yoga genannt? Q: Was inspirierte dich zu Yoga? Balance «‹ A: Ich kam auf den Namen, weil ich vor einem A: Mein gesamtes Schaffen ist vom humanis- Jahr das Yoga in Indien kennengelernt habe tischen Stil beeinflusst, also vor allem vom und es noch heute jeden Morgen nach dem holländischen und zeitgenössischen amerika- Aufstehen praktiziere. Yoga hilft, dem Körper nischen Typedesign. Und natürlich schwingt Elastizität, Balance und Spannung zu geben, immer meine Leidenschaft für die Kalligrafie Eigenschaften, die ich auch beim Schriftdesign Elastizität »› mit. Bei FF Yoga haben mich wahrscheinlich als wichtig erachte. Der Körper eines Buchsta- Gerard Ungers und Fred Smeijers’ Arbeiten am bens ist durchaus mit dem eines Menschens meisten beeinflusst. vergleichbar – und beide interessieren mich brennend. Q: Was bedeutet es, eine Sans und eine Serif parallel zu entwickeln? A: Für mich ist es einfacher und interessanter, beide gemeinsam zu entwerfen, weil ich stän- dig umschalten kann zwischen Sans und Serif. Wenn ein Baustein im einen oder anderen Fall Xavier Dupré wurde 1977 in Frankreich gebo- nicht funktioniert, kann ich ihn gleich über ren. Er studierte Kunst und Design in Paris. Bord werfen. So habe ich immer einen Über- Zwei Jahre nach seinem Studium ging er ins blick über das gesamte Werk. Scriptorium zu Toulouse, um bei Bernard Arin und Rodolphe Giuglardo Kalligrafie and Typo- Q: Worin siehst du die Stärke grafie zu studieren. Ab 1999 arbeitete Dupré in der FF-Yoga-Familie? einem Büro für Verpackungsdesign in Paris, wo er auch Ladislas Mandel begegnete, bekannt für A: Die Stärke der Familie ist seine Telefonbuchschriften. Von ihre ausgezeichnete Lesbarkeit, 2001 – 2004 lebte Xavier Dupré in gepaart mit kuriosen Details, Kambodscha, wo er auch Schrif- die ihr Persönlichkeit geben. ten entwarf. Die Sans hat ein recht lineares Design, vergleichbar einer Gill Duprés Werke erschienen bei Sans. Doch in Kombination mit FontFont (FF Absara, FF Absara der Serif ergibt sich ein Span- Sans, FF Angkoon, FF Jambono, nungsbogen zwischen neutral FF Megano, FF Parango, FF Re- und persönlich. Die kräftigen minga, FF Sanuk und FF Tartine), Serifen helfen beim Lesen klei- bei Emigre (Malaga, Vista, Vista nerer Texte und verleihen dem Sans, Vista Slab), T.26 (Meteor, Schriftbild einen Bleisatzeffekt. Spotka) und The Font Bureau (Zingha). Xavier Dupré Basilique Danton Louis F f Convetion E e H B N D d W C c A Châtelet AR_ B b A a Les Halles Villiers Trocadéro Pont Sabine Hôpital Voltaire Laplace YOGA Campo Libération Vincennes Le Kremlin Q M Plaisance Gâité Brochant Simplon Rouge Cadet Melun Raspail Couronnes Wagram Alésia L l Marché K k Métiers J j St-Paul I i Rome H h Cadeau g G Concorde Mongallet Bastille Orly St-Alexandre Soa École T Tolbiac La Muette Sartre Bolivar Jaurès Varenne Eau Z Lilia Blanche Maison F Bel-Air Ivry Opéra R K R r Robespierre Q q Europe P p Bagneux O o Liberté N n Pyrénées M m Chachan Cimetière Saint-Alexandre Porte Dorée Port-Royal St-Vitalique Cambronne Ourcq Belleville Chemin Vert Solférino Ségur Pyramides W Duschanbé Goncourt La Tour Flora Cité X x Charonne W w V v U u T t S s Cathedral Rue de Bac Aéroport Boucicaut Cardinal N Z Léna Mon Boulevard Olympiades Passy Louvre Raspail Chaville N Strasbourg S G Sorbonne Château Temple Ranelagh SS ß Lourmel E Y Ü ü Ö ö © 2009 FontShop International Ä ä Z z Y y Basilique Danton Louis F f Convetion E e H B N D d W C c A Châtelet AR_ B b A a Les Halles Villiers Trocadéro Pont Sabine Hôpital Voltaire Laplace YOGA Campo Libération Vincennes Le Kremlin Q M Plaisance Gâité Brochant Simplon Rouge Cadet Melun Raspail Couronnes Wagram Alésia L l Marché K k Métiers J j St-Paul I i Rome H h Cadeau g G Concorde Mongallet Bastille Orly St-Alexandre Soa École T Tolbiac La Muette Sartre Bolivar Jaurès Varenne Eau Z Lilia Blanche Maison F Bel-Air Ivry Opéra R K R r Robespierre Q q Europe P p Bagneux O o Liberté N n Pyrénées M m Chachan Cimetière Saint-Alexandre Porte Dorée Port-Royal St-Vitalique Cambronne Ourcq Belleville Chemin Vert Solférino Ségur Pyramides W Duschanbé Goncourt La Tour Flora Cité X x Charonne W w V v U u T t S s Cathedral Rue de Bac Aéroport Boucicaut Cardinal N Z Léna Mon Boulevard Olympiades Passy Louvre Raspail Chaville N Strasbourg S G Sorbonne Château Temple Ranelagh SS ß Lourmel E Y Ü ü Ö ö © 2009 FontShop International Ä ä Z z Y y periodensystem der fontelemente gesetzt aus FF Yoga und FF Yoga Sans 1 .otf OpenType Font File PostScript = CFF (TrueType = TTF) Glyphs: x³-Bézier splines aDobe (microsoFt) Flavour Mac OS, Windows 3 4 5 6 7 .pfb .pfm .afm .inf .pfa PostScript Font Binary PostScript Font Metric Adobe Font Metric Information Printer Font ascii PostScript Type 1 PostScript Type 1 PostScript Type 1 PostScript Type 1 PostScript Type 1 Glyph data Font metric information Metric information (ascii) Font information (ascii) ascii version of PFB aDobe aDobe aDobe aDobe aDobe Windows Windows Mac OS, Linux Windows, DOS Linux Dateien 13 14 15 16 17 18 19 20 21 Exp sc osF lF tF alt tExt head d Expert (Set) Small Caps Old Style Figures Lining Figures Tabular Figures Alternates Text Headline Display PostScript Type 1 PostScript PostScript PostScript, TrueType PostScript, TrueType PostScript (TrueType) PostScript PostScript, TrueType PostScript Special character addition Standard glyph variant Standard figures variant Standard figures variant Standard figures variant Glyph variants Optical size Optical size Optical size aDobe et al aDobe et al aDobe et al aDobe et al aDobe et al FontFont et al FontFont et al various URW Eigenschaften Mac OS, Windows Mac OS, Windows Mac OS, Windows Mac OS, Windows Mac OS, Windows Mac OS, Windows Mac OS, Windows Mac OS, Windows Mac OS, Windows 64 65 66 67 68 69 70 71 – 79 ot std pro com W1G WGl GlB OpenType Standard Professional Communication World Glyph Set 1 Windows Glyph List 4 Global Font siehe OpenType Language support OpenType OpenType OpenType OpenType OpenType OpenType, TrueType OpenType, TrueType Western languages 21+ languages 33+ languages 48 languages 56 languages 56 languages + DOS-glyphs latin + non latin languages various manuFacturers various manuFacturers various manuFacturers linotype linotype monotype urw ++ Mac OS, Windows Mac OS, Windows Mac OS, Windows Mac OS, Windows Mac OS, Windows Mac OS, Windows, DOS Mac OS, Windows, DOS Produkte 86 87 88 89 90 91 92 93 94 a*i BB BE Bt ca cs ck dF dtl Alphabets Bo Berndal Berthold Bitstream Creative Alliance Castle Systems Chank Fonts Device Fonts Dutch Type Library semiotx bigg, hålet bertholD Direct corp. bitstream agFa compugraphic castle type the chank co DeviceFonts Dutch type library Galena, Illinois, USA Stockholm, Sweden (Berlin) Chicago Cambridge, MA, USA Wilmington, MA, USA San Rafael, CA, USA Minneapolis, MN, USA London, UK ’s-Hertogenbosch, NL est. 1986 est. 1994 est. 1858 est. 1981 est. 1995 est. 1990 est. 1996 est. 1993 est. 1990 104 105 107 108 108 109 110 111 112 HFJ itc lt ltr mt ot p22 pn psy Hoefler Frere-Jones Int. Typeface Corp. Linotype LettError Monotype OurType P22 Type Foundry Panache Psy/Ops hoeFler & Frere-jones monotype imaging linotype gmbh letterror Fonts monotype imaging ourtype castle type panache graphics psy/ops type FounDry New York, NY, USA Woburn, MA, USA Bad Homburg, D The Hague, NL Surrey, GB De Pinte, B Buffalo, NY, USA Essex, UK San Francisco, CA, USA est. 2004 est. 1970 est. 1997 est. 1989 est. 1887 est. 2002 est. 1994 est. 1993 est. 1995 Bibliotheken 24 N 25 F 26 D 27 I 28 Q 29 K 30 T 31 H 32 u Access all alternates Contextual Alternates Stylistic Alternates Standard
Load more

Recommended publications
  • 1 Introduction 1
    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]
  • Pdflib Reference Manual
    PDFlib GmbH München, Germany Reference Manual ® A library for generating PDF on the fly Version 5.0.2 www.pdflib.com Copyright © 1997–2003 PDFlib GmbH and Thomas Merz. All rights reserved. PDFlib GmbH Tal 40, 80331 München, Germany http://www.pdflib.com phone +49 • 89 • 29 16 46 87 fax +49 • 89 • 29 16 46 86 If you have questions check the PDFlib mailing list and archive at http://groups.yahoo.com/group/pdflib Licensing contact: [email protected] Support for commercial PDFlib licensees: [email protected] (please include your license number) This publication and the information herein is furnished as is, is subject to change without notice, and should not be construed as a commitment by PDFlib GmbH. PDFlib GmbH assumes no responsibility or lia- bility for any errors or inaccuracies, makes no warranty of any kind (express, implied or statutory) with re- spect to this publication, and expressly disclaims any and all warranties of merchantability, fitness for par- ticular purposes and noninfringement of third party rights. PDFlib and the PDFlib logo are registered trademarks of PDFlib GmbH. PDFlib licensees are granted the right to use the PDFlib name and logo in their product documentation. However, this is not required. Adobe, Acrobat, and PostScript are trademarks of Adobe Systems Inc. AIX, IBM, OS/390, WebSphere, iSeries, and zSeries are trademarks of International Business Machines Corporation. ActiveX, Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation. Apple, Macintosh and TrueType are trademarks of Apple Computer, Inc. Unicode and the Unicode logo are trademarks of Unicode, Inc. Unix is a trademark of The Open Group.
    [Show full text]
  • ISO/IEC JTC1/SC2/WG2/Irgn2456eisofeedback 2021-3-15
    ISO/IEC JTC1/SC2/WG2/IRGN2456EisoFeedback 2021-3-15 Universal Multiple-Octet Coded Character Set International Organization for Standardization Organisation Internationale de Normalisation Международная организация по стандартизации Doc Type: Working Group Document Title: Feedback on MSCS-2020 Source: Eiso Chan (陈永聪, Culture and Art Publishing House) Status: Individual Contribution to online IRG #56 Action: For consideration by IRG and MSARG Date: 2021-3-15 Macao SARG has (pre-)published MSCS-2020 as the appendix of IRGN2456. After reviewing the chart during IRG #56 online meeting, I point out some comments as below for reference only. 1. Feedback on the ME-9759-001 glyph Fig. 1 Current ME-9759-001 glyph The first stoke of the bottom left component of the current ME-9758-001 glyph is Stroke P (撇), but this stroke of the component 靑 under other characters / glyphs should be Stroke S (竖/ 竪/豎, aka the vertical bar) in MSCS-2020, such as ME-701E-001, ME-83C1-001, ME-84A8- 001 and ME-975C-001. Maybe it will be better to make this stroke form consistent. 2. Feedback on the version of HKSCS In IRGN2430R, MSARG clearly showed the version of HKSCS which would be used in Macao SAR is HKSCS-2008 not the latest version or the future version, so it’s better to clarify the version of HKSCS means HKSCS-2008 in MSCS-2020 and the future version. 3. Feedback on the subtitles for 1.1.3.2 and 1.1.3.3 The current subtitles for these two sections are “《大五碼字符集》中的基本字” and “《香港 增補字符集》中的基本字”.
    [Show full text]
  • 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]
  • Cyrillic Languages Support in LATEX
    Cyrillic languages support in LATEX © Copyright 1998{1999, Vladimir Volovich, Werner Lemberg and LATEX Project Team. All rights reserved. 12 March 1999 Contents 1 Introduction1 1.1 Acknowledgments...........................2 2 Installation2 2.1 Fonts..................................2 2.2 Hyphenation patterns........................3 2.3 babel support for Russian and Ukrainian..............3 2.4 Getting pre-built packages......................3 3 Usage3 4 Font encodings for Cyrillic languages4 5 Input encodings5 6 Reporting bugs6 7 Miscellanea in the T2 bundle7 Abstract This document contains basic information on the Cyrillic setup for LATEX: how to get the fonts, how to set them up, how to use the interface, its interaction with babel, etc. This is only a first draft of the document and it will probably be modified in future; so please send in comments on it via the latexbug system (see below). 1 Introduction Most Latin-based European languages were supported in LATEX by introducing the T1 font encoding and by using the fontenc and inputenc packages; these use only standard TEX means to support any 8-bit input encoding and this one 1 standard font encoding. The restriction to a single font encoding guarantees that multiple languages can happily coexist in one document (e.g., hyphenation will be correct for all languages). Starting with the December 1998 Release, LATEX finally supports Cyrillic languages. This support is based on the new standard Cyrillic TEX font encodings|T2A, T2B, T2C, and X2. The first three of these satisfy some ba- sic requirements for LATEX T* encodings, and thus can be used in multi-lingual documents with other languages based on standard font encodings.
    [Show full text]
  • Chapter 13, Using Fonts with X
    13 Using Fonts With X Most X clients let you specify the font used to display text in the window, in menus and labels, or in other text fields. For example, you can choose the font used for the text in fvwm menus or in xterm windows. This chapter gives you the information you need to be able to do that. It describes what you need to know to select display fonts for use with X client applications. Some of the topics the chapter covers are: The basic characteristics of a font. The font-naming conventions and the logical font description. The use of wildcards and aliases for simplifying font specification The font search path. The use of a font server for accessing fonts resident on other systems on the network. The utilities available for managing fonts. The use of international fonts and character sets. The use of TrueType fonts. Font technology suffers from a tension between what printers want and what display monitors want. For example, printers have enough intelligence built in these days to know how best to handle outline fonts. Sending a printer a bitmap font bypasses this intelligence and generally produces a lower quality printed page. With a monitor, on the other hand, anything more than bitmapped information is wasted. Also, printers produce more attractive print with variable-width fonts. While this is true for monitors as well, the utility of monospaced fonts usually overrides the aesthetic of variable width for most contexts in which we’re looking at text on a monitor. This chapter is primarily concerned with the use of fonts on the screen.
    [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]
  • International Language Environments Guide
    International Language Environments Guide Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 806–6642–10 May, 2002 Copyright 2002 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, Java, XView, ToolTalk, Solstice AdminTools, SunVideo and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. SunOS, Solaris, X11, SPARC, UNIX, PostScript, OpenWindows, AnswerBook, SunExpress, SPARCprinter, JumpStart, Xlib The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry.
    [Show full text]
  • Using International Characters in Bartender How to Read Data and Print Characters from Almost Every Language and Writing System in the World
    Using International Characters in BarTender How to Read Data and Print Characters from Almost Every Language and Writing System in the World Supports the following BarTender software versions: BarTender 2016, BarTender 2019 WHITE PAPER Contents Overview 3 BarTender's Unicode Support 3 Understanding International Character Support 4 Fonts 4 Scripts 4 Asian Characters 5 Writing Systems that Read Right to Left 5 Entering International Text Into Text Objects 7 Using the Insert Symbols or Special Characters Dialog 7 Using the Windows Character Map 7 Using the Keyboard 8 Reading International Characters from a Database 9 Encoding International Characters in Barcodes 10 Using Unicode Data 10 ECI Protocol 11 Formatting According to Locale 12 About Data Types 12 Example 12 Appendix A: Languages, Encodings and Scripts 13 Appendix B: Configuring Windows 14 Installing Windows Input Support for International Languages 14 Windows Support for Additional Display Languages 15 Related Documentation 16 Overview With the built-in international character support that BarTender provides, you can add international characters to your design and encode them into barcodes or RFID tags on your template. When you design items for a single locale, you can configure the format (or appearance) of information that may vary between regions, such as date and time, currency, numbering, and so on. By using BarTender, you can also globalize your design and print international materials by inserting text in multiple languages. For example, the following item illustrates how BarTender can be used with many locales with its built-in Unicode support. BarTender's Unicode Support Unicode is a universal character encoding standard that defines the basis for the processing, storage and interchange of text data in any language.
    [Show full text]
  • Can R Speak Your Language? R Uses English for Its Keywords and Its (Several Thousand) Built-In Functions
    Languages The lingua franca of computing is (American) English. Can R Speak Your Language? R uses English for its keywords and its (several thousand) built-in functions. However, the data used in computing can be in any human language (or none). One issue is to represent that data: we will discuss character sets (aka charsets) shortly. Another is to display the data in a human-readable form, both on the console and on graphics devices. Brian D. Ripley Part of the data is information related to the packages themselves. This Professor of Applied Statistics includes the manuals, help files and so on. The terser the information, the University of Oxford harder it is for non-native speakers to comprehend: this applies especially to menus and information/warning/error messages. [email protected] Internationalization (aka i18n) is the process of enabling support for data http://www.stats.ox.ac.uk/∼ripley and messages in different languages. Localization (aka i10n) is the process of adding language-specific features, such as translations of messages. Character Sets Character Sets II Long ago encodings such as EBCDIC and ASCII were developed to rep- People writing non-American English (even UK English) need other char- resent characters in decimal and binary computers. The ‘A’ abbreviates acters sets. Initially there were many proprietary extensions (DEC, HP, American, and these only handled upper- and lower-case letters A-Z, digits, MacRoman, Windows), but a fairly small number of character sets became punctuation symbols, American currency ($ but not cent), and some ‘odds’ common. These represent up to 255 characters, using a single 8-bit byte for such as # % * + / \ ^ _ | ~.
    [Show full text]
  • DICOM PS3.5 2021C
    PS3.5​ DICOM PS3.5 2021d - Data Structures and Encoding​ Page 2​ PS3.5: DICOM PS3.5 2021d - Data Structures and Encoding​ Copyright © 2021 NEMA​ A DICOM® publication​ - Standard -​ DICOM PS3.5 2021d - Data Structures and Encoding​ Page 3​ Table of Contents​ Notice and Disclaimer ........................................................................................................................................... 13​ Foreword ............................................................................................................................................................ 15​ 1. Scope and Field of Application ............................................................................................................................. 17​ 2. Normative References ....................................................................................................................................... 19​ 3. Definitions ....................................................................................................................................................... 23​ 4. Symbols and Abbreviations ................................................................................................................................. 27​ 5. Conventions ..................................................................................................................................................... 29​ 6. Value Encoding ...............................................................................................................................................
    [Show full text]
  • Windows NLS Considerations Version 2.1
    Windows NLS Considerations version 2.1 Radoslav Rusinov [email protected] Windows NLS Considerations Contents 1. Introduction ............................................................................................................................................... 3 1.1. Windows and Code Pages .................................................................................................................... 3 1.2. CharacterSet ........................................................................................................................................ 3 1.3. Encoding Scheme ................................................................................................................................ 3 1.4. Fonts ................................................................................................................................................... 4 1.5. So Why Are There Different Charactersets? ........................................................................................ 4 1.6. What are the Difference Between 7 bit, 8 bit and Unicode Charactersets? ........................................... 4 2. NLS_LANG .............................................................................................................................................. 4 2.1. Setting the Character Set in NLS_LANG ............................................................................................ 4 2.2. Where is the Character Conversion Done? .........................................................................................
    [Show full text]