Océ | Printing for...

Paris Boston Bristol www.sefas.com

Open Print

Remake 6.3

Normalization Guide

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.

© Sefas Innovation, 2009 3

Ta b l e o f C o n t e n t s

. . . . . . . . . . . . . . . . . . . . . . .Introduction 5

Introduction . . . . . . . . . . . . . . . . . . . . . 5About this document . . . . . . . . . . . . . . . . . . . 5

Overview of normalization . . . . . . . . . . . . 5Scenarios that require normalization . . . . . . . . . 6The normalization process . . . . . . . . . . . . . . . . 6

Stage 1 - Analysis . . . . . . . . . . . . . . . . . . . . . . . . . 6Stage 2 - Resource extraction . . . . . . . . . . . . . . . . 6Stage 3 - Normalization . . . . . . . . . . . . . . . . . . . . . 6

Normalization engines . . . . . . . . . . . . . . . 7Dynamic vs. manual mode . . . . . . . . . . . . 8

About TechFont . . . . . . . . . . . . . . . . . . . . . . 8About the Remake user interface . . . . . . . 8About the sample applications . . . . . . . . . 9

. . . . . . . . . . . . . . . . . . . . . . .AFP-DS normalization 11

Overview . . . . . . . . . . . . . . . . . . . . . . . 11About the TechAFP normalization engine . . . . . 11

Configuration file and keywords . . . . . . . . . . . . . . 11Command line parameters . . . . . . . . . . . . . . . . . . 11

Before you begin . . . . . . . . . . . . . . . . . . 12Verifying third-party applications . . . . . . . . . . 12Gathering AFP resources . . . . . . . . . . . . . . . . 12

For all types of streams . . . . . . . . . . . . . . . . . . . . 12For MO:DCA ACIF streams . . . . . . . . . . . . . . . . . . 12For MO:DCA non-ACIF streams . . . . . . . . . . . . . . 12For streams in mixed or line mode . . . . . . . . . . . . 12

Creating the application directory structure 13Setting up the sample application . . . . . . . . . . 13

Creating project directories . . . . . . . . . . . . . . . . . 13Copying directories and files. . . . . . . . . . . . . . . . . 13

Creating a new project . . . . . . . . . . . . . . 14Preparing the input file . . . . . . . . . . . . . . 15

Spooling the file to be normalized . . . . . . . . . 15Configuring the application . . . . . . . . . . . 15

Verifying the operating mode. . . . . . . . . . . . . 16Selecting the input file and configuration file . . 16

Configuring the normalization engine . . . . . 19Overview of the configuration file. . . . . . . . . . 19

Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Editing the configuration file . . . . . . . . . . . . . 22Keywords and descriptions . . . . . . . . . . . . . . 24

General keywords . . . . . . . . . . . . . . . . . . . . . . . . 24Line mode keywords . . . . . . . . . . . . . . . . . . . . . . 43

Managing color . . . . . . . . . . . . . . . . . . . 45Overview of substituting color . . . . . . . . . . . . 45

Color substitution table . . . . . . . . . . . . . . . . . . . . 45Color modes . . . . . . . . . . . . . . . . . . . . . . . . 45

Standard colors (OCA) . . . . . . . . . . . . . . . . . . . . . 45RGB colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45CMYK colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Highlight colors. . . . . . . . . . . . . . . . . . . . . . . . . . 46CIELab colors . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Color substitution table . . . . . . . . . . . . . . . . 46IBM color codes and default values . . . . . . . . . . . . 47Default color substitution table . . . . . . . . . . . . . . . 47Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Managing images . . . . . . . . . . . . . . . . . . 50Image configuration table. . . . . . . . . . . . . . . . . . . 50

Managing de-imposition . . . . . . . . . . . . . . 51Normalizing the stream . . . . . . . . . . . . . . 52

Verifying required input . . . . . . . . . . . . . . . . 52Processing External Resources . . . . . . . . . . . . . . . 52

Entering command line parameters. . . . . . . . . 53Command line parameters . . . . . . . . . . . . . . . . . . 53Command Line Example . . . . . . . . . . . . . . . . . . . . 55

Executing the normalization . . . . . . . . . . . . . 55Locating the VPF output . . . . . . . . . . . . . 56

. . . . . . . . . . . . . . . . . . . . . . .HP-PCL normalization 57About the TechPCL normalization engine . . . . . 57


Before you begin . . . . . . . . . . . . . . . . . . 58Verifying third-party applications . . . . . . . . . . 58Gathering PCL resources . . . . . . . . . . . . . . . . 58

Creating the application directory structure 58Setting up the sample application . . . . . . . . . 59

Creating project directories . . . . . . . . . . . . . . . . . . 59Copying directories and files . . . . . . . . . . . . . . . . . 59

Preparing the font environment . . . . . . . . 60Resident fonts . . . . . . . . . . . . . . . . . . . . . . 60

Example of Font Substitution . . . . . . . . . . . . . . . . 60Soft fonts . . . . . . . . . . . . . . . . . . . . . . . . . 60


Spooling the file to be normalized . . . . . . . . . 62Configuring the application . . . . . . . . . . . 62

Verifying the operating mode . . . . . . . . . . . . 62Selecting the input file and configuration file . . 63

Configuring the normalization engine . . . . . 65Overview of the configuration file . . . . . . . . . 65

Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Editing the configuration file. . . . . . . . . . . . . 67Keywords and descriptions . . . . . . . . . . . . . . 68

Normalizing the stream . . . . . . . . . . . . . . 71Entering command line parameters. . . . . . . . . 71

Command line parameters . . . . . . . . . . . . . . . . . . 71Example command line . . . . . . . . . . . . . . . . . . . . 72

Normalizing the PCL file . . . . . . . . . . . . . . . . 73Locating the VPF output . . . . . . . . . . . . . 73

. . . . . . . . . . . . . . . . . . . . . . .LCDS/Metacode normalization 75

Overview . . . . . . . . . . . . . . . . . . . . . . . 75About the TechLCDS normalization engine . . . . 75

Configuration file and keywords . . . . . . . . . . . . . . 75

4 Open Print Remake Normalization Guide

Command line parameters . . . . . . . . . . . . . . . . . . 75Before you begin . . . . . . . . . . . . . . . . . . 76

Verifying third-party applications . . . . . . . . . . 76Gathering resources . . . . . . . . . . . . . . . . . . . 76

Creating the application directory structure 76Setting up the sample application . . . . . . . . . . 77

Creating project directories . . . . . . . . . . . . . . . . . . 77Copying directories and files . . . . . . . . . . . . . . . . . 77


Spooling the file to be normalized. . . . . . . . . . 79Configuring the application . . . . . . . . . . . 79

Verifying the operating mode . . . . . . . . . . . . . 79Selecting the input file and configuration file . . 80

Configuring the normalization engine . . . . . 83Overview of the configuration file. . . . . . . . . . 83

Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Example - techlcds.cfg . . . . . . . . . . . . . . . . . . . . . 83

Editing the configuration file . . . . . . . . . . . . . 84Keywords and descriptions. . . . . . . . . . . . . . . 85

General keywords (all streams) . . . . . . . . . . . . . . . 85Fixed-record-length data streams . . . . . . . . . . . . . 86Variable-length data streams . . . . . . . . . . . . . . . . 87Delimited-record data streams . . . . . . . . . . . . . . . 87

Normalizing the stream . . . . . . . . . . . . . . 88Verifying required input . . . . . . . . . . . . . . . . 88Entering command line parameters . . . . . . . . . 88

Command line parameters . . . . . . . . . . . . . . . . . . 89Command line example . . . . . . . . . . . . . . . . . . . . 90

Executing the normalization . . . . . . . . . . . . . 91Locating the VPF output. . . . . . . . . . . . . . 91

. . . . . . . . . . . . . . . . . . . . . . .PDF normalization 93

Overview . . . . . . . . . . . . . . . . . . . . . . . 93About the TechPDF normalization engine . . . . . 93


Before you begin . . . . . . . . . . . . . . . . . . 94Verifying third-party applications . . . . . . . . . . 94Gathering the required resources . . . . . . . . . . 94

Creating the application directory structure 94Creating project directories. . . . . . . . . . . . . . 95

Preparing the font environment. . . . . . . . . 95Font substitution . . . . . . . . . . . . . . . . . . . . . . . . . 96

Managing images . . . . . . . . . . . . . . . . . . 97Preparing the input file . . . . . . . . . . . . . . 97

Spooling the file to be normalized. . . . . . . . . . 97Configuring the normalization engine . . . . . 97

Overview of the configuration file. . . . . . . . . . 97Example - techpdf.cfg . . . . . . . . . . . . . . . . . . . . . 97

Keywords and descriptions. . . . . . . . . . . . . . . 98Normalizing the stream . . . . . . . . . . . . . . 98

Setting environment variables . . . . . . . . . . . . 99Entering command line parameters . . . . . . . . . 99

Command line parameters . . . . . . . . . . . . . . . . . . 99Example command line. . . . . . . . . . . . . . . . . . . . 100

Handling errors (missing fonts) . . . . . . . . . . . 100TechPDF engine resources . . . . . . . . . . . . . . 101

Locating the VPF output. . . . . . . . . . . . . 101

. . . . . . . . . . . . . . . . . . . . . . .Postscript normalization 103

Overview . . . . . . . . . . . . . . . . . . . . . . 103The TechMulti normalization engine . . . . . . . . 103

Configuration files. . . . . . . . . . . . . . . . . . . . . . . 103Before you begin . . . . . . . . . . . . . . . . . 104

Verifying third-party applications . . . . . . . . . . 104Gathering the required resources . . . . . . . . . . 104

Creating the application directory structure 104Creating project directories . . . . . . . . . . . . . 104

Managing fonts and images . . . . . . . . . . . 105Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Images . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Preparing the input file . . . . . . . . . . . . . 106Configuring the normalization engine . . . . 106

Overview of techmulti.cfg. . . . . . . . . . . . . . . 106Keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Overview of techmulti_ibin.cfg . . . . . . . . . . . 107Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Overview of techmulti_font.cfg . . . . . . . . . . . 109Creating the batch file . . . . . . . . . . . . . 109

Setting environment variables . . . . . . . . . . . . 109Command line parameters . . . . . . . . . . . . . . 110

Example command line . . . . . . . . . . . . . . . . . . . 110Normalizing the stream . . . . . . . . . . . . . 112

Handling errors . . . . . . . . . . . . . . . . . . . . . . 112Locating the VPF output. . . . . . . . . . . . . 112Index 113


I n t r o d u c t i o nAbou t t h i s d o cu men t

Introd

uctio

n

C h a p t e r 1 : I n t r o d u c t i o n

Introduction

Open Print Remake is a print stream enhancement and transformation tool that enables you to re-engineer and repurpose legacy data streams without requiring use of the original application.

Normalization is the first of the three phases in working with Remake: Normalization,Enhancement, and Rendering. It is used to transform a legacy print stream into a more flexible,easier-to-modify Virtual Page Format (VPF) file.

Once a stream is normalized to VPF, you can modify its contents using Remake. This includeschanging colors, adding marketing messages, converting pages from simplex to duplex, addingbarcodes, adding or modifying inserter marks, and adding or removing sections for online versions.You can then integrate the converted data into the production chain.

About this document

This guide provides information and instructions on the Normalization phase of working withRemake. It does not provide information about the Enhancement or Rendering phases.

Overview of normalization

Normalization becomes necessary when a rendered format limits the possibilities of using adocument. The solution is to convert the rendered file to a pivot format (VPF) that allowsmodifications.

The current version of Remake supports normalization of legacy data streams in any of thefollowing protocol formats:

• AFP-DS (IBM®)• LCDS (Xerox®)• Metacode (Xerox)• PCL (HP®)

• PDF (Adobe®)

Note For information about Enhancement and Rendering, see the Open Print Remake User Guide.

NoteSince each protocol has its own unique characteristics, there is no standard way to process eachprotocol. Therefore, the normalization of each protocol is presented in a specific chapter of thisguide.


O v e r v i e w o f n o r m a l i z a t i o nS cena r i o s t h a t r e qu i r e n o rma l i z a t i o n

Scenarios that require normalization

Following are three scenarios that require normalization:

• Document enhancementSince it is often not possible to modify the contents of a rendered document, it must be converted to a format that allows enhancement. By normalizing a file in VPF pivot format, it is possible to modify the document using Remake.

• Acquisition of equipment that uses another protocolWhen new printing or mailing equipment is acquired, the legacy document protocol is likely no longer compatible with the protocol of the new equipment. To continue using the rendered file, it must be converted to a protocol that can be recognized by the equipment. This conversion is carried out in two steps; the first step is to normalize the document and the second step is to convert it from VPF to the desired protocol. For example, you might convert a file from AFP -> VPF -> PDF.

• Online document publishingPublishing documents online, to make them available for use with Open Print Projector for example, requires they are indexed by a search engine and displayed in a standard interface. Since most legacy protocol formats cannot be published online, they must be normalized first.

The normalization process

A best practice normalization occurs in three stages.

Stage 1 - Analysis

Identifies a stream’s resources, such as fonts, images, macros, metrics, and overlays. The actualmix of resources in the stream is based on a number of factors, including the protocol and thecontents of the stream. Depending on the stream’s source, resources may be embedded in thestream (that is, inline) or external (for example, fonts resident on a printer).

Stage 2 - Resource extraction

For inline resources, Remake automatically extracts them and embeds them in the VPF file. Forresources not inline, pointers must be specified to their locations (to the network location of afont library, for example). These pointers can be specified using Remake’s user interface alongwith a configuration file.

Stage 3 - Normalization

This is the actual conversion of the data stream and all of its resources into a self-contained VPFfile. Regardless of whether the legacy file’s resources are internal or external, the VPF contains allof the resources inline.


N o r m a l i z a t i o n e n g i n e sThe no rma l i z a t i o n p ro ce s s

Introd

uctio

n

The diagram below provides a generalized view of how Remake converts a protocolized datastream into a VPF file.

Normalization can be compared to the way a printer works. This is because, in both cases, theinformation contained in the rendered stream is interpreted in order to compose the pages of adocument. The difference between the two processes lies in the nature of the documentobtained. Normalization does not produce a printed document but an electronic documentconverted into VPF pivot format.

Normalization engines

The legacy input stream is processed using the appropriate normalization engine.

The normalization engines are described in the following table:

By default, the rendered stream must be placed in the spool directory of the application.

Protocol Engine Name

AFP-DS TechAFP

PCL TechPCL

PDF TechPDF

LCDS/Metacode TechLCDS


D y n a m i c v s . m a n u a l m o d eAbou t Te chFon t

The VPF file is generated in the same directory.

Dynamic vs. manual mode

The normalization engine for each protocol can be configured to use a dynamic normalizationmethod. This is the current, recommended method as it provides automated conversion ofresources in the AFP steam. A manual-mode, classic normalization method, requiring additionalsteps but providing additional flexibility, is also supported.

About TechFont

TechFont is the font conversion tool of the Open Print software suite. It is typically only requiredfor resource processing in manual mode, with few exceptions. TechFont can be used to processTrueType, AFP-DS, Xerox-Metacode, SDP, or PostScript (Type1) input fonts and generate PostScript,IJPDS, AFP-DS, and Xerox-Metacode output fonts.

About the Remake user interface

For all of the protocols, except for Adobe PDF, stream processing can be achieved using theRemake user interface under Microsoft Windows®.

This document provides step-by-step procedures for the using the Windows interface whererelevant to achieve normalization. It is not intended to be a comprehensive guide to using theRemake user interface.

Note

Normalization engines are designed to work in an Open Print environment. During the variousprocesses that use these engines, it is recommended that the Open Print environment be definedusing environment variables. For more information on environment variables, consult the OpenPrint Operating Manual.

NoteThis guide provides information about dynamic mode normalization. For information aboutadvanced processing options using manual mode, please contact Sefas Customer Support.

NoteFor more information about TechFont, see the Open Print TechFont Reference Manual orcontact Sefas Customer Support.

NoteNormalization of PDF files cannot be achieved using the Remake user interface; it must be carriedout using a batch file. Batch file examples are provided for PDF normalization as an option tousing the Windows user interface for each protocol.

Note For general information about Remake, see the Open Print Remake User Guide.


A b o u t t h e s a m p l e a p p l i c a t i o n sAbou t Te chFon t

Introd

uctio

n

About the sample applications

This normalization procedure for each protocol references a sample application that contains:

• A standard directory structure for the normalization of each protocol• A sample configuration file and sample batch files, where applicable• A sample protocol file that you can use for training• An example of the VPF output for that protocol

The examples may be used as a starting place and customized to meet your needs.

The sample application is either located in the Remake installation folder or was provided to youby a Sefas representative (for example, during training).

Note If you do not have access to the sample application, contact Sefas Customer Support.


A b o u t t h e s a m p l e a p p l i c a t i o n sAbou t Te chFon t


O v e r v i e wAbou t t h e Te chAFP no rma l i z a t i o n e ng i ne

AF

P-D

S n

orm

aliz

atio

n

C h a p t e r 2 : A F P - D S n o r m a l i z a t i o n

Overview

Open Print Remake supports normalization of Advanced Function Printing Data Stream (AFP-DS)files in the following formats:

• MO:DCA (Mixed Object Document Content Architecture)• Line mode• Mixed mode (MO:DCA and line mode)

Regardless of a file’s format, AFP streams are made up of several types of resources. Theseinclude:

• Fonts• Font charset files - Font files relating the character set IDs and glyphs• Font codepage files - Font files relating the character set IDs and code points• Font coded files - Font files referencing the character set/codepage pair

• Images - Page segment or inline images• Overlays - Static resources (text and images)• a FORMDEF- Paper imposition configuration file• a PAGEDEF - Page formatting information file (for line mode and mixed mode files)

The actual mix of resources in an AFP stream depends on the contents of the file. Resources areeither embedded (inline), or externally (if not inline).

The goal of AFP normalization with Open Print Remake is to convert an AFP data stream into aVirtual Page Format (VPF) file. The normalized VPF output file contains all of the resources (eitherembedded or translated into VPF resource objects).

About the TechAFP normalization engine

The TechAFP normalization engine converts an AFP data stream into a VPF file. Processing optionsfor the engine are set using a configuration file. Additional parameters are set at run time. Theconfiguration file is edited using a standard text editor. Runtime parameters are set and thenormalization is executed using Remake’s user interface.

Configuration file and keywords

The standard configuration file used by the engine is techafp.cfg. The file contains keywordsthat tell the engine how to process the incoming AFP data stream.

For example, the font_embedding keyword must be present in the configuration file, and set to1, to enable dynamic font processing.

The configuration file can be edited using any standard text editor. For syntax of the configurationfile along with the list of keywords that can be used, see Configuring the normalization engine

on page 19.

Command line parameters

The engine supports parameters that can be processed with the command line at runtime. Theseparameters are used to set environment variables and other options not set using theconfiguration file.


B e f o r e y o u b e g i nVe r i f y i n g t h i r d - pa r t y a pp l i c a t i o n s

For example, the -i parameter sets the access path to the AFP input stream.

For more information on available parameters, see Entering command line parameters onpage 53.

Before you begin

Verifying third-party applications

Sefas recommends that you have the following third-party tools installed on the computer whereyou perform the AFP normalization.

• AFP viewer: BetaBrowser, IBM workbench• AFP Analyzer• Hexidecimal text editor

It is also helpful to have an AFP printer connected to the computer for testing purposes.

Gathering AFP resources

Before launching an AFP normalization, you should compile a list of the resources contained in thestream.

For all types of streams• Gather and have available a selection of original documents printed on the AFP system

(to be used as a reference).• Determine the resolution of the existing stream and of the resources to normalized.• Determine the resolution of the target stream.

For MO:DCA ACIF streams• Analyze the AFP stream (in AFP MO:DCA ACIF mode, the stream contains all of the

resources).

For MO:DCA non-ACIF streams• Locate the AFP stream.• Locate any overlays (usually files of type O1*) referenced by the stream.• Locate any the page segments (usually files of type S1*) referenced by the stream and

by the overlays .• Determine the font sets used by the stream and by the overlays.• Locate the font set comprised of charset (C0*), codepage (T*), and coded (X0*) files.• Locate the FORMDEF associated to the stream during the printing (F1*).

For streams in mixed or line mode• Locate all of the elements necessary for the AFP MO:DCA non-ACIF streams (see above).• Locate the PAGEDEF associated with the stream.• Locate the JCL file used for launching the printing if it is made by z/OS, MVS, or OS390

system.

Note The resources you gather will depend on the type of AFP stream to be normalized.


C r e a t i n g t h e a p p l i c a t i o n d i r e c t o ry s t r u c t u r eSe t t i n g up t h e s amp l e app l i c a t i o n

