DOCSLIB.ORG

Adobe Type 1 Font Format Adobe Systems Incorporated

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Adobe Type 1 Font Format Adobe Systems Incorporated Type 1 Specifications 6/21/90 final front.legal.doc Adobe Type 1 Font Format Adobe Systems Incorporated Addison-Wesley Publishing Company, Inc. Reading, Massachusetts • Menlo Park, California • New York Don Mills, Ontario • Wokingham, England • Amsterdam Bonn • Sydney • Singapore • Tokyo • Madrid • San Juan Library of Congress Cataloging-in-Publication Data Adobe type 1 font format / Adobe Systems Incorporated. p. cm Includes index ISBN 0-201-57044-0 1. PostScript (Computer program language) 2. Adobe Type 1 font (Computer program) I. Adobe Systems. QA76.73.P67A36 1990 686.2’2544536—dc20 90-42516 Copyright © 1990 Adobe Systems Incorporated. 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 otherwise, without the prior written permission of Adobe Systems Incorporated and Addison-Wesley, Inc. Printed in the United States of America. Published simultaneously in Canada. The information in this book is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies that may appear in this book. The software described in this book is furnished under license and may only be used or copied in accordance with the terms of such license. Please remember that existing font software programs that you may desire to access as a result of information described in this book may be protected under copyright law. The unauthorized use or modification of any existing font software program could be a violation of the rights of the author. Please be sure you obtain any permission required from such authors. PostScript, the PostScript logo, Display PostScript, Adobe, and the Adobe logo are trademarks of Adobe Systems Incorporated registered in the U.S. Adobe Type Manager is a trademark of Adobe Systems Incorporated. IBM is a registered trade- mark of International Business Machines Corporation. Macintosh and LaserWriter are registered trademarks of Apple Computer, Inc. Helvetica and Optima are trademarks of Linotype AG and/or its subsidiaries. ITC Stone is a reg- istered trademark of International Typeface Corporation. Other brand or product names are the trademarks or registered trademarks of their respective holders. 3456789-MU-96959493 Third printing, February 1993, Version 1.1 Type 1 Specifications 2/12/90 final contents Contents Chapter 1: Introduction ................................................................. 1 1.1 What Is a Type 1 Font Program?.................................................... 2 1.2 What This Document Does............................................................ 3 1.3 Versions and Compatibility........................................................... 4 1.4 Copyrights for Type 1 Font Programs............................................ 5 Chapter 2: Font Program Organization.......................................... 7 2.1 Building Characters........................................................................ 7 2.2 Font Dictionary.............................................................................. 9 2.3 Explanation of a Typical Font Program....................................... 10 2.4 Inside the Encrypted Portion....................................................... 14 2.5 Unique Identification Numbers and Font Names ....................... 17 Chapter 3: Character Outline Considerations ............................... 21 3.1 Character Geography................................................................... 21 3.2 Alignments and Overshoots ........................................................ 23 3.3 Character Coordinate Space ........................................................ 25 3.4 Character Paths ............................................................................ 26 3.5 Direction of Paths ........................................................................ 27 3.6 Overlapping Paths........................................................................ 28 Chapter 4: Technical Design Considerations ................................. 29 4.1 Points at Extremes........................................................................ 29 4.2 Tangent Continuity ..................................................................... 30 4.3 Conciseness.................................................................................. 31 4.4 Consistency.................................................................................. 32 i Type 1 Specifications 2/12/90 final contents Chapter 5: Private Dictionary....................................................... 35 5.1 Declarative Hints.......................................................................... 35 5.2 Font Level Hints........................................................................... 36 5.3 BlueValues.................................................................................... 36 5.4 OtherBlues.................................................................................... 38 5.5 FamilyBlues and FamilyOtherBlues ............................................. 38 5.6 BlueScale....................................................................................... 39 5.7 BlueShift....................................................................................... 40 5.8 BlueFuzz ....................................................................................... 41 5.9 Stem Width Information ............................................................. 42 5.10 ForceBold...................................................................................... 43 5.11 LanguageGroup............................................................................ 44 5.12 lenIV............................................................................................. 45 5.13 Compatibility Entries................................................................... 45 5.14 ExpansionFactor........................................................................... 45 Chapter 6: CharStrings Dictionary................................................ 47 6.1 Charstring Encoding.................................................................... 47 6.2 Charstring Number Encoding...................................................... 48 6.3 Charstring Command Encoding.................................................. 48 6.4 Charstring Command List ........................................................... 49 6.5 Character Level Hints................................................................... 56 6.6 Encoding Example ....................................................................... 58 Chapter 7: Encryption .................................................................. 61 7.1 Encryption Method...................................................................... 61 7.2 eexec Encryption.......................................................................... 63 7.3 Charstring Encryption ................................................................. 64 Chapter 8: Using Subroutines ....................................................... 67 8.1 Changing Hints Within a Character ........................................... 69 8.2 Dot Sections ................................................................................. 71 8.3 Flex ............................................................................................... 72 8.4 First Four Subrs Entries................................................................. 78 Chapter 9: Special Font Organizations ......................................... 79 9.1 Synthetic Fonts ............................................................................ 79 9.2 Hybrid Fonts ................................................................................ 80 Chapter 10: Adobe Type Manager Compatibility .......................... 83 10.1 Simple Values ............................................................................... 84 10.2 Arrays ........................................................................................... 84 10.3 Keywords ...................................................................................... 85 ii Adobe Type 1 Font Format Type 1 Specifications 2/12/90 final contents Appendix 1: Private Dictionary Entries ......................................... 87 Appendix 2: Charstring Command Values .................................... 89 Appendix 3: OtherSubrs Programs ............................................... 91 Appendix 4: Changes................................................................... 97 Index ............................................................................................ 99 Contents iii Type 1 Specifications 2/12/90 final contents iv Adobe Type 1 Font Format Type 1 Specifications 2/12/90 final chapter 1 CHAPTER 1 Introduction This document describes the organization of the Adobe Type 1 font format and how to create a Type 1 font program. A Type 1 font program is actually a special case of a PostScript® language program. The PostScript interpreter renders the font intelligently, in a device-independent manner. This allows a font developer to create one font program that can be rendered on a wide variety of devices and at many different resolutions. • A Type 1 font program consists of a clear text (ASCII) portion, and an encoded and encrypted portion. • The PostScript language
Load more

