DOCSLIB.ORG

Progress Internationalization Guide © 2002 Progress Software Corporation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Progress Internationalization Guide © 2002 Progress Software Corporation Progress Internationalization Guide © 2002 Progress Software Corporation. All rights reserved. Progress® software products are copyrighted and all rights are reserved by Progress Software Corporation. This manual is also copyrighted and all rights are reserved. This manual may not, in whole or in part, be copied, photocopied, translated, or reduced to any electronic medium or machine-readable form without prior consent, in writing, from Progress Software Corporation. The information in this manual is subject to change without notice, and Progress Software Corporation assumes no responsibility for any errors that may appear in this document. The references in this manual to specific platforms supported are subject to change. Progress, Powered by Progress, Progress Fast Track, Progress Profiles, Partners in Progress, Partners en Progress, Progress en Partners, Progress in Progress, P.I.P., Progress Results, ProVision, ProCare, ProtoSpeed, SmartBeans, SpeedScript, and WebSpeed are registered trademarks of Progress Software Corporation in the U.S. and other countries. A Data Center of Your Very Own, Allegrix, Apptivity, AppsAlive, AppServer, ASPen, ASP-in-a-Box, Empowerment Center, Fathom, Future Proof, IntelliStream, OpenEdge, PeerDirect, POSSE, POSSENET, Progress Dynamics, Progress Software Developers Network, SectorAlliance, SmartObjects and WebClient are trademarks or service marks of Progress Software Corporation in the U.S. and other countries. SonicMQ is a registered trademark of Sonic Software Corporation in the U.S. and other countries. Vermont Views is a registered trademark of Vermont Creative Software in the U.S. and other countries. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Any other trademarks and/or service marks contained herein are the property of their respective owners. Progress Software Corporation acknowledges the use of Raster Imaging Technology copyrighted by Snowbound Software 1993- 1997, the IBM XML Parser for Java Edition, and software developed by the Apache Software Foundation (http:// www.apache.org/). © IBM Corporation 1998-1999. All rights reserved. U.S. Government Users Restricted Rights — Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Progress is a registered trademark of Progress Software Corporation and is used by IBM Corporation in the mark Progress/400 under license. Progress/400 AND 400® are trademarks of IBM Corporation and are used by Progress Software Corporation under license. The implementation of the MD5 Message-Digest Algorithm used by Progress Software Corporation in certain of its products is derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm. May 2002 Product Code: 4524 Item Number: 89431;V9.1D Contents Preface . xiii Purpose . xiii Audience . xiii Organization Of This Manual . xiii Typographical Conventions . xv Syntax Notation . xvi Example Procedures . xx Progress Messages . xxiii Other Useful Documentation . xxv Getting Started . xxv Development Tools . xxvi Reporting Tools . xxviii 4GL . xxviii Database . xxix DataServers. xxx SQL-89/Open Access . xxx SQL-92 . xxxi Deployment . xxxii WebSpeed. xxxii Reference . xxxiii SQL-92 Reference. xxxiii 1. Developing Applications For Deployment Worldwide . 1–1 1.1 The Importance Of Internationalization and Localization . 1–2 1.2 Strategies For Responding To a Global Market . 1–3 1.2.1 Internationalized Applications. 1–3 1.2.2 Localized Applications . 1–4 Contents 1.3 How Progress Supports Internationalization . 1–4 1.3.1 Multi-byte Applications . 1–5 1.3.2 Progress Support For Unicode . 1–5 1.3.3 Character Processing . 1–5 1.3.4 Translation Manager System . 1–6 1.3.5 Progress 4GL Elements . 1–6 1.3.6 International Databases . 1–6 1.3.7 Progress Messages . 1–7 1.3.8 Regional Parameter Files . 1–7 1.4 How Progress Products Support Internationalization . 1–8 1.5 Design Guidelines . 1–9 2. Understanding Code Pages . 2–1 2.1 Code Pages and Character Sets . 2–2 2.1.1 Code Pages . 2–2 2.1.2 Character Sets . 2–5 2.2 Environments With Multiple Code Pages . 2–7 2.3 Code-page Conversion . 2–7 2.3.1 Streams and Code-page Conversion . 2–9 2.3.2 Valid and Invalid Code-page Conversions . 2–10 2.3.3 Sockets and Code-page Conversion . 2–10 2.4 The Undefined Code Page . 2–11 2.5 Figuring Out the Code Page an Application Component Uses . 2–12 2.5.1 7-bit Character Data . 2–12 2.5.2 8-bit Character Data . 2–12 2.5.3 Progress Databases . 2–13 2.5.4 Character Terminals . 2–14 2.5.5 Windows Screen and Keyboard . 2–15 2.5.6 Printers . 2–16 2.5.7 Table Dump (.d) Files and Other External Text Files . 2–17 2.5.8 Progress Libraries . 2–17 3. Understanding Character Processing Tables . 3–1 3.1 The convmap.dat File and Its Tables . 3–2 3.1.1 Character Attribute Tables . 3–5 3.1.2 Case Tables . 3–6 3.1.3 Collation Tables . 3–9 3.1.4 Code-page Conversion Tables . 3–11 3.1.5 Modifying convmap.dat Or a File It Includes . 3–13 3.1.6 Compiling the convmap.dat File . 3–14 3.1.7 Providing Access To the convmap.cp File . 3–14 3.1.8 Modifying Collation Tables . 3–15 3.1.9 Finding Additional Information On Character Processing Tables Other Than Word-break Tables . 3–20 iv Contents 3.2 Word-break Tables . 3–21 3.2.1 Why Progress Uses Word-break Tables . 3–21 3.2.2 Creating and Modifying Word-break Tables . 3–22 3.2.3 Compiling Word-break Tables . 3–27 3.2.4 Providing Access To Word-break Tables. 3–27 3.2.5 Associating Word-break Tables With Databases . 3–28 3.2.6 Rebuilding the Indexes . 3–29 4. Preparing the Code . 4–1 4.1 Guidelines and Methodology . 4–2 4.1.1 Structuring Source Code . 4–2 4.1.2 Processing By Characters . 4–4 4.1.3 Using Variables . 4–5 4.1.4 Coding With Translation In Mind . 4–5 4.2 Input and Output . 4–6 4.2.1 Keyboards . 4–6 4.2.2 Printers . 4–7 4.3 Data-processing Issues . 4–8 4.3.1 Numeric Formats . ..
Load more

Recommended publications
  • Unicode Ate My Brain
    UNICODE ATE MY BRAIN John Cowan Reuters Health Information Copyright 2001-04 John Cowan under GNU GPL 1 Copyright • Copyright © 2001 John Cowan • Licensed under the GNU General Public License • ABSOLUTELY NO WARRANTIES; USE AT YOUR OWN RISK • Portions written by Tim Bray; used by permission • Title devised by Smarasderagd; used by permission • Black and white for readability Copyright 2001-04 John Cowan under GNU GPL 2 Abstract Unicode, the universal character set, is one of the foundation technologies of XML. However, it is not as widely understood as it should be, because of the unavoidable complexity of handling all of the world's writing systems, even in a fairly uniform way. This tutorial will provide the basics about using Unicode and XML to save lots of money and achieve world domination at the same time. Copyright 2001-04 John Cowan under GNU GPL 3 Roadmap • Brief introduction (4 slides) • Before Unicode (16 slides) • The Unicode Standard (25 slides) • Encodings (11 slides) • XML (10 slides) • The Programmer's View (27 slides) • Points to Remember (1 slide) Copyright 2001-04 John Cowan under GNU GPL 4 How Many Different Characters? a A à á â ã ä å ā ă ą a a a a a a a a a a a Copyright 2001-04 John Cowan under GNU GPL 5 How Computers Do Text • Characters in computer storage are represented by “small” numbers • The numbers use a small number of bits: from 6 (BCD) to 21 (Unicode) to 32 (wchar_t on some Unix boxes) • Design choices: – Which numbers encode which characters – How to pack the numbers into bytes Copyright 2001-04 John Cowan under GNU GPL 6 Where Does XML Come In? • XML is a textual data format • XML software is required to handle all commercially important characters in the world; a promise to “handle XML” implies a promise to be international • Applications can do what they want; monolingual applications can mostly ignore internationalization Copyright 2001-04 John Cowan under GNU GPL 7 $$$ £££ ¥¥¥ • Extra cost of building-in internationalization to a new computer application: about 20% (assuming XML and Unicode).
    [Show full text]
  • Character Set Migration Best Practices For
    Character Set Migration Best Practices $Q2UDFOH:KLWH3DSHU October 2002 Server Globalization Technology Oracle Corporation Introduction - Database Character Set Migration Migrating from one database character set to another requires proper strategy and tools. This paper outlines the best practices for database character set migration that has been utilized on behalf of hundreds of customers successfully. Following these methods will help determine what strategies are best suited for your environment and will help minimize risk and downtime. This paper also highlights migration to Unicode. Many customers today are finding Unicode to be essential to supporting their global businesses. Oracle provides consulting services for very large or complex environments to help minimize the downtime while maximizing the safe migration of business critical data. Why migrate? Database character set migration often occurs from a requirement to support new languages. As companies internationalize their operations and expand services to customers all around the world, they find the need to support data storage of more World languages than are available within their existing database character set. Historically, many legacy systems required support for only one or possibly a few languages; therefore, the original character set chosen had a limited repertoire of characters that could be supported. For example, in America a 7-bit character set called ASCII is satisfactory for supporting English data exclusively. While in Europe a variety of 8 bit European character sets can support specific subsets of European languages together with English. In Asia, multi byte character sets that could support a given Asian language and English were chosen. These were reasonable choices that fulfilled the initial requirements and provided the best combination of economy and performance.
    [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]
  • [MS-VUVP-Diff]: VT-UTF8 and VT100+ Protocols
    [MS-VUVP-Diff]: VT-UTF8 and VT100+ Protocols Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards as well as overviews of the interaction among each of these technologiessupport. Additionally, overview documents cover inter-protocol relationships and interactions. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you maycan make copies of it in order to develop implementations of the technologies that are described in the Open Specifications this documentation and maycan distribute portions of it in your implementations usingthat use these technologies or in your documentation as necessary to properly document the implementation. You maycan also distribute in your implementation, with or without modification, any schema, IDL'sschemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. documentation. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that maymight cover your implementations of the technologies described in the Open Specifications. documentation. Neither this notice nor Microsoft's delivery of thethis documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specification maySpecifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in the Open Specificationsthis documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected].
    [Show full text]
  • Electronic Document Preparation Pocket Primer
    Electronic Document Preparation Pocket Primer Vít Novotný December 4, 2018 Creative Commons Attribution 3.0 Unported (cc by 3.0) Contents Introduction 1 1 Writing 3 1.1 Text Processing 4 1.1.1 Character Encoding 4 1.1.2 Text Input 12 1.1.3 Text Editors 13 1.1.4 Interactive Document Preparation Systems 13 1.1.5 Regular Expressions 14 1.2 Version Control 17 2 Markup 21 2.1 Meta Markup Languages 22 2.1.1 The General Markup Language 22 2.1.2 The Extensible Markup Language 23 2.2 Markup on the World Wide Web 28 2.2.1 The Hypertext Markup Language 28 2.2.2 The Extensible Hypertext Markup Language 29 2.2.3 The Semantic Web and Linked Data 31 2.3 Document Preparation Systems 32 2.3.1 Batch-oriented Systems 35 2.3.2 Interactive Systems 36 2.4 Lightweight Markup Languages 39 3 Design 41 3.1 Fonts 41 3.2 Structural Elements 42 3.2.1 Paragraphs and Stanzas 42 iv CONTENTS 3.2.2 Headings 45 3.2.3 Tables and Lists 46 3.2.4 Notes 46 3.2.5 Quotations 47 3.3 Page Layout 48 3.4 Color 48 3.4.1 Theory 48 3.4.2 Schemes 51 Bibliography 53 Acronyms 61 Index 65 Introduction With the advent of the digital age, typesetting has become available to virtually anyone equipped with a personal computer. Beautiful text documents can now be crafted using free and consumer-grade software, which often obviates the need for the involvement of a professional designer and typesetter.
    [Show full text]
  • Electronic Discovery Workbook
    Computer Metadata File Electronic Discovery Workbook 2016 University of Texas School of Law LAW335E: E-Discovery and Digital Evidence Fall 2016 Ver. 16.0818 © Craig Ball, All Rights Reserved Name: Course Workbook Reading Assignments NOTE: This table is for your convenience; but, the timing and scope of your responsibilities in this course are established by the latest Syllabus, not this table. Always go by the Syllabus!! The following Workbook exercises and readings should be completed prior to the start of class on the dates set out for same below. There will always be additional readings on Canvas. Monday, August 29 Read pp. 4-84; Complete Exercise 1 Monday, September 12 Read pp. 85-101; Complete Exercise 2 Monday, September 19 (No class meeting this date) Read pp. 102-175; Complete Exercises 3-8 Monday, September 26 Read pp. 176-234; Complete Exercises 9-12 Monday, October 3 Read pp. 235-283, Complete Exercise 13 Monday, October 10 Read pp. 284-327; Complete Exercise 14, Part 1, pp. 282 Monday, October 17 No Workbook selections Monday, October 24 Read pp. 328-351; Complete Exercise 15 Monday, October 31 Read pp. 352-385; Complete Exercises 16-17 Monday, November 7 Read pp. 386-402; Begin Exercise 18 1 Contents Goals for this Workbook ...................................................................................................... 4 Introduction to Electronic Discovery and Digital Evidence .................................................... 6 Introduction to Discovery in U.S. Civil Litigation ................................................................... 9 The “E-Discovery Rules” (1,16,26,34 & 45) of the Federal Rules of Civil Procedure With Committee Notes accompanying 2006 and 2015 Amendments .......................................... 14 TRCP Rule 196.4 Electronic or Magnetic Data (enacted 1999) ...........................................
    [Show full text]
  • Windows Mbox Viewer User Manual 1.0.2.6 Table of Contents 1 Modification History
    Windows MBox Viewer User Manual 1.0.2.6 Table of Contents 1 Modification History.......................................................................................................................3 2 Feedback..........................................................................................................................................3 3 Overview.........................................................................................................................................4 4 Installation.......................................................................................................................................4 5 Running the MBox viewer..............................................................................................................4 5.1 Argument List Summary..............................................................................................................4 5.2 Setting Options from GUI............................................................................................................5 5.3 Basic Use Case.............................................................................................................................6 5.4 Mail Context Menu.......................................................................................................................7 5.5 Mail Archive Context menu.........................................................................................................8 5.6 Mail Attachments..........................................................................................................................9
    [Show full text]
  • ASCII, Unicode, and in Between Douglas A. Kerr Issue 3 June 15, 2010 ABSTRACT the Standard Coded Character Set ASCII Was Formall
    ASCII, Unicode, and In Between Douglas A. Kerr Issue 3 June 15, 2010 ABSTRACT The standard coded character set ASCII was formally standardized in 1963 and, in its “complete” form, in 1967. It is a 7-bit character set, including 95 graphic characters. As personal computers emerged, they typically had an 8-bit architecture. To exploit that, they typically came to use character sets that were “8-bit extensions of ASCII”, providing numerous additional graphic characters. One family of these became common in computers using the MS-DOS operating system. Another similar but distinct family later became common in computers operating with the Windows operating system. In the late 1980s, a true second-generation coded character set, called Unicode, was developed, and was standardized in 1991. Its structure provides an ultimate capacity of about a million graphic characters, catering thoroughly to the needs of hundreds of languages and many specialized and parochial uses. Various encoding techniques are used to represent characters from this set in 8- and 16-bit computer environments. In this article, we will describe and discuss these coded character sets, their development, their status, the relationships between them, and practical implications of their use. Information is included on the entry, in Windows computer systems, of characters not directly accessible from the keyboard. BEFORE ASCII As of 1960, the interchange of data within and between information communication and processing systems was made difficult by the lack of a uniform coded character set. Information communication in the traditional “teletypewriter” sense generally used a 5-bit coded character set, best described as the “Murray code” (although as a result of historical misunderstandings it is often called the “Baudot code”).
    [Show full text]
  • Windows Code Page -Wikipedia, the Free Encyclopedia Page 1 of 4
    Windows code page -Wikipedia, the free encyclopedia Page 1 of 4 Windows code page From Wikipedia, the free encyclopedia Windows code pages are sets of characters or code pages (known as character encodings in other operating systems) used in Microsoft Windows from the 1980s and 1990s. Windows code pages were gradually superseded when Unicode was implemented in Windows, although they are still supported both within Windows and other platforms. There are two groups of code pages in Windows systems: OEM and ANSI code pages. Code pages in both of these groups are extended ASCII code pages. Contents ◾ 1 ANSI code page ◾ 2 OEM code page ◾ 3 History ◾ 4 List ◾ 5 Problems arising from the use of code pages ◾ 6 See also ◾ 7 References ◾ 8 External links ANSI code page ANSI code pages (officially called "Windows code pages"[1] after Microsoft accepted the former term being a misnomer[2]) are used for native non-Unicode (say, byte oriented) applications using a graphical user interface on Windows systems. ANSI Windows code pages, and especially the code page 1252, were called that way since they were purportedly based on drafts submitted or intended for ANSI. However, ANSI and ISO have not standardized any of these code pages. Instead they are either supersets of the standard sets such as those of ISO 8859 and the various national standards (like Windows-1252 vs. ISO-8859-1), major modifications of these (making them incompatible to various degrees, like Windows-1250 vs. ISO-8859-2) or having no parallel encoding (like Windows- 1257 vs. ISO-8859-4; ISO-8859-13 was introduced much later).[2] About twelve of the typography and business characters from CP1252 at code points 0x80–0x9F (in ISO 8859 occupied by C1 control codes, which are useless in Windows) are present in many other ANSI/Windows code pages at the same codes.
    [Show full text]
  • Dl4 Installation & Configuration Guide for Unix
    Installation & Configuration Guide Unix Revision 4.3 Information in this document is subject to change without notice and does not represent a commitment on the part of Dynamic Concepts Inc. (DCI). Every attempt was made to present this document in a complete and accurate form. DCI shall not be responsible for any damages (including, but not limited to consequential) caused by the use of or reliance upon the product(s) described herein. The software described in this document is furnished under a license agreement or nondisclosure agreement. The purchaser may use and/or copy the software only in accordance with the terms of the agreement. No part of this manual may be reproduced in any way, shape or form, for any purpose, without the express written consent of DCI. © Copyright 2001 Dynamic Concepts Inc. (DCI). All rights reserved. Dynamic Concepts Inc. 18-B Journey Aliso Viejo, CA 92656 www.dynamic.com dL4 is a trademark of Dynamic Concepts Inc. UniBasic is a trademark of Dynamic Concepts Inc. Dynamic Windows is a trademark of Dynamic Concepts Inc. BITS is a trademark of Dynamic Concepts Inc. IRIS is a trademark of Point 4 Data Corporation. c-tree is a trademark of Faircom. IQ is a trademark of IQ Software Corporation. UNIX is a registered trademark of UNIX Systems Laboratories. SYBASE is a registered trademark of Sybase Inc. CodeBase is a trademark of Sequiter Software Inc. Microsoft, MS, MS-DOS, Microsoft Access, and FoxPro are registered trademarks, and ODBC, Windows and Windows NT are trademarks of Microsoft Corporation in the USA and other countries.
    [Show full text]
  • Supporting the Chinese Language in Oracle Text
    Supporting the Chinese Language in Oracle® Text Masterarbeit im Fach Arbeits-, Lern- und Präsentationstechniken Masterstudiengang Informationswirtschaft der Fachhochschule Stuttgart – Hochschule der Medien Poh Choo Lai Erstprüfer: Prof. Dr.-Ing. Peter Lehmann Zweitprüferin: Frau Barbara Steinhanses Bearbeitungszeitraum: 20. Okt 2003 bis 31. Mär 2004 Stuttgart, März 2004 Erklärung ii Erklärung Hiermit erkläre ich, dass ich die vorliegende Masterarbeit selbständig angefertigt habe. Es wurden nur die in der Arbeit ausdrücklich benannten Quellen und Hilfsmittel benutzt. Wörtlich oder sinngemäß übernommenes Gedankengut habe ich als solches kenntlich gemacht. Ort, Datum Unterschrift Kurzfassung iii Kurzfassung Gegenstand dieser Arbeit sind die Problematik von chinesischem Information Retrieval (IR) sowie die Faktoren, die die Leistung eines chinesischen IR-System beeinflussen können. Experimente wurden im Rahmen des Bewertungsmodells von „TREC-5 Chinese Track“ und der Nutzung eines großen Korpusses von über 160.000 chinesischen Nachrichtenartikeln auf einer Oracle10g (Beta Version) Datenbank durchgeführt. Schließlich wurde die Leistung von Oracle® Text in einem so genannten „Benchmarking“ Prozess gegenüber den Ergebnissen der Teilnehmer von TREC-5 verglichen. Die Hauptergebnisse dieser Arbeit sind: (a) Die Wirksamkeit eines chinesischen IR Systems ist durch die Art und Weise der Formulierung einer Abfrage stark beeinflusst. Besonders sollte man während der Formulierung einer Anfrage die Vielzahl von Abkürzungen und die regionalen Unterschiede
    [Show full text]
  • Using Unicode Skywire Software, L.L.C
    Start Using Unicode Skywire Software, L.L.C. Phone: (U. S.) 972.377.1110 3000 Internet Boulevard (EMEA) +44 (0) 1372 366 200 Suite 200 FAX: (U. S.) 972.377.1109 Notice Frisco, Texas 75034 (EMEA) +44 (0) 1372 366 201 www.skywiresoftware.com Support: (U. S.) 866.4SKYWIRE (EMEA) +44 (0) 1372 366 222 [email protected] PUBLICATION COPYRIGHT NOTICE Copyright © 2008 Skywire Software, L.L.C. All rights reserved. Printed in the United States of America. This publication contains proprietary information which is the property of Skywire Software or its subsidiaries. This publication may also be protected under the copyright and trade secret laws of other countries. TRADEMARKS Skywire® is a registered trademark of Skywire Software, L.L.C. Docucorp®, its products (Docucreate™, Documaker™, Docupresentment™, Docusave®, Documanage™, Poweroffice®, Docutoolbox™, and Transall™) , and its logo are trademarks or registered trademarks of Skywire Software or its subsidiaries. The Docucorp product modules (Commcommander™, Docuflex®, Documerge®, Docugraph™, Docusolve®, Docuword™, Dynacomp®, DWSD™, DBL™, Freeform®, Grafxcommander™, Imagecreate™, I.R.I.S. ™, MARS/NT™, Powermapping™, Printcommander®, Rulecommander™, Shuttle™, VLAM®, Virtual Library Access Method™, Template Technology™, and X/HP™ are trademarks of Skywire Software or its subsidiaries. Skywire Software (or its subsidiaries) and Mynd Corporation are joint owners of the DAP™ and Document Automation Platform™ product trademarks. Docuflex is based in part on the work of Jean-loup Gailly and Mark Adler. Docuflex is based in part on the work of Sam Leffler and Silicon Graphic, Inc. Copyright © 1988-1997 Sam Leffler. Copyright © 1991-1997 Silicon Graphics, Inc. Docuflex is based in part on the work of the Independent JPEG Group.
    [Show full text]