AF

P-D

S n

orm

aliz

atio

n

Creating the application directory structure

While virtually any directory structure can be used to perform the normalization, it is helpful touse a standard directory structure and standard naming conventions. Sefas recommends that youuse a structure based on the $opWD (working), $opFam (group), and $opAppli (application)Open Print environment variables.

There are several ways you can establish the environment. For example, you can:

• Create the initial project directories, then copy the rest of the directory structure and sample files from the sample application delivered with Remake. This is the recommended option for new Remake users.

• Create the directory structure from scratch.• Use the Create New Project capability of Remake’s user interface to have software

create the directory structure automatically.

The remainder of this section explains how to set up the directory structure using the sampleapplication.

Setting up the sample application

Creating project directories

The first step in working with Remake is to establish the environment you will use to store thedirectories and files used to normalize the stream and process the VPF output.

A recommended directory structure is provided with the sample application delivered withRemake. Therefore, it is easiest to set up the directories by copying them from the sampleapplication to the computer you will use to run Remake.

Do the following to create the initial project and group directories that will contain the sampleapplication:

1. Using Windows Explorer, create the following directory on your hard drive:

C:\normalization

This is the group-entry point directory.

2. Under this directory, create the group subdirectory \samples:

C:\normalization\samples

Copying directories and files

Do the following to copy the sample application delivered with Remake into the group directoryyou just created:

1. Locate the directory containing your sample application. The directory is either located in the Remake installation folder or was provided to you by a Sefas representative (for example, during training).

2. Copy the entire directory labeled \afp_sample to the normalization directory you created previously:

C:\normalization\samples\afp_sample

Note For more information about the Open Print environment variables, see the Open Print

Operating Manual.



C r e a t i n g a n e w p ro j e c tS e t t i n g up t h e s amp l e app l i c a t i o n

When finished, your application directory structure appears as follows:

Creating a new project

After setting up the application directory structure, you are ready to create the project usingRemake’s user interface. Do the following:

1. Launch Remake. Go to Start menu > All Programs >SEFAS INNOVATION > Open Print Remake 6.2. The Open Print Remake application window appears:

2. Select File > Create a Project.

The Create a New Open Print Remake Project window appears.

3. Click the ellipsis button [...] beside the Group Entry-Point field:

4. In the Group Entry-Point dialog box, select C:\normalization. This is the group entry-point you created using Windows Explorer. Click OK:

5. From the Group drop-down list, select samples.This is the group directory that you created earlier.

6. In the Application field, type afp_sample. This entry corresponds to the sample application directory you copied into the Group directory.

7. When finished, click OK.

8. Click OK.

Note A message appears notifying you that the application already exists. Since we are creating thisproject from the sample application, this is expected.


P r e p a r i n g t h e i n p u t f i l eSpoo l i n g t h e f i l e t o b e no rma l i z e d

AF

P-D

S n

orm

aliz

atio

n

Preparing the input file

Spooling the file to be normalized

Sefas recommends that you use a standard directory for the storage and selection of the AFP fileyou want to normalize. The \spool subdirectory inside the sample application directory isintended for this purpose.

Copy the file you want to normalize to:

C:\normalization\samples\afp_sample\spool

For example:

C:\normalization\samples\afp_sample\spool\afp_sample.afp

Configuring the application

To configure the application, use the Remake user interface to:

• Verify directory path settings and client/server environment and update them if needed.

• Set the location of the AFP input file.• Set the location of the configuration file.

Note A sample AFP file with inline resources, named afp_sample.afp, is provided with the sampleapplication in the \afp_sample directory. You can substitute the sample file with any AFP fileyou would like to normalize.


C o n f i g u r i n g t h e a p p l i c a t i o nVe r i f y i n g t h e ope ra t i n g mode

Verifying the operating mode

Do the following to verify that Remake’s client/server operating mode settings are correct:

1. Select File > Configuration.

2. Review the settings for StandAlone or Client/Server operating mode and make any required changes:

3. Click OK.

Selecting the input file and configuration file

The TechAFP normalization engine configuration file, techafp.cfg, contains sections that mustbe configured depending on the type of processing that needs to be performed. For moreinformation about techafp.cfg, see Configuration file and keywords on page 11.

Before you can normalize the AFP file, you must set:

• The location of AFP file to be normalized• The location of the configuration file used to set processing options• The section of the configuration file to process

To do this:

1. From the Remake user interface, select File > Configuration.

Note If Client/Server operating mode is selected, you can select the Transfer Data check box toautomatically transfer data generated by the server to the client or by the client to the server.


C o n f i g u r i n g t h e ap p l i c a t i o nSe l e c t i n g t h e i n pu t f i l e a nd c on f i g u ra t i o n f i l e

AF

P-D

S n

orm

aliz

atio

n

2. Click the Data file button:

3. Next to the Input file field, click the […] button to browse your computer for the AFP file to be normalized:

4. Navigate to the \spool directory, select the AFP file, and click Open. After you select the file, its path is displayed in the Input file field:

5. Under File type, select AFP.

Note If you do not see an AFP file in the \spool directory, see Setting up the sample application

on page 13 for help with copying the sample file to this directory.


C o n f i g u r i n g t h e a p p l i c a t i o nS e l e c t i n g t h e i n pu t f i l e and c on f i gu ra t i o n f i l e

6. Click […] beside the Cfg File field to browse your computer for the configuration file.

7. Select the file, and click Open. The path to the file is displayed in the Cfg File field:

8. In the Section field, type AFP_VPF:

Note Following our sample application, this is located in:

C:\normalization\samples\afp_sample\common\config\afp\techafp.cfg

Note By specifying AFP_VPF in the section field, the normalization engine processes this section of theconfiguration file when the normalization is executed. For more information, see Overview of

the configuration file on page 19


C o n f i g u r i n g t h e n o r m a l i z a t i o n e n g i n eOve r v i ew o f t h e c on f i g u ra t i o n f i l e

AF

P-D

S n

orm

aliz

atio

n

Configuring the normalization engine

Overview of the configuration file

Processing options for the TechAFP normalization engine are set using a configuration file,techafp.cfg.

Sections

The configuration file is made up of one or more sections. For example,[SECTION_1]

If a [COMMON] section exists, it is read prior to any other section. Include this section if yournormalization requires that certain keywords are processed first or if your configuration file isused to process multiple streams with common attributes.

Keywords

Each section contains a set of keywords. Each keyword corresponds to a process to be carried outon the AFP stream. Keywords are systematically followed by a value. Possible values includeaccess paths, names, and list attributes. A keyword and its value are separated by the “=” equalcharacter. For example:

[SECTION_1]

key_word1=value

key_word2=value

For the full list of keywords that can be used, see Keywords and descriptions on page 24.

Comments

