DOCSLIB.ORG

SAP-Migrationen Auf Unicode

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
SAP-Migrationen Auf Unicode SAP-Migrationen auf Unicode Sebastian Buhlinger SAP Consultant, HP-SAP EMEA CC © 2004 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice Agenda 1. Introduction to Unicode 2. Unicode & SAP in General 3. Technology in Depth 3/31/2004 2 Introduction to Unicode 3/31/2004 3 1. Introduction to Unicode • History of character encoding • Problem of character encoding • From ACII to Unicode • What is Unicode exactly? • Unicode Encodings 3/31/2004 4 History of Character Encoding • Historically, computers were pretty slow, had fairly little memory and were very expensive • Up to 1960s I/O meant pushing holes into paper tapes • Most of the character sets date back to punch-card age and are designed with these cards in mind • In the early days of computers every hardware manufacturer used proprietary technology (and encodings) • International data interchange was no issue and so nothing needed to fit together 3/31/2004 5 Problem of character encoding • Which number is assigned to which character? • When typing an ‘A’ on the keyboard, the computer uses the character code as a basis for pulling the character shape of ‘A’ from a font file listing with the same binary number, and displays or prints it • The character ‘A’ may also have different integer values in different programs or data files (‘A’ might be ‘•’ in an Arabic font file) • In some instances no number available for certain characters (f.i. “&auml” à Ä) • All data encoded in the form of binary numerical codes 3/31/2004 6 Character repertoire • English alphabet: with some digits and little more: ~ 60 characters • Western European Standard: ~ 300 characters for several languages • Korean: ~12.000 syllables • Chinese dictionaries: ~ 50.000 letters • Hundreds of other characters in common use, such as math and currency symbols 3/31/2004 7 From ASCII to Unicode • Most character sets and encodings in 70s/80s were modifications or extensions of ASCII • Many of them used 8-bit with a subset of the 94 used ASCII characters • Most common encodings nowadays use single byte per character (SBCS) • They are all limited to 256 characters • Due to that, none of them can even cover the letters for the Western European languages 3/31/2004 8 What is Unicode exactly? • Unicode = universally encoded character set to store information from any language • Unicode defines • properties for each character • standardizes script behavior • provides a standard algorithm for bi directional text • defines cross-mappings for other standards • Unicode defines a unique code value for every character, regardless of platform, program or programming language used 3/31/2004 9 What is Unicode exactly? • The Unicode standard primarily encodes scripts rather than languages • Scripts comprise several languages that historically share the same set of symbols • In many cases a script may serve to write dozens of languages (e.g. the Latin script) • In other cases one script complies to one language (e.g. Hangul) 3/31/2004 10 Unicode Encodings • UTF = Unicode Transformation Format • UCS = Universal Character Set • CESU = Compatibility Encoding Scheme • Conversion between different encodings is a simple, bit-wise operation (defined in standard) • No performance excessive conversion table necessary! 3/31/2004 11 Unicode Encodings • UTF-8: Unicode Transformation based on 8- bit representation • CESU-8: Compatibility Encoding Scheme of UTF-16 on an 8-bit base • UTF-16: Unicode Transformation based on 16-bit representation 3/31/2004 12 Unicode Encodings • UCS-2: Universal Character Set 2 byte variation (16-bit) • UTF-32: Unicode Transformation based on 32-bit representation • UCS-4: Universal Character Set 4 byte variation (32 bit) 3/31/2004 13 Unicode Encodings • Not all Unicode characters are 2 bytes long ’ no doubling of hw requirements in the first place • Unicode encoding determines the length of a character • Character in one Unicode encoding can be longer than 1 byte; therefore Unicode characters can be longer than characters defined in a standard code page 3/31/2004 14 Example #1 Character UTF-8 UCS-2 UTF-16 A 41 0041 0041 c 63 0063 0063 Æ C3 86 00C6 00C6 Ö C3 B6 00F6 00F6 • DA 64 0664 0664 • E4 BA 75 9875 9875 • F0 9D 84 9E N/A D834 DD1E 3/31/2004 15 Example #2 – character “•” U+AC00 UTF- 8 HEX E A B 0 8 0 BIN 1110 1010 1011 0000 1000 0000 Lead Byte Indicator Trailing Byte Indicator Remove lead bytes 1110 1010 1011 0000 1000 0000 1010 11 0000 00 0000 Regroup bits 1010 1100 0000 0000 UTF- 16 BIN 1010 1100 0000 0000 HEX A C 0 0 3/31/2004 16 Unicode & SAP in General 3/31/2004 17 2. Unicode & SAP in General • Code Pages • SAP & Code Pages • Language Combinations before Unicode • Recommendations from SAP (w/o Unicode) • When/why do customers need Unicode? 3/31/2004 18 Code Pages • The code page determine what character you can see and enter Characters on Disk/Memory 3/31/2004 19 Code Pages • different code pages map different characters to the same byte sequence Single Byte Double Byte Characters on Disk/Memory 3/31/2004 20 SAP & Code Pages 3/31/2004 21 Language Combinations before Unicode • Single Standard Code Pages • supports specific sets of languages • the number and combination of languages that are supported cannot be altered • Standard code pages and R/3 languages (w/o EBCDIC) Double-Byte Code Pages 3/31/2004 22 Language Combinations before Unicode • It is also possible to specify a customer- specific language; this language must use one of the code pages that SAP supports; see Note 0112065 3/31/2004 23 Language Combinations before Unicode • Blended Code Pages (³ Rel. 3.1D) • SAP proprietary code pages that contain characters from one or more standard code pages • increases the combinations of languages that can be used • functionally, a Blended Code Page system uses a single code page • a Blended Code Page is a single code page system • users can see and enter all characters contained in the code page, regardless of their log-in language 3/31/2004 24 Language Combinations before Unicode SAP Code Page Supported Languages 3/31/2004 25 Language Combinations before Unicode • the availability of SAP blended code pages is platform dependent, because SAP blended locales need to be created for each platform • Blended Locale Status (x = available -- = not available) 3/31/2004 26 Language Combinations before Unicode • MDMP (³ Rel. 3.1I) Multi-Display / Multi-Processing • allows dynamic code page switching on the application server • therefore permits any combination of standard code pages on one system • the log-on language determines the code page that is active for each user • an MDMP system is recommended if: 1. one or more additional code pages are required to add languages to your existing installation 2. a blended code page cannot support the combination of languages you need for a new installation. For example, an MDMP system with the code pages 1100 and 8000, allows German and Japanese users to log onto the same R/3 system in their respective languages 3/31/2004 27 Language Combinations before Unicode Front End Example 8000 - SJIS Japan Application DB Server 1100 – ISO-1 Germany • Each user can only access one code page at a time: a user who logs in as a Japanese user cannot enter German characters, and all German characters in the database will not be correctly displayed 3/31/2004 28 Language Combinations before Unicode Example Japanese German User User 3/31/2004 29 Language Combinations before Unicode Please Note: • It is possible for a user to log on with German and then manipulate the character set and font settings so that he can enter what appear to be Japanese characters; these characters will not be correctly stored in the database and this data will be corrupt • If a user wants to enter f.i. Japanese, he/she must log on in Japanese 3/31/2004 30 Language Combinations before Unicode Please Note: • To insure that no data corruption occurs, the following restrictions must be followed: •Global data must contain only 7-bit ASCII characters, which are in all code pages •Users may use only the characters of their log-in language or 7-bit ASCII •Batch processes must be assigned with the correct user ID and language •EBCDIC code pages are not supported 3/31/2004 31 Recommendations from SAP (w/o Unicode) • In general, using a single standard code page for new installations and upgrades is the optimal decision • If additional languages or language combinations are needed, SAP recommends Unambiguous Blended Code Pages for new installations and MDMP for existing installations • Unambiguous Blended Code Pages only support certain language combinations and therefore an MDMP setup may be the only possibility for new installations as well 3/31/2004 32 Unicode-compliant SAP products • All Unicode installations are currently planned only with written permission of SAP carried out as customer projects together with SAP, except of new installations of R/3 Enterprise Extension Set 2.0 3/31/2004 33 When/why do customers need Unciode? • Global businesses that require IT systems to support multilingual data without any restrictions ’ f.i. customers with one WW central SAP system • Web interfaces open the door to a global customer base, and IT systems must consequently be able to support multiple local languages simultaneously 3/31/2004 34 When/why do customers need Unciode? • With J2EE integration, mySAP components fully support web standards, and with Unicode, it now can take full advantage of XML and Java • Only Unicode makes it possible to seamlessly integrate inhomogeneous SAP and non-SAP system landscapes ’ NetWeaver 3/31/2004 35 Technology in Depth 3/31/2004 36 3.
Load more

