DOCSLIB.ORG

Postscript Language Reference Manual / Adobe Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

See also cross-references: abcdefghijklmnopqrltuvw PLRM 2nd Edition July 27, 1992 PostScript® Language Reference Manual SECOND EDITION 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 PLRM 2nd Edition July 27, 1992 Library of Congress Cataloging-in-Publication Data PostScript language reference manual / Adobe Systems. — 2nd ed. p. cm. Includes index. ISBN 0-201-18127-4 1. PostScript (Computer program language) I. Adobe Systems. QA76.73.P67P67 1990 005.13’3—dc20 90-43535 Copyright © 1985, 1986, 1987, 1988, 1990 Adobe Systems Incorporated. All Rights Reserved. Patents Pending. No part of this publication may be repro- duced, 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 Publish- ing Company, 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 responsi- bility 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. The name 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 Incorporated unless otherwise stated. The name PostScript also is used as a product trademark for Adobe Systems’ imple- mentation 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 writ- ten in or support the PostScript language. The sentences in this book that use “PostScript language” as an adjective phrase are so constructed to reinforce that the name refers to the standard language definition as set forth by Adobe Systems Incorporated. PostScript, the PostScript logo, Display PostScript, Adobe, the Adobe logo, Adobe Illustrator, TranScript, Carta, and Sonata are trademarks of Adobe Systems Incor- porated registered in the U.S. Adobe Garamond and Lithos are trademarks of Adobe Systems Incorporated. QuickDraw and LocalTalk are trademarks and Mac- intosh and LaserWriter are registered trademarks of Apple Computer, Inc. FrameMaker is a registered trademark of Frame Technology Corporation. ITC Stone is a registered trademark of International Typeface Corporation. IBM is a registered trademark of International Business Machines Corporation. Helvetica, Times, and Palatino are trademarks of Linotype AG and/or its subsidiaries. Microsoft and MS-DOS are registered trademarks and Windows is a trademark of Microsoft Corporation. Times New Roman is a registered trademark of The Monotype Corporation plc. NeXT is a trademark of NeXT, Inc. Sun-3 is a trade- mark of Sun Microsystems, Inc. UNIX is a registered trademark of AT&T Information Systems. X Window System is a trademark of the Massachusetts Institute of Technology. Other brand or product names are the trademarks or reg- istered trademarks of their respective holders. ABCDEFGHIJ-MW-90 First printing, December 1990 PLRM 2nd Edition January 27, 1994 Contents Preface vii Chapter 1: Introduction 1 1.1 About This Manual 3 1.2 Evolution of the PostScript Language 5 1.3 PostScript Level 2 Overview 7 1.4 Copyrights and Trademarks 9 Chapter 2: Basic Ideas 11 2.1 Raster Output Devices 11 2.2 Scan Conversion 12 2.3 Page-Description Languages 13 2.4 Using the PostScript Language 16 Chapter 3: Language 23 3.1 Interpreter 24 3.2 Syntax 25 3.3 Data Types and Objects 33 3.4 Stacks 43 3.5 Execution 45 3.6 Overview of Basic Operators 50 3.7 Memory Management 55 3.8 File Input and Output 71 3.9 Named Resources 85 3.10 Errors 99 3.11 Early Name Binding 101 3.12 Binary Encoding Details 105 3.13 Filtered Files Details 122 i PLRM 2nd Edition January 27, 1994 Chapter 4: Graphics 143 4.1 Imaging Model 144 4.2 Graphics State 146 4.3 Coordinate Systems and Transformations 150 4.4 Path Construction 157 4.5 Painting 160 4.6 User Paths 164 4.7 Forms 172 4.8 Color Spaces 176 4.9 Patterns 200 4.10 Images 210 4.11 Device Setup 226 Chapter 5: Fonts 257 5.1 Organization and Use of Fonts 257 5.2 Font Dictionaries 264 5.3 Character Encoding 269 5.4 Font Metric Information 271 5.5 Font Cache 274 5.6 Modifications to Existing Fonts 275 5.7 Type 3 Fonts 278 5.8 Unique ID Generation 283 5.9 Composite Fonts 285 Chapter 6: Rendering 293 6.1 CIE-Based Color to Device Color 294 6.2 Conversions Among Device Color Spaces 303 6.3 Transfer Functions 307 6.4 Halftones 309 6.5 Scan Conversion Details 320 Chapter 7: Display PostScript 325 7.1 Multiple Execution Contexts 326 7.2 Encoded User Names 332 7.3 Graphics and Window Systems 334 7.4 Bitmap Fonts 339 Chapter 8: Operators 343 8.1 Operator Summary 346 8.2 Operator Details 360 ii Contents PLRM 2nd Edition January 27, 1994 Appendix A: Changes to Language and Implementation 555 A.1 Language Extensions 555 A.2 Language Changes Affecting Existing Operators 560 A.3 Implementation and Documentation Changes 562 Appendix B: Implementation Limits 565 B.1 Typical Limits 566 B.2 Virtual Memory Use 569 Appendix C: Interpreter Parameters 571 C.1 Defined User and System Parameters 572 C.2 General Properties of User and System Parameters 574 C.3 Parameter Details 576 C.4 Device Parameters 579 Appendix D: Compatibility Strategies 581 D.1 The Level Approach 581 D.2 When To Provide Compatibility 582 D.3 Compatibility Techniques 585 D.4 Installing Emulations 588 Appendix E: Standard Character Sets and Encoding Vectors 591 E.1 Times Family 592 E.2 Helvetica Family 593 E.3 Courier Family 594 E.4 Symbol 595 E.5 Standard Roman Character Set 596 E.6 StandardEncoding Encoding Vector 598 E.7 ISOLatin1Encoding Encoding Vector 599 E.8 Expert Character Set 600 E.9 Expert Encoding Vector 602 E.10 ExpertSubset Encoding Vector 603 E.11 Symbol Character Set 604 E.12 Symbol Encoding Vector 606 Appendix F: System Name Encodings 607 Contents iii PLRM 2nd Edition January 27, 1994 Appendix G: Document Structuring Conventions—Version 3.0 611 G.1 Using the Document Structuring Conventions 613 G.2 Document Manager Services 614 G.3 DSC Conformance 620 G.4 Document Structure Rules 624 G.5 General Conventions 639 G.6 Requirement Conventions 658 G.7 Color Separation Conventions 685 G.8 Query Conventions 688 G.9 Open Structuring Conventions 696 G.10 Special Structuring Conventions 698 G.11 Changes Since Earlier Versions 699 G.12 DSC Version 3.0 Summary 706 Appendix H: Encapsulated PostScript File Format—Version 3.0 709 H.1 Introduction 709 H.2 Guidelines for Creating EPS Files 712 H.3 Guidelines for Importing EPS Files 718 H.4 File Types and Naming 727 H.5 Device-Specific Screen Preview 728 H.6 Device-Independent Screen Preview 730 H.7 EPS Example 733 H.8 Changes Since Version 2.0 735 Appendix I: Guidelines for Specific Operators 737 Bibliography 745 Index 747 iv Contents PLRM 2nd Edition January 27, 1994 Preface Preface It has been only five years since the first PostScript Language Reference Manual was published and the first products based on the PostScript language were introduced. In 1985, we had no reason to anticipate the far-reaching effects that the PostScript language would have on the printing and publishing industry. At that time, there were no effective page-description standards, popular typefaces were used only with spe- cific typesetting equipment, producing high-quality visual materials was restricted to specialists, and the cost of producing most corporate communication pieces was prohibitive. In its brief history, the PostScript language and the many corporations and individuals working with PostScript products have changed all that. Today all major computer, printer, and imagesetter vendors sup- port the PostScript language as a standard. The major type libraries are becoming available in PostScript-compatible formats. The cost of pro- ducing high-quality, printed material has dropped substantially. As a result, the PostScript language is becoming a part of the basic fabric of the printing, publishing, and computing industries. We at Adobe not only take great pride in this success, but more impor- tantly, we feel a significant responsibility to those who have placed their trust in us and in this technology. We are committed to enhancing the PostScript language standard so that we can continue to earn that trust. In developing this language, we have tried to remember that PostScript is only one advancement in the rich 500-year history of printing and typography. We are constantly sensitive to the fact that we are working with a delicate combination of art, tradition, and technology. Not only must the technological effectiveness of the PostScript language be improved, but our aspiration to provide the highest-quality printed results must be preserved and enhanced in each implementation of a PostScript product. v PLRM 2nd Edition January 27, 1994 Preface Any standard, if it is to continue to serve the community in the face of technological change, must grow and adapt; the PostScript language is no exception. We hope that you, the users, will find that this second edition of the PostScript Language Reference Manual incorporates many of the ideas you have given us.
Recommended publications
  • How to Create a Word Document That Uses Different Page Numbering Formats

    How to Create a Word Document That Uses Different Page Numbering Formats

    How to create a Word document that uses different page numbering formats You can use Microsoft Word to create complex documents. Books and other large documents occasionally require different page number formats in different sections of one document. For example, you can number the index pages with Roman numerals (for example, "i.", "ii.", "iii.") and the main document with Arabic numerals (for example, "1", "2", "3"). This article describes how to set up different page numbering formats. Format Page Numbering To format the page numbering for different sections, follow these steps: 1. Click between two parts of your document that you want to number differently. 2. On the Insert menu, click Break. 3. Click Next Page, Even Page, or Odd Page, and then click OK. For Help on an option, click the question mark, and then click the option. 4. Click in the first section. 5. On the View menu, click Header and Footer. 6. Click in the header or footer where you want the page number. 7. On the Header and Footer toolbar, click Insert Page Number. 8. On the Header and Footer toolbar, click Format Page Number. 9. In the Number format box, click the format that you want for the numbers in this section. 10. Do one of the following: o If you want the page numbering for the first page in this section to start at a particular number other than the first number in the format series, click Start at under Page numbering, and then enter the first number that you want to appear on the first page of the section.
  • Copy — Copy file from Disk Or URL

    Copy — Copy file from Disk Or URL

    Title stata.com copy — Copy file from disk or URL Syntax Description Options Remarks and examples Also see Syntax copy filename1 filename2 , options filename1 may be a filename or a URL. filename2 may be the name of a file or a directory. If filename2 is a directory name, filename1 will be copied to that directory. filename2 may not be a URL. Note: Double quotes may be used to enclose the filenames, and the quotes must be used if the filename contains embedded blanks. options Description public make filename2 readable by all text interpret filename1 as text file and translate to native text format replace may overwrite filename2 replace does not appear in the dialog box. Description copy copies filename1 to filename2. Options public specifies that filename2 be readable by everyone; otherwise, the file will be created according to the default permissions of your operating system. text specifies that filename1 be interpreted as a text file and be translated to the native form of text files on your computer. Computers differ on how end-of-line is recorded: Unix systems record one line-feed character, Windows computers record a carriage-return/line-feed combination, and Mac computers record just a carriage return. text specifies that filename1 be examined to determine how it has end-of-line recorded and that the line-end characters be switched to whatever is appropriate for your computer when the copy is made. There is no reason to specify text when copying a file already on your computer to a different location because the file would already be in your computer’s format.
  • Bid Check Report * * * Time: 14:04

    Bid Check Report * * * Time: 14:04

    DOT_RGGB01 WASHINGTON STATE DEPARTMENT OF TRANSPORTATION DATE: 05/28/2013 * * * BID CHECK REPORT * * * TIME: 14:04 PS &E JOB NO : 11W101 REVISION NO : BIDS OPENED ON : Jun 26 2013 CONTRACT NO : 008498 REGION NO : 9 AWARDED ON : Jul 1 2013 VERSION NO : 2 WORK ORDER# : XL4078 ------- LOW BIDDER ------- ------- 2ND BIDDER ------- ------- 3RD BIDDER ------- HWY : SR 104 TITLE : SR104 ORION MARINE CONTRACTORS, INC. BLACKWATER MARINE, LLC QUIGG BROS., INC. KINGSTON TML SLIPS 1112 E ALEXANDER AVE 12019 76TH PLACE NE 819 W STATE ST DOLPHIN PRESERVATION - PHASE 4 98520-5934 11W101 PROJECT : NH-2013(079) TACOMA WA 984214102 KIRKLAND WA 980342437 ABERDEEN WA 985200281 COUNTY(S) : KITSAP CONTRACTOR NUMBER : 100767 CONTRACTOR NUMBER : 100874 CONTRACTOR NUMBER : 680000 ENGR'S. EST. ITEM ITEM DESCRIPTION UNIT PRICE PER UNIT/ PRICE PER UNIT/ % DIFF./ PRICE PER UNIT/ % DIFF./ PRICE PER UNIT/ % DIFF./ NO. EST. QUANTITY MEAS TOTAL AMOUNT TOTAL AMOUNT AMT.DIFF. TOTAL AMOUNT AMT.DIFF. TOTAL AMOUNT AMT.DIFF. PREPARATION 1 MOBILIZATION L.S. -25.20 % -25.48 % 40.00 % 25,000.00 18,700.00 -6,300.00 18,630.00 -6,370.00 35,000.00 10,000.00 2 REMOVAL OF STRUCTURE AND OBSTRUCTION L.S. -56.10 % -65.08 % -56.71 % 115,500.00 50,700.00 -64,800.00 40,338.00 -75,162.00 50,000.00 -65,500.00 3 DISPOSAL OF CREOSOTED MATERIAL L.S. -21.05 % -8.99 % -15.79 % 47,500.00 37,500.00 -10,000.00 43,228.35 -4,271.65 40,000.00 -7,500.00 STRUCTURE 4 STRUCTURAL LOW ALLOY STEEL - DOLPHINS L.S.
  • Attachment D to Adm. Memo No. 004 INSTRUCTIONS FOR

    Attachment D to Adm. Memo No. 004 INSTRUCTIONS FOR

    Attachment D to Adm. Memo No. 004 INSTRUCTIONS FOR FORMATTING A DISKETTE Formatting is the preparation of diskettes for storage of information. There are several different versions of the format command that can be used. The version that you use depends upon the type of diskette and the type of disk drive in which the diskette is being formatted. In order for us to be able to read the Tuition Grant diskettes you send, the diskettes should be properly formatted. Below is a table that identifies the more commonly used diskette types and disk drive specifications. The correct version of the format command will appear in the row for your diskette type and drive type. The format command uses the parameter “d:” to indicate the disk drive designation. For example, your 5 ¼ drive may be the “A:” drive. Instead of typing “FORMAT D:”, replace the drive designation with “A:” and type “FORMAT A:”. To verify that the disks were formatted correctly, perform the CHKDSK command on the newly formatted diskette. The format for the CHKDSK command is “CHKDSK d:”. When the command returns the disk information, compare it to the information in the fourth column of the table that corresponds to your diskette type and disk drive.. If the “total disk space” numbers are the same, the diskette is formatted correctly. DISK TYPE DRIVE TYPE FORMAT COMMAND SPACE INFO. 5 ¼” DSDD DSDD FORMAT d: 362,496 bytes total disk space 5 ¼” DSDD HD FORMAT d: /T:40 /N:9 362,496 bytes total disk space 5 ¼” HD DSDD Cannot be formatted 5 ¼” HD HD FORMAT d: 1,213,952 bytes total disk space 3 ½” DSDD DSDD FORMAT d: 730,112 bytes total disk space 3 ½” DSDD HD FORMAT d: /T:80 /N:9 730,112 bytes total disk space 3 ½” HD DSDD Cannot be formatted 3 ½” HD HD FORMAT d: 1,457,664 bytes total disk space 3 ½” DSHD FORMAT d: 1,457,664 bytes total disk space.
  • Using a Next Workstation As a Development Platform for Version 5 Sas Applications

    Using a Next Workstation As a Development Platform for Version 5 Sas Applications

    USING A NEXT WORKSTATION AS A DEVELOPMENT PLATFORM FOR VERSION 5 SAS APPLICATIONS Joseph E St Sauver, Office of University Computing, University of Oregon ABSTRACT Similarly. there is liUle sense in tieing up a PC for hours (or days) running a large statistical analysis when a sha.red SAS Institute has yet to announce any firm plans to port the mainframe will often have abundant horsepower to handle just SAS System* to NeXT* workstations. Nonetheless, a NeXT those sorts of CPU-intensive jobs. workstation can serve as an excellent platform for developing VAXNMS· (or other mainframe) SAS System code for remote The PC version of SAS atte~s to explott this philosophy by execution. giving the user the option of either processing SAS code locally using the SUBMIT command, or processing SAS code on a The combination of a strong windowing environment, display remote mainframe SAS host using the RSUBMIT command. In a PostScript support. a built-in athemet interlace and copious perfect world. this approach would allow the user to elect the slorage eapacny bundled on lOP of more-or-Iess BSD 4.3 UNIX" best mix of local and remote resources to achieve his or her make development of SAS System code on the NeXT for objectives in a timely and cost effective manner. remote execution on another mainframe quite easy. Unfortunately, in my experience, the happy symbiosis The author's experience with use of a NeXT as a remote code envisioned between the PC version of the SAS System and the development plaHorm for SAS and SAS/Graph" on a VAXNMS mainframe version of the SAS system often breaks down.
  • Humidity Definitions

    Humidity Definitions

    ROTRONIC TECHNICAL NOTE Humidity Definitions 1 Relative humidity Table of Contents Relative humidity is the ratio of two pressures: %RH = 100 x p/ps where p is 1 Relative humidity the actual partial pressure of the water vapor present in the ambient and ps 2 Dew point / Frost the saturation pressure of water at the temperature of the ambient. point temperature Relative humidity sensors are usually calibrated at normal room temper - 3 Wet bulb ature (above freezing). Consequently, it generally accepted that this type of sensor indicates relative humidity with respect to water at all temperatures temperature (including below freezing). 4 Vapor concentration Ice produces a lower vapor pressure than liquid water. Therefore, when 5 Specific humidity ice is present, saturation occurs at a relative humidity of less than 100 %. 6 Enthalpy For instance, a humidity reading of 75 %RH at a temperature of -30°C corre - 7 Mixing ratio sponds to saturation above ice. by weight 2 Dew point / Frost point temperature The dew point temperature of moist air at the temperature T, pressure P b and mixing ratio r is the temperature to which air must be cooled in order to be saturated with respect to water (liquid). The frost point temperature of moist air at temperature T, pressure P b and mixing ratio r is the temperature to which air must be cooled in order to be saturated with respect to ice. Magnus Formula for dew point (over water): Td = (243.12 x ln (pw/611.2)) / (17.62 - ln (pw/611.2)) Frost point (over ice): Tf = (272.62 x ln (pi/611.2)) / (22.46 -
  • Sun Ultratm 5 Workstation Just the Facts

    Sun Ultratm 5 Workstation Just the Facts

    Sun UltraTM 5 Workstation Just the Facts Copyrights 1999 Sun Microsystems, Inc. All Rights Reserved. Sun, Sun Microsystems, the Sun logo, Ultra, PGX, PGX24, Solaris, Sun Enterprise, SunClient, UltraComputing, Catalyst, SunPCi, OpenWindows, PGX32, VIS, Java, JDK, XGL, XIL, Java 3D, SunVTS, ShowMe, ShowMe TV, SunForum, Java WorkShop, Java Studio, AnswerBook, AnswerBook2, Sun Enterprise SyMON, Solstice, Solstice AutoClient, ShowMe How, SunCD, SunCD 2Plus, Sun StorEdge, SunButtons, SunDials, SunMicrophone, SunFDDI, SunLink, SunHSI, SunATM, SLC, ELC, IPC, IPX, SunSpectrum, JavaStation, SunSpectrum Platinum, SunSpectrum Gold, SunSpectrum Silver, SunSpectrum Bronze, SunVIP, SunSolve, and SunSolve EarlyNotifier are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the United States and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. UNIX is a registered trademark in the United States and other countries, exclusively licensed through X/Open Company, Ltd. OpenGL is a registered trademark of Silicon Graphics, Inc. Display PostScript and PostScript are trademarks of Adobe Systems, Incorporated, which may be registered in certain jurisdictions. Netscape is a trademark of Netscape Communications Corporation. DLT is claimed as a trademark of Quantum Corporation in the United States and other countries. Just the Facts May 1999 Positioning The Sun UltraTM 5 Workstation Figure 1. The Ultra 5 workstation The Sun UltraTM 5 workstation is an entry-level workstation based upon the 333- and 360-MHz UltraSPARCTM-IIi processors. The Ultra 5 is Sun’s lowest-priced workstation, designed to meet the needs of price-sensitive and volume-purchase customers in the personal workstation market without sacrificing performance.
  • BUGS Code for Item Response Theory

    BUGS Code for Item Response Theory

    JSS Journal of Statistical Software August 2010, Volume 36, Code Snippet 1. http://www.jstatsoft.org/ BUGS Code for Item Response Theory S. McKay Curtis University of Washington Abstract I present BUGS code to fit common models from item response theory (IRT), such as the two parameter logistic model, three parameter logisitic model, graded response model, generalized partial credit model, testlet model, and generalized testlet models. I demonstrate how the code in this article can easily be extended to fit more complicated IRT models, when the data at hand require a more sophisticated approach. Specifically, I describe modifications to the BUGS code that accommodate longitudinal item response data. Keywords: education, psychometrics, latent variable model, measurement model, Bayesian inference, Markov chain Monte Carlo, longitudinal data. 1. Introduction In this paper, I present BUGS (Gilks, Thomas, and Spiegelhalter 1994) code to fit several models from item response theory (IRT). Several different software packages are available for fitting IRT models. These programs include packages from Scientific Software International (du Toit 2003), such as PARSCALE (Muraki and Bock 2005), BILOG-MG (Zimowski, Mu- raki, Mislevy, and Bock 2005), MULTILOG (Thissen, Chen, and Bock 2003), and TESTFACT (Wood, Wilson, Gibbons, Schilling, Muraki, and Bock 2003). The Comprehensive R Archive Network (CRAN) task view \Psychometric Models and Methods" (Mair and Hatzinger 2010) contains a description of many different R packages that can be used to fit IRT models in the R computing environment (R Development Core Team 2010). Among these R packages are ltm (Rizopoulos 2006) and gpcm (Johnson 2007), which contain several functions to fit IRT models using marginal maximum likelihood methods, and eRm (Mair and Hatzinger 2007), which contains functions to fit several variations of the Rasch model (Fischer and Molenaar 1995).
  • XMP SPECIFICATION PART 3 STORAGE in FILES Copyright © 2016 Adobe Systems Incorporated

    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 .
  • Encapsulated Postscript File Format Specification

    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.
  • No. 25 a Secret Index—

    No. 25 a Secret Index—

    a secret index— division leap no. 25 a secret index— Booksellers, publishers and researchers of the history of print culture. Collections purchased. Books found. Appraisals performed. Libraries built. divisionleap.com no. 25 83. 35. 59. 39. 39. 27. 30. 25. 21. 65. 48. 72. 6. contents a. Walter Benjamin—German Expressionism—Raubdrucke 17 b. Reproduction—Computing—Classification—Architecture 23 c. The Body—Tattooing—Incarceration—Crime—Sexuality 33 d. Social Movements—1968—Feminism—The SI & After 47 e. Music 57 f. Literature—Poetry—Periodicals 63 g. Film—Chris Marker 77 h. Art 85 i. Punk Zines 91 Additional images of all items available at divisionleap.com or by request. a. Walter Benjamin—German Expressionism—Raubdrucke 17 2. 1. 18 a. The Birth of Walter Benjamin’s Theory Heuber so messianically feels is near … ” of the Messianic McCole, analyzing this same letter, notes that this appears to be Benjamin’s first use of the term 1. [Victor Hueber] Die Organisierung der “Messianic” in his writings [McCole, p. 61]. The Intelligenz. Ein Aufruf. Zweite, erweiterte Auflage. idea would haunt Benjamin’s subsequent works Als Manuskript gedruckt. on history, and reach its conclusion in the second [Prague]: Druck H. Mercy, [1910]. 8vo, thesis in On the Concept of History, written just 107 pp, stab-stapled and glue bound into violet before his march into the mountains. “The past printed wraps. Front and back panels of wraps carries with it a secret index, by which it is referred detached but present, with the paper covering to its resurrection. There is an agreement and an the spine mostly perished.
  • Pdflib Text and Image Extraction Toolkit (TET) Manual

    Pdflib Text and Image Extraction Toolkit (TET) Manual

    ABC Text and Image Extraction Toolkit (TET) Version 5.2 Toolkit for extracting Text, Images, and other items from PDF Copyright © 2002–2019 PDFlib GmbH. All rights reserved. Protected by European and U.S. patents. PDFlib GmbH Franziska-Bilek-Weg 9, 80339 München, Germany www.pdflib.com phone +49 • 89 • 452 33 84-0 If you have questions check the PDFlib mailing list and archive at groups.yahoo.com/neo/groups/pdflib/info 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. TET contains modified parts of the following third-party software: CMap resources. Copyright © 1990-2019 Adobe Zlib compression library, Copyright © 1995-2017 Jean-loup Gailly and Mark Adler TIFFlib image library, Copyright © 1988-1997 Sam Leffler, Copyright © 1991-1997 Silicon Graphics, Inc. Cryptographic software written by Eric Young, Copyright © 1995-1998 Eric Young ([email protected]) Independent JPEG Group’s JPEG software, Copyright © Copyright © 1991-2017, Thomas G. Lane, Guido Vollbeding Cryptographic software, Copyright © 1998-2002 The OpenSSL Project (www.openssl.org) Expat XML parser, Copyright © 2001-2017 Expat maintainers ICU International Components for Unicode, Copyright © 1995-2012 International Business Machines Corpo- ration and others OpenJPEG library, Copyright © 2002-2014, Université catholique de Louvain (UCL), Belgium TET contains the RSA Security, Inc.