A semicolon (;) or a hashmark (#) at the beginning of a line indicates that the line is a comment.Comments are ignored by the TechAFP engine.

For example:

; Creation of the font list

# Creation of the font list

Note Space and dash (-) characters are not permitted in section names.

Important The sections and keywords in your configuration file depend on the stream to be normalized andthe requirements of your organization. Examples:

• For a simple MO:DCA ACIF normalization, there may be a single section of the file containing just a few keywords.

• For a complex mixed mode file, or if you plan to process different types of files using the same techafp.cfg, there might be many sections in the file, each corresponding to a stream group and a specific process.

• For a line mode file, keywords specific to line mode processing will be used.• You could also create multiple configuration files, each corresponding to a specific

document type or department, such as techafp-invoices.cfg, techafp-mailers.cfg, or accountingdept.cfg. If a custom file name is used, you specify the name of the file using the -C or -c command line parameter. For more information, see -c or -C on page 53.

Please see below for specific examples of the configuration file.


C o n f i g u r i n g t h e n o r m a l i z a t i o n e n g i n eOve r v i ew o f t h e c on f i gu ra t i o n f i l e

Examples

techafp.cfg example 1 - Simple configuration

The following is a simple example of the techafp.cfg configuration file with a minimal set ofkeywords. For a description of each keyword and possible values, see Keywords and

descriptions on page 24.

[AFP_VPF]

include_overlay_mode=vpf

include_pageseg_mode=vpf

font_embedding=1

techafp.cfg example 2 - Complex configuration

The following is an example of a more complex techafp.cfg configuration file. This examplecontains four sections. Each section is used to process a stream with different characteristics. Fora description of each keyword and possible values, see Keywords and descriptions on page 24.

[COMMON]

output_doc_compress=0

verbose=-1

include_overlay_mode=afp

include_pageseg_mode=afp

fill_gray_im=2

image_mode=0

delete_white_line=0

input_format=variable_native

res_input_format=variable_flat

input_type=mixed_mode

use_trc=no

carriage_control=ansi

chars=none

[NORM_MODCA_STREAM_1]

stderr=/user/sfdvbdr/op_wd/op_fam/customer/printer/modca_stream_1_err.log

stdout=/user/sfdvbdr/op_wd/op_fam/customer/printer/modca_stream_1_out.log

input_format=variable_flat

res_input_format=variable_flat

input_type=modca

use_trc=no

carriage_control=none

chars=none

fem_fname=/user/sfdvbdr/op_wd/op_fam/customer/printer/t01_fem.cfg

[NORM_MIXED_STREAM_1]

stderr=/user/sfdvbdr/op_wd/op_fam/customer/printer/mixed_stream_2.err

stdout=/user/sfdvbdr/op_wd/op_fam/customer/printer/mixed_stream_2.out

form_map_name=F1NICOLM

page_def_name=P1NICOLM

record_length=8205

[NORM_MIXED_STREAM_2]

stderr=/user/sfdvbdr/op_wd/op_fam/customer/printer/mixed_stream_1_err.log

stdout=/user/sfdvbdr/op_wd/op_fam/customer/printer/mixed_stream_1_out.log

form_map_name=F1D409

record_length=5004

fem_fname=/user/sfdvbdr/op_wd/op_fam/customer/printer/mixed_stream_1_fem.cfg

paper_width=35cm



AF

P-D

S n

orm

aliz

atio

n

paper_height=34cm

Notes on Example 2

The [COMMON] section is the same for all streams. It is read before the section corresponding to thestream to be processed. If the section corresponding to the stream to be processed redefines anoption, then this new value replaces the one defined in the [COMMON] section.

• The [COMMON] section defines the following characteristics:• The stream is in an OS390 (DATASET) native file system (for example, VB or FB).• Resources (overlays, page segments, FORMDEF, and PAGEDEF) are found on a UNIX file

system.• The stream is mixed (MO:DCA and line mode).• The checks for switching to line mode are of the ANSI type.

• The [NORM_MODCA_STREAM_1] section, used to process a MO:DCA stream, modifies and completes the characteristics of the [COMMON] section by the following characteristics:

• The format of the stream is modified.• The nature of the input file system is modified.• Deimposition characteristics are added.

• The [NORM_MIXED_STREAM_1] section, used to process a mixed mode stream, completes the characteristics of the [COMMON] section by the following characteristics:

• The log files are defined.• The FORMDEF and PAGEDEF names are defined.• The maximum length of the input DATASET record is set at 8205.

• The [NORM_MIXED_STREAM_2] section, used to process a mixed mode stream, completes the characteristics of the [COMMON] section by the deimposition characteristics.

techafp.cfg example 3- Line mode configuration

The following is an example of the techafp.cfg configuration file for a line mode stream. Ascreen capture of the line mode file is provided below the example. For line mode AFP files, amanual analysis of the data in the file is necessary to understand the record and block structure ofthe file. Keywords can then be assigned accordingly. For a description of line mode keywords andpossible values, see Line mode keywords on page 43.

[COMMON]

verbose=-1

stderr=stderr.txt

stdout=stdout.txt

show_file_offset=yes

statistic_file=stat.txt



dump_resource=0

input_format=fixed_flat

record_length=16

input_type=mixed_mode

carriage_control=ansi

page_def_name=P1SEFAS3

form_def_name=F1SEFAS4

font_embedding=1

use_index_file=0

barcode_mode=keep

resource_map=ttf_map.txt


C o n f i g u r i n g t h e n o r m a l i z a t i o n e n g i n eEd i t i n g t h e c on f i g u ra t i o n f i l e

Notes on Example 3

The configuration file above is used to process a line mode file with a fixed-length record format.See the sample file below. Each record is 16 bytes long with a machine carriage control (CC) and atable reference character (TRC). The data begins at offset 2 of each record:

Editing the configuration file

Do the following to configure the techafp.cfg:

1. Launch Remake, and select File > Configuration...

2. Click the Data file button.

3. Next to the Cfg file field, click Edit:

Note This step assumes you have already selected the configuration file using Remake. For moreinformation, see Selecting the input file and configuration file on page 16.


C o n f i g u r i n g t h e n o r m a l i z a t i o n e n g i n eEd i t i n g t h e c on f i gu ra t i o n f i l e

AF

P-D

S n

orm

aliz

atio

n

The techafp.cfg file opens in a text editor:

4. Make any required changes to the file. See Overview of the configuration file on page 19 and Keywords and descriptions on page 24.

5. When finished, select File > Save.


C o n f i g u r i n g t h e n o r m a l i z a t i o n e n g i n eKeywo rd s a nd d e s c r i p t i o n s

Keywords and descriptions

General keywords

The following is a list of general keywords. For keywords specific to line/mixed mode files, seeLine mode keywords on page 43.

Keyword Description

barcode_mode Specifies whether AFP barcodes are converted to VPF barcodes or to text. If barcodes are converted to text, you can use Remake to create new barcodes after normalization.

This keyword applies to all barcodes in the input. It is not possible to convert some barcodes to text and some to VPF barcodes. Valid values are:

• as_text (default) - The AFP barcodes are converted into text.

• keep - The AFP barcodes are converted into VPF barcodes.

For example:

barcode_mode=as_text

Barcodes might also include barcode data in Human Readable Interpretation (HRI) format. HRI numbers appear above or below the barcode so that people, as well as scanners, can understand the barcode. For example:

Whether the HRI is displayed is determined by a flag in the barcode.

You can also specify the position of the HRI data relative to the barcode. For more information, see barcode_hri_above_gap on page 24and barcode_hri_below_gap on page 25.

The AFP barcode also includes a font number. This font number is a local page variable; it is mapped to a font name using a page-specific mapping table generated by Remake. Remake uses the font number to look up the charset and codepage in the font table. Remake uses the specified charset and codepage to print:

• The text equivalent of the barcode, if barcode_mode=as_text.

• The HRI, if the flag indicates that it should be displayed and barcode_mode=keep.

A font number of -1 (or 0xFF) is a special case:

• If the font number is -1 and barcode_mode=as_text: Remake prints the text equivalent of the barcode using the charset and codepage of the first element in the font table, regardless of the actual font number of the first element. If there is no font table, Remake generates an error.

• If the font number is -1 and barcode_mode=keep: The font for the HRI must be specified with the keyword resource_map. For more information, see resource_map on page 37.

barcode_hri_above_gap Specifies the space between the top of the barcode and the bottom of the HRI. The space is specified in logical units (ULs). UL is a Sefas-specific unit of measurement, where 1 UL = 1/144000 inch. The default is 9333 UL; 9333 UL = 2/3 of 7 pica points.

For example:

barcode_hri_above_gap=5000

A


C o n f i g u r i n g t h e n o r m a l i z a t i o n e n g i n eKe ywo rd s a nd d e s c r i p t i o n s

AF

P-D

S n

orm

aliz

atio

n

barcode_hri_below_gap Specifies the space between the bottom of the barcode and the top of the HRI. The space is specified in logical units (ULs). UL is a Sefas-specific unit of measurement, where 1 UL = 1/144000 inch. The default is 3500 UL; 3500 UL = 1/3 of 7 pica points.

For example:

barcode_hri_below_gap=3200

box_width_factor Specifies the percentage of the VPF input vector width to apply to the output GOCA box.

GOCA is the subset of the AFP protocol dedicated to vectorial drawing. GOCA support is enabled when the keyword goca_enable is set to 1 in the drivers.cnf file. GOCA boxes are rectangular shapes. During normalization, two types of boxes are created:

• Boxes comprised of borders without filling

• Boxes comprised of inside filling without borders

The corresponding VPF elements are BRBOX vectors and IRBOX vectors. B indicates that there is a border and I indicates inside filling with no border. The width of the vector corresponds to the width of the border for the BRBOX and to the width of the erased border for the IRBOX.

In some cases, the printer-rendered width is not the one expected even though the AFP is correct. The width must be corrected.

By default, box_width_factor equals 100. Setting box_width_factor=130 means all GOCA boxes with have a width 1.3 higher than expected.

charset_dir Specifies the search path for charsets. This overrides the path specified in res_dir. For more information, see res_dir on page 36.

charset_dump_folder Specifies the extraction output path for charsets. This overrides the path specified in res_dump_folder. For more information, see res_dump_folder on page 36.

Use dump_resource to specify whether resources remain in this directory after normalization, or if they are only placed here temporarily and then deleted. For more information, see dump_resource on page 27.

coded_dir Specifies the search path for coded fonts. This overrides the path specified in res_dir. For more information, see res_dir on page 36.

coded_dump_folder Specifies the extraction output path for coded fonts. This overrides the path spec-ified in res_dump_folder. For more information, see res_dump_folder on page 36.

Use dump_resource to specify whether resources remain in this directory after normalization, or if they are only placed here temporarily and then deleted. For more information, see dump_resource on page 27.

code_page_dir Specifies the search path for code page fonts. This overrides the path specified using the res_dir keyword. For more information, see res_dir on page 36.

codepage_dump_folder Specifies the extraction output path for code pages. This overrides the path specified in res_dump_folder. For more information, see res_dump_folder on page 36.

Use dump_resource to specify whether resources remain in this directory after normalization, or whether they are placed here temporarily and then deleted. For more information, see dump_resource on page 27.

Keyword Description



color_mapping_table Specifies the location and name of an optional color mapping table that can be used for color substitution during normalization.

The path to the mapping table file may be specified as absolute or relative. If the path is relative, Remake searches the current path and then in: <opInstallDir>/common/config/afp

For example:

color_mapping_table=color_table.cfg

For more information about this option, Managing color on page 45.

convert_begin_document Specifies whether Begin Document (BDT) fields in the AFP file are converted to $DOC resources in the VPF file. Valid values are:

• 0 (default) - BDT fields are converted to $DOC resources.

• 1 - BDT fields are not converted to $DOC resources.

decompress_g4_mmr_ioca Specifies if G4 MMR IOCA images are converted to TIFF format during normalization. Valid values are:

• no (default) - G4 MMR IOCA images are converted to TIFF.

• yes - G4 MMR IOCA images are not converted to TIFF.

By default, G4 MMR IOCA images are converted to TIFF images. This requires minimal processing by Remake, but a few AFP viewers do not properly display the TIFF images. To display the images in one of these viewers, use decompress_g4_mmr_ioca=yes. The G4 IOCA MMR images are decompressed and then recompressed. Use image_extension to specify the format of the recompressed images. For more information, see image_extension on page 30.

default_codepage Specifies the default codepage. This codepage is used:

• If no font is declared in an AFP page

• If a font is declared in an MCF with an unknown GRID code

For example:

default_codepage=T1D0BASE

The keywords default_codepage and default_charset must be used together. For more information, see default_charset on page 43.

default_medium_map Specifies which medium map to use. The default is the first medium map in the FORMDEF. Use default_medium_map to specify the name of any other medium map in the FORMDEF.

delete_white_line Deletes the white lines generated in the VPF stream. Valid values are:

• 0 - The white lines are not deleted.

• 1 (default) - The white lines are deleted.

Keyword Description



AF

P-D

S n

orm

aliz

atio

n

dump_resource Specifies whether resources remain in the directories to which they were extracted after normalization, or if they are only placed there temporarily and then deleted. Valid values are:

Possible values:

• 0 - The resources are not deleted.

• 1 (default) - The resources are deleted.

This keyword impacts the storage of any files extracted to directories specified by the following keywords:

• charset_dump_folder (page 25)

• coded_dump_folder (page 25)

• codepage_dump_folder (page 25)

• form_dump_folder (page 28)

• overlay_dump_folder (page 34)

• page_dump_folder (page 34)

• psg_dump_folder (page 35)

• res_dump_folder (page 36)

• ttf_dump_folder (page 38)

enable_cfc Specifies whether the Constant Forms Control (CFC) flag in the FORMDEF is enabled or disabled. Valid values are:

• 0 - The CFC flag is disabled.

• 1 (default) - The CFC flag is enabled.

If the CFC flag causes unwanted blank pages at the end of the VPF file, use enable_cfc=0 to disable the flag.

end_page Specifies how many AFP pages to normalize.

The page count is based on the AFP file, not the VPF file. If the AFP file does not use 1-up imposition, the number of pages in the AFP file is different from the number of pages in the VPF file. For example:

end_page=20

The above example normalizes the first 20 pages of the AFP file.

The -p NN option (page 54) on the command line is the same as and overrides this keyword.

fem_fname Specifies the deimposition configuration file. By default, the file is located in \common\config. For a file located in the \common\config directory, specifying the file name (without the path) is sufficient. If the file is located in a subdirectory under \common\config, the path can be relative. If the file is located in any other directory, specify the full path. For example:

fem_fname=deimposition.cfg

Keyword Description



fgid_table Specifies the name and path for an optional external Font Global Identifier (FGID) file for mapping the charset of fonts. Remake searches this table before searching its internal table. The path can be relative or absolute, but cannot include opWD, opFam, opAppli, or opInstallDir.

For example:

fgid_table=..\config\fgid_table.txt

Format of the fgid_table file

Each line contains the name of the charset and the FGID code, as a decimal value. Specify only the charset, not the codepage.

Empty lines are allowed. They are ignored. Begin a comment with a semicolon (;).

For example:

; This is a comment.

C0HL07GP 5815

C0HL08NP 222

fill_gray_im Specifies how to normalize a gray area in the AFP file. Valid values are:

• 1 (default) - Converts the gray area to a PCX image with the same level of gray.

• 2 - Converts the gray area to a VPF box.

Details to consider with each of these options:

• fill_gray_im=1 - The VPF image might require more disk space than the original image.

• fill_gray_im=2 - There might be problems with opacity. If so, use image_under=2 to correct them. For more information, see image_under on page 30.

flush_log Specifies whether Remake writes the log file to disk if the verbose keyword is not set to 11. This keyword is useful during debugging to manage the size of the log file. Valid values are:

• 0 (default) - Write the log based on the verbose setting.

• 1 - Write the log to disk after each line, regardless of the verbose setting.

Remake also writes the log file to disk after each line if either the verbose keyword or the -v command line option is set to 11. For more information, see verbose on page 42 and -v on page 54.

font_embedding Controls whether the normalization is executed in dynamic or classic mode. Use font_embedding=1 to specify dynamic mode unless Sefas instructs you to use a different value.

formdef_dir Specifies the search path for FORMDEF. This overrides the path specified in res_dir. For more information, see res_dir on page 36.

form_def_name Specifies the name of the FORMDEF file containing the various imposition sections used by the AFP stream to be normalized.

For example:

form_def_name=STARTIMP

If the input stream contains a FORMDEF, this keyword can be omitted.

The value form_def_name=none forces Remake to ignore the included FORMDEF.

form_dump_folder Specifies the extraction output path for FORMDEF. This overrides the path specified in res_dump_folder. For more information, see res_dump_folder on page 36.

Use dump_resource to specify whether resources remain in this directory after normalization, or are only placed here temporarily and then deleted. For more information, see dump_resource on page 27.

Keyword Description



AF

P-D

S n

orm

aliz

atio

n

force_n_up Specifies how to handle a file with an imposition that Remake does not support, such as 4-up. Valid values are:

• keep (default) - The imposition is treated as specified in the FORMDEF. Use this for any supported imposition.

• 1-up - The imposition is set as 1-up.

• 2-up - The imposition is set as 2-up. This requires an additional deimposition configuration file.

Remake only supports 1-up and 2-up FORMDEFs. However, force_n_up can be used as a work-around in some cases. The number and position of blank pages will be different between a VPF file created with force_n_up=1-up and a VPF file created with force_n_up=2-up. Use the option that creates the most appropriate layout.

To use force_n_up=2-up, you must also create a deimposition configuration file. For more information about creating a deimposition configuration file, see the Open Print Operating Manual.

Use fem_fname to specify the name of the deimposition configuration file. For more information, see fem_fname on page 27.

If needed, use form_def_name to:

• specify the name of a FORMDEF that is not embedded

• specify no FORMDEF

For more information, see form_def_name on page 28.

Please note that medium overlays are not positioned correctly with force_n_up. If you want to normalize a file with an unsupported imposition that uses medium overlays, please contact Sefas Customer Support.

goca_pattern_gray_levels Specifies how to map GOCA patterns to grayscale. The GOCA patterns are not supported by Remake. Instead Remake translates the GOCA patterns to levels of gray. Use goca_pattern_gray_levels to specify the level of gray for each of the GOCA patterns.

The default gray levels are:

The pattern is the number of the GOCA pattern and can be any number from 1-16. The level is the percentage of gray and can be any number from 0-100.

The syntax is:

goca_pattern_gray_levels=(pattern,level), ...(pattern,level)

For example:

goca_pattern_gray_levels=(11,50),(14,75)

In this example, GOCA pattern number 11 will be 50% gray. GOCA pattern number 14 will be 75% gray.

ignore_mdd_orientation Specifies if the orientation specified in the Medium Descriptor (MDD) is used or ignored. Use ignore_mdd_orientation only if the MDD specifies an orientation other than 0, and the output using that orientation is not satisfactory. This keyword is rarely used. In almost all cases the orientation specified in the MDD is satisfactory. Valid values are:

• 0 (default) - The orientation specified in the MDD is used.

• 1 - The orientation specified in the MDD is ignored.

Keyword Description

pattern 1 2 3 4 5 6 7 8 9 10 11 12 13 14

level 50 25 25 13 19 17 14 7 38 51 25 25 25 25



image_extension Specifies the format of the images to be used in the VPF file. Valid values are:

• pcx (default) - The images are converted to PCX format.

• jpg - The images are converted to JPG format.

The format of G4 MMR IOCA images could also be TIFF images. For more information, see decompress_g4_mmr_ioca on page 26.

image_reuse Specifies whether or not repeated IOCA images are consolidated and reused to reduce the size of the VPF file. Valid values are:

• 0 (default) - The images are not consolidated and reused.

• 1 - The images are consolidated and reused.

Use image_reuse only if the AFP file contains the same compressed image that is repeatedly inserted inline, such as a compressed background image.

A compressed image in the VPF file might be larger than the same compressed image in the AFP file. If the image is used repeatedly, this can result in a very large VPF file, even if the AFP file is a reasonable size. Remake also might need to decompress the image and then recompress it in order to create an image that can be used in the VPF file. This results in unnecessary engine overhead if the same image is repeatedly decompressed and recompressed.

Note: Use of this keyword can slow down normalization speed, so it should only be used when needed.

For the VPF file, when factoring is on, an IOCA image is inserted as an image element the first time it is found. After the first reference, a LOGO element is used.

image_under Places some types of resources in the background. Use image_under to solve some types of problems with opacity. It is most commonly used if the final output will be IJPDS, but can also be used with other protocols, if needed. Valid values are:

• 0 (default) - The placement of resources is not changed.

• 1 - Images and LOGO resources are put in the background.

• 2 - Shaded boxes are put in the background.

Keyword Description



AF

P-D

S n

orm

aliz

atio

n

imm_mode Important: Use of this keyword may override the FORMDEF. Therefore, this keyword should only be used by personnel experienced in advanced print stream manipulation.

Specifies how Invoke Medium Map (IMM) records are handled in the VPF file. Use imm_mode only if the final output is AFP. Valid values are:

• use (default) - The IMM records are parsed and applied to the VPF file.

• keep - The IMM records are not parsed. They are included in the VPF file as AFP MEDIUMMAP (for example, $$AFP MEDIUMMAP F1SEFAS4). When the IMM records are included in the VPF file (imm_mode=keep), all the options in the FORMDEF are ignored, including:

• form_map_name

• form_def_name

• paper_width

• paper_height

• fem_fname

For example:

imm_mode=use $$AFP MEDIUMMAP

To apply the options in the FORMDEF during printing, the protocol of the final output must be AFP. Include the keyword embedded_formdef_name in the drivers.cnf file.

If you manipulate the VPF file so that the number of pages or their order in the VPF file changes from the number of pages or their order in the original AFP file, add $$AFP MEDIUMMAP to the VPF file to preserve the original formatting.

For more information about embedded_formdef_name, the drivers.cnf file, or $$AFP MEDIUMMAP, see the Open Print Operating Manual.

include_empty_page Specifies whether blank pages in the document are retained.

Note: Pages with No Operator (NOP) or MEF resources ($DUPLEX, $SIMPLEX, $OFFSET) make the page non-empty. Also, when switching to a new medium map after a duplex medium map, a blank page may be added that may not be removed using this option. Valid values are:

• 0 - Blank pages are not included in the VPF file.

• 1 (default) - Blank pages are included in the VPF file.

include_mef Specifies whether to include imposition resources in the VPF. Valid values are:

• 0 (default) - Imposition resources are not included in the VPF.

• 1 - Imposition resources are included in the VPF.

The way that resources are parsed and applied to the VPF is the same for either value of include_mef. This keyword affects only whether or not they are also included in the VPF. The resources that are included are:

• SIMPLEX

• DUPLEX

• DUPLEX 2

include_overlay_mode Creates links on the overlays. The corresponding values depend on the context. Valid values are:

• vpf (default) - AFP overlays are converted in the form of VPF format files. A link will therefore be inserted in the master VFP file. To use this value, you must have overlays in the \macro directory.

The VPF stream then refers to a VPF overlay page that contains the overlay text, the vectors and references to the PCX and JPEG of the overlay.

• afp - Used to create a link in the VPF stream on an AFP resource through the $$AFP IPO name x y o composition statement. This mode is used only if the VPF stream is intended for production in the AFP format. In this case, the overlays are not visible in the VPF viewer. Only the VPF master file can be viewed. The overlays must be present in the spool directory.

Keyword Description



include_pageseg_mode Creates links on images. The corresponding value varies according to the context. Valid values are:

• vpf (default) - Page segments are converted to PCX format images and the VPF stream will contain $LOGO statements to call each image.

To use this value, you must have page segments in the \macro directory. The VPF stream then refers to a VPF overlay page that contains the references to the PCX and JPEG of the overlay.

• afp - Used to create a link in the VPF stream on an AFP page segment through the $$AFP IPS name x y o composition statement. This mode is used only if the VPF stream is intended for production in the AFP format. In this case, the images are not visible in the VPF viewer. Only the VPF master file can be viewed. The images must be present in the \spool directory.

include_stacking Specifies whether the OFFSET instructions in the AFP file are retained in the VPF. A media map may have the stacking flag enabled. The include_stacking keyword lets you determine whether the normalization engine must interpret that flag. Valid values are:

• discard (default) - OFFSET instructions are not included in the VPF.

• include - OFFSET instructions are included in the VPF.

include_tray Specifies how to handle bin calls in the FORMDEF. Valid values are:

• 0 (default) - Bin calls specified in FORMDEF are ignored.

• 1 - Convert bin calls in the FORMDEF to $IBIN resources in the VPF file.

For example:

include_tray=1

Note: You can also enter a n value here to insert a fixed $IBIN resource in the VPF file. The value assigned to the $IBIN is n-1 because include_tray=1 specifies bin calls according to the FORMDEF. For example, include_tray=3, inserts $IBIN 2 in the VPF file. For more information about $IBIN, see the Open Print Language Guide.

The media source of the MMC record is the tray number.

index_fname Specifies the name of the index configuration file containing information about the TLEs embedded in the AFP. This is useful when data about a page is held in the TLE and not in the page itself. The lines in the file are numbered with the page number and the name of the TLE type. The application reads these and matches them to the page in the VPF file.

For example:

index_fname=index.cfg

To specify whether or not to create an index file, use the use_index_file keyword. For more information, see use_index_file on page 42.

keep_n_left_spaces Determines the number of spaces to keep to the left of all character strings.

By default, the value is -1, in order not to modify the space characters of the stream.

For example:

keep_n_left_spaces=2

This keeps the first two spaces to the left of all the character strings.

Keyword Description



AF

P-D

S n

orm

aliz

atio

n

nop Extracts NOP comments and their location. Valid values are:

• guess - Deduces the codepage format based on the NOP content. If the engine detects an Extended Binary Coded Decimal Interchange Code (EBCDIC) format, the NOP content is converted to ASCII.

• ebcdic - Converts NOP content to ASCII.

• ASCII - Keeps the NOP content to ASCII.

• binary - Codes the content of the NOP in hexadecimal, without conversion.

• discard (default) - Ignores NOPs.

Keyword Description

For the different values of the nop keyword, information may be lost depending on the NOP characteristics. Recommendations for using this keyword arthe following table:

Characteristics of NOPs comments in the stream

Values

guess ebcdic ASCII binary discard

Stream does not contain NOPs

NOPs contain only EBCDIC text

cdpe

NOPs contain only ASCII text

NOPs contain ASCII and EBCDIC texts

NOPs contain EBCDIC data cdpe

NOPs contain ASCII data

NOPs contain binary data

NOPs contain binary data and EBCDIC texts

NOPs contain binary data and ASCII texts

No information loss.

cdpe

Possible to use an external codepage using the option -E OP_ASCII_EBDCDIC.

EBDIC text converts to ASCII using an internal conversion table. The -E OP_ASCII_EBDCDIC allows you to specify an alternative conversion table. This table is a binary file consisting of 256 characters. Each character specifies the corresponding value in the EBCDIC code page. For example, the tenth character of the table defines the EBCDIC value of the ASCII character 0x10. This table must be located in the \common\config directory of the Open Print installation directory.

Possible loss of information.

Note • ASCII or EBCDIC text: characters 0-9, a-z, A-Z, space and binary zero (no accented character)

• ASCII or ebcdic data: text, special characters (-+,;_@) and accented characters

• Binary data: codes from 0 to 255



output_doc_compress Determines whether or not to compress the output VPF file. Valid values are:

• 1 - VPF file compression is used. The volume of the file generated is reduced by half. Compression extends the time required to generate the VPF file.

• 0 (default) - No VPF file compression is used.

overlay_dir Specifies the search path for overlays. This overrides the path specified in res_dir. For more information, see res_dir on page 36.

overlay_dump_folder Specifies the extraction output path for overlays. This overrides the path specified in res_dump_folder. For more information, see res_dump_folder on page 36.


padding_mode Specifies if Carriage Return Line Feed (CR LF) is processed as the end of a record. Use padding_mode if records end in CR LF (0x0D 0x0A). Valid values are:

• none (default) - Records are parsed without CR LF.

• cr_lf - Records are parsed with CR LF.

If padding_mode=cr_lf, and Remake does not find the 0x0D 0x0A in the file, it stops processing the file and gives the message, “Unexpected end of file in filename.”

page_dump_folder Specifies the extraction output path for PAGEDEF. This overrides the path specified in res_dump_folder. For more information, see res_dump_folder on page 36.


pageseg_dir Specifies the search path for page segments. This overrides the path specified in res_dir. For more information, see res_dir on page 36.

paper_height Specifies the height of paper from printer. The default value is A4, i.e. 21cm x 29.7cm. Valid units are:

• pica for pica points (default unit)

• cm for centimeters

• mm for millimeters

• inch for inches,

• mils for 1/1000th of an inch

• dot for pixels

For example:

paper_ height=750pica

• Sefas recommends you do not use different units in a single configuration file.

• This keyword is taken into account if a FORMDEF is used, and if the FORMDEF is configured in 2-UP mode and contains no medium size.

Keyword Description



AF

P-D

S n

orm

aliz

atio

n

paper_width Specifies the width of paper from printer. The default value is A4, i.e. 21cm x 29.7cm. Valid units are:

• pica for pica points (default unit)

• cm for centimeters

• mm for millimeters

• inch for inches,

• mils for 1/1000th of an inch

• dot for pixels

For example:

paper_ width=500pica

Please note:

• Sefas recommends you do not use different units in a single configuration file.

• These keywords are taken into account if a FORMDEF is used, and if this FORMDEF forces to work in 2-UP and contains no medium size.

psg_dump_folder Specifies the extraction output path for page segments. This overrides the path specified in res_dump_folder. For more information, see res_dump_folder on page 36.


quit_on_unsupported_features

Specifies whether Remake stops processing a file if it encounters a GOCA (Graphics Object Content Architecture) feature that is not supported. Valid values are:

• no (default) - Unsupported GOCA features are ignored.

• yes - Remake displays a warning message and stops processing the file if it encounters an unsupported GOCA feature.

ref_map Specifies the correspondence to apply to GCGID, input AFP codes and output VPF codes. For example:

ref_map=file 1, file 2…, file n

You can use the space character, a tab, or a comma to split files.

The files are searched either in the absolute directory if specified or under the common/config/afp/maps/ref directory which is pointed by opInstallDir.

During codepage conversions, some code conversion tables for ASCII are automatically generated by the engine. However, in some cases, codepages cannot be automatically processed. For these cases, we can use an external table indicating the right way to transcode the codepoints of the codepage for ASCII.

File format is the same as the one for CP files.

remove_crlf Specifies if CR/LF are converted to spaces. Use this only with ASCII files. Valid values are:

• 0 (default) - The text is not modified.

• 1 - Each instance of either CR (0x0D) or LF (0x0A) is converted to a space.

remove_n_right_spaces Determines the maximum number of spaces to delete to the right of all character strings.

By default, the value is equal to 0 in order to avoid the deletion of any characters.

The maximum value recommended is 50. For example:

remove_n_right_spaces=50

This deletes all space characters to the right up to the 50th.

Keyword Description



remove_right_spaces Determines whether to delete spaces to the right of all the character strings. Valid values are:

• 0 (default) - The spaces are kept.

• 1 - The spaces are deleted.

This mode may cause justification problems.

For example: remove_right_spaces=1

res_dir Specifies the default search path for resources. If another path is specified in a more specific keyword, the more specific keyword overrides this. Examples of more specific keywords that override res_dir are:

• charset_dir (see page 25)

• coded_dir (see page 25)

• codepage_dir (see page 25)

• formdef_dir (see page 28)

• overlay_dir (see page 34)

• pageseg_dir (see page 34)

• ttf_dir (see page 38)

res_dump_folder Specifies the default extraction output path where Remake places resources. If another path is specified in a more specific keyword, the more specific keyword overrides this. Examples of more specific keywords that override res_dump_folder are:

• charset_dump_folder (see page 25)

• coded_dump_folder (see page 25)

• codepage_dump_folder (see page 25)

• form_dump_folder (see page 28)

• overlay_dump_folder (see page 34)

• page_dump_folder (see page 34)

• psg_dump_folder (see page 35)

• ttf_dump_folder (see page 38)


Keyword Description



AF

P-D

S n

orm

aliz

atio

n

resource_map Specifies the font file for printing the Human Readable Interpretation (HRI) that accompanies a VPF barcode. The HRI must be converted separately from the barcode, because VPF barcodes do not include the HRI.

This keyword requires:

• barcode_mode=keep, which converts an AFP barcode to a VPF barcode. For more information, see barcode_mode on page 24.

• The AFP barcode must have the flag set to show the HRI.

• The AFP barcode must have the font number set to -1.

Specify the name of the font file. Do not specify a path.

For example:

resource_map=fonts.txt

Place the font file in:

common/config/afp

If Remake cannot find the font, it generates an error message and discards the HRI.

File format for the font file

Create the font file as a simple text file. This text file can be used as a general font file, or it can be a specific font file for barcodes.

Include one line in the following format:

"protocol" "barcode type" "font" "logical name"

Quotes are required. For example:

"afp" "Interleaved 2-of-5, AIM USS-I 2/5" "C0OCRA10,T1D0BASE""ocra"

Position of the HRI

In addition to specifying the font for the HRI, you can also specify its position.

If the HRI is above the barcode, use barcode_hri_above_gap to specify the position of the HRI relative to the barcode. See barcode_hri_above_gap on page 24.

If the HRI is below the barcode, use barcode_hri_below_gap to specify the position of the HRI relative to the barcode. See barcode_hri_below_gap on page 25.

show_file_offset Specifies whether the lines of the log file are prefixed with the offset and record number. Use this during debugging to link a parsing problem to a specific location in the AFP file. Valid values are:

• no (default) - Do not display the offset and record number.

• yes - Display the offset and record number.

Keyword Description

Data Description

protocol This must be: afp

barcode type This must be: Interleaved 2-of-5, AIM USS-I 2/5

font This is the charset and codepage of the font. They must be separated with a comma, with no space. For example:

C0OCRA10,T1D0BASE

The font size must be 10 points.

logical name This is the name of the font that will appear in the VPF output.



stderr For non-Windows environments, this keyword can be used to specify the access path to trace file in which TechAFP writes information about execution errors.

For example:

stderr=/user/sfdvbdr/op_wd/op_fam/customer/printer/modca_stream_1_err.log

Use this in conjunction with the verbose keyword to control the detail level of the error reporting. For more information, see verbose on page 42.

stdout Access path and name of the resource list file, when execution is launched with the options -i and -r.

Access path and the name of the log file containing processing comments, when execution is launched with the options -i and -o. For example:

stdout=C:\normalization\samples\afp_sample\printer\list.log

ttf_dir Specifies the search path for True Type fonts. This overrides the path specified in res_dir. For more information, see res_dir on page 36.

ttf_dump_folder Specifies the extraction output path for True Type fonts. This overrides the path specified in res_dump_folder. For more information, see res_dump_folder on page 36.


tle_embedding Specifies if TLEs in the AFP file are translated to $DOC resources in the VPF file. Valid values are:

• no (default) - TLEs are ignored when creating the VPF.

• yes - Each TLE is translated to a single $DOC resource in the VPF file.

When used alone, tle_embedding=yes translates each TLE in the AFP file to a single $DOC resource in the VPF file. To repeat the $DOC resources, use one or more of these additional keywords:

• tle_embedding.reset_on_epg (see page 38)• tle_embedding.reset_on_eng (see page 39)• tle_embedding.reset_on_edt (see page 39)• tle_embedding.reset_on_new_tle (see page 39)

Each of these additional keywords also requires tle_embedding=yes. These additional keywords can also be used in combination.

For examples of using the keywords, see Examples of embedding TLEs on page 40.

tle_embedding.reset_on_epg

Specifies if $DOC resources from TLEs repeat after the end of a page. Valid valuesare:

• yes (default) - $DOC resources stop repeating at the end of each page (EPG).

• no - Each TLE is translated to a single $DOC resource in the VPF file.

This keyword also requires tle_embedding=yes. For more information, see tle_embedding on page 38.

Keyword Description



AF

P-D

S n

orm

aliz

atio

n

tle_embedding.reset_on_eng

Specifies if $DOC resources from TLEs repeat after the end of a named group. Valid values are:

• yes (default) - $DOC resources stop repeating at the end of each named group (ENG).

• no - When used with tle_embedding.reset_on_epg=no, but none of the other TLE keywords, $DOC resources repeat until one of the following:

• the beginning of a named group (BNG)

• the end of a document (EDT)

• the next TLE

This keyword also requires tle_embedding=yes and tle_embedding.reset_on_epg=no. For more information, see tle_embedding on page 38 and tle_embedding.reset_on_epg on page 38.

For examples of using this keyword, see Examples of embedding TLEs on page 40.

tle_embedding.reset_on_edt

Specifies if $DOC resources from TLEs repeat after the end of a document. Valid values are:

• yes (default) - $DOC resources stop repeating at the end of each document (EDT).

• no - When used with tle_embedding.reset_on_epg=no, but none of the other TLE keywords, $DOC resources repeat until one of the following is encountered:


• the end of the a named group (ENG)

• the next TLE



tle_embedding.reset_on_new_tle

Specifies if $DOC resources from TLEs repeat after a new TLE. Valid values are:

• yes (default) - $DOC resources stop repeating at a new TLE.

• no - When used with tle_embedding.reset_on_epg=no, but none of the other TLE keywords, $DOC resources repeat until one of:


• the end of the a named group (ENG)

• the end of a document (EDT)



Keyword Description



Examples of embedding TLEs

This section gives examples for each of the keywords for embedded TLEs, and for combinations of keywords.

For a description of each of the keywords, see the previous sections:

• tle_embedding (see page 38)• tle_embedding.reset_on_epg (see page 38)• tle_embedding.reset_on_eng (see page 39)• tle_embedding.reset_on_edt (see page 39)• tle_embedding.reset_on_new_tle (see page 39)

Each of the examples in this section (except the last one) use the same AFP file asinput. A diagram of the AFP file and the fields contained in it is shown below.

The color coding in the diagram is:

• Green, document (BDT - EDT)

• Orange, named group (BNG - ENG)

• Yellow, page (BPG - EPG) without a page-level TLE

• Pink, page (BPG - EPG) with a page-level TLE

The structure of the AFP file is:

BDT BNG TLE a BPG Page1 EPG BPG Page2 EPG ENG BPG TLE b Page3 EPG BPG Page4 EPG BNG TLE c BPG Page5 EPG BPG Page6 EPG ENG BPG Page7 EPG BPG Page8 EPG BNG BPG Page9 EPG BPG Page10 EPG ENG BPG TLE d Page11 EPG BPG Page12 EPG BPG Page13 EPG BPG Page14 EPG EDT

BDT BPG Page15 EPG BPG Page16 EPG BPG TLE e Page17 EPG BPG Page18 EPG BPG TLE f Page19 EPG BPG Page20 EPG BNG BPG Page21 EPG BPG TLE g Page22 EPG ENG EDT

BDT BPG Page23 EPG BPG Page24 EPG BPG TLE h Page25 EPG BPGPage26 EPG BNG TLE i BPG Page27 EPG BPG Page28 EPG ENG BPGPage29 EPG BPG Page30 EPG BPG TLE j Page31 EPG BPG Page32 EPGBNG BPG Page33 EPG BPG Page34 EPG ENG EDT

Keyword Description



AF

P-D

S n

orm

aliz

atio

n

Example 1

With tle_embedding=no, the structure of the VPF file is:

Page1 Page2 Page3 Page4 Page5 Page6 Page7 Page8 Page9 Page10 Page11 Page12 Page13 Page14

Page15 Page16 Page17 Page18 Page19 Page20 Page21 Page22

Page23 Page24 Page25 Page26 Page27 Page28 Page29 Page30 Page31 Page32 Page33 Page34

Notice that the TLEs in the AFP file are not translated to $DOC resources in the VPF file.

Example 2

With tle_embedding=yes, the structure of the VPF file is:

$DOC a Page1 Page2 $DOC b Page3 Page4 $DOC c Page5 Page6 Page7 Page8 Page9 Page10 $DOC d Page11 Page12 Page13 Page14

Page15 Page16 $DOC e Page17 Page18 $DOC f Page19 Page20 Page21 $DOC g Page22

Page23 Page24 $DOC h Page25 Page26 $DOC i Page27 Page28 Page29 Page30 $DOC j Page31 Page32 Page33 Page34

Notice that each TLE in the AFP file is translated to a single $DOC resources in the VPF file. Compare this to Example 1, which uses tle_embedding=no.

Example 3

With tle_embedding=yes and tle_embedding.reset_on_epg=no, the structure of the VPF file is:

$DOC a Page1 $DOC a Page2 $DOC b Page3 $DOC b Page4 $DOC c Page5 $DOC c Page6 Page7 Page8 Page9 Page10 $DOC d Page11 $DOC d Page12 $DOC d Page13 $DOC d Page14

Page15 Page16 $DOC e Page17 $DOC e Page18 $DOC f Page19 $DOC f Page20 Page21 $DOC g Page22

Page23 Page24 $DOC h Page25 $DOC h Page26 $DOC i Page27 $DOC i Page28 Page29 Page30 $DOC j Page31 $DOC j Page32 Page33 Page34

Notice that the $DOC resources now repeat beyond the end of each page. Compare this with Example 2, which uses tle_embedding.reset_on_epg=yes. For example:

• $DOC c repeats until Page6. It stops repeating at the ENG. In Example 2, $DOC c is only on Page5.

• $DOC d repeats until Page14. It stops repeating at the EDT. In Example 2, $DOC d is only on Page11.

• $DOC e repeats until Page18. It stops repeating at the TLE. In Example 2, $DOC e is only on Page17.

• $DOC f repeats until Page20. It stops repeating at the BNG. In Example 2, $DOC f is only on Page19.

Keyword Description



Example 4

With tle_embedding=yes, tle_embedding.reset_on_epg=no, and tle_embedding.reset_on_eng=no, the structure of the VPF file is:

$DOC a Page1 $DOC a Page2 $DOC b Page3 $DOC b Page4 $DOC c Page5 $DOC c Page6 $DOC c Page7 $DOC c Page8 Page9 Page10 $DOC d Page11 $DOC d Page12 $DOC d Page13 $DOC d Page14

Page15 Page16 $DOC e Page17 $DOC e Page18 $DOC f Page19 $DOC f Page20 Page21 $DOC g Page22

Page23 Page24 $DOC h Page25 $DOC h Page26 $DOC i Page27 $DOC i Page28 $DOC i Page29 $DOC i Page30 $DOC j Page31 $DOC j Page32 Page33 Page34

Notice that the $DOC resources now repeat beyond the end of each named group. Compare this with Example 3 on page 31, which uses tle_embedding.reset_on_eng=yes. For example:

• $DOC c repeats until Page8. It stops repeating at the BNG. In Example 3, $DOC c stops repeating on Page6, at the ENG.

• $DOC i repeats until Page30. It stops repeating at the TLE. In Example 3, $DOC i stops repeating on Page28, at the ENG.

use_index_file Defines an index file if the keyword index_fname is not entered. Valid values are:

• 0 - No index file.

• 1 (default) - The name of the index file is that of the input file with the extension *.tle.

For an input file invoice.afp, the index file will be invoice.tle.

The normalization engine does not normalize the index block found before the beginning of the AFP document.

verbose Specifies the quantity of information contained in the trace file and/or error logs. For more information, see stderr on page 38 and stdout on page 38. Valid values are:

• -1 - displays only the errors. This value is ESSENTIAL when going into production.

• 0 (default) - does not display a message in the trace file.

• 10 - displays all the information in the trace file in English and French.

• 11 - commands the simultaneous writing of the output file and displays all of the information in the trace file. This option is reserved for experienced users.

Keyword Description



AF

P-D

S n

orm

aliz

atio

n

Line mode keywords

The following is a list of keywords that are specific to AFP line mode and mixed mode streams. Forgeneral keywords, see General keywords on page 24.

Keyword Description

carriage_control Specifies the type of carriage controls that drive the PAGEDEF. Valid values are:

• none (default) - No carriage controls are used.

• ansi - ANSI carriage controls are used.

• machine - Machine carriage controls are used.

chars Declares up to four coded fonts during the analysis of a stream. Valid values are:

• none (default) - No declared coded fonts.

• XFONT1,XFONT2,XFONT3,XFONT4 - Names of up to four coded fonts, separated by a comma. The names must begin with the character X and must have at least three characters.

When needed, the coded font information can be found in the print JCL.

default_charset Specifies the default charset. This charset is used:

• If no font is declared in an AFP page• If a font is declared in a MCF with an unknown GRID code

For example:

default_charset=C0S0CR12

The keywords default_charset and default_codepage must be used together. For more information, see default_codepage on page 26.

input_format Specifies the format of the input file. Valid values are:

• variable_flat (default) - The input file is a flat file with records of variable length. This is the standard MO:DCA format.

• fixed_flat - The input file contains 0x0D 0x25 terminated records.

• variable_native - The input file contains data in logical blocks of variable length. This option is typically used to process MO:DCA or line streams on z/OS (or MVS / OS390) systems.

• fixed_native - The input file is an FB dataset file.

• xmit_flat - The input file is an encapsulated xmit archive.

This option processes streams on Windows, UNIX, and z/OS (or MVS / OS390) systems. Please note that the xmit must contain a sequential dataset, not a PDS or a PDSE. PDS are libraries containing one or more members and are not supported.

• cr_lf - The input file contains 0x0D 0x25 terminated records.

• bl_rl - The input file contains block length + record length prefixed records.

• block - The input file is a FTP block mode file.

• rl - The input file contains record length prefixed records.

This keyword specifies the format of the input file. To specify the format of the resources, use res_input_format. For more information, see res_input_format on page 44.

input_type Specifies the nature of blocks of the AFP stream. Valid values are:

• modca (default) - Blocks are records in MO:DCA format.

• line_mode - Blocks are made up of data in line mode, or the stream contains both line mode and MO:DCA blocks.

page_def_name Specifies the name of the PAGEDEF file (without the directory path) containing the various line imposition sections used by the AFP stream to be normalized.

For example:

page_def_name=P1SEFAS4



pagedef_dir Specifies the output path for the PAGEDEF. This overrides the path specified in res_dump_folder. For more information, see res_dump_folder on page 36.


record_length Specifies the length of non-encapsulated stream records in an xmit archive. If the records are of fixed length, it is this value that must be specified. If they are of variable length, then you must specify the maximum length. Valid values are:

• 0 (default) - The length of records is not specified.

• [length] - The length of records is a fixed size (in octets).

For example:

record_length=8205

res_input_format Specifies the nature of stream resources for input file overlays, page segments, FORMDEF, and PAGEDEF.

The format of the actual stream must be specified with the input_format parameter. Valid values are:

• variable_flat (default) - The input file is a flat file with records of variable length. This is the standard MO:DCA format.

• fixed_flat - The input file contains 0x0D 0x25 terminated records.

• variable_native - The input file contains data in logical blocks of variable length. This option is typically used to process MO:DCA or line streams on z/OS (or MVS / OS390) systems.

• fixed_native - The input file is an FB dataset file.

• xmit_flat - The input file is an encapsulated xmit archive. This option processes streams on Windows, Unix and OS 390 Open Edition systems.

• cr_lf - The input file contains 0x0D 0x25 terminated records.

• bl_rl - The input file contains block length + record length prefixed records.

• block - The input file is a FTP block mode file.

• rl - The input file contains record length prefixed records.

use_trc Specifies whether the stream contains table reference characters. Valid values are:

• no (default) - The stream contains no table reference characters.

• yes - The stream contains table reference characters.

Keyword Description


M a n a g i n g c o l o rOve r v i ew o f s ub s t i t u t i n g c o l o r

AF

P-D

S n

orm

aliz

atio

n

Managing color

Overview of substituting color

Remake can be configured to convert the color of texts, lines, boxes, shadings or images in AFPMO:DCA steams during normalization.

Colors in the input file may be expressed in any of the following modes:

• Standard (OCA)• RGB • CMYK• Highlight• CIELab

The AFP normalization engine transforms colors of the input stream into CMYK colors.

Color substitution table

The conversion of colors, if needed, is managed via a substitution table. The table is defined usingthe configuration file keyword color_mapping_table. For more information, seecolor_mapping_table on page 26.

The remaining information in this section is provided as reference information to help you createand enable a color mapping table, if transformation of color is required during normalization.

Color modes

Standard colors (OCA)

Standard colors are basic colors. The corresponding color codes are as follows:

0x0000 = 0xFF00 = drawing default

0x0001 = 0xFF01 = blue

0x0002 = 0xFF02 = red

0x0003 = 0xFF03 = magenta

0x0004 = 0xFF04 = green

0x0005 = 0xFF05 = cyan

0x0006 = 0xFF06 = yellow

0x0007 = black for printers, white for displays

0x0008 = black

0x0009 = dark blue

0x000A = orange

0x000B = purple

0x000C = dark green

0x000D = dark turquoise

0x000E = mustard

0x000F = gray

0x0010 = brown

0xFF07 = presentation-process default

0xFF08 = color of medium

RGB colors

The components of the RGB system are Red, Green, and Blue.


M a n a g i n g c o l o rCo l o r s ub s t i t u t i o n t a b l e

CMYK colors

The components of the CMYK system (also known as PANTONE) are Cyan, Magenta, Yellow, andBlack.

Highlight colors

This is not a real color system but a reference to an external table which is location-independentfrom the controller, PSF, InfoPrint, and other hardware.

The color number is an index in the external table. Two other parameters can be specified:

• Coverage, which defines the element filling • Shading, which lets you add a black value to the output color

CIELab colors

The white reference points are D50 or D65, depending on the element concerned.

The components of this system are L*, a* and b*.

Color substitution table

The substitution table contains lines in text format:

• Values introduced with a semicolon (;) or a hash (#) character are comments.

• The syntax of an expression id is key=value (no space).

• Space and tab characters are separators between expressions.

• A line is composed of an input color and an output color.

• Two modes are used to set the output color:

• cyan=0..255 magenta=0..255 yellow=0..255 black=0..255• red=0..255 green=0..255 blue=0..255

• Three modes are used to describe the input color:

• oca=0x0000..0xFF08

For example: oca=0x0006 (for yellow).

• number=0x0000..0xFFFF [[coverage=0..100] [shading=-1]]

For example: number=0x0005 (all coverage and shading values match).

• cielab=0xLab where L is in 0..0xFFFF and a and b are in 0x00..0xFF

For example: ceilab= 0x3C62BC1

The next two sections of this document provide details about the default substitution table and anexample of the actual table that corresponds to the default. See below.

1.CIELab colors capture is processed using the 32 bytes keys located in the MO:DCA stream and not using Lab values in floating point.


M a n a g i n g c o l o rCo l o r s u b s t i t u t i o n t a b l e

AF

P-D

S n

orm

aliz

atio

n

IBM color codes and default values

Default color substitution table

The following table corresponds to the color substitution table that is integrated with TechAFP.:

Color Number

Code IBM color Label

Default values

C M Y K

0 0x00000xFF00

Colorby default

0 0 0 255

1 0x00010xFF01

Blue 254 254 0 1

2 0x00020xFF02

Red 0 254 254 1

3 0x00030xFF03

Magenta 0 254 0 1

4 0x00040xFF04

Green 254 0 254 1

5 0x00050xFF05

Cyan 254 0 0 1

6 0x00060xFF06

Yellow 0 0 254 1

7 0x0006 Black for printerWhite for screen

0 0 0 255

8 0x0008 Black 0 0 0 255

9 0x0009 Dark blue 254 254 84 1

10 0x000A Orange 0 126 254 1

11 0x000B Purple 84 254 84 1

12 0x000C Dark green 254 108 254 1

13 0x000D Dark cyan 254 108 84 1

14 0x000E Mustard 58 94 222 1

15 0x000F Gray 0 0 0 124

16 0x0010 Brown 110 206 254 1

17 0xFF07 Default presentation (Black)

0 0 0 255

18 0xFF08 Supporting color (White)

0 0 0 0

; Highlight colors are composed of one to three components:; 1) (Mandatory) the color number: between 0x0000 and 0xFFFF. 0x0000 is the presentation device default color.; 2) (Optional) the color percent coverage: between 0 and 100. 100 means plain fill.; 3) (Optional) the black percent coverage: between 0 and 100. 100 means plain black.;; For (2) and (3), -1 means any value;; Valid OCA colors are:;;; 0x0000 = 0xFF00 = drawing default; 0x0001 = 0xFF01 = blue; 0x0002 = 0xFF02 = red; 0x0003 = 0xFF03 = magenta