Recommended publications
  • Performance Analysis of Text-Oriented Printing Using Postscript
    Rochester Institute of Technology RIT Scholar Works Theses 1988 Performance analysis of text-oriented printing using PostScript Thomas Kowalczyk Follow this and additional works at: https://scholarworks.rit.edu/theses Recommended Citation Kowalczyk, Thomas, "Performance analysis of text-oriented printing using PostScript" (1988). Thesis. Rochester Institute of Technology. Accessed from This Thesis is brought to you for free and open access by RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. Rochester Institute ofTechnology School ofComputer Science and Technology Perfonnance Analysis of Text-Oriented Printing Using POSTSCRIPT® by Thomas L. Kowalczyk A thesis, submitted to The Faculty ofthe School ofComputer Science and Technology, in partial fulfillment ofthe requirements for the degree of Master ofScience in Computer Science Approved by: Guy Johnson Professor and Chairman of Applied Computer Studies Dr. Vishwas G. Abhyankar instructor Frank R.Hubbell instructor October 10, 1988 Thesis Title: Performance Analysis of Text-Oriented Printing Using POSTSCRIPT® I, Thomas L. Kowalczyk, hereby grant permission to the Wallace Memorial Libra.ry, of R.I.T., to reproduce my thesis in whole or in part under the following conditions: 1. I am contacted each time a reproduction is made. I can be reached at the fol1mving address: 82 Brush Hollow Road Rochester, New York 14626 Phone # (716) 225-8569 2. Any reproduction will not be for commercial use orprofit. Date: October 10,1988 i Pennission Statement Apple, Appletalk, LaserWriter, and Macintosh are registered trademarks of Apple Computer, Inc. Fluent Laser Fonts and Galileo Roman are trademarks of CasadyWare Inc.
    [Show full text]
  • Institutionen För Datavetenskap Department of Computer and Information Science
    Institutionen för datavetenskap Department of Computer and Information Science Final thesis GPU accelerated rendering of vector based maps on iOS by Jonas Bromö and Alexander Qvick Faxå LIU-IDA/LITH-EX-A--14/023--SE 2014-05-30 Linköpings universitet Linköpings universitet SE-581 83 Linköping, Sweden 581 83 Linköping Linköpings universitet Institutionen för datavetenskap Final thesis GPU accelerated rendering of vector based maps on iOS by Jonas Bromö and Alexander Qvick Faxå LIU-IDA/LITH-EX-A--14/023--SE 2014-05-30 Supervisor: Anders Fröberg (IDA), Thibault Durand (IT-Bolaget Per & Per AB) Examiner: Erik Berglund Abstract Digital maps can be represented as either raster (bitmap images) or vector data. Vector maps are often preferable as they can be stored more efficiently and rendered irrespective of screen resolution. Vector map rendering on demand can be a computationally intensive task and has to be implemented in an efficient manner to ensure good performance and a satisfied end-user, especially on mobile devices with limited computational resources. This thesis discusses different ways of utilizing the on-chip GPU to improve the vector map rendering performance of an existing iOS app. It describes an implementation that uses OpenGL ES 2.0 to achieve the same end-result as the old CPU-based implementation using the same underlying map infras- tructure. By using the OpenGL based map renderer as well as implementing other performance optimizations, the authors were able to achieve an almost fivefold increase in rendering performance on an iPad Air. i Glossary AGG Anti-Grain Geometry. Open source graphics library with a software renderer that supports Anti-Aliasing and Subpixel Accuracy.
    [Show full text]
  • Bluebook Citation in Scholarly Legal Writing
    BLUEBOOK CITATION IN SCHOLARLY LEGAL WRITING © 2016 The Writing Center at GULC. All Rights Reserved. The writing assignments you receive in 1L Legal Research and Writing or Legal Practice are primarily practice-based documents such as memoranda and briefs, so your experience using the Bluebook as a first year student has likely been limited to the practitioner style of legal writing. When writing scholarly papers and for your law journal, however, you will need to use the Bluebook’s typeface conventions for law review articles. Although answers to all your citation questions can be found in the Bluebook itself, there are some key, but subtle differences between practitioner writing and scholarly writing you should be careful not to overlook. Your first encounter with law review-style citations will probably be the journal Write-On competition at the end of your first year. This guide may help you in the transition from providing Bluebook citations in court documents to doing the same for law review articles, with a focus on the sources that you are likely to encounter in the Write-On competition. 1. Typeface (Rule 2) Most law reviews use the same typeface style, which includes Ordinary Times New Roman, Italics, and SMALL CAPITALS. In court documents, use Ordinary Roman, Italics, and Underlining. Scholarly Writing In scholarly writing footnotes, use Ordinary Roman type for case names in full citations, including in citation sentences contained in footnotes. This typeface is also used in the main text of a document. Use Italics for the short form of case citations. Use Italics for article titles, introductory signals, procedural phrases in case names, and explanatory signals in citations.
    [Show full text]
  • Introducing Opentype Ab
    UBS AG ab Postfach CH-8098 Zürich Tel. +41-44-234 11 11 Brand Management Visual Identity Stephanie Teige FG09 G5R4-Z8S Tel. +41-1-234 59 09 Introducing OpenType Fax +41-1-234 36 41 [email protected] July 2005 www.ubs.com OpenType is a new font format developed collaboratively by Adobe and Microsoft. OpenType enhances the TrueType and PostScript technologies and extends their capabilities. Most fonts today are released in the OpenType format, now considered the industry standard. The resulting new generation of UBSHeadline and Frutiger fonts offers improved typographic and layout features. 1. What is OpenType? Frutiger is not always Frutiger Due to the wide variety of Frutiger styles available world- A single font format wide, be sure to install and use only the client-specific UBS OpenType provides a single universally acceptable font licensed version of this font. Do not use any other versions format that can be used on any major operating system of Frutiger to create UBS media. and in any application. Using the client-specific UBS Frutiger guarantees access to Macintosh Windows UBS-relevant cuts. It also prevents changes to kerning and line-break in comparison to random Frutiger styles. UBSHeadline, Frutiger UBSHeadline, Frutiger (PostScript) (TrueType) Linotype Frutiger UBS Frutiger Frutiger LT 45 Light Frutiger 45 Light Macintosh and Frutiger LT 46 Light Italic Frutiger 45 Light Italic Windows Frutiger LT 55 Roman Frutiger 55 Roman Frutiger LT 56 Italic Frutiger 55 Roman Italic UBSHeadline, Frutiger Frutiger LT 65 Bold Frutiger 45 Light Bold (OpenType) Frutiger LT 75 Black Frutiger 55 Roman Bold Frutiger LT 47 Light Condensed Frutiger 47 Light CN Unicode OpenType supports Unicode, which allows much larger Comparison of common Linotype Frutiger versus UBS client- character sets – more than 65,000 glyphs per font in many specific Frutiger.
    [Show full text]
  • Paratext in Bible Translations with Special Reference to Selected Bible Translations Into Beninese Languages
    DigitalResources SIL eBook 58 ® Paratext in Bible Translations with Special Reference to Selected Bible Translations into Beninese Languages Geerhard Kloppenburg Paratext in Bible Translations with Special Reference to Selected Bible Translations into Beninese Languages Geerhard Kloppenburg SIL International® 2013 SIL e-Books 58 2013 SIL International® ISSN: 1934-2470 Fair-Use Policy: Books published in the SIL e-Books (SILEB) series are intended for scholarly research and educational use. You may make copies of these publications for research or instructional purposes free of charge (within fair-use guidelines) and without further permission. Republication or commercial use of SILEB or the documents contained therein is expressly prohibited without the written consent of the copyright holder(s). Editor-in-Chief Mike Cahill Compositor Margaret González VRIJE UNIVERSITEIT AMSTERDAM PARATEXT IN BIBLE TRANSLATIONS WITH SPECIAL REFERENCE TO SELECTED BIBLE TRANSLATIONS INTO BENINESE LANGUAGES THESIS MASTER IN LINGUISTICS (BIBLE TRANSLATION) THESIS ADVISOR: DR. L.J. DE VRIES GEERHARD KLOPPENBURG 2006 TABLE OF CONTENTS 1. INTRODUCTION.................................................................................................................. 3 1.1 The phenomenon of paratext............................................................................................ 3 1.2 The purpose of this study ................................................................................................. 5 2. PARATEXT: DEFINITION AND DESCRIPTION.............................................................
    [Show full text]
  • XMP SPECIFICATION PART 3 STORAGE in FILES Copyright © 2016 Adobe Systems Incorporated
    XMP SPECIFICATION PART 3 STORAGE IN FILES Copyright © 2016 Adobe Systems Incorporated. All rights reserved. Adobe XMP Specification Part 3: Storage in Files NOTICE: All information contained herein is the property of Adobe Systems Incorporated. No part of this publication (whether in hardcopy or electronic form) may be reproduced or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written consent of Adobe Systems Incorporated. Adobe, the Adobe logo, Acrobat, Acrobat Distiller, Flash, FrameMaker, InDesign, Illustrator, Photoshop, PostScript, and the XMP logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. MS-DOS, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Apple, Macintosh, Mac OS and QuickTime are trademarks of Apple Computer, Inc., registered in the United States and other countries. UNIX is a trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. All other trademarks are the property of their respective owners. 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 Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies, makes no warranty of any kind (express, implied, or statutory) with respect to this publication, and expressly disclaims any and all warranties of merchantability, fitness for particular purposes, and noninfringement of third party rights. Contents 1 Embedding XMP metadata in application files .
    [Show full text]
  • Encapsulated Postscript File Format Specification
    ® Encapsulated PostScript File Format Specification ®® Adobe Developer Support Version 3.0 1 May 1992 Adobe Systems Incorporated Adobe Developer Technologies 345 Park Avenue San Jose, CA 95110 http://partners.adobe.com/ PN LPS5002 Copyright 1985–1988, 1990, 1992 by Adobe Systems Incorporated. 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 otherwise, without the prior written consent of the publisher. Any software referred to herein is furnished under license and may only be used or copied in accordance with the terms of such license. PostScript is a registered trademark of Adobe Systems Incorporated. All instances of the name PostScript in the text are references to the PostScript language as defined by Adobe Systems Incorpo- rated unless otherwise stated. The name PostScript also is used as a product trademark for Adobe Sys- tems’ implementation of the PostScript language interpreter. Any references to a “PostScript printer,” a “PostScript file,” or a “PostScript driver” refer to printers, files, and driver programs (respectively) which are written in or support the PostScript language. The sentences in this book that use “PostScript language” as an adjective phrase are so constructed to rein- force that the name refers to the standard language definition as set forth by Adobe Systems Incorpo- rated. PostScript, the PostScript logo, Display PostScript, Adobe, the Adobe logo, Adobe Illustrator, Tran- Script, Carta, and Sonata are trademarks of Adobe Systems Incorporated registered in the U.S.A. and other countries. Adobe Garamond and Lithos are trademarks of Adobe Systems Incorporated.
    [Show full text]
  • Dissertation Body Text FINAL SUBMISSION VERSION
    UCLA UCLA Electronic Theses and Dissertations Title Openness to the Development of the Relationship: A Theory of Close Relationships Permalink https://escholarship.org/uc/item/2030n6jk Author Page, Emily Publication Date 2021 Peer reviewed|Thesis/dissertation eScholarship.org Powered by the California Digital Library University of California UNIVERSITY OF CALIFORNIA Los Angeles Openness to the Development of the Relationship: A Theory of Close Relationships A dissertation submitted in partial satisfaction of the requirements for the degree of Doctor of Philosophy in Philosophy by Emily Page 2021 © Copyright by Emily Page 2021 ABSTRACT OF THE DISSERTATION Openness to the Development of the Relationship: A Theory of Close Relationships by Emily Page Doctor of Philosophy in Philosophy University of California, Los Angeles, 2021 Professor Alexander Jacob Julius, Chair In a word, this dissertation is about friendship. I begin by raising a problem related to one traditionally found within some of the philosophical literature regarding moral egalitarianism: that of partiality and friendship, except that I raise the issue of partiality within the context of one’s close relationships. From here I propose a solution to the problem based on understanding a close relationship as one in which friends possess the attitude of openness to the development of the relationship. The remainder of the dissertation is concerned with elaborating upon and explaining this conception of friendship and its consequences. In the course of doing this I propose a theory of the self and how we relate to one another, consider the importance of the psychophysical self, explore the notion of mutual recognition, reflect on relationship’s end, and, finally, explore the connections between friendship and play.
    [Show full text]
  • Quick Start Every Effort Has Been Made to Ensure That the Information in We Welcome You to Visit Our Web Site: This Document Is Complete, Accurate, and Up-To-Date
    Quick Start Every effort has been made to ensure that the information in We welcome you to visit our web site: this document is complete, accurate, and up-to-date. Oki Data http://www.okidata.com assumes no responsibility for the results of errors beyond its control. Oki Data also cannot guarantee that changes in OKI is a registered trademarks/marques déposées/marcas software and equipment made by other manufacturers and registradas, and OKICOLOR is a trademark of Oki Electric referred to in this guide will not affect the applicability of the Industry Company, Ltd. information in it. Mention of software products manufactured Adobe, Acrobat, Acrobat Reader, Illustrator, PageMaker, by other companies does not necessarily constitute Photoshop, PostScript and Type Manager are trademarks of endorsement by Oki Data. Adobe Systems Inc., which may be registered in certain Copyright 1999 Oki Data Americas, Inc. All rights reserved. jurisdictions. CorelDRAW is a registered trademark of Corel Corporation. Energy Star is a registered trademark of the First edition September, 1999. United States Environmental Protection Agency. HP and PCL Written and produced by the Oki Data Training & are registered trademarks of Hewlett-Packard. Macintosh is a Publications Department. Please address any comments on trademark of Apple Computer, Inc., registered in the U.S. and this publication other countries. Macromedia and FreeHand are registered • by mail to: trademarks of Macromedia, Inc. PANTONE is a registered Training & Publications Department trademark of Pantone, Inc. QuarkXPress is a registered Oki Data Americas, Inc. trademark of Quark, Inc. and all applicable affiliated 2000 Bishops Gate Blvd. companies. Windows is either a registered trademark or a Mt.
    [Show full text]
  • Font HOWTO Font HOWTO
    Font HOWTO Font HOWTO Table of Contents Font HOWTO......................................................................................................................................................1 Donovan Rebbechi, elflord@panix.com..................................................................................................1 1.Introduction...........................................................................................................................................1 2.Fonts 101 −− A Quick Introduction to Fonts........................................................................................1 3.Fonts 102 −− Typography.....................................................................................................................1 4.Making Fonts Available To X..............................................................................................................1 5.Making Fonts Available To Ghostscript...............................................................................................1 6.True Type to Type1 Conversion...........................................................................................................2 7.WYSIWYG Publishing and Fonts........................................................................................................2 8.TeX / LaTeX.........................................................................................................................................2 9.Getting Fonts For Linux.......................................................................................................................2
    [Show full text]
  • How to Build a Newton Font on Macos X
    How To build a Newton Font on MacOS X by Paul Guyot <[email protected]> 16th April 2004 1 Introduction This How-To explains how to port a MacOS font to NewtonOS on MacOS X. Porting fonts rely on old Apple font tools and therefore on Classic. We (the DCL Group) are currently investigating a method to port fonts without relying on these tools, but some features of these old tools we need are apparently not available in MacOS X Font Tools. Important Note : Fonts are copyrightable and usually copyrighted. Please make sure that porting a font is compatible with the license you were granted on it. This tutorial supposes that you have basic knowledge of MacOS X, that you know what the Terminal is, but it does not require that you have a long experience with the tools involved. We may use terms that would require a definition or a clarification. Most unusual terms used here are defined in the Newton Glossary1. Do not hesitate to send me corrections or ask me for clarifications if required. This tutorial will guide through porting Gill Sans. The font book application shows this font: 1http://www.splorp.com/newton/glossary/ 1 Newton Fonts How-To 2 This font actually exists in 6 forms: • Gill Sans Regular • Gill Sans Bold • Gill Sans Italic • Gill Sans Bold Italic • Gill Sans Light • Gill Sans Light Italic This font can be ported as two Newton font packages (Gill Sans and Gill Sans Light). The Gill Sans package will include regular (or plain), bold, italic and bold-italic forms and the Gill Sans Light package will include regular and italic forms.
    [Show full text]
  • Web Compatible SAS/GRAPH Output the Easy
    Web Compatible SAS/GRAPH® Output the Easy Way Ahsan Ullah, Pinkerton Computer Consultants, Inc., Alexandria, VA ABSTRACT • Proper use of colors is a must to make the image attractive. • (TM) This paper describes some concepts and analyses required If there is an option to print the image, a PostScript to create SAS/GRAPH images for use in WEB pages. It file needs to be tagged along with the image which will deals with an automated SAS/AF® Frame system designed to keep the usual form of the printed output create and print a number of graphs and produce suitable • In order to print a hard copy of the graph from the graph image files for inclusion on WEB pages. Topics internet, a PostScript color or black and white with discussed include drill-down design, programming minimum of 0.5 X 0.5 inch margin should be selected. (TM) techniques for creating GIF files, and the creation of custom Most Hewlett Packard printers satisfy the SAS Device Drivers. requirements. INTRODUCTION A user-friendly SAS/AF Frame system needs to be created to perform the following functions: • Interactive or batch process to create images. SAS software is a major leader in information and • Support the selection of device drivers to print or management systems. It has powerful features that support transport postscript or GIF file. the creation of customized hard copy output that includes • both data and graphic output. Until now, SAS custom graphs Automatically add HTML code to create Web-ready could not take their place in the Web world because of: graph images • Sophistication of SAS custom graphs • True portability across platforms Device Drivers • Interactive way to create and process graphs A GIF device driver is needed for SAS software to create a GIF Image file of the graph.
    [Show full text]