Open Print Remake 6.3 Normalization Guide

Total Page:16

File Type:pdf, Size:1020Kb

Open Print Remake 6.3 Normalization Guide Open Print Remake 6.3 Normalization Guide Paris Boston Bristol www.sefas.com This manual, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. The content of this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Sefas Innovation. Sefas Innovation assumes no responsibility or liability for any errors or inaccuracies that may appear in this documentation. Except as per- mitted by such license, no part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Sefas Innovation, Inc. All cited product names and logos are the respective property of their owners. Document version: 6.3.e © Sefas Innovation, 2009. All rights reserved. Table of Contents Introduction 5 Color substitution table . 46 . IBM color codes and default values . 47 Introduction . 5 Default color substitution table . 47 Compatibility . 49 About this document . 5 Managing images . 50 Overview of normalization . 5 Image configuration table. 50 Scenarios that require normalization . 6 The normalization process. 6 Managing de-imposition . 51 Stage 1 - Analysis . 6 Normalizing the stream . 52 Stage 2 - Resource extraction . 6 Verifying required input . 52 Stage 3 - Normalization . 6 Processing External Resources . 52 Normalization engines . 7 Entering command line parameters. 53 Dynamic vs. manual mode . 8 Command line parameters . 53 Command Line Example . 55 About TechFont . 8 Executing the normalization . 55 About the Remake user interface . 8 Locating the VPF output . 56 About the sample applications . 9 HP-PCL normalization 57 AFP-DS normalization 11 . About the TechPCL normalization engine . 57 Overview . 11 Configuration file and keywords . 57 About the TechAFP normalization engine . 11 Command line parameters . 57 Configuration file and keywords . 11 Before you begin . 58 Command line parameters . 11 Verifying third-party applications . 58 Before you begin . 12 Gathering PCL resources. 58 Verifying third-party applications . 12 Creating the application directory structure 58 Gathering AFP resources . 12 Setting up the sample application . 59 For all types of streams . 12 Creating project directories. 59 For MO:DCA ACIF streams . 12 Copying directories and files . 59 For MO:DCA non-ACIF streams . 12 Preparing the font environment . 60 For streams in mixed or line mode . 12 Resident fonts . 60 Creating the application directory structure 13 Example of Font Substitution . 60 Setting up the sample application . 13 Soft fonts . 60 Creating project directories . 13 Creating a new project . 61 Copying directories and files. 13 Preparing the input file . 62 Creating a new project . 14 Spooling the file to be normalized . 62 Preparing the input file . 15 Configuring the application . 62 Spooling the file to be normalized . 15 Verifying the operating mode . 62 Configuring the application . 15 Selecting the input file and configuration file . 63 Verifying the operating mode. 16 Configuring the normalization engine . 65 Selecting the input file and configuration file . 16 Overview of the configuration file . 65 Configuring the normalization engine . 19 Sections . 65 Overview of the configuration file. 19 Keywords . 66 Sections . 19 Comments . 66 Keywords . 19 Examples . 66 Comments . 19 Editing the configuration file. 67 Examples . 20 Keywords and descriptions . 68 Editing the configuration file . 22 Normalizing the stream . 71 Keywords and descriptions . 24 Entering command line parameters. 71 General keywords . 24 Command line parameters . 71 Line mode keywords . 43 Example command line . 72 Managing color . 45 Normalizing the PCL file . 73 Overview of substituting color . 45 Locating the VPF output . 73 Color substitution table . 45 Color modes . 45 Standard colors (OCA). 45 LCDS/Metacode normalization 75 RGB colors . 45 . CMYK colors . 46 Overview . 75 Highlight colors. 46 About the TechLCDS normalization engine . 75 CIELab colors . 46 Configuration file and keywords . 75 © Sefas Innovation, 2009 3 Command line parameters . 75 Locating the VPF output. 101 Before you begin . 76 Verifying third-party applications . 76 Postscript normalization 103 Gathering resources . 76 . Creating the application directory structure 76 Overview . 103 Setting up the sample application . 77 The TechMulti normalization engine . 103 Creating project directories . 77 Configuration files. 103 Copying directories and files . 77 Before you begin . 104 Creating a new project . 78 Verifying third-party applications . 104 Preparing the input file . 79 Gathering the required resources . 104 Spooling the file to be normalized. 79 Creating the application directory structure 104 Configuring the application . 79 Creating project directories . 104 Verifying the operating mode . 79 Managing fonts and images . 105 Selecting the input file and configuration file . 80 Fonts . 105 Configuring the normalization engine . 83 Images . 105 Overview of the configuration file. 83 Preparing the input file . 106 Sections . 83 Configuring the normalization engine . 106 Keywords . 83 Overview of techmulti.cfg. 106 Example - techlcds.cfg . 83 Keywords. 107 Editing the configuration file . 84 Overview of techmulti_ibin.cfg . 107 Keywords and descriptions. 85 Example 1 . 107 General keywords (all streams) . 85 Example 2 . 108 Fixed-record-length data streams . 86 Overview of techmulti_font.cfg . 109 Variable-length data streams . 87 Delimited-record data streams . 87 Creating the batch file . 109 Normalizing the stream . 88 Setting environment variables . 109 Command line parameters . 110 Verifying required input . 88 Example command line . 110 Entering command line parameters . 88 Command line parameters . 89 Normalizing the stream . 112 Command line example . 90 Handling errors . 112 Executing the normalization . 91 Locating the VPF output. 112 Locating the VPF output. 91 Index 113 PDF. normalization. 93. Overview . 93.
Recommended publications
  • The Microsoft Office Open XML Formats New File Formats for “Office 12”
    The Microsoft Office Open XML Formats New File Formats for “Office 12” White Paper Published: June 2005 For the latest information, please see http://www.microsoft.com/office/wave12 Contents Introduction ...............................................................................................................................1 From .doc to .docx: a brief history of the Office file formats.................................................1 Benefits of the Microsoft Office Open XML Formats ................................................................2 Integration with Business Data .............................................................................................2 Openness and Transparency ...............................................................................................4 Robustness...........................................................................................................................7 Description of the Microsoft Office Open XML Format .............................................................9 Document Parts....................................................................................................................9 Microsoft Office Open XML Format specifications ...............................................................9 Compatibility with new file formats........................................................................................9 For more information ..............................................................................................................10
    [Show full text]
  • Background Information History, Licensing, and File Formats Copyright This Document Is Copyright © 2008 by Its Contributors As Listed in the Section Titled Authors
    Getting Started Guide Appendix B Background Information History, licensing, and file formats Copyright This document is Copyright © 2008 by its contributors as listed in the section titled Authors. You may distribute it and/or modify it under the terms of either the GNU General Public License, version 3 or later, or the Creative Commons Attribution License, version 3.0 or later. All trademarks within this guide belong to their legitimate owners. Authors Jean Hollis Weber Feedback Please direct any comments or suggestions about this document to: [email protected] Acknowledgments This Appendix includes material written by Richard Barnes and others for Chapter 1 of Getting Started with OpenOffice.org 2.x. Publication date and software version Published 13 October 2008. Based on OpenOffice.org 3.0. You can download an editable version of this document from http://oooauthors.org/en/authors/userguide3/published/ Contents Introduction...........................................................................................4 A short history of OpenOffice.org..........................................................4 The OpenOffice.org community.............................................................4 How is OpenOffice.org licensed?...........................................................5 What is “open source”?..........................................................................5 What is OpenDocument?........................................................................6 File formats OOo can open.....................................................................6
    [Show full text]
  • Sharing Files with Microsoft Office Users
    Sharing Files with Microsoft Office Users Title: Sharing Files with Microsoft Office Users: Version: 1.0 First edition: November 2004 Contents Overview.........................................................................................................................................iv Copyright and trademark information........................................................................................iv Feedback.................................................................................................................................... iv Acknowledgments......................................................................................................................iv Modifications and updates......................................................................................................... iv File formats...................................................................................................................................... 1 Bulk conversion............................................................................................................................... 1 Opening files....................................................................................................................................2 Opening text format files.............................................................................................................2 Opening spreadsheets..................................................................................................................2 Opening presentations.................................................................................................................2
    [Show full text]
  • Document Conversion Technical Manual Version: 10.3.0
    Kofax Communication Server KCS Document Conversion Technical Manual Version: 10.3.0 Date: 2019-12-13 © 2019 Kofax. All rights reserved. Kofax is a trademark of Kofax, Inc., registered in the U.S. and/or other countries. All other trademarks are the property of their respective owners. No part of this publication may be reproduced, stored, or transmitted in any form without the prior written permission of Kofax. Table of Contents Chapter 1: Preface...................................................................................................................................... 7 Purpose...............................................................................................................................................7 Third Party Licenses................................................................................................................7 Usage..................................................................................................................................................7 Feature Comparison (Links Versus TWS)......................................................................................... 8 Conversion Tools................................................................................................................................ 8 Imgio.......................................................................................................................................10 File Formats......................................................................................................................................10
    [Show full text]
  • Microsoft Office Word 2003 Rich Text Format (RTF) Specification White Paper Published: April 2004 Table of Contents
    Microsoft Office Word 2003 Rich Text Format (RTF) Specification White Paper Published: April 2004 Table of Contents Introduction......................................................................................................................................1 RTF Syntax.......................................................................................................................................2 Conventions of an RTF Reader.............................................................................................................4 Formal Syntax...................................................................................................................................5 Contents of an RTF File.......................................................................................................................6 Header.........................................................................................................................................6 Document Area............................................................................................................................29 East ASIAN Support........................................................................................................................142 Escaped Expressions...................................................................................................................142 Character Set.............................................................................................................................143 Character Mapping......................................................................................................................143
    [Show full text]
  • Microsoft Exchange 2007 Journaling Guide
    Microsoft Exchange 2007 Journaling Guide Digital Archives Updated on 12/9/2010 Document Information Microsoft Exchange 2007 Journaling Guide Published August, 2008 Iron Mountain Support Information U.S. 1.800.888.2774 [email protected] Copyright © 2008 Iron Mountain Incorporated. All Rights Reserved. Trademarks Iron Mountain and the design of the mountain are registered trademarks of Iron Mountain Incorporated. All other trademarks and registered trademarks are the property of their respective owners. Entities under license agreement: Please consult the Iron Mountain & Affiliates Copyright Notices by Country. Confidentiality CONFIDENTIAL AND PROPRIETARY INFORMATION OF IRON MOUNTAIN. The information set forth herein represents the confidential and proprietary information of Iron Mountain. Such information shall only be used for the express purpose authorized by Iron Mountain and shall not be published, communicated, disclosed or divulged to any person, firm, corporation or legal entity, directly or indirectly, or to any third person without the prior written consent of Iron Mountain. Disclaimer While Iron Mountain has made every effort to ensure the accuracy and completeness of this document, it assumes no responsibility for the consequences to users of any errors that may be contained herein. The information in this document is subject to change without notice and should not be considered a commitment by Iron Mountain. Iron Mountain Incorporated 745 Atlantic Avenue Boston, MA 02111 +1.800.934.0956 www.ironmountain.com/digital
    [Show full text]
  • Rastermaster® for Java™ V20.2 Programmer's Guide
    RasterMaster® for Java™ v20.2 Programmer’s Guide RasterMaster® is the industry’s leading document/image conversion and imaging library for Java. It is continually enhanced with new functionality and formats and was developed by Snowbound’s experts who have nearly a hundred years of combined imaging expertise. It provides High-Speed File Conversion as well as Extensive Format Support. This guide is designed to provide developers with a high-level overview of RasterMaster’s functionality and capabilities, including conceptual information as well as code samples. For the full API reference, please see the Javadocs included with your build or visit docs.snowbound.com/rastermaster/latest/java/rastermaster-api/. IMPORTANT NOTICE: The online version of this manual contains information on the latest updates to RasterMaster. To find the most recent version of this manual, please visit the online version at www.rastermaster.com or download the most recent version from our website at www.snowbound.com/support/manuals.html. Copyright Information While Snowbound® Software believes the information included in this publication is correct as of the publication date, information in this document is subject to change without notice. UNLESS EXPRESSLY SET FORTH IN A WRITTEN AGREEMENT SIGNED BY AN AUTHORIZED REPRESENTATIVE OF SNOWBOUND SOFTWARE CORPORATION MAKES NO WARRANTY OR REPRESENTATION OF ANY KIND WITH RESPECT TO THE INFORMATION CONTAINED HEREIN, INCLUDING WARRANTY OF MERCHANTABILITY AND FITNESS FOR A PURPOSE, NON-INFRINGEMENT, OR THOSE WHICH MAY BE IMPLIED THROUGH COURSE OF DEALING OR CUSTOM OF TRADE. WITHOUT LIMITING THE FOREGOING, CUSTOMER UNDERSTANDS THAT SNOWBOUND DOES NOT WARRANT THAT CUSTOMER’S OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE, THAT ALL DEFECTS IN THE SOFTWARE WILL BE CORRECTED, OR THAT THE RESULTS OF THE SOFTWARE WILL BE ERROR-FREE.
    [Show full text]
  • Office File Formats Overview
    Office File Formats Overview Tom Jebo Sr Escalation Engineer Agenda • Microsoft Office Supported Formats • Open Specifications File Format Documents and Resources • Benefits of broadly-adopted standards • Microsoft Office Extensibility • OOXML Format Overview Microsoft Office 2016 File Format Support • Office Open XML (.docx, .xlsx, .pptx) • Microsoft Office Binary Formats (.doc, .xls, .ppt) (legacy) • OpenDocument Format (.odt, .ods, .odp) • Portable Document Format (.pdf) • Open XML Paper Specification (.xps) Microsoft File Formats Documents and Resources File Format Related Documents • Documentation Intro & Reference Binary Formats Standards • https://msdn.microsoft.com/en- [MS-OFFDI] [MS-DOC] [MS-DOCX] us/library/gg134029.aspx [MS-OFCGLOS] [MS-XLS] [MS-XLSX] [MS-OFREF] [MS-XLSB] [MS-PPTX] • [MS-OFFDI] start here [MS-OSHARED] [MS-PPT] [MS-OE376] • Standards implementation notes [MS-OFFCRYPTO] [MS-OI29500] • File format documentation Macros [MS-OODF] OneNote [MS-OFFMACRO] [MS-OODF2] • SharePoint & Exchange/Outlook client-server protocols [MS-ONE] [MS-OFFMACRO2] [MS-OODF3] • Windows client and server protocols [MS-ONESTORE] [MS-OVBA] [MS-ODRAWXML] • .NET Framework Office Drawing/Graphics Other • XAML Customization [MS-CTDOC] [MS-ODRAW] [MS-DSEXPORT] • Support [MS-CTXLS] [MS-OGRAPH] [MS-ODCFF] [MS-CUSTOMUI] [MS-OFORMS] • [email protected] [MS-CUSTOMUI2] [MS-WORDLFF] • MSDN Open Specifications forums [MS-OWEMXML] Outlook [MS-XLDM] [MS-PST] [MS-3DMDTP] Reviewing Binary Formats • CFB – [MS-CFB] storages and streams Binary Formats • Drawing
    [Show full text]
  • How to Create Accessible Documents in Microsoft Office (Word, Powerpoint Or Excel) Or Google Doc
    How to Create Accessible Documents in Microsoft Office (Word, PowerPoint or Excel) or Google Doc Microsoft Word application is commonly used among individuals with and without disabilities, and it has accessibility features. The following part provides information to guide you to build accessible documents in Microsoft Word. Those steps are applicable in other Microsoft Office (PowerPoint or Excel) and Google Doc as well. The major components include use of Font, ​ ​ Headings, Lists, Meaningful Hyperlinks, Alternate Text for Images, Table, and Document ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ Language Identification. ​ ❖ Use Sans Serif Fonts ​ ➢ Sans serif fonts (Helvetica, Arial, Verdana, Calibri, Comic Sans, and Geneva) are easier to read by digital, for learners with dyslexia ➢ Serif fonts (i.e., Times New Roman) are easier to read in print ➢ Suggest the use of an 11- or 12-point font size ❖ Use Headings to Organize the Document Instead of Manual Formatting ​ ​ ➢ Point your mouse to Home tab ➢ Find and click on Styles ➢ Use the built-in Heading styles, such as “Heading 1” (as the main heading) and “Heading 2” (as subheadings) ➢ The default, light blue, can be hard to read and is not accessible. Use the right mouse button to click on Heading 1, select Modify, and change the color of the heading from blue to black ➢ Change the default font from Calibri to any other san serif font, select a different size, or select bold; the American Federation for the Blind suggests, “Use bold. Avoid using italics or all capital letters.” ➢ Form an outline with headings ➢ With additional levels of headings within the document’s outline, use “Heading 3”, “Heading 4”, etc.
    [Show full text]
  • File Formatsformats
    FILEFILE FORMATSFORMATS Summary records created or formatted electronically are Rapid changes in technology mean that file formats covered under the act. can become obsolete quickly and cause problems for Proprietary, Non-proprietary, Open your records management strategy. A long-term view Standard and Open Source File Formats and careful planning can overcome this risk and ◆ ensure that you can meet your legal and operational Proprietary formats. Proprietary file formats are requirements. controlled and supported by just one software developer. Microsoft Word (.DOC) format is an Legally, your records must be trustworthy, complete, example. accessible, admissible in court, and durable for as ◆ Non-proprietary formats. These formats are long as your approved records retention schedules supported by more than one developer and can require. For example, you can convert a record to be accessed with different software systems. For another, more durable format (e.g., from a nearly example, eXtensible Markup Language (XML) is obsolete software program to a text file). That copy, becoming an increasingly popular non-proprietary as long as it is created in a trustworthy manner, is format. legally acceptable. ◆ Open Source formats. In general, open source The software in which a file is created usually has a refers to any program whose source code is made default format, often indicated by a file name suffix available for use or modification as users or other (e.g., *.PDF for portable document format). Most developers see fit. Open source software may be software allows authors to select from a variety of developed, modified and distributed by formats when they save a file (e.g., document independent software companies for profit.
    [Show full text]
  • An Introduction to R Notes on R: a Programming Environment for Data Analysis and Graphics Version 4.1.1 (2021-08-10)
    An Introduction to R Notes on R: A Programming Environment for Data Analysis and Graphics Version 4.1.1 (2021-08-10) W. N. Venables, D. M. Smith and the R Core Team This manual is for R, version 4.1.1 (2021-08-10). Copyright c 1990 W. N. Venables Copyright c 1992 W. N. Venables & D. M. Smith Copyright c 1997 R. Gentleman & R. Ihaka Copyright c 1997, 1998 M. Maechler Copyright c 1999{2021 R Core Team Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into an- other language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the R Core Team. i Table of Contents Preface :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1 Introduction and preliminaries :::::::::::::::::::::::::::::::: 2 1.1 The R environment :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 1.2 Related software and documentation ::::::::::::::::::::::::::::::::::::::::::::::: 2 1.3 R and statistics :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 1.4 R and the window system ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Openoffice.Org User Guide for Version 2.X
    OpenOffice.org User Guide for Version 2.x [OpenOffice.org User Guide for 2.x] [0.2] First edition: [2005-04-11] First English edition: [2005-04-11] Copyright and trademark information The contents of this Documentation are subject to the Public Documentation License, Version 1.0 (the "License"); you may only use this Documentation if you comply with the terms of this License. A copy of the License is available at: http://www.openoffice.org/licenses/PDL.rtf. The Original Documentation is ªOpenOffice.org User Guide for Version 2.xº. Contributor(s): G. Roderick Singleton. Portions created by G. Roderick Singleton are Copyright © 2005, 2006. All Rights Reserved. All trademarks within this guide belong to legitimate owners. [Note: a copy of the PDL is included in this template and is also available at: http://www.openoffice.org/licenses/PDL.rtf.] Feedback Please direct any comments or suggestions about this document to: [email protected] Acknowledgements I wish to recognize the Technical Writers of Sun Microsystems for the fine model they have provided for organizing this document. I also wish to thank Erwin Tenhumberg for his blog, Mary Ellen Dawley for her indexing effort, Ross Johnson for his editing/correctionsand manitoban for the docking text in chapter 2. Modifications and updates Version Date Description of Change [0.9] [2005-11-11] [grs: 9th draft issued for comment ± switched to master doc, stewart©s amendments and added a chapter on XML usage (flat file)] [0.10] [2005-11-11] [grs: 10th draft issued for comment ± fix page numbering [0.11] [2006-01-31] [grs:11th draft issued for comment ± updated index [0.12a] [2006-02-20] [rj: 12th draft issued for comment ± corrections for 2.0 to replace 1.1.x references [0.13] [2006-02-21] [grs 13th draft issued for comment ± integrated Ross Johnson©s changes and edited for consistent grammar.
    [Show full text]