M a n a g i n g c o l o rCo l o r s ub s t i t u t i o n t a b l e

; 0x0004 = 0xFF04 = green; 0x0005 = 0xFF05 = cyan; 0x0006 = 0xFF06 = yellow; 0x0007 = black for printers, white for displays; 0x0008 = black; 0x0009 = dark blue; 0x000A = orange; 0x000B = purple; 0x000C = dark green; 0x000D = dark turquoise; 0x000E = mustard; 0x000F = gray; 0x0010 = brown; 0xFF07 = presentation-process default; 0xFF08 = color of medium;;; both RGB and CMYK values are allowed:; -RGB values are given in the order r,g and b; -CMYK value are given in the order c,m ,y and k; -color values are between 0 and 255;;; Highlight color Syntax:;; number=0x0000..0xFFFF[coverage=-1..255][shading=-1..255]cyan=0..255magenta=0..255yellow=0..255black=0..255 ;; number=0x0000..0xFFFF[coverage=-1..255][shading=-1..255]red=0..255green=0..255blue=0..255 ;; OCA color Syntax:;; oca=0x0000..0xFF08cyan=0..255magenta=0..255yellow=0..255black=0..255 ;; oca=0x0000..0xFF08red=0..255green=0..255blue=0..255 ;;;; default color;number=0x0000coverage=-1shading=-1red=0green=0 blue=0

;number=0x0001red=0green=255 blue=0;number=0x0002coverage=-1shading=-1red=105green=50 blue=255;number=0x0003coverage=-1shading=-1red=255green=0 blue=255;number=0x0004coverage=-1shading=-1red=0green=0 blue=255

; missing value in the workbench table;number=0x0005coverage=-1shading=-1cyan=128magenta=0 yellow=0black=0

;oca=0x0000 red=0 green=0 blue=0;oca=0xFF00 red=0 green=0 blue=0;oca=0x0001 red=255 green=0 blue=0

;oca=0x0000 red=0 green=0 blue=0;oca=0xFF00 red=0 green=0 blue=0;oca=0x0001 cyan=24 magenta=13 yellow=13 black=0;oca=0x0002 red=0 green=0 blue=0 ;oca=0x0003 cyan=128 magenta=20 yellow=5 black=100

; CIELab colors are defined by a three-byte hexadecimal key;cielab=0x3C62BC cyan=128 magenta=0 yellow=0 black=10 ;cielab=0x5BB08E cyan=0 magenta=128 yellow=0 black=100