Recommended publications
  • PCL PC-8, Code Page 437 Page 1 of 5 PCL PC-8, Code Page 437
    PCL PC-8, Code Page 437 Page 1 of 5 PCL PC-8, Code Page 437 PCL Symbol Set: 10U Unicode glyph correspondence tables. Contact:[email protected] http://pcl.to -- -- -- -- $90 U00C9 Ê Uppercase e acute $21 U0021 Ë Exclamation $91 U00E6 Ì Lowercase ae diphthong $22 U0022 Í Neutral double quote $92 U00C6 Î Uppercase ae diphthong $23 U0023 Ï Number $93 U00F4 & Lowercase o circumflex $24 U0024 ' Dollar $94 U00F6 ( Lowercase o dieresis $25 U0025 ) Per cent $95 U00F2 * Lowercase o grave $26 U0026 + Ampersand $96 U00FB , Lowercase u circumflex $27 U0027 - Neutral single quote $97 U00F9 . Lowercase u grave $28 U0028 / Left parenthesis $98 U00FF 0 Lowercase y dieresis $29 U0029 1 Right parenthesis $99 U00D6 2 Uppercase o dieresis $2A U002A 3 Asterisk $9A U00DC 4 Uppercase u dieresis $2B U002B 5 Plus $9B U00A2 6 Cent sign $2C U002C 7 Comma, decimal separator $9C U00A3 8 Pound sterling $2D U002D 9 Hyphen $9D U00A5 : Yen sign $2E U002E ; Period, full stop $9E U20A7 < Pesetas $2F U002F = Solidus, slash $9F U0192 > Florin sign $30 U0030 ? Numeral zero $A0 U00E1 ê Lowercase a acute $31 U0031 A Numeral one $A1 U00ED B Lowercase i acute $32 U0032 C Numeral two $A2 U00F3 D Lowercase o acute $33 U0033 E Numeral three $A3 U00FA F Lowercase u acute $34 U0034 G Numeral four $A4 U00F1 H Lowercase n tilde $35 U0035 I Numeral five $A5 U00D1 J Uppercase n tilde $36 U0036 K Numeral six $A6 U00AA L Female ordinal (a) http://www.pclviewer.com (c) RedTitan Technology 2005 PCL PC-8, Code Page 437 Page 2 of 5 $37 U0037 M Numeral seven $A7 U00BA N Male ordinal (o) $38 U0038
    [Show full text]
  • Unicode and Code Page Support
    Natural for Mainframes Unicode and Code Page Support Version 4.2.6 for Mainframes October 2009 This document applies to Natural Version 4.2.6 for Mainframes and to all subsequent releases. Specifications contained herein are subject to change and these changes will be reported in subsequent release notes or new editions. Copyright © Software AG 1979-2009. All rights reserved. The name Software AG, webMethods and all Software AG product names are either trademarks or registered trademarks of Software AG and/or Software AG USA, Inc. Other company and product names mentioned herein may be trademarks of their respective owners. Table of Contents 1 Unicode and Code Page Support .................................................................................... 1 2 Introduction ..................................................................................................................... 3 About Code Pages and Unicode ................................................................................ 4 About Unicode and Code Page Support in Natural .................................................. 5 ICU on Mainframe Platforms ..................................................................................... 6 3 Unicode and Code Page Support in the Natural Programming Language .................... 7 Natural Data Format U for Unicode-Based Data ....................................................... 8 Statements .................................................................................................................. 9 Logical
    [Show full text]
  • United States Patent (19) 11 Patent Number: 5,689,723 Lim Et Al
    US005689723A United States Patent (19) 11 Patent Number: 5,689,723 Lim et al. 45) Date of Patent: Nov. 18, 1997 (54) METHOD FOR ALLOWINGSINGLE-BYTE 5,091,878 2/1992 Nagasawa et al. ..................... 364/419 CHARACTER SET AND DOUBLE-BYTE 5,257,351 10/1993 Leonard et al. ... ... 395/150 CHARACTER SET FONTS IN ADOUBLE 5,287,094 2/1994 Yi....................... ... 345/143 BYTE CHARACTER SET CODE PAGE 5,309,358 5/1994 Andrews et al. ... 364/419.01 5,317,509 5/1994 Caldwell ............................ 364/419.08 75 Inventors: Chan S. Lim, Potomac; Gregg A. OTHER PUBLICATIONS Salsi, Germantown, both of Md.; Isao Nozaki, Yamato, Japan Japanese PUPA number 1-261774, Oct. 18, 1989, pp. 1-2. Inside Macintosh, vol. VI, Apple Computer, Inc., Cupertino, (73) Assignee: International Business Machines CA, Second printing, Jun. 1991, pp. 15-4 through 15-39. Corp, Armonk, N.Y. Karew Acerson, WordPerfect: The Complete Reference, Eds., p. 177-179, 1988. 21) Appl. No.: 13,271 IBM Manual, "DOSBunsho (Language) Program II Opera 22 Filed: Feb. 3, 1993 tion Guide” (N:SH 18-2131-2) (Partial Translation of p. 79). 51 Int. Cl. ... G09G 1/00 Primary Examiner-Phu K. Nguyen 52) U.S. Cl. .................. 395/805; 395/798 Assistant Examiner-Cliff N. Vo (58) Field of Search ..................................... 395/144-151, Attorney, Agent, or Firm-Edward H. Duffield 395/792, 793, 798, 805, 774; 34.5/171, 127-130, 23-26, 143, 116, 192-195: 364/419 57 ABSTRACT The method of the invention allows both single-byte char 56) References Cited acter set (SBCS) and double-byte character set (DBCS) U.S.
    [Show full text]
  • IBM Data Conversion Under Websphere MQ
    IBM WebSphere MQ Data Conversion Under WebSphere MQ Table of Contents .................................................................................................................................................... 3 .................................................................................................................................................... 3 Int roduction............................................................................................................................... 4 Ac ronyms and terms used in Data Conversion........................................................................ 5 T he Pieces in the Data Conversion Puzzle............................................................................... 7 Coded Character Set Identifier (CCSID)........................................................................................ 7 Encoding .............................................................................................................................................. 7 What Gets Converted, and How............................................................................................... 9 The Message Descriptor.................................................................................................................... 9 The User portion of the message..................................................................................................... 10 Common Procedures when doing the MQPUT................................................................. 10 The message
    [Show full text]
  • 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]
  • Data Encoding: All Characters for All Countries
    PhUSE 2015 Paper DH03 Data Encoding: All Characters for All Countries Donna Dutton, SAS Institute Inc., Cary, NC, USA ABSTRACT The internal representation of data, formats, indexes, programs and catalogs collected for clinical studies is typically defined by the country(ies) in which the study is conducted. When data from multiple languages must be combined, the internal encoding must support all characters present, to prevent truncation and misinterpretation of characters. Migration to different operating systems with or without an encoding change make it impossible to use catalogs and existing data features such as indexes and constraints, unless the new operating system’s internal representation is adopted. UTF-8 encoding on the Linux OS is used by SAS® Drug Development and SAS® Clinical Trial Data Transparency Solutions to support these requirements. UTF-8 encoding correctly represents all characters found in all languages by using multiple bytes to represent some characters. This paper explains transcoding data into UTF-8 without data loss, writing programs which work correctly with MBCS data, and handling format catalogs and programs. INTRODUCTION The internal representation of data, formats, indexes, programs and catalogs collected for clinical studies is typically defined by the country or countries in which the study is conducted. The operating system on which the data was entered defines the internal data representation, such as Windows_64, HP_UX_64, Solaris_64, and Linux_X86_64.1 Although SAS Software can read SAS data sets copied from one operating system to another, it impossible to use existing data features such as indexes and constraints, or SAS catalogs without converting them to the new operating system’s data representation.
    [Show full text]
  • JFP Reference Manual 5 : Standards, Environments, and Macros
    JFP Reference Manual 5 : Standards, Environments, and Macros Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 817–0648–10 December 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, 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. 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. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
    [Show full text]
  • Bitmap Fonts
    .com Bitmap Fonts 1 .com Contents Introduction .................................................................................................................................................. 3 Writing Code to Write Code.......................................................................................................................... 4 Measuring Your Grid ..................................................................................................................................... 5 Converting an Image with PHP ..................................................................................................................... 6 Step 1: Load the Image ............................................................................................................................. 6 Step 2: Scan the Image .............................................................................................................................. 7 Step 3: Save the Header File ..................................................................................................................... 8 The 1602 Character Set ............................................................................................................................... 10 The 1602 Character Map ............................................................................................................................ 11 Converting the Image to Code .................................................................................................................... 12 Conclusion
    [Show full text]
  • Unicode and Code Page Support
    Natural Unicode and Code Page Support Version 8.2.4 November 2016 This document applies to Natural Version 8.2.4. Specifications contained herein are subject to change and these changes will be reported in subsequent release notes or new editions. Copyright © 1979-2016 Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors. The name Software AG and all Software AG product names are either trademarks or registered trademarks of Software AG and/or Software AG USA, Inc. and/or its subsidiaries and/or its affiliates and/or their licensors. Other company and product names mentioned herein may be trademarks of their respective owners. Detailed information on trademarks and patents owned by Software AG and/or its subsidiaries is located at http://softwareag.com/licenses. Use of this software is subject to adherence to Software AG's licensing conditions and terms. These terms are part of the product documentation, located at http://softwareag.com/licenses/ and/or in the root installation directory of the licensed product(s). This software may include portions of third-party products. For third-party copyright notices, license terms, additional rights or re- strictions, please refer to "License Texts, Copyright Notices and Disclaimers of Third-Party Products". For certain specific third-party license restrictions, please refer to section E of the Legal Notices available under "License Terms and Conditions for Use of Software AG Products / Copyright and Trademark Notices of Software AG Products". These documents are part of the product documentation, located at http://softwareag.com/licenses and/or in the root installation directory of the licensed product(s).
    [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]
  • Iso/Iec Jtc 1/Sc 2/ Wg 2 N ___Ncits-L2-98
    Unicode support in EBCDIC based systems ISO/IEC JTC 1/SC 2/ WG 2 N _______ NCITS-L2-98-257REV 1998-09-01 Title: EBCDIC-Friendly UCS Transformation Format -- UTF-8-EBCDIC Source: US, Unicode Consortium and V.S. UMAmaheswaran, IBM National Language Technical Centre, Toronto Status: For information and comment Distribution: WG2 and UTC Abstract: This paper defines the EBCDIC-Friendly Universal Multiple-Octet Coded Character Set (UCS) Transformation Format (TF) -- UTF-8-EBCDIC. This transform converts data encoded using UCS (as defined in ISO/IEC 10646 and the Unicode Standard defined by the Unicode Consortium) to and from an encoding form compatible with IBM's Extended Binary Coded Decimal Interchange Code (EBCDIC). This revised document incorporates the suggestions made by Unicode Technical Committee Meeting No. 77, on 31 July 98, and several editoiral changes. It is also being presented at the Internationalization and Unicode Conference no. 13, in San Jose, on 11 September 98. It has been accepted by the UTC as the basis for a Unicode Technical Report and is being distributed to SC 2/WG 2 for information and comments at this time. 13th International Unicode Conference 1 San Jose, CA, September 1998 Unicode support in EBCDIC based systems 1 Background UCS Transformation Format UTF-8 (defined in Amendment No. 2 to ISO/IEC 10646-1) is a transform for UCS data that preserves the subset of 128 ISO-646-IRV (ASCII) characters of UCS as single octets in the range X'00' to X'7F', with all the remaining UCS values converted to multiple-octet sequences containing only octets greater than X'7F'.
    [Show full text]
  • Character Sets Reference Manual for Line Matrix Printers
    R Character Sets Reference Manual for Line Matrix Printers Character Sets Reference Manual for Line Matrix Printers R P/N 164308–001, Rev B Printronix, Inc. makes no representations or warranties of any kind regarding this material, including, but not limited to, implied warranties of merchantability and fitness for a particular purpose. Printronix, Inc. shall not be held responsible for errors contained herein or any omissions from this material or for any damages, whether direct, indirect, incidental or consequential, in connection with the furnishing, distribution, performance or use of this material. The information in this manual is subject to change without notice. This document contains proprietary information protected by copyright. No part of this document may be reproduced, copied, translated or incorporated in any other material in any form or by any means, whether manual, graphic, electronic, mechanical or otherwise, without the prior written consent of Printronix, Inc. All rights reserved. TRADEMARK ACKNOWLEDGMENTS Printronix, LinePrinter Plus, PGL and IGP are registered trademarks of Printronix, Inc. DEC is a registered trademark of Digital Equipment Corporation. Epson is a registered trademark of Seiko Epson. IBM is a registered trademark of Internation Business Machines Corporation. Proprinter is a registered trademark of IBM. Scalable type outlines are licensed from Agfa Corporation. Agfa is a registered trademark of Agfa Division, Miles Incorporated (Agfa). CG, Garth Graphic, Intellifont, and Type Director are registered trademarks of Agfa Corporation, and Shannon and CG Triumvirate are trademarks of Agfa Corporation. CG Bodoni, CG Century Schoolbook, CG Goudy Old Style, CG Melliza, Microstyle, CG Omega, and CG Palacio are products of Agfa Corporation.
    [Show full text]