number=0x0000 cyan=0 magenta=0 yellow=0 black=0 number=0x0001 cyan=64 magenta=0 yellow=0 black=0number=0x0002 cyan=0 magenta=64 yellow=0 black=0number=0x0003 cyan=64 magenta=64 yellow=0 black=0number=0x0004 cyan=0 magenta=0 yellow=64 black=0number=0x0005 cyan=64 magenta=0 yellow=64 black=0 number=0x0006 cyan=0 magenta=64 yellow=64 black=0number=0x0007 cyan=64 magenta=64 yellow=64 black=0number=0x0008 cyan=0 magenta=0 yellow=0 black=64number=0x0009 cyan=64 magenta=0 yellow=0 black=64number=0x000A cyan=0 magenta=64 yellow=0 black=64


M a n a g i n g c o l o rCo l o r s u b s t i t u t i o n t a b l e

AF

P-D

S n

orm

aliz

atio

n

Compatibility

Principle

The AFP protocol assigns a color to an element of a document. There are 19 predefined colorsavailable. They are defined in the Standard OCA Color Value of the IBM documentation (MO:DCARef SC31-6802-04).

The principle is to match one or several colors among the 19 with values other than those definedin the IBM documentation.

Enabling the substitution table

The substitution table is enabled using the color_mapping_table keyword in theconfiguration file. The syntax is:

color_mapping_table=filename

filename is the name of the substitution table. It may be one of the following

• A complete path• A relative path. In this case, the file is searched for in the configuration directory

($opInstallDir/common/config).

By default, a substitution table is enabled by the normalization engine. This table is inside thenormalization engine. It is used in the following cases:

• When no substitution table has been defined• When no color has been defined in the substitution table enabled (default table values

are kept)

For more information, see Default color substitution table on page 47.

number=0x000B cyan=64 magenta=64 yellow=0 black=64number=0x000C cyan=0 magenta=0 yellow=64 black=64number=0x000D cyan=64 magenta=0 yellow=64 black=64number=0x000E cyan=0 magenta=64 yellow=64 black=64number=0x000F cyan=64 magenta=64 yellow=64 black=64 number=0x0010 cyan=0 magenta=0 yellow=0 black=128

Note When verbose=1 (or more), the engine displays the translation table read.


M a n a g i n g i m a ge sCo l o r s ub s t i t u t i o n t a b l e

Managing images

Remake converts AFP images as described in the table below.

Image configuration table

This table determines the colors attributed to the images. It is called by the keywordcolor_table_fname of the TechAFP configuration file.

It contains the following information, separated by tabs:

x

IMAGE C Y M K O T

• x is the number of referenced images.• IMAGE is the name of the image.• C, Y, M and K represent the colors of the image; these values are between 0 and 255.• O defines the opacity of the image: 0 = transparent, 1 = opaque.• T defines the texture or shading pattern of the image. Refer to the Open Print

Language Guide for the possible values.

Input format Output format

IM1 1bit PCX black & white

IOCA FS11 G4 PCX black & white

IOCA FS11 IBM MMR PCX black & white

IOCA FS11 24 bits RGB JPEG JPEG RGB

IOCA FS42 4bits CMYK G4 JPEG CMYK

IOCA FS42 4bits CMYK IBM MMR JPEG CMYK

IOCA FS45 32bits CMYK JPEG JPEG CMYK

IOCA FS45 32bits CMYK TIFF LZW JPEG CMYK

ICOA G4 MMR G4 TIFF

To convert to PCX, use keyword decompress_g4_mmr_icoa=yes (See decompress_g4_mmr_ioca on page 26.)


M a n a g i n g d e - i m p o s i t i o nCo l o r s u b s t i t u t i o n t a b l e

AF

P-D

S n

orm

aliz

atio

n

Managing de-imposition

De-imposition of an AFP stream may require specific treatment. Therefore, an option is providedto let you define the stream de-imposition mode. It is called by the keyword fem_fname of theTechAFP configuration file. The fem_fname keyword lets you specify an additional configurationfile containing keywords specific to deimposition.

[OPIMPOSITION]

output_mode=SIMPLEX

default_imposition=imp1

[imp1]

medium=medium1

output_medium=omed1

[omed1]

physical_page=ph1,ph2

;---------------------------------

; RECTO

;---------------------------------

[ph1]

side=Recto

xoffset= 0cm

yoffset = 0cm

orientation=0

dimension=PG1

data_page=p1

[ph2]

side=Recto

xoffset= 17cm

yoffset = 0cm

orientation=0

dimension=PG1

data_page=p1

[p1]

xoffset= 0cm

yoffset = 0cm

orientation=0

dimension=PG1

[medium1]

dimension=M1

[M1]

width=34cm

height=31cm

[PG1]

width=17cm

height=31cm

NoteAn example of the file is provided below for reference purposes. For more information regardingdeimposition options, contact Sefas Customer Support.


N o r m a l i z i n g t h e s t r e a mVe r i f y i n g r equ i r ed i n pu t

Normalizing the stream

Verifying required input

The following elements must be available before launching normalization.

• AFP stream• Any external AFP resources: fonts, overlays, page segment, FORMDEF (optional),

PAGEDEF (optional)

The \spool directory of the application should contain the AFP stream. For more information,see Spooling the file to be normalized on page 15.

The configuration file should be in the directory specified in the Cfg File field of the Remake userinterface.

Any external fonts, overlay, page segment, PAGEDEF and FORMDEF files should be present at thelocations specified in the configuration file (see below).

Processing External Resources

If the resources are not inline, Remake automatically searches through a set of predefineddirectories to determine whether the resources are available. The directories must be set byassigning paths to the appropriate keywords in the techafp.cfg configuration file.

Dedicated search paths

Search paths dedicated to various types of input resources are specified using the followingkeywords:

• charset_dir on page 25

• code_page_dir on page 25

• pageseg_dir on page 34

• formdef_dir on page 28

• pagedef_dir on page 44

• overlay_dir on page 34

Optionally, you can include all or some of the resources in a single directory specified using theres_dir keyword or -R parameter. For more information, see res_dir on page 36 and -R on

page 54.

Search order

Remake searches your local disk for resources that are not embedded in the AFP file. For eachresource, the directory searched depends on the resource type. The following search order ispredefined and always the same:

• Dedicated search paths are searched first, if defined.• The /spool directory of the application, if search paths are not defined.

Optionally, the -R parameter can be used to specify a single location for all external resources.For more information, see -R on page 54.

Note Overlays and page segments are necessary only if the target format is not AFP.

Note For information on how to set up extraction output paths for resources, seecharset_dump_folder on page 25, codepage_dump_folder on page 25, psg_dump_folder

on page 35, form_dump_folder on page 28, page_dump_folder on page 34, andoverlay_dump_folder on page 34 keywords. If no specific output paths are specified, thedefault path can be set using the keyword res_dump_folder on page 36.


N o r m a l i z i n g t h e s t r e a mEn t e r i ng c omman d l i n e pa rame te r s

AF

P-D

S n

orm

aliz

atio

n

Entering command line parameters

Once all required resources are in place, do the following to enter any command line parametersrequired for the normalization:


2. Click the Normalize button:

3. Enter any required command line parameters in the Normalize field. For a list of parameters, see below.

4. Click OK.


The command line parameters for the TechAFP normalization engine are presented in the tablebelow.

Note The sample values below are provided as general examples for demonstration purposes.Depending on the system and shell you are using, the use of quotes and other operators may berequired for specific variables. For example, either format -E opAppli="" or -E opAppli= must beused be used depending on your environment.

Parameter Description

-A Specifies external file name which gets parsed with extra command line parameters. You can put all of your command line parameters in a file. For example:

-A myparameters.txt

Note: This feature is useful on z/OS (or MVS / OS390) systems where JCL scripts have limitations with command line length.

-c or -C

Access path to configuration file followed by the section containing the settings relating to the AFP stream process specified with the option -i.

When lowercase -c option is used, the section name is specified by appending it to the path following the sharp character (#). For example:

• -c C:\normalization\techafp.cfg#LIST_FONTS

To specify a section with the capital letter -C option you must also use the -S parameter. For example:

• -C C:\normalization\techafp.cfg -S LIST_FONTS

Important• The # separator must be attached to the configuration filename and section

name.

• If the section name is not specified, the # character is not needed. By default, the processing occurs on the first section of the configuration file.

• As an alternative to using this parameter, the section name may be provided in the Windows user interface.

-E Sets an environment variable.


N o r m a l i z i n g t h e s t r e a mEn t e r i n g c ommand l i n e p a rame t e r s

-E opInstallDir= Sets an environment variable to indicate the path to the bin and common directories. For example:

-E opInstallDir=C:\oprint

-E opWD= Sets the environment variable to indicate the group entry point. For example:

-E opWD=C:\normalization

-E opFam= Sets the environment variable to indicate the name of the directory containing the group of applications. For example:

-E opFam=samples

-E opAppli= Sets the environment variable to indicate the name of the application directory.

For example:

-E opAppli=afp_sample

-E opTmpDir Sets the environment variable used to specify the path to temporary files and directories. The use of an absolute path with this parameter is required. For example:

-E opTmpDir=C:\temp

-e Defines of the resolution used by the fonts. Valid values are:

• 240 (default)

• 300

In dynamic mode, this option is ignored.

-h or -help Displays command line parameter help for the normalization engine you are running.

-H Displays extended command line help for the version of the normalization engine you are running.

-i Access path to the input AFP stream, including file name and extension. For example:

-i C:\normalization\invoice.afp

-o Specifies the access path to the VPF resulting from the AFP to VPF conversion.

Use when the Open Print normalization environment has been created. The complete path must be specified in standard mode. A relative path can be used in dynamic mode. For example:

-o C:\normalization\spool\document.vpf

This option cannot be used with the -r option.

-p Corresponds to the end_page keyword. For more information, see end_page on page 27

-R Specifies the path to the resources.This option can be used to replace the directory keywords charset_dir, code_dir, etc. However, if specified, these keywords take priority over the -R parameter. For example:

-R C:\myresources

-v Corresponds to the verbose keyword. For more information, see verbose on page 42.

The -v option on the command line overrides the verbose keyword in the configuration file.

-z Determines whether or not to compress the output VPF file.

This option corresponds to the output_doc_compress keyword. For more information, see output_doc_compress on page 34.

The -z option overrides the output_doc_compress keyword.



N o r m a l i z i n g t h e s t r e a mExe cu t i ng t h e n o rma l i z a t i o n

AF

P-D

S n

orm

aliz

atio

n

Command Line Example

You can also execute parameters using the command line outside of the Remake user interface.The following example shows how a command line is used to call the NORMALIZATION section ofthe configuration file. For an example of executing parameters using the Remake interface, seeEntering command line parameters on page 53.

C:\oprint\bin\go.exe techafp-E opInstallDir=C:\oprint


-E opFam=samples -E opAppli=afp_sample

-E opTmpDir=C:\temp

-i C:\normalization\samples\afp_sample\spool\invoice.afp

-o C:\normalization\samples\afp_sample\spool\invoice.vpf

-e 240

-c C:\normalization\samples\afp_sample\common\config\techafp.cfg#NORMALIZATION

The command line calls the section of the configuration file below:

[NORMALIZATION]

verbose= -1

stderr=C:\normalization\samples\afp_sample\log_files\err.log

stdout=C:\normalization\samples\afp_sample\log_files\out.log



stdout=C:\normalization\samples\afp_sample\log_files\out.log

fill_gray_im = 1

img_dir=C:\normalization\samples\afp_sample\macro

output_doc_compress=0

form_def_name=FORMDEF

Executing the normalization

Do the following to execute the normalization:

1. Launch Remake.

2. Click View > Trace to display the Trace window:

3. Click the up arrow icon to display the EXECUTE toolbar.

NoteFor general information about the Remake user interface, see the Open Print Remake User

Guide.


L o c a t i n g t h e V P F o u t p u tExe cu t i n g t h e no rma l i z a t i o n

4. Click Normalize.

5. Click Run:

Locating the VPF output

Unless specified otherwise with a keyword or parameter, the VPF file is output to the \spooldirectory of the application. Following our sample application, the VPF file will be:

C:\normalization\samples\afp_sample\spool\afp_sample.vpf

The VPF file contains all of the original fonts and resources. Charset and codepage are embeddedin the VPF file. Other resources (coded files, FORMDEF, page segments, overlays, and PAGEDEF aretranslated into VPF resource objects.


Abou t t h e Te chPCL no rma l i z a t i o n en g i ne

HP

-PC

L n

orm

aliz

atio

n

C h a p t e r 3 : H P - P C L n o r m a l i z a t i o n

Open Print Remake supports normalization of black-and-white, Hewlett-Packard Printer CommandLanguage (HP-PCL) files created with versions 3, 4, and 5 of the PCL language. Normalization ofcolor PCL files is not supported.

PCL files are made up of data and the following types of resources:

• Fonts• Images• Macros

The actual mix of resources in a PCL stream depends on the contents of the file. For PCL files,images and macros are inline (that is, they are embedded in the file). Fonts may be either inlineor external to the stream. Inline fonts are processed automatically during normalization. Thereare two types of external fonts:

• Resident fonts - These are stored in the printer hardware.• Soft fonts - These must be downloaded to the printer before they can be used in the

PCL stream.

External fonts are referenced in the stream by an identifier and require special processing.

PCL normalization converts a PCL file to a Virtual Page Format (VPF) file. Regardless of whetherthe fonts are external or embedded, the normalized VPF output file contains all the resourcesinline.

About the TechPCL normalization engine

The TechPCL normalization engine converts a PCL data stream into a VPF file. Processing optionsfor the engine are set using a configuration file. Additional parameters are set at run time. Theconfiguration file is edited using a standard text editor. Runtime parameters are set and thenormalization is executed using Remake’s user interface.


The standard configuration file used by the TechPCL normalization engine is techpcl.tab. Thefile contains sections and keywords that tell the engine how to process the incoming PCL datastream.

For example, the font_embedding keyword must be present in the configuration file, and set to1, to enable dynamic font processing.


on page 65.


The engine also supports parameters that can be processed using the command line at runtime.These parameters are used to set environment variables and other options not set using theconfiguration file.

For example, the -i parameter can be used to set the access path to the PCL input stream.




Before you begin


Sefas recommends that you have the following third-party tools installed on the computer whereyou are performing the PCL normalization.

• PCL viewer• Hexadecimal text editor

It is also helpful to have a PCL-compatible printer connected to the computer for testing purposes.

Gathering PCL resources

Before launching a PCL normalization, you should compile a list of the resources contained in thestream.

Sefas recommends that you:

• Gather and have available a selection of the original, printed PCL documents as a reference.

• Review and assess the nature of the resources to be normalized.• Determine the location and names of any fonts that are not inline.


While virtually any directory structure can be used to peform the normalization, it is helpful touse a standard directory struture and standard naming conventions. Sefas recommends that youuse a structure based on the $opWD (working), $opFam (group), and $opAppli (application)Open Print environment variables.

There are a number of ways you can establish the environment. For example, you can:


• Create the directory structure from scratch.• Use the Create New Project capability in the Remake user interface to have the

software create the directory structure automatically.



Operating Manual.



HP

-PC

L n

orm

aliz

atio

n







C:\normalization






1. Locate the directory containing your sample application. The directory is either located in the Remake installation folder or was provided to you by a Sefas representative (for example, during training).

2. Copy the entire directory labeled \pcl_sample to the normalization directory you created previously; the resulting directory is:

C:\normalization\samples\pcl_sample




P r e p a r i n g t h e f o n t e n v i r o n m e n tRes i den t f on t s

Preparing the font environment

If the fonts are embedded in the PCL file, Remake processes them automatically. If the streamcontains printer-resident and/or soft fonts, please see the appropriate section below to establishthe proper font environment for normalization.

Resident fonts

Fonts that reside on the printer are vectorial, for example, TrueType or Type 1. Remake requiresthat vectorial fonts be converted to bitmap fonts prior to normalization. Therefore, you must doone of the following for each vectorial font in the stream:

• Substitute the font with a standard font provided with Remake (Times, Arial, Courier, Wingdings).

• Create bitmap fonts from the vectorial fonts using TechFont.

Example of Font Substitution

To substitute the fonts:

1. Locate the file hp.fnt. Following the sample application, this is in:

C:\normalization\samples\pcl_sample\common\chasse

2. Locate the section of the file that contains the entry for the target font you want to use.

3. Edit the substitute= parameter for the entry to include the font you want to substitute.

The below example shows substitution of Garamond and Helvetica with Arial.

[hl05np]

family=Arial

substitute=ARIAL,arial,Helvetica,HELVETICA,Helv,Garamond

style=normal

size=5

load=yes

file=hl05np.sfp

type=bitmap

[hl06np]

file=hl06np.sfp

size=6

Soft fonts

Fonts downloaded to the the printer may be vector or bitmap. Vector soft font processing is notsupported. For PCL bitmap soft fonts, do the following:

1. Locate the font files.

2. Copy the files into a single directory.

3. Specify the absolute path to the directory in the techpcl.tab configuration file using the ext_soft_font_dir keyword. For more information, see ext_soft_font_dir on page 69.

Note For help with TechFont, contact Sefas Customer Support.

Note If an entry for the desired font family (for example, Arial) does not exist, you will need to createone.


C r e a t i n g a n e w p r o j e c tSo f t f o n t s

HP

-PC

L n

orm

aliz

atio

n


After setting up the application directory structure and font environment, you are ready to createthe project using Remake’s user interface. Do the following:


2. Select File > Create a Project…The Create a New Open Print Remake Project window appears.


4. In the Group Entry-Point dialog box, select C:\normalization. This is the group entry-point you created using Windows Explorer. Click OK.

5. From the Group drop-down list, select samples. This is the group directory that you created earlier.

6. In the Application field, type pcl_sample. This entry corresponds to the sample application directory you copied into the Group directory.


8. Click OK.

Note A message displays notifying you that the application already exists. Since we are creating thisproject from the sample application, this is expected.


P r e p a r i n g t h e i n p u t f i l eSpoo l i n g t h e f i l e t o b e no rma l i z ed



Sefas recommends that you use a standard directory structure for the storage and selection of thePCL file you want to normalize. The \spool subdirectory inside the sample application directoryis intended for this purpose.


C:\normalization\samples\pcl_sample\spool

For example:

C:\normalization\samples\pcl_sample\pcl_sample.pcl


To configure the application, you use the Remake user interface to:

• Verify directory path and client/server environment settings, and update them if needed.

• Set the location of the PCL input file.• Set the location of the configuration file.



1. Select File > Configuration… .

Note A sample PCL file (with inline resources), named pcl_sample.pcl, is provided with the sampleapplication in the \pcl_sample directory. You can substitute the sample file with any PCL fileyou would like to normalize.



HP

-PC

L n

orm

aliz

atio

n


3. Click OK.


The TechPCL normalization engine configuration file, techpcl.tab, contains sections that mustbe configured depending on the type of processing that needs to be performed. For moreinformation about techpcl.tab, see Configuration file and keywords on page 57.

Before you can normalize the PCL file, you must set the following:

• The location of PCL file to be normalized• The location of the configuration file used to set processing options

To do this:


Note If Client/Server operating mode is selected, you can select the Transfer Data check box toautomatically transfer data generated by the server to the client or by the client to the server.




3. Next to the Input file field, click […] to browse your computer for the PCL file to be normalized:

4. Navigate to the \spool directory, select the PCL file, and click Open. After you select the file, the path apepars in the Input file field:

5. Under File type, select PCL.

Note If you do not see a PCL file in the \spool directory, see Setting up the sample application onpage 59 for help with copying the sample file to this directory.



HP

-PC

L n

orm

aliz

atio

n

6. Under Options, beside the Fonts Substitution Table field, click […] to browse your computer for the configuration file:

7. Select the file and click Open. The path to the file appears in the Fonts Substitution Table field:



Processing options for the normalization engine are set using a configuration file, techpcl.tab.

Sections

Depending on the needs of your organization, the configuration file is made up of either one ortwo sections:

• The [PROCESS] section

This section sets the normalization engine’s processing options. It is required and common to all streams.

For a description of the keywords that can be used in this section, see Keywords and

descriptions on page 68).

• The [FONTS] section

Note Following our sample application, the sample configuration file is located in:

C:\normalization\samples\pcl_sample\common\config\pcl\techpcl.tab


C o n f i g u r i n g t h e n o r m a l i z a t i o n e n g i n eOve r v i ew o f t h e c on f i gu ra t i o n f i l e

The [FONTS] section is used for advanced font substitution options that can be carried out using manual mode normalization. For more information on this option, contact Sefas Customer Support.

Keywords

Each section of the configuration file contains a set of keywords. Each keyword corresponds to aprocess to be carried out on the PCL stream. Keywords are systematically followed by a value. Akeyword and its value are separated by the = (equal) character.

For example:

STDVECT=Y

DOWNLOADFONT=N

The keywords you use in your configuration file will depend on the PCL stream to be normalizedand the needs and preferences of your organization. For a simple normalization, there may be asingle section of the file with just a few keywords. For a complex normalization, there might bemany keywords. For the full list of keywords that can be used, see Keywords and descriptions

on page 68.

Comments

A semicolon (;) or a hashmark (#) at the beginning of a line indicates that the line is a comment.Comments are ignored by the engine.

Examples:

; Creation of the font list

# Creation of the font list

Examples

techpcl.tab example 1 - Embedded fonts

The following is an example of the techpcl.tab configuration file used to process a streamwhere the fonts are stored internally. For a description of each keyword and possible values, seeKeywords and descriptions on page 68.

[PROCESS]

DOWNLOADFONT=N

STDVECT=Y

IMAGES=$LOGO

OPACITY=N

RESLIST=N

INCLUDEPIC=Y

BLANKSHEET=N

REFFONTPATH=C:\

font_embedding=1

techpcl.tab example 2 - External soft fonts

This following is an example of a techpcl.tab configuration file used to process a stream thatreferences soft fonts externally. The soft font files were copied to the directoryC:\myfonts\pclsoftfonts. For a description of each keyword and possible values, seeKeywords and descriptions on page 68.

[PROCESS]

STDVECT=Y

DOWNLOADFONT=N

IMAGES=$LOGO

Note Each PCL application requires a specific configuration file. You can create multiple configurationfiles to accommodate various normalization scenarios by making duplicates of techpcl.tab andediting the files accordingly.


C o n f i g u r i n g t h e n o r m a l i z a t i o n e n g i n eEd i t i n g t h e c on f i gu ra t i o n f i l e

HP

-PC

L n

orm

aliz

atio

n

OPACITY=N

RESLIST=N

INCLUDEPIC=Y

BLANKSHEET=N

REFFONTPATH=C:\

font_embedding=1

image_reuse=1

external_soft_font_dir=C:\myfonts\pclsoftfonts


Do the following to make changes to techpcl.tab:

1. Launch Remake, and select File > Configuration...

2. Click the Data file tab.

3. Click the Edit button.

The techpcl.tab file opens in a text editor:



Note This step assumes you have already selected the configuration file using the Remake userinterface. For more information, see Selecting the input file and configuration file onpage 63.




The following is a list of keywords for the [PROCESS] section of the configuration file. Forinformation about advanced font substitution options using a [FONTS] section, contact SefasCustomer Support.

Keyword Description

BLANKSHEET Maintains the recto/verso sequence during the normalization of a Duplex application, by keeping the blank pages. Valid values are:

• Y - The blank sheets are left in the VPF, maintaining the sequence of recto and verso pages.

• N (default) - The blank pages are deleted from the VPF.

copy_pages Determines whether to process the PCL command that designates the number of printedcopies for each page of a document. This command can be set anywhere within a PCL document and affects the current page as well as subsequent pages.

The command is <ESC>&I#X, where # is the number of copies. The number of copies can be from 1 to a maximum of 32767.

To have the number of copies command processed during normalization, you must add copy_pages=1 to the configuration file. The VPF file will contain the corresponding number of copies of the targeted pages the same way they would appear on a printer.

Valid values are:

• 0 (default) - The number of copies command is ignored.

• 1 - The number of copies command is processed.

DEFCODEPAGE Specifies a code page to be used if there is none defined in the PCL stream.

Valid values are 0N, 18N, 8U, 9U, 10U, 12U, 2N, 19M, 6J, 579L and NO. NO means that no codepage for character transcoding is used and tthe same value will be kept for output.

The default value is 8U.

default_font_id When the PCL stream starts without defining any font, use this option in conjunction with default_font_size, default_font_style, and default_font_spacing, to specify the font ID of a default font, where XXXX is a standard resident font ID.

For example:

default_font_id=4099

default_font_size When the PCL stream starts without defining any font, use this option to specify the font size of a default font. For example:

default_font_size=12

default_font_style When the PCL stream starts without defining any font, use this option to specify the font size of a default font. Valid values are:

• n - normal (default value)

• g - bold

• i - italic

• r - bold italic

default_font_spacing When the PCL stream starts without defining any font, use this option to specify the spacing style of a default font. Valid values are:

• 0 (default) - The font uses a fixed pitch width.

• 1 - The font uses a proportional width.

DOWNLOADFONT Specifies whether to extract the fonts included in the stream. Valid values are:

• Y (default) - The fonts are extracted from the stream and saved in the macro directory of the application.

• N - The fonts are not extracted from the stream.



HP

-PC

L n

orm

aliz

atio

n

ext_soft_font_dir Specifies the absolute path of a directory containing the soft fonts to be used for normalization. For example:

ext_soft_font_dir=C:\pclsoftfonts


image_reuse Specifies whether or not repeated images are consolidated and reused to reduce the size of the VPF file. Valid values are:

• 0 (default) - The images are not consolidated and reused.

• 1 - The images are consolidated and reused.

Use image_reuse only if the PCL file contains the same compressed image that is repeatedly inserted inline, such as a compressed background image.

A compressed image in the VPF file might be larger than the same compressed image in the PCL file. If the image is used repeatedly, this can result in a very large VPF file, even if the PCL file is a reasonable size. Remake also might need to decompress the image and then recompress it in order to create an image that can be used in the VPF file. This results in unnecessary engine overhead if the same image is repeatedly decompressed and recompressed. The size of the protcolized file produced via rendering is reduced as well.

Note: Use of this keyword can slow down normalization speed, so it should only be used when needed.

INCLUDEPIC Specifies whether to include image files in the VPF file. Valid values are:

• Y (default) - The VPF file contains the image files. The image files are also saved in PCX format, in the macro directory of the application.

This option must not be used with the -m parameter of the TechPCL engine if it specifies a macro directory that is not the application directory.

• N - The VPF file does not contain the image files. The image files are saved in PCX format in the macro directory of the application.

LAYOUTMODE Specifies the path and name of an imposition file used to deimpose the PCL input stream. For example, if you have a two-up input PCL file, you can change it to one-up mode in the VPF output, by specifying the location of the imposition file with the one-up setting.

This option is disabled unless the path and filename of the imposition file are specified.

For example:

LAYOUTMODE=C:\imposition\file.mef

MACROPROCESSING Defines the macro processing mode. Valid values are:

• Y (default) - The macros are extracted, saved in the macro directory of the application, and processed. The result of the macro processing is placed in the VPF file.

• N - The macros are neither extracted nor their result placed in the VPF stream.

X_OFFSET Specifies the positioning offset of the job in xabsciss coordinates. The origin is the top left corner of the page. Units allowed are pica, inch, centimeter (cm), millimeter (mm), dot, and logical unit (ul).

Note: A logical unit (ul) is a Sefas-specific unit of measurement, where 1 UL = 1/144000 inch.

Default value: 0

When the value is expressed in dots, the result depends on the job resolution.

Keyword Description



Y_OFFSET Specifies the positioning offset of the job in ordinate coordinates. The origin is the top left corner of the page. Units allowed are pica, inch, centimeter (cm), millimeter (mm), dot and logical unit (ul).

Note: A logical unit (ul) is a Sefas-specific unit of measurement, where 1 UL = 1/144000 inch.

Default value: 0

When the value is expressed in dots, the result depends on the job resolution.

REFFONTPATH This keyword is required by the normalization engine and must contain a directory path used to keep fonts extracted from PCL streams. Each time a new font is found, it is compared with the fonts in this directory. If the same font is found, that name is used. Therefore, TechFont is not required to process the fonts again.

Note: This keyword is useful for manual mode normalization. It is also required in dynamic mode; however, no fonts are written to the directory.

RESLIST Generates a list of resources associated with the stream or starts the normalization of the stream. Valid values are:

• Y - Normalization is not executed when the TechPCL engine is launched.

Instead, the list of resources integrated or referenced in the stream is generated. This list is saved in the macro directory of the application, in the file Resource.tab.For included fonts: A shell document of the [FONTS] section of the font substitution table is generated, by using the font characteristics included in the stream. The name of this file is composed of the name of the table followed by the extension.emb.For example: If the name of the substitution table file is techpcl_1.tab, then the name of shell document file is techpcl_1.tab.emb.This file is saved in the directory containing the font substitution table (by default: $opInstallDir\common\config).

• N (default) - Normalization is executed when the TechPCL engine is launched.

The list of resources is not generated.

STDVECT Defines the normalization mode of vector-type graphic elements. Valid values are:

• Y (default) - Vector graphic elements and images are processed in standard fashion; that is, they are embedded in the VPF file as separate elements. Vector graphic elements are represented in the VPF file as lines, polygons, arcs, etc.

• N - All of the vector elements are merged into one bitmap which is saved in PCX format. Use of this option is not recommended as representation is less accurate and the elements are not available individually for enhancement.

VERBOSE Indicates whether messages and warnings encountered during normalization are displayed. Valid values are:

• Y (default) - Messages are displayed.

• N - Messages are not displayed.

Keyword Description



HP

-PC

L n

orm

aliz

atio

n




1. Launch Remake and select File > Configuration.


3. Enter any command line parameters in the Normalize field. For a list of parameters, see below.

4. Click OK.


The command line parameters for the TechPCL normalization engine are presented in the tablebelow.



-E opInstallDir= Sets the environment variable to indicate the access path to the bin and common directories. For example:


-E opWD= Sets the environment variable to indicate the group entry point.



-E opFam=samples


For example:

-E opAppli=pcl_sample

-f Specifies the access path to the configuration file. For example:

-f C:\normalization\samples\pcl_sample\config\techpcl.tab

-h Specifies the access path to the hp.fnt font table used for external font processing. For example:

-f C:\oprint\common\chasse\hp.fnt

-i Specifies the access path to the PCL input stream. For example:

-i C:\normalization\samples\pcl_sample\spool\present.hp



Example command line

Parameters can also be executed using the command line outside of the Windows user interface.The following command line parameters are executed automatically using the Windows userinterface during normalization:

C:\oprint\bin\go.exe techpcl

-i C:\normalization\samples\pcl_sample\spool\present.hp

-o C:\normalization\samples\pcl_sample\spool\present.vpf

-f C:\normalization\samples\pcl_sample\common\config\techpcl.tab

-E opAppli=pcl_sample

-E am=samples



-E opMessLang=en

-l Specifies the access path to the file that records the messages generated .

For example:

-l C:\normalization\norm_pcl\trace\norm_pcl.log

To use this option, the TechPCL engine must be launched from the executable file techpcl.exe. When the engine is launched using the Windows GUI or via go.exe / go_wait.exe in a batch file, the messages are not saved in the file. In the two cases, the messages are also saved in a *.BCK file (op_temp directory).

-m Specifies the access path to the directory in which the fonts and images extracted from the stream are saved.

By default, the images are saved in the macro directory of the application. For example:

-m C:\normalization\samples\pcl_sample\macro

-o Specifies the access path to the output VPF file. For example:

-o C:\normalization\samples\pcl_sample\spool\pcl_sample.vpf

-p Defines the four characters that make up the prefix of the name of the PCX images generated. For example:

-p IMGE

By default, the prefix is composed of the first four letters of the name of the input file. The suffix is a four-digit number, incremented as from 0000.

-ps / -pe Specifies the page start and/or end. For example:

-ps 5 -pe 1562

-r Specifies the Trace window message reporting will be displayed in extended verbose mode.



L o c a t i n g t h e V P F o u t p u tNo rma l i z i n g t h e PCL f i l e

HP

-PC

L n

orm

aliz

atio

n

Normalizing the PCL file


1. Launch Remake.

2. Click View > Trace to display the Trace window:

The Trace window displays the status and other messages as the normalization is executed.

3. Click the up arrow icon to display the EXECUTE toolbar.

4. Click Normalize:

5. Click Run:


Unless specified otherwise (via keyword or parameter), the VPF file is output to the \spooldirectory of the application. Following our sample application, the VPF file is:

C:\training\remake\normalization\pcl_sample\spool\pcl_sample.vpf

The file contains all of the fonts and resources, regardless of the whether the fonts were externalto the stream or inline.


Guide.


L o c a t i n g t h e V P F o u t p u tNo rma l i z i n g t h e PCL f i l e


O v e r v i e wAbou t t h e Te chLCDS no rma l i z a t i o n e ng i ne

LC

DS/M

etacod

e n

orm

aliz

atio

n

C h a p t e r 4 : L C D S /M e t a c o d e n o r m a l i z a t i o n

Overview

Open Print Remake supports normalization of Xerox Line Conditioned Data Stream (LCDS) andMetacode files.

These files consist of data and the following types of Xerox resources:

• Fonts• Page Form (FRM) file(s)• Images and logos• Job Source Library (JSL) file

The actual mix of resources in a LCDS/Metacode stream depends on the contents of the file. ForLCDS files, resources are external to the stream. Therefore, all resources must be identified andlocated prior to normalization. The structure of a stream, such as data source, record structure,and data encoding, is described in the JSL file. When compiled, the JSL is called the JobDescriptor Library (JDL). The JDL is used by the printer controller to read the stream.

The goal of LCDS/Metacode normalization is to convert an LCDS/Metacode file to a Virtual PageFormat (VPF) file. Regardless of whether the fonts are external or embedded, the normalized VPFoutput file contains all of the resources inline.

About the TechLCDS normalization engine

The TechLCDS normalization engine converts an LCDS or Metacode data stream into a VPF file.Processing options for the engine are set using a configuration file. Additional parameters are setat run time. The configuration file is edited using a standard text editor. Runtime parameters areset and the normalization is executed via Remake’s user interface.


The default configuration file used by the engine is techlcds.cfg. The file contains keywordsthat tell the engine how to process the incoming AFP data stream. For example, thefont_embedding keyword must be present in the configuration file, and set to 1, to enabledynamic font processing.


on page 83.


The engine supports parameters that can be processed with the command line at run time. Theseparameters are used to set environment variables and other options not set using theconfiguration file. For example, the -i parameter is used to set the access path to the LCDS inputstream.


Important Sefas recommends that you conduct a careful analysis of the JSL file to understand the structureof the stream prior to normalization.



Before you begin


Sefas recommends that you have Hexadecimal text editor installed on the computer where youperform the normalization.

It is also recommended that you have a scan or hard copy of the print stream for analysispurposes.

Gathering resources

Before launching an LCDS or Metacode normalization, you should gather and have available thefollowing resources:

• LCDS or Metacode file• Fonts used in the file• FRM file(s) and images• JSL and section of JSL used to print the file


While virtually any directory structure can be used to perform the normalization, it is helpful touse a standard directory structure and standard naming conventions. Sefas recommends that youuse a structure based on the $opWD (working), $opFam (group), and $opAppli (application)Open Print environment variables.

There are a number of ways you can establish the environment. For example, you can:


• Create the directory structure from scratch.• Use the Create New Project capability of Remake’s user interface to have software

create the directory structure automatically.



Operating Manual.



LC

DS/M

etacod

e n

orm

aliz

atio

n







C:\normalization






1. Locate the directory containing your sample application. The directory is either located in the Remake installation folder or was provided to you by a Sefas representative.

2. Copy the entire directory labeled \lcds_sample to the normalization directory you created previously:

C:\normalization\samples\lcds_sample




C r e a t i n g a n e w p ro j e c tS e t t i n g up t h e s amp l e app l i c a t i o n


After setting up the application directory structure, you are ready to create the project usingRemake’s user interface. Do the following:


2. Select File > Create a Project.

The Create a New Open Print Remake Project window appears.


4. In the Group Entry-Point dialog box, select C:\normalization. This is the group entry-point you created using Windows Explorer. Click OK.

5. From the Group drop-down list, select samples.This is the group directory that you created earlier.

6. In the Application field, type lcds_sample. This entry corresponds to the sample application directory you copied into the group directory.


8. Click OK.

Note A message appears notifying you that the application already exists. Since this project is beingcreated from the sample application, this is expected.


P r e p a r i n g t h e i n p u t f i l eSpoo l i n g t h e f i l e t o b e no rma l i z e d

LC

DS/M

etacod

e n

orm

aliz

atio

n



Sefas recommends that you use a standard directory for the storage and selection of the LCDS/Metacode file you want to normalize. The \spool subdirectory inside the sample applicationdirectory is intended for this purpose.


C:\normalization\samples\lcds_sample\spool

For example:

C:\normalization\samples\lcds_sample\spool\lcds_sample.lcds


To configure the application, you use the Remake user interface to:

• Verify directory path settings and client/server environment and update them if needed.• Set the location of the input file.• Set the location of the configuration file.



1. Select File > Configuration.

Note A sample LCDS and Metacode file are provided with the sample application in the..\lcds_sample\spool directory. You can substitute the sample file with any LCDS file youwould like to normalize.




3. Click OK.


The normalization engine configuration file, techlcds.cfg, contains a single section, labeled[TECHLCDS] that must be configured depending on the type of processing that needs to beperformed. For more information about techlcds.cfg, see Configuration file and keywords

on page 75.

Before you can normalize the file, you must set the:

• The location of the file to be normalized• The location of the configuration file used to set processing options, including the JSL

file name• The section used in the JSL file to print the file

To do this:


Note If the Client/Server option is selected, you can select the Transfer Data check box toautomatically transfer data generated by the server to the client or by the client to the server.



LC

DS/M

etacod

e n

orm

aliz

atio

n


3. Next to the Input file field, click the […] button to browse your computer for the file to be normalized:

4. Navigate to the \spool directory, select the file, and click Open. After you select the file, its path is displayed in the Input file field:

5. Under File type, select LCDS or Metacode.

Note If you do not see a file in the \spool directory, see Setting up the sample application onpage 77 for help with copying the sample file to this directory.



6. Click […] beside the Cfg File field to browse your computer for the configuration file.

7. Select the file, and click Open. The path to the file is displayed in the Cfg File field:

8. In the Job Name field, enter the name of the section in the JSL file used to print the file. For example, JC0021:

9. Set the following additional options as required for your application:

• Select the Generate a resource list file check box if you want Remake to generate a list of resources contained in the stream, instead of a VPF file. After normalization is executed, the list is available at the location you specify in the text field beside the check box. For example: C:\normalization\samples\lcds_sample\spool\norm_1.res

• Select a Verbose mode option from the drop-down list to control the level of detail that Remake displays in the Trace window and log file. The options are:• 0 = mute (default value)• 1 = verbose• 2 = very verbose

• Enter a value in the NbPages field to specify the number of pages to normalize. For example, entering 367 in this field normalizes the first 367 pages of the file.

• Click [...] next to the Log file field to specify the location and file name of the log file used for recording informational and error messages. For example: C:\normalization\samples\lcds_sample\spool\logfile.txt


Note Following our sample application, this is located here:

C:\normalization\samples\lcds_sample\common\config\techlcds.cfg

Note No VPF file is generated if this option used.



LC

DS/M

etacod

e n

orm

aliz

atio

n



Processing options for the TechLCDS normalization engine are set using a configuration file,techlcds.cfg.

Sections

The configuration file contains a single section, labeled as [TECHLCDS].

Keywords

The [TECHLCDS] section of the configuration file contains a set of keywords. Each keywordcorresponds to a process to be carried out on the LCDS or Metacode stream. Keywords aresystematically followed by a value. Possible values include access paths, names, and otherattributes. A keyword and its value are separated by the = (equal) character. For example:

[TECHLCDS]

key_word1=value

key_word2=value

For the full list of keywords that can be used, see Keywords and descriptions on page 85.

Example - techlcds.cfg

The following is an example of the techlcds.cfg configuration file. For a description of eachkeyword and possible values, see Keywords and descriptions on page 85.

[TECHLCDS]

res_dir_path=C:\normalization\samples\lcds_sample\spool\Resources\JSL

xerox_forms_dir=C:\normalization\samples\lcds_sample\spool\Resources\FRM

xerox_font_dir=C:\normalization\samples\lcds_sample\common\fontxrx

img_dir_path=C:\normalization\samples\lcds_sample\spool\Resources\Images

job_jsl_name=Checks.jsl

carriage_control=ANSI

mixed_mode=1

record_delimiter=

record_len_bin=1

record_len_size=2

count_type=1

fixed_record_length=0

stock_conversion=2

itext_process=1

side_process=2

font_embedding=1

medium=LETTER

[END]

Note The keywords you use in your configuration file depend on the type of stream to be normalizedand the needs and preferences of your organization. Examples:

• If the input stream has a string header, the engine needs to know the length (in bytes) of the header in order to skip over it when reading the records. For more information, see the keywords hdr_block_size, hdr_file_size, and hdr_record_size on page 85.

• For fixed-length record formats, the length must be specified with the keywords in the section of this document entitled, Fixed-record-length data streams on page 86.

• For variable-length record formats, the length must be specified using the relevant keywords in the section of this document entitled, Variable-length data streams on page 87.


C o n f i g u r i n g t h e n o r m a l i z a t i o n e n g i n eEd i t i n g t h e c on f i g u ra t i o n f i l e


Do the following to make changes to techlcds.cfg:

1. Launch Remake, and select File > Configuration.

2. Click the Data file button.

3. Next to the Cfg file field, click Edit:

The techlcds.cfg file opens in a text editor:



Note This step assumes you have already selected the configuration file using Remake. For moreinformation, see Selecting the input file and configuration file on page 80.



LC

DS/M

etacod

e n

orm

aliz

atio

n


General keywords (all streams)

The following is a list of general keywords that can be used to process all streams regardless ofdata format. For keywords specific to fixed-length data streams, see page 86. For variable-lengthdata stream keywords, see page 87. For data streams with delimited records, see page 87.

Keyword Description

auto_form_conversion Specifies whether forms are automatically converted. Valid values are:

• 0 -The forms are converted.

• 1 - The forms are not converted.

carriage_control Indicates the type of Print Carriage Control (PCC) used; this replaces the value indicated in the JSL. Valid values are:

carriage_control=IBM3211

carriage_control=ANSI


hdr_block_size If the input stream has a string header, specifies the length (in bytes) of the header blocks in order to skip over the bytes when reading blocks. The default value is 0.

Example:

hdr_block_size=53

hdr_file_size If the input stream has a string header, specifies the length (in bytes) of the header file size in order to skip over the bytes when reading the beginning of the input file. The default value is 0.

Example:

hdr_block_size=53

hdr_record_size If the input stream has a string header, specifies the length (in bytes) of the header record size in order to skip over the bytes when reading records. The default value is 0.

Example:

hdr_block_size=53

img_dir_path Specifies the access path to Xerox IMG images.

Depending on the image type (MONOCHROME or BI-COLOR), the engine inserts a PCX or a JPG image. For example:

C:\normalization\samples\lcds_sample\spool\Resources\Images

itext_process Specifies the management mode of messages intended for the operator (itext, otext). Valid values are:

• 0 (default) - The itext commands are ignored.

• 1 - The itext commands are transmitted as a specific commands ($$XRX)

job_jsl_name Required. Specifies the name of JSL file containing the JOB section used at start-up. For example:

job_jsl_name=xrxsta.jsl

medium Specifies the paper medium.

Note: This option is used only when the PAPERSIZE parameter is not specified in the JSL file. Valid values are:

• A4

• LETTER

• USLETTER



Fixed-record-length data streams

If the input stream is a collection of blocks or records of fixed length, the engine needs to knowthis fixed length.

metrics_dir_path Specifies the access path to the metrics directory, if required.

By default this is: opInstallDir\common\chasse

otext_process Specifies the management mode of messages intended for the operator (otext). Valid values are:

• 0 (default) - The otext commands are ignored.

• 1 - The commands otext are transmitted as specific commands ($$XRX)

res_dir_path Specifies the access path to the directory containing the JSL file used by this application. This is location of the *.JSL and *.CME resources. By default, these files should be saved in the spool directory. For example:

res_dir_path=C:\normalization\samples\lcds_sample\spool

side_process Specifies the processing mode of SIDE command. Valid values are:

• 0 (default) - This command is ignored.

• 1 - This command is processed normally and the correct side is set.

• 2 - This command is replaced with $$XRX SIDE in the output file.

xerox_font_dir Specifies the access path to Xerox fonts used in the original stream. These fonts are required to carry out the normalization.

The default value is: $opInstallDir\common\fontxrx

xerox_forms_dir Specifies the access path to Xerox forms used in the original stream.

The default value is the value attributed to keyword res_dir_path. For more information, see res_dir_path on page 86

xerox_img_dir See img_dir_path on page 85.

xerox_lgo_dir Specifies the access path to Xerox logos used in the original stream. The default value is $opInstalldir/common/fontxrx.

Keyword Description

Keyword Description

fixed_record_length Specifies the length of records, if they are fixed. The value 0 indicates that the records are of variable length. For example:

fixed_record_length=18

padding_char Specifies the number of characters to use for padding if the data is not filling the block or the record. The default value is 0 (no padding). For example:

padding_char=6



LC

DS/M

etacod

e n

orm

aliz

atio

n

Variable-length data streams

The table below describes the keywords to use when the input stream is either a collection ofrecords of a variable length or a collection of blocked records of variable length..

Delimited-record data streams

For a stream with records separated by a character, be sure to include the keyword describedbelow.

Note A block can contain one or may records.

Keyword Description

block_len_size Specifies the number of bytes used to code the block length and the coding used.

The value is an integer from 2 - 4; the default is 0. For example:

block_len_size=2

count_coding Specifies type of field coding that indicates the length of the block and the record. This is a required keyword. Valid values are:

• 0 (default) - No inversion in encoding order (Big Endian).

• 1 - Inversion by the middle.

• 2 - Total inversion (Little Endian).

• 3 -Inversion in pairs.

count_type Specifies an integer value resulting from the value of each bit or the three low-level bits b2b1b0.

• b0=0 - The bytes coding the length of a record are included in this length.

• b0=1 - The bytes coding the length of a record are not included in the length.

• b1=0 - The bytes coding the record length are not repeated at the end of the record

• b1=1 - The bytes coding the record length are repeated at the end of the record.

• b2=0 - The bytes coding the block length are not repeated at the end of the block.

• b2=1 - The bytes coding the block length are repeated at the end of the block.

record_len_size Specifies the record length for a record of variable length. This keyword must be provided when records have a variable length. For example:

record_len_size=2

stock_conversion Processing mode of FEED command. This keyword is optional. Valid values are:

• 0 (default) - This command is ignored.

• 1 - This command is replaced with $IBIN FEEDNAME in the output file.

• 2 - This command is replaced with $XRX FEED=FEEDNAME in the output file.

Keyword Description

record_delimiter Specifies the record delimiter for records (of any length) separated by a character. If the value is in octal code, it must be preceded by \o, if it is in hexadecimal code, it must be preceded by \X.

Syntax:

octal: \ovalue

hexadecimal: \Xvalue

For example:

record_delimiter=\X0A


N o r m a l i z i n g t h e s t r e a mVe r i f y i n g r equ i r ed i n pu t


Verifying required input

The following elements must be available before launching normalization.

• LCDS or Metacode file• JSL and the section of the JSL used to print the file• Fonts used in the file• LCDS resources: FRM and images

The \spool directory of the application should contain the LCDS stream. For more information,see Spooling the file to be normalized on page 79.

The configuration file should be in the directory specified in the Cfg File field of the Remake userinterface.

Any fonts, forms, and images, as well as the JSL file should be present at the dedicated pathlocations specified in the configuration file (see below).

Resource paths

Paths dedicated to various types of resources are specified using the following keywords:

• res_dir_path (page 86)• xerox_forms_dir (page 86)• xerox_font_dir (page 86)• img_dir_path (page 85)• job_jsl_name (page 85)




Note Overlays and page segments are necessary only if the target format is AFP.



LC

DS/M

etacod

e n

orm

aliz

atio

n


3. Enter any command line required parameters in the Normalize field. For a list of parameters, see below.

4. Click OK.


The command line parameters for the LCDS/Metacode normalization engine are presented in thetable below.

Note For an LCDS or Metacode normalization, most parameters are entered automatically using fieldsin the Windows user interface. Therefore, this field may be blank. The field is available for userswho prefer to type the commands manually.


-C Specifies the access path to the configuration file. For example:

-C C:\normalization\samples\lcds_sample\spool\lcds_sample.cfg


-E opInstallDir= Sets the environment variable to indicate the access path to the bin and common directories. For example:


-E opWD= Sets the environment variable to indicate the group entry point. For example:



-E opFam=samples


For example:

-E opAppli=lcds_sample

-i Specifies the access path to the directory and file containing the LCDS stream.

For example:

-i C:\normalization\samples\lcds_sample\spool\lcds_sample.lcds



Command line example

Parameters can also be executed using the command line outside of the Remake user interface.The following example shows how a command line processes an LCDS or Metacode stream.

set opInstallDir=C:\oprint

set opWD=C:\normalization

set opFam=samples

set opAppli=lcds_sample

set path=%opWD%\%opFam%\%opAppli%\

set CFG=techlcds.cfg

set JDE=PRINT

echo LCDS Stream normalization

C:\oprint\bin\go.exe lcds -E opWD=%opWD% -E opFam=%opFam% -E opAppli=%opAppli%

-E opInstallDir=%opInstallDir% -i %opWD%\%opFam%\%opAppli%\spool\lcds_sample.lcds

-o %opWD%\%opFam%\%opAppli%\spool\lcds_sample.vpf -S %JDE%

-C %opWD%\%opFam%\%opAppli%\spool\%CFG%

-l %opWD%\%opFam%\%opAppli%\scripts\lcds_normalize.log -E opMessLang=us

pause

-l Specifies the access path to the directory containing the trace file (file for recording messages). For example:

-l C:\normalization\samples\lcds_sample\spool\lcds_sample.log

-o Specifies the access path to the VPF file created at the end of the normalization process. It is located in the current directory if a full path is not specified. For example:

-o C:\normalization\samples\lcds_sample\spool\lcds_sample.vpf

-p Specifies the page number. For example:

-p 234

-R Launches the normalization engine in analysis mode and generates the list of resources used by the stream. The name of the list file is shown by the option R. The LCDS stream is not normalized in this mode. For example:

-R C:\normalization\samples\lcds_sample\spool\lcds_resources.res

-S Specifies the job name in the JDE section of the start-up JSL. For example:

-S JC0021

-v Specifies the option used for verbose mode. Valid values are:

• 0 - mute

• 1 - verbose

• 2 - very verbose



L o c a t i n g t h e V P F o u t p u tExe cu t i ng t h e n o rma l i z a t i o n

LC

DS/M

etacod

e n

orm

aliz

atio

n

Executing the normalization


1. Launch Remake.

2. Select View > Trace to display the Trace window.

3. Click the up arrow icon to display the EXECUTE toolbar:

4. Click Normalize:

5. Click Run:


Unless specified otherwise (via keyword or parameter), the VPF file is output to the \spooldirectory of the application. Following our sample application, the VPF file is:

C:\normalization\samples\lcds_sample\spool\lcds_sample.vpf

The file contains all of the original fonts and resources (either embedded directly in the file or asVPF objects), regardless of the whether the resources were external to the stream or inline.


Guide.


L o c a t i n g t h e V P F o u t p u tExe cu t i n g t h e no rma l i z a t i o n


O v e r v i e wAbou t t h e Te chPDF no rma l i z a t i o n e ng i n e

PD

F n

orm

aliz

atio

n

C h a p t e r 5 : P D F n o r m a l i z a t i o n

Overview

Open Print Remake supports normalization of Adobe Portable Document Format (PDF) files.

PDF files are made up text and the following types of resources:

• Fonts• Images• 2-D vector graphics

For PDF files, resources may be inline or external to the stream. Inline fonts are processedautomatically during normalization. External fonts must be stored in a common directory. Theactual mix of resources in a PDF stream depends on the contents of the file

PDF normalization converts a PDF data stream into a Virtual Page Format (VPF) file. Regardless ofwhether the resources are external or embedded, the normalized VPF output file contains all ofthe resources inline.

PDF normalization is not available in the Remake user interface. You need to use the following toperform PDF normalization via a batch script.

• The input .pdf file• A configuration file, techpdf.cfg, which is used to how the normalization is run• A batch file to set the environment variables and run the command lines necessary to

perform normalization. Sefas supplies a batch file sample; you can modify this to meet your organization’s needs.

The PDF normalization process includes:

• Determining what fonts are in the .pdf input file• Setting configuration keywords and values• Executing the command line using one or more scripts

About the TechPDF normalization engine

TheTechPDF normalization engine converts a PDF data stream into a VPF file. Processing optionsfor the engine are set using a configuration file. Additional parameters are set at run time. Theconfiguration file is edited using a standard text editor. Runtime parameters are set and thenormalization is executed with a batch file.


The default configuration file used by the engine is techpdf.cfg. The file contains keywordsthat tell the engine how to process the incoming AFP data stream.


on page 97.




The engine supports parameters that can be processed using the command line at run time. Theseparameters are used to set environment variables and other options not set using theconfiguration file.

For example, the -i parameter sets the access path to the PDF input stream.

For more information on available parameters, see Entering command line parameters on page99.

Before you begin


Sefas recommends that you have the following third-party tools installed on the computer whereyou perform the normalization.

• Adobe Reader• Hexadecimal text editor

It is also recommended that you have both electronic and print copies of the stream for analysispurposes.

Gathering the required resources

Before launching a PDF normalization, you should compile a list of the resources contained in thestream.

Sefas recommends that you:

• Gather and have available a selection of the original, printed and electronic PDF documents as a reference.

• Review and assess the nature of the resources to be normalized.• Determine the location and names of any fonts that are not inline.


While virtually any directory structure can be used to perform the normalization, it is helpful touse a standard directory structure and standard naming conventions. Sefas recommends that youuse a structure based on the $opWD (working), $opFam (group), and $opAppli (application) OpenPrint environment variables.

You have two basic options:


• Create the directory structure from scratch.


Operating Manual.


P r e p a r i n g t h e f o n t e n v i r o n m e n tC rea t i n g p ro j e c t d i r e c t o r i e s

PD

F n

orm

aliz

atio

n

The remainder of this section explains how to set up the directory structure from scratch.


Sefas recommends you use a directory structure based on the following environment variables:

opWD - The working directory that acts as the group entry point

opFAM - The group directory

opAppli - The application directory that contains all the subdirectories and files needed to run normalization

A sample directory structure follows:

In the sample above:

normalization is the opWD directory.

samples is the opFAM directory.

pdf_sample is the opAppli directory.

In addition, the opInstallDir variable is used to define the installation directory path (oftenC:\oprint). This path is used in the command line to execute the engine.

Preparing the font environment

If the fonts are embedded in the PDF file, Remake processes them automatically. If the streamcontains printer-resident fonts, they require special processing.

Fonts needed for PDF normalization are stored in .../<install directory>/oprint/common/fonts. All fonts that are not embedded in your .pdf file must be stored in this directoryfor normalization to be successful. To see what fonts are in your file, do the following:

1. Use Adobe Reader to open the .pdf file you want to normalize.


P r e p a r i n g t h e f o n t e n v i r o n m e n tC rea t i n g p r o j e c t d i r e c t o r i e s

2. Select File > Properties, and click on the Font tab. The following displays:

This list contains all the fonts available in the file. Sefas recommends the use of subset fonts inthe PDF input to optimize the amount of processed data and speed. TechPDF does not processfonts to output subsets.

A subset of fonts consists of a minimal group of characters from a specific character set. Forexample, if the document only uses numeric characters 1 to 9 in Arial, the subset will contain onlythese characters. This optimizes the size of the .pdf.

PDF normalization accepts the following fonts as input:

• FBitmap-only Type 3 fonts• Type 1 fonts (.pfb extension for external fonts)• TrueType fonts (.ttf extension for external fonts)

Fonts are dynamically inserted in the VPF output when you execute the normalization.

Font substitution

If you do not have access to an embedded font that exists in the .pdf file, you can substituteembedded fonts as necessary. When substituting fonts, note the following:

• If a PDF that contains a font subset, only those characters used have metrics. If those metrics are not standard metrics, gaps may exist in the justification of new and old characters.

• In the PDF file, a distinctive encoding is used and the same font (or same font name) may be linked to several encodings. Since the encoding can not be easily retrieved, and glyphs will not reproduce properly for the characters you want to insert.

Note For help with advanced font substitution, contact Sefas Customer Support.


M a n a g i n g i m a g e sSpoo l i n g t h e f i l e t o b e no rma l i z e d

PD

F n

orm

aliz

atio

n

Managing images

PDF normalization converts images as follows:

• black and white images (colorized or not) to TIFF• color images to JPEG



Sefas recommends that you use a standard directory for the storage and selection of the Metacodefile you want to normalize. The \spool subdirectory inside the sample application directory isintended for this purpose.


C:\normalization\samples\pdf_sample\spool

For example:

C:\normalization\samples\pdf_sample\spool\pdf_sample.pdf



Processing options for the normalization engine are set using a configuration file, techdpdf.cfg.

The configuration file is made up of keywords. Each keyword corresponds to a process to becarried out on the stream.

Example - techpdf.cfg

The following is an example of the techpdf.cfg configuration file used to process a stream inoffline mode with no string header and a maximum record size of 12000 bytes. For a description ofeach keyword and possible values, see below.

x_offset=3

y_offset=20

Note A sample PDF file, named pdf_sample.pdf, is provided with the sample application in the..\pdf_sample\spool directory. You can substitute the sample file with any PDF file you wouldlike to normalize.


N o r m a l i z i n g t h e s t r e a mKeywo rd s a nd d e s c r i p t i o n s


The following is a list of keywords that can be used in the techpdf.cfg configuration file.


Normalizing PDF files is accomplished outside of the Remake user interface using the following files:

• PDF input file - The .pdf file to be normalized, such as pdf_sample.pdf.• techpdf.cfg - The configuration file where you set parameters that determine how

normalization is accomplished.• go.exe - The executable entered in the techpdf.cfg command line that runs the

normalization engine.• normalize.bat - Command line batch file that contains environment variables and

executables (go.exe) necessary for normalization. When you execute this file, normalization runs.

Run a PDF normalization as follows:

1. Make sure the .pdf file you want to normalize is in the spool directory. For example:

C:\normalization\samples\pdf_sample\spool\filename.pdf

2. Edit techpdf.cfg in a text editor and add/edit keywords and values. For more information, see Configuring the normalization engine on page 97.

3. Edit the batch file normalize.bat to set the environment variables and any command line parameters you want to run during normalization. When entering command line data, you can use engine parameters to customize how you want normalization to run. For example:

-o lets you specify the name of the output file

Keyword Description

Compression_mode Compresses the VPF file. Valid values are:

• 0 (default) - does not compress the file

• 1 - compresses the file

images_mode Determines how images are handled in the generated VPF file. Valid values are:

• IMAGE (default) - The images are placed with the composition statement Y.

• LOGO - The images are placed with the composition statement $LOGO.

load_logos Copiies images. Valid values are:

• O (default) - does not copy the images,

• 1 - copies the images.

pdf_font_dir Specifies the directory that contains the font files extracted from the PDF file.

res_dir_path Specifies the directory that contains the image files extracted from the PDF file.

x_offset The offset of the job as measured by its distance from the y-axis parallel to the x-axis. The starting point is the top left corner of the page.

Default value is 0.

y_offset The offset of the job as measured by its distance from the x-axis measured parallel to the y-axis. The starting point is the top left corner of the page.

Default value is 0.


N o r m a l i z i n g t h e s t r e a mSe t t i n g env i r on men t va r i a b l e s

PD

F n

orm

aliz

atio

n

-R generates a list of resources

For more information on engine parameters, see the next section.

4. Execute the batch file to run normalization.

Setting environment variables

Use the batch file to set environment variables and enter command line parameters necessary torun normalization. Environment variables consist of the directory structure and information aboutthe file to be normalized. For example:

set opWD=C:\normalizationset opFam=samplesset opAppli=pdf_samplesset opInstallDir=%opWD%\%opFam%\%opAppli%\oprint

The command line consists of the name of the executable that runs normalization (go.exe) andparameters to run the engine. For example:

%opInstallDir%\bin\go.exe %opInstallDir%\bin\techpdf -E opInstallDir=%opInstallDir% -E opWD=%opWD% -E opFam=%opFam% -E opAppli=%opAppli% -i %file%.PDF -o %opWD%\%opFam%\%opAppli%\printer\%file%.vpf -C %opInstallDir%\common\config\pdf\techpdf.cfg -S pdfnormalize

Note that the command line contains engine parameters that determine how the normalizationengine processes the file. See Command Line Parameters below for more information.


The command line parameters for the TechPDF normalization engine are presented in the tablebelow.


Use the following parameters in the command line for running the TechPDF normalization engine:


-C file_name Indicates the name of the configuration file (*.cfg) used to configure PDF nor-malization, for example techpdf.cfg.

-E Sets an environment variable to the installation directory.

-E opInstallDir= Sets the environment variable to indicate the access path to the bin and com-mon directories.


-E opFam= Sets the environment variable to indicate the name of the directory containing the group of applications.


-i file_name Indicates the name of the input file. By default, this file is located in the spool directory of the application.

-l file_name Optional parameter that generates a log file. Use this parameter with -v, with valid entries for -v being 1 to 10, with 1 being the lowest level of logging.IMPORTANT: Use these parameters only in development.

-o file_name Indicates the name of the output VPF file. By default, this file is located in the printer directory.


N o r m a l i z i n g t h e s t r e a mHan d l i n g e r r o r s (m i s s i ng f on t s )


%opInstallDir%\bin\go.exe %opInstallDir%\bin\techpdf -E opInstallDir=%opInstallDir% -E opWD=%opWD% -E opFam=%opFam% -E opAppli=%opAppli% -i %file%.PDF -o %opWD%\%opFam%\%opAppli%\printer\%file%.vpf -C %opInstallDir%\common\config\pdf\techpdf.cfg -S pdfnormalize

The sample command line above does the following:

%opInstallDir%\bin\go.exe - The directory path to the executable that runs normalization.

%opInstallDir%\bin\techpdf - The path to the normalization engine.

-E opInstallDir=%opInstallDir% - The directory path to the installation directory environment variable.

-E opWD=%opWD% - The environment variable pointing to the Open Print working directory (group entry point).

-E opFam=%opFam% - The environment variable pointing to the name of the group application.

-E opAppli=%opAppli% - The environment variable pointing to the application name.

-i %file%.PDF - The name of the input file to be normalized.

-o %opWD%\%opFam%\%opAppli%\printer\%file%.vpf - The directory path and name of the output file.

-C %opInstallDir%\common\config\pdf\techpdf.cfg - The directory path and filename of the configuration file.

-S pdfnormalize - The section of the configuration file used in normalization; pdfnormalize.

Handling errors (missing fonts)

If you do not have all the PDF fonts in the font directory, the an error message is generated during normalization. For example:

Fatal error (-1): External font [CalibriBoldItalic.ttf]

This message appears in the <filename>.bck file. If normalization is not successful, view this file in a text editor to look for the message above. if you are missing a font and have it available for use, copy the font to the /<install directory>/oprint/common/fonts directory and rerun normalization.

If you do not have the missing font available, see Font substitution on page 96.

-ps n Optional parameter that starts the normalization at page n.

-pe n Optional parameter that stops the normalization at page n.

-S section_name Indicates the section of the configuration file to be used.

clip_mode Controls unexpected element overlap. Valid values are:• O (default value) - does not reduce overlap• 1 - reduces overlap.



L o c a t i n g t h e V P F o u t p u tTechPDF eng i n e r e s ou r c e s

PD

F n

orm

aliz

atio

n

TechPDF engine resources

The table below lists the supported and non-supported resources of the TechPDF engine:


Unless specified otherwise (via the -O parameter), the VPF file is output to the \spool directoryof the application. Following our sample application, the VPF file is:

C:\normalization\samples\pdf_sample\spool\pdf_sample.vpf

The file contains all of the original fonts and resources, regardless of the whether the resourceswere external to the stream or inline.

Resources Supported Not supported

Fonts • TTF, TYPE1 and Type3 bitmap-only fonts

• Normal, Bold, Italic, Bold italic fonts• Size less than 32 points• Text orientations: 0° , 90°, 180°, and

270° only• Colors expressed in CMYK or RGB

mode

• CID fonts• Empty fonts, ie only the outline appears• Individual zoom on characters

Ex: Times New Roman• Text orientations which are not 0° , 90°,

180°, or 270°• Size larger than 33 points• Text clipping• Opacity

Vectors • Boxes• Lines• Polygons• Textures similar to the ones used in

Open Print• Orientations: 0° , 90°, 180°, and

270° only• Colors expressed in CMYK or RGB

mode only

• Textures different from the ones used in Open Print

• Orientations which are not 0° , 90°, 180°, or 270°

• Colors not in CMYK or RGB mode• Clipping• Opacity

Beziers curves

• Simple Bézier curves• Colors expressed in CMYK or RGB

mode only

• Every texture.• Orientations which are not 0° , 90°, 180°,

or 270°• Colors not in CMYK or RGB mode• Clipping• Opacity

Images • JPEG images• Black and white or color images• Orientations: 0°, 90°, 180°, and 270°• Colors expressed in CMYK or RGB

mode

• Other fomats (not JPEG or PCX)• Text Orientations which are not 0° , 90°,

180°, or 270°• Colors not in CMYK or RGB mode• Clipping• Opacity


L o c a t i n g t h e V P F o u t p u tTe chPDF en g i ne r e sou r c e s


O v e r v i e wThe Te chMu l t i n o rma l i z a t i o n eng i ne

Postscrip

t n

orm

aliz

atio

n

C h a p t e r 6 : P o s t s c r i p t n o r m a l i z a t i o n

Overview

Open Print Remake supports normalization of PostScript files.

PostScript normalization converts a PostScript data stream into a Virtual Page Format (VPF) file.

PostScript resources may be inline or external to the stream. Inline resources are processedautomatically during normalization.

PostScript normalization is not available in the Remake user interface. You need to use thefollowing to perform a PostScript normalization:

• The input .ps file• The TechMulti normalization engine, as indentified in the next section• A batch file to set the environment variables and run the command line parameters

necessary to perform normalization. Sefas supplies a batch file sample; you can modify this to meet your organization’s needs.

Two additional files, techmulti.cfg and techmulti_ibin.cfg, may also be used to setconfiguration options for the normalization engine.

The PostScript normalization process includes:

• Analyzing the .ps file to determine its contents• Setting optional configuration keywords and values, if needed• Executing the command line using a batch file

If you are running Windows, PostScript normalization also requires a hardware USB dongle andassociated third-party software to validate licensing information. For more information aboutthese requirements, see the Open Print Prerequisites Guide or contact Sefas CustomerSupport.

The TechMulti normalization engine

The TechMulti normalization engine converts a PostScript data stream into a VPF file.

A batch file executes the normalization engine using a set of runtime parameters.

For example, the -i parameter sets the access path to the PostScript input stream. For moreinformation on available parameters, see Command line parameters on page 110.

Configuration files

Additional processing options for the engine are set using two optional configuration files

• techmulti.cfg - The file contains keywords that can be used to set special options for processing the PostScript data stream.

• techmulti_ibin.cfg - This file is used to set options for printer trays.

The configuration files are edited using a standard text editor. For the syntax and keywords, seeConfiguring the normalization engine on page 106.



Before you begin


For all supported platforms, PostScript normalization requires Adept Suite software. Adept Suiteprovides files required by the TechMulti engine.

Under Windows, PostScript normalization also requires:

• Sentinel Protection software and USB dongle - These are required by Adept for authentication purposes.

Sefas also recommends that you have a:

• PostScript viewer installed on the computer where you perform the normalization. Ghostview is recommended on UNIX and GSView is recommended for Windows. Both of these programs require GhostScript.

• PostScript printer connected to the computer for testing purposes.

Gathering the required resources

Before launching a PostScript normalization, you should:

• Gather and have available a selection of the original printed and electronic PostScript documents as a reference.

• Review and assess the nature of the resources to be normalized.


While virtually any directory structure can be used to perform the normalization, it is helpful touse a standard directory structure and standard naming conventions.


Sefas recommends you use a directory structure based on the following environment variables:

opWd - The working directory that acts as the group entry point

opFam - The group directory

opAppli - The application directory that contains all the subdirectories and files needed to run normalization

Note All the Adept and, if necessary, Sentinel components are provided by Sefas at install time.

NoteFor detailed system and software requirements, see the Open Print Prerequisites Guide orcontact Sefas Customer Support.

NoteFor more information about the Open Print environment variables, see the Open Print

Operating Manual.


M a n a g i n g f o n t s a n d i m a g e sFon t s

Postscrip

t n

orm

aliz

atio

n

A sample directory structure follows:

In the sample above:

normalization is the opWd directory.

samples is the opFam directory.

ps_sample is the opAppli directory.

In addition, the opInstallDir variable is used to define the installation directory path (oftenC:\oprint). All of the above variables are used in the command line to execute the engine.

Managing fonts and images

Fonts

PostScript normalization automatically includes fonts that are embedded in the PostScript file inthe VPF.

PostScript supports Type1 and Type3 fonts as input. PostScript does not support TrueType fonts.

In the VPF file, fonts are rendered as 300 dots per inch (DPI) bitmap fonts.

Images

Images are converted as follows:

• Black and white images (colorized or not) to TIFF• Color images to JPEG


P r e p a r i n g t h e i n p u t f i l eO ve r v i ew o f t e chmu l t i . c f g


Sefas recommends that you use a standard directory for the storage and selection of the PostScriptfile you want to normalize. The \spool subdirectory inside the sample application directory isintended for this purpose.


C:\normalization\samples\ps_sample\spool

For example:

C:\normalization\samples\ps_sample\spool\ps_sample.ps


Overview of techmulti.cfg

Processing options for the normalization engine are set using a configuration file,techmulti.cfg.

The configuration file is made up of one or more sections, such as [psnormalize], followed bykeywords. Each keyword contains a value that corresponds to a process to be carried out on thestream.

The following is an example of the techmulti.cfg configuration file.

[psnormalize]

verbose=1

page_information=1

comment filter=%%MSD;%%KLF

NoteA sample PostScript file, named ps_sample.ps, is provided with the sample application in the..\ps_sample\spool directory. You can substitute the sample file with any PostScript file youwould like to normalize.


C o n f i g u r i n g t h e n o r m a l i z a t i o n e n g i n eOve r v i ew o f t e c hmu l t i _ i b i n . c f g

Postscrip

t n

orm

aliz

atio

n

Keywords

The following is a list of keywords that can be used in the techmulti.cfg configuration file.

Overview of techmulti_ibin.cfg

This optional configuration file can be used to preserve the tray selection settings from thePostScript file and translate them in the VPF file.

This file is enabled by the keyword page_information=1 in the techmulti.cfg configurationfile.

IMPORTANT: For the PageSize parameter, a space character is required before and after thebrackets to match the syntax of an array in postscript, for example:

/IBIN1

<<

/MediaType (Manual)

/PageSize [ 612 1008 ]

>>

Example 1

<<

/MediaType (BIN2)

/Duplex false

/PageSize [ 612 792 ]

>> setpagedevice

This calls the input tray named IBIN 2 ($IBIN 2 composer equivalent), providing thatTechmulti_ibin.cfg contains the following:

<<

/IBIN1

Keyword Description

comment_filter Specifies whether to extract comments from the PostScript file and embed them in the VPF. For example:

comment_filter=%% MSD; %% KLF

The above example extracts all comments starting with %% MSD or %%KLF. In the VPF output this will appear as:

DRV NOTE + BPAGE "%% MSD....."

DRV NOTE + BPAGE "%% KLF....."

page_information Enables the processing of printer tray information in accordance with the configuration file, techmulti_ibin.cfg. Valid values are:

• 0 (Default) - No printer tray information is specified.

• 1 - Printer tray information is set in accordance with techmulti_ibin.cfg.

For more information, see Overview of techmulti_ibin.cfg below.

verbose Specifies whether to display debugging information in the trace logs. Valid values are:

• 0 - No debugging information is displayed.

• 1 - Displays the debugging information on the command line.

Note This option activates the PostScript /Duplex and /Tumble commands.


C o n f i g u r i n g t h e n o r m a l i z a t i o n e n g i n eOve r v i ew o f t e chmu l t i _ i b i n . c f g

<<

/MediaType (BIN1)

/PageSize [ 612 792 ]

>>

/IBIN2

<<

/MediaType (BIN2)

/PageSize [ 612 792 ]

>>

/IBIN3

<<

/MediaType (BIN3)

/PageSize [ 612 792 ]

>>

/IBIN4

<<

/MediaType (BIN4)

/PageSize [ 612 792 ]

>>

>>

Example 2

<<

/MediaPosition 2

/Duplex false

>> setpagedevice

The following can be used to select IBIN 2:

<<

/IBIN1

<<

/MediaPosition 1

>>

/IBIN2

<<

/MediaPosition 2

>>

/IBIN3

<<

/MediaPosition 3

>>

/IBIN4

<<

/MediaPosition 4

>>


C r e a t i n g t h e b at c h f i l eOve r v i ew o f t e c hmu l t i _ f on t . c f g

Postscrip

t n

orm

aliz

atio

n

Overview of techmulti_font.cfg

This file contains a list of substitution fonts found in the input PostScript file. The file must reside in oprint/common/config. A sample entry follows:

Arial=Arial.pfa

This entry indicates that each time the PostScript file searches for an Arial font, techmulti uses the Arial.pfa file located on the disk.

IMPORTANT: This should be a type1 font.

Creating the batch file

Setting environment variables

Use the batch file to set environment variables and enter command line parameters necessary torun the normalization. Environment variables consist of the directory structure and informationabout the file to be normalized. For example:

set opInstallDir=C:\oprintset opWD=C:\normalizationset opFam=samplesset opAppli=ps_sample

The command line consists of the name of the executable that runs normalization(techmulti.exe), along with parameters and environment variables used to determine how theengine processes the file. For example:

%opInstallDir%\bin\techmulti.exe -E opInstallDir=%opInstallDir% -E opWD=%opWD% -E opFam=%opFam% -E opAppli=%opAppli% -i ps_sample.ps -o %opWD%\%opFam%\%opAppli%\printer\ps_sample.vpf -C %opInstallDir%\common\config\ps\techmulti.cfg -S psnormalize

pause

See Entering Command Line Parameters below for more information.


C r e a t i n g t h e b a t c h f i l eCommand l i n e pa rame t e r s


Use the following case-sensitive parameters in the command line for running the TechMultinormalization engine:

IMPORTANT: To use a parameter file on a command line, you must specify the parameter file onthe command line using the -C and -S parameters, for example:

-C techmulti.cfg -S psnormalize

Also, the parameter file must be in the current directory or in the spool directory. If theparameter resides elsewhere (such as %common_path%\config), you need to prefix the filenamewith the path.


%opInstallDir%\bin\techmulti.exe -E opInstallDir=%opInstallDir% -E opWD=%opWD% -E opFam=%opFam% -E opAppli=%opAppli% -i ps_sample.ps -o %opWD%\%opFam%\%opAppli%\printer\ps_sample.vpf -C %opInstallDir%\common\config\ps\techmulti.cfg -S psnormalize

pause

The example command line above does the following:

%opInstallDir%\bin\techmulti.exe - The directory path to the executable (normalizationengine) that runs normalization.

-E opInstallDir=%opInstallDir% - The directory path to the installation directoryenvironment variable.


-C file_name Indicates the name of the optional configuration file (*.cfg) used for Post-Script normalization, for example techmulti.cfg.

-E Sets the environment variables for the application. This parameter is required.

-E opInstallDir= Sets the environment variable to indicate the access path for where the product is installed, including the bin and common subdirectories.


-E opFam= Sets the environment variable to indicate the name of the directory containing the group of applications.


-f Generates an intermediate PDF copy during normalization.

-h or -help Displays command line parameter help for the normalization engine you are running.

-i file_name Indicates the location and name of the input PostScript file. This parameter is required.

-o file_name Indicates the location and name of the output VPF file. This parameter is required.

-ps n Starts the normalization at page n.

-pe n Stops the normalization at page n.

-S section_name Indicates the section of the configuration file to be used.

-v Corresponds to the verbose keyword. -v 1 displays debugging information dur-ing the normalization.


C r e a t i n g t h e b at c h f i l eCommand l i n e p a rame t e r s

Postscrip

t n

orm

aliz

atio

n

-E opWD=%opWD% - The environment variable pointing to the Open Print working directory (groupentry point).

-E opFam=%opFam% - The environment variable pointing to the name of the group application.

-E opAppli=%opAppli% - The environment variable pointing to the application name.

-i ps_sample.ps - The name of the PostScript input file to be normalized. Unless pathinformation is specified, the engine assumes the file is located in spool directory of theapplication.

-o %opWD%\%opFam%\%opAppli%\printer\ps_sample.vpf - The directory path and name of theoutput file. In this example, ps_sample.vpf is output to the printer directory of theapplication.

-C %opInstallDir%\common\config\ps\techPostScript.cfg - The directory path andfilename of the optional configuration file.

-S - The section of the configuration file used in normalization - [psnormalize].

Normalize PostScript files outside of the Remake user interface using the following files:

• techmulti.exe - The executable for the normalization engine entered on the command line.• PostScript input file - The .ps file to be normalized, such as ps_sample.ps.• techmulti.cfg - The optional configuration used to set keywords that determine how

normalization is accomplished.• techmulti_ibin.cfg - The optional configuration file used to preserve printer tray settings

from the PostScript file. • normalize.bat - Command line batch file that contains environment variables and

executable (techmulti.exe) necessary for normalization. When you execute this file, normalization runs.


N o r m a l i z i n g t h e s t r e a mHan d l i n g e r r o r s


Run a PostScript normalization as follows:

1. Insert the dongle into an available USB port on your computer.

2. Make sure the .ps file you want to normalize is in the spool directory. For example:

C:\normalization\samples\ps_sample\spool\filename.ps

3. If applicable, edit techmulti.cfg in a text editor and add/edit keywords and values. For more information, see Overview of techmulti.cfg on page 106.

4. If applicable, edit techmulti_ibin.cfg in a text editor to configure printer tray information. For more information, see Overview of techmulti_ibin.cfg on page 107.

5. Create and edit the batch file normalize.bat to set the environment variables and any command line parameters you want to run during normalization. For more information and examples, see Creating the batch file on page 109.

6. Execute the batch file to run normalization.

Handling errors

If you receive an error message during the normalization, try opening the PostScript file with arecent version of GhostView. If an error occurs in Ghostview, the PostScript file may be corrupt.Contact Sefas Customer Support for assistance.

Following are some limitations of the TechMulti engine:

• External resources cannot be found by TechMulti.• There is a limit of 65535 objects per page in the VPF. • Clipping is not supported.


The VPF file is output to the directory that is specified using the -O parameter. Following thesample above, this is the printer directory. For example:

C:\normalization\samples\ps_sample\printer\ps_sample.vpf

The VPF file contains all of the original fonts and resources.


I n d e x

. . . . . . . . . . . . . . AAFP

command line parameters 53configuring the application 15keywords, general 24keywords, line mode 43locating the VPF output 52managing color 45managing de-imposition 51managing images 50normalizing the stream 52spooling the input file 15

. . . . . . . . . . . . . . CColor

managing AFP 45Command line parameters

AFP 53HP-PCL 71LCDS 89PDF 99

. . . . . . . . . . . . . . DDe-imposition, managing AFP51Directory structure

AFP application 13HP-PCL application 58LCDS application 76PDF application 94, 104

Dynamic mode 8

. . . . . . . . . . . . . . EEngine

TechAFP 11TechLCDS 75TechPCL 57TechPDF 93

. . . . . . . . . . . . . . FFont environment

preparing HP-PCL 60preparing PDF 95

. . . . . . . . . . . . . . HHP-PCL

command line parameters 71configuring the application 62

keywords 68locating the VPF output 73normalizing the stream 71preparing the font environment

60spooling the input file 62

. . . . . . . . . . . . . . IImages

managing AFP 50managing PDF 97, 105

. . . . . . . . . . . . . . KKeywords

list of AFP 24list of HP-PCL 68list of LCDS 85list of PDF 98, 107

. . . . . . . . . . . . . . LLCDS

command line parameters 89configuring the application 79creating a new project 78keywords 85locating the VPF output 91normalization overview 75normalizing the stream 88spooling the input file 79

. . . . . . . . . . . . . . MManual mode 8

. . . . . . . . . . . . . . NNormalization

dynamic mode 8engines 7manual mode 8of the AFP stream 52of the HP-PCL stream 71of the LCDS stream 88of the PDF stream 98overview of 5process 6scenarios 6

. . . . . . . . . . . . . . Ooutput_doc_compress 34

. . . . . . . . . . . . . . PPDF

command line parameters 99keywords 98, 107locating the VPF output 101,

112managing images 97, 105normalization overview 93,

103normalizing the stream 98preparing the font environment

95spooling the input file 97supported resources 101unsupported resources 101

ProjectCreating AFP 13creating HP-PCL 61creating LCDS 78

. . . . . . . . . . . . . . SSample applications 8Spooling

AFP input file 15HP-PCL input file 62LCDS input file 79PDF input file 97

. . . . . . . . . . . . . . TTechFont, about 8

. . . . . . . . . . . . . . UUser Interface, about Re-make’s 8

. . . . . . . . . . . . . . VVPF

locating the AFP output file 52locating the HP-PCL output file

73locating the LCDS output file 91locating the PDF output file

101, 112

Océ | Printing for...

Documents

Transcript of Océ | Printing for...