xpression compuset reference...produce. the xpression compuset reference contains the information...

xPression 2.5xPression CompuSet Reference

© 2001-2006 by Document Sciences Corporation. All rights reserved. The copyright protection claimed includes all formats of copyrightable material and information governed by current or future statutory or judicial law. This includes, without limitations, any material generated by the software programs that display icons or other screen interfaces. You may not copy or transmit any part of this document in electronic or printed format without the express written permission of Document Sciences Corporation. xPression, CompuSet, and all other Document Sciences Corporation products mentioned in this publication are trademarks of Document Sciences Corporation. For complete copyright information, please see the file xPression Licensing Document.pdf located on your eBook Library CD.Document Sciences Corporation, 5958 Priestly Drive, Carlsbad, CA 92008www.docscience.com

Document Sciences Corporation

2

3

Table of Contents

Chapter 1. Introduction ...................................................................................... 17Who Should Read This Book .................................................................................................................................18Icons and Revision Bars ........................................................................................................................................ 18Solution Support .................................................................................................................................................... 19

Chapter 2. Configuring CompuSet..................................................................... 20What is CompuSet’s Role in xPression? ...............................................................................................................21CompuSet Composition Engine Modes................................................................................................................. 22

CompuSet Regular Mode vs. Linked Emitter Mode.................................................................................. 22Can I Direct Which CompuSet Mode xPression Uses? ............................................................................ 23How Do I Know Which Mode Was Used?................................................................................................. 23

Preparing CompuSet Files..................................................................................................................................... 24Step 1: Create Your Font Database and Widths Files............................................................................... 24Step 2: Create Your PDEF Files ............................................................................................................... 25Step 3: Create Your Font Map Files.......................................................................................................... 26Step 4: Define Your Font Definitions and Format Definitions.................................................................... 28

Job Control Files .................................................................................................................................................... 29Windows Platforms ................................................................................................................................... 29UNIX Platforms ......................................................................................................................................... 30Logical Unit Numbers................................................................................................................................ 30WDPORT Processor Logical Unit Numbers ............................................................................................. 32File Names................................................................................................................................................ 33Using Job Control Files............................................................................................................................. 34

Using Two Pass Functionality with xPression........................................................................................................ 36


Table of Contents4

Chapter 3. Creating Your Font Files................................................................... 37How to Create and Configure Your Font Files .......................................................................................................38Creating a Font Database ...................................................................................................................................... 39Adding Fonts for AFP Output ................................................................................................................................. 40

Step One: Backup Existing Configuration and Widths Files...................................................................... 40Step Two: Edit Configuration File .............................................................................................................. 40Step Three: Edit Font Loader .................................................................................................................... 45Step Four: Run Font Loader...................................................................................................................... 46Step Five: Edit Afpfwids.bat ...................................................................................................................... 46Step Six: Run Afpfwids.bat ........................................................................................................................ 46Step Seven: Verify Changes ..................................................................................................................... 46

Adding Fonts for Metacode Output ........................................................................................................................ 46Step Two: Edit Configuration File .............................................................................................................. 47Step Three: Run Font Loader.................................................................................................................... 51Step Four: Run Metfwids.bat..................................................................................................................... 52Step Five: Verify Changes......................................................................................................................... 52

Adding Fonts for PCL Output ................................................................................................................................. 52Do I need to use the Font Converter?....................................................................................................... 52Step Two: Create Font List........................................................................................................................ 53Step Three: Edit Configuration File ........................................................................................................... 54Step Four: Edit Font Loader ...................................................................................................................... 57Step Five: Run Font Loader ...................................................................................................................... 57Step Six: Run Pclfwids.bat ........................................................................................................................ 57Step Seven: Verify Changes ..................................................................................................................... 57

Adding Fonts for PDF Output................................................................................................................................. 57Step Two: Edit Configuration File .............................................................................................................. 58Step Three: Create Font List ..................................................................................................................... 61


Table of Contents5

Step Four: Edit Font Loader ...................................................................................................................... 62Step Five: Run Font Loader ...................................................................................................................... 63Step Six: Load Fonts Into the Width/Configuration File............................................................................. 63Step Seven: Verify Changes ..................................................................................................................... 63Three Issues with PDF Output .................................................................................................................. 64

Adding Fonts for PostScript Output........................................................................................................................ 64Step Two: Edit Configuration File .............................................................................................................. 65Step Three: Create Font List ..................................................................................................................... 67Step Four: Edit Font Loader ...................................................................................................................... 68Step Five: Run Font Loader ...................................................................................................................... 69Step Six: Load Fonts Into the Width/Configuration File............................................................................. 69Step Seven: Verify Changes ..................................................................................................................... 69Three Issues with PDF Output .................................................................................................................. 70

Moving Your Widths Files....................................................................................................................................... 70

Chapter 4. Configuring Your PDEF File ............................................................. 71What Can I Specify in my PDEF File? ...................................................................................................................72The Output Format Tool ......................................................................................................................................... 76

Are You Creating PCL Output? ................................................................................................................. 77Launching an Output Format Tool............................................................................................................. 77The Output Format Tool Interface ............................................................................................................. 78Selecting Options ...................................................................................................................................... 82Editing the PDEF File................................................................................................................................ 85

Page Setup ............................................................................................................................................................ 85Paper Size................................................................................................................................................. 85Tray Selection ........................................................................................................................................... 87Tray Setup................................................................................................................................................. 89


Table of Contents6

Tray Setup Policies ................................................................................................................................... 96Page Offset ............................................................................................................................................... 98Medium Maps............................................................................................................................................ 99

Index Settings ...................................................................................................................................................... 101Index Setup ............................................................................................................................................. 102

Special Document Type ....................................................................................................................................... 103Select Document Type ............................................................................................................................ 104Booklet Options....................................................................................................................................... 105Duplicate Page Side-By-Side Printing..................................................................................................... 111

Document Merge.................................................................................................................................................. 114Merging from the Content Repository ..................................................................................................... 115Merging from Memory ............................................................................................................................. 117

Document Save.................................................................................................................................................... 118Saving to Content Repository ................................................................................................................. 119Saving to Memory ................................................................................................................................... 121

Content Repository Setup .................................................................................................................................... 122Content Repository Resource Disposition .............................................................................................. 123

Color..................................................................................................................................................................... 124Color Selection........................................................................................................................................ 124Color Mapping Setup .............................................................................................................................. 127

Fonts .................................................................................................................................................................... 129Font Options............................................................................................................................................ 129Font List for Printing ................................................................................................................................ 131

Proofing................................................................................................................................................................ 134Proofing Selection ................................................................................................................................... 135Font Mapping Setup................................................................................................................................ 136Proofing Font Translation Table .............................................................................................................. 137


Table of Contents7

Proofing Justification ............................................................................................................................... 138PDF Encryption Setup.......................................................................................................................................... 139

PDF Encryption Tab ................................................................................................................................ 140Document Permissions Tab .................................................................................................................... 141Information Directory............................................................................................................................... 143

Output Options ..................................................................................................................................................... 143AFP ......................................................................................................................................................... 144Metacode ................................................................................................................................................ 151PDF......................................................................................................................................................... 161PostScript................................................................................................................................................ 169

Print Job Reporting .............................................................................................................................................. 179Messages and Accounting ...................................................................................................................... 180

Printer-Specific Settings ....................................................................................................................................... 181Printer Features ...................................................................................................................................... 181Printer Finishing ...................................................................................................................................... 186Variable Print Specification...................................................................................................................... 188

Emitter Log........................................................................................................................................................... 189Message Log........................................................................................................................................... 190Customize Error Messages..................................................................................................................... 191Message Format ..................................................................................................................................... 193

Embedding Tag Logical Elements (TLEs) in Your AFP Output File ..................................................................... 194Setup CompuSet Indexing for AFP ......................................................................................................... 194Configure Settings in ofp.properties........................................................................................................ 195Ensure All Settings Match ....................................................................................................................... 195

Chapter 5. Working With the Image Utility ....................................................... 196When Do I Use the Image Utility? ........................................................................................................................197


Table of Contents8

What CompuSet Resources Can I Manage with This Utility? .............................................................................. 197Resource Specifications and Formats..................................................................................................... 198Naming Your Resources ......................................................................................................................... 202What About My Merge Libraries?............................................................................................................ 202

Using the Image Utility ......................................................................................................................................... 203Launching the Image Utility..................................................................................................................... 204The Main Window ................................................................................................................................... 205Working with CompuSet Resources ....................................................................................................... 207Copying Resources From a Merge Library ............................................................................................. 208Converting Images to xPression Publish Images.................................................................................... 210Importing Resources ............................................................................................................................... 211Exporting Resources............................................................................................................................... 222Viewing an Image.................................................................................................................................... 228Rotating an Image................................................................................................................................... 228Combining Images .................................................................................................................................. 229Viewing Properties .................................................................................................................................. 231Searching for a Resource ....................................................................................................................... 231Variable Merge Frames........................................................................................................................... 232

Chapter 6. PCL Font Converter ....................................................................... 239Launching the PCL Font Converter ......................................................................................................................240Converting A Font ................................................................................................................................................ 241Finding the Best Symbol Set................................................................................................................................ 243Tips for Converting Fonts ..................................................................................................................................... 245Symbol Sets ......................................................................................................................................................... 245Font Converter Error Messages........................................................................................................................... 249

1–49: Tagged Font Metric Error Messages ............................................................................................. 249


Table of Contents9

50–69: File Management Error Messages .............................................................................................. 25170–99: Invalid Font Files ......................................................................................................................... 253100–299 .................................................................................................................................................. 255300–399 .................................................................................................................................................. 260400–499: Warnings ................................................................................................................................. 263500–599 .................................................................................................................................................. 264600–699 .................................................................................................................................................. 265700–799 .................................................................................................................................................. 271800–899 .................................................................................................................................................. 272900–999 .................................................................................................................................................. 273

Appendix A. FDB Utility Commands ................................................................ 275FDB Utility Commands .........................................................................................................................................276File and Path Names............................................................................................................................................ 276Sample FDB Job ..................................................................................................................................................277AEXT - Specify Extension (AFP, PCL, PostScript) ..............................................................................................279APTH - Directory Name (AFP, PCL, and PostScript) ...........................................................................................281

Example .................................................................................................................................................. 282CCOD - Override Condition Code ........................................................................................................................283

Condition Code Values............................................................................................................................ 284CONF - Generate Configuration File ....................................................................................................................285

Example .................................................................................................................................................. 285DELE - Delete Font ..............................................................................................................................................286

Example .................................................................................................................................................. 286EDIT - Edit Font ...................................................................................................................................................288

Saving the Changes................................................................................................................................ 290Renaming................................................................................................................................................ 290


Table of Contents10

Examples ................................................................................................................................................ 290FJOB - Create Font Job Command File (Xerox LPS and PCL 5) .......................................................................292

PCL Printers............................................................................................................................................ 295PCC Byte ................................................................................................................................................ 295Example .................................................................................................................................................. 296

FONT - Specify Font ............................................................................................................................................298Example .................................................................................................................................................. 298

FTAP - Write Font to Tape or Disk .......................................................................................................................299Block and Record Size............................................................................................................................ 301Multiple Fonts.......................................................................................................................................... 301Disk File Specifications ........................................................................................................................... 301Example .................................................................................................................................................. 302

GETC - Map Characters from a Source Font .......................................................................................................303Special Functions .................................................................................................................................... 304Example .................................................................................................................................................. 304

INFF - Define INFO Font ......................................................................................................................................306Example .................................................................................................................................................. 306

INFO - Display Font Data..................................................................................................................................... 307Example .................................................................................................................................................. 307

INIT - Initialize New Font Database .....................................................................................................................310Example .................................................................................................................................................. 311

LANG - Language Selection ................................................................................................................................312Example .................................................................................................................................................. 313

LIST - Display Font List ........................................................................................................................................314Example .................................................................................................................................................. 315

LOAD - Load Fonts into the Font Database .........................................................................................................316Block and Record Size............................................................................................................................ 318


Table of Contents11

Multiple Fonts.......................................................................................................................................... 318Disk File Specifications ........................................................................................................................... 318Using the LOAD Command..................................................................................................................... 319PostScript ISO Latin1 Character Encoding ............................................................................................. 319Example .................................................................................................................................................. 319

MACH - Identify Output Device ............................................................................................................................321Example .................................................................................................................................................. 322

MAKE - Convert Font ...........................................................................................................................................323Example .................................................................................................................................................. 324

MOVC - Map Characters to Font .........................................................................................................................326Special Functions .................................................................................................................................... 327Example .................................................................................................................................................. 327

PACK - Compress Font Database .......................................................................................................................329Example .................................................................................................................................................. 329

QUIT - Terminate FDB .........................................................................................................................................330Example .................................................................................................................................................. 330

RENM - Rename Font ..........................................................................................................................................331Example .................................................................................................................................................. 332

SAMP - Create Font Sample Display (Decentralized LPS) ..................................................................................333PCC Byte ................................................................................................................................................ 336Example .................................................................................................................................................. 337

SAVE - Save Temporary Font ..............................................................................................................................338Example .................................................................................................................................................. 339

UPDT - Update Font Database ............................................................................................................................341Examples ................................................................................................................................................ 342

WIDS - Create Configuration/Widths File .............................................................................................................343PCL Printing ............................................................................................................................................ 345


Table of Contents12

Appendix B. WDPORT Commands ................................................................. 346Command Format ................................................................................................................................................347CCOD - Override Condition Code ........................................................................................................................348

Condition Code Values............................................................................................................................ 349CONF - Output a Configuration File .....................................................................................................................351LANG - Language Selection ................................................................................................................................352

Example .................................................................................................................................................. 354WCVT - Export or Import a Configuration/Widths File .........................................................................................355

Appendix C. Font Commands.......................................................................... 358EFNT - Define Raster Font Correlation ................................................................................................................359FNSZ - Font Number, Size and Orientation .........................................................................................................362MFNT - Machine Font Definition ..........................................................................................................................364SIZE - Point Sizes Available ................................................................................................................................366EFNT - Logical User Font ....................................................................................................................................367FNAM - Font Names for Viewing .........................................................................................................................369FNSZ - Font Number, Size and Orientation .........................................................................................................371MFNT - Machine Font Definition ..........................................................................................................................373SIZE - Point Sizes Available ................................................................................................................................375FNAM - Font Names for Viewing .........................................................................................................................376FONT - Define User Font Correlation ..................................................................................................................378MFNT - Machine Font ..........................................................................................................................................380NOLD - Font Location (Resident or Downloaded) ...............................................................................................383CHDF - Define Character Layout .........................................................................................................................385FNAM - Font Names for Viewing .........................................................................................................................387FONT - Define Font Correlation ...........................................................................................................................388


Table of Contents13

MFNT - Machine Font Definition ..........................................................................................................................390CHDF - Define Character Layout .........................................................................................................................393FNAM - Font Names for Viewing .........................................................................................................................395FONT - Define Font Correlation ...........................................................................................................................397MFNT - Machine Font Definition ..........................................................................................................................399

Appendix D. INDRPR Commands ................................................................... 402Format of Index Records ......................................................................................................................................403

Index Tags for Duplicate Records ........................................................................................................... 405File and Path Names............................................................................................................................................ 406INDRPR Sample Job ........................................................................................................................................... 406Command Format ................................................................................................................................................408CCOD - Override Condition Code ........................................................................................................................410

Condition Code Values............................................................................................................................ 411FLDS - Key and Label Fields ...............................................................................................................................413IFMT - Field Size.................................................................................................................................................. 414IOPT - Index File Format ......................................................................................................................................416

Example .................................................................................................................................................. 417LANG - Language Selection ................................................................................................................................419LINK - Generate COMPUSET LINK Commands .................................................................................................421

Example .................................................................................................................................................. 422OFMT - Variable- or Fixed-Length Records .........................................................................................................423

Example .................................................................................................................................................. 423

Appendix E. PCL Output Formatter Commands.............................................. 424Command Format ................................................................................................................................................425


Table of Contents14

AMAC - Page Offset .............................................................................................................................................426CCOD - Condition Code Override ........................................................................................................................429CMAP - Character Mapping .................................................................................................................................431COPY - Number of Copies ...................................................................................................................................433DELE - Delete Merge Library Entry ......................................................................................................................434DJDE - Dynamic Job Descriptor Entry .................................................................................................................435DLBL - Merge Library Block Length .....................................................................................................................436DMRG - Merging and Saving Documents ............................................................................................................438DUPL - Duplex Printing ........................................................................................................................................442FNAM - Font Names for Viewing .........................................................................................................................443FNLD - Font Downloading ....................................................................................................................................445FONT - Define User Font Correlation ..................................................................................................................447FTYP - Output Device and Scaling Factor ...........................................................................................................449ILAT - Inverse Translation Table ..........................................................................................................................450LANG - Language Selection ................................................................................................................................451MFNT - Machine Font ..........................................................................................................................................453MIMP - Multiple Imposition ...................................................................................................................................456NOLD - Font Location (Resident or Downloaded) ...............................................................................................460OBFM - Output Record Format ............................................................................................................................462OPTN - Define Orientation ...................................................................................................................................463PAGE - Output Formatter Page Range ................................................................................................................467PDEF - Print Descriptor Entry Format ..................................................................................................................468PDFM - Output Printer and Font Memory ............................................................................................................469PFID - Final Output Device ..................................................................................................................................470PFNT - Proof Font Numbers (Printers) ................................................................................................................471PGSZ - Output Paper Size ...................................................................................................................................472PPNM - Page Count Sentinel ...............................................................................................................................474


Table of Contents15

RENM - Merge Library Entry Rename .................................................................................................................475SIZE - Maximum Point Size .................................................................................................................................476SPHC - Special Hyphenation Characters ............................................................................................................477TRAY - Select Input Tray ......................................................................................................................................483TXFL - Text String Definition Characters .............................................................................................................486XLAT - Translation Table .....................................................................................................................................487XPSM - Select Composition Mode .......................................................................................................................490

Appendix F. The Compubld.ini File.................................................................. 492Sample Compubld.ini File ....................................................................................................................................493[dirs] Section ........................................................................................................................................................ 494

compuset................................................................................................................................................. 494WordType................................................................................................................................................ 494Optional Keys.......................................................................................................................................... 495

[MergeOptions] Section........................................................................................................................................ 495[layout] Section..................................................................................................................................................... 495[PostScript] Section.............................................................................................................................................. 496

MaxResolution ........................................................................................................................................ 496FontPath.................................................................................................................................................. 496

[Hardware] Section............................................................................................................................................... 496ShadingMethod ....................................................................................................................................... 496MaxPrinterResolution.............................................................................................................................. 497Optional Settings..................................................................................................................................... 498

[Afp] Section......................................................................................................................................................... 501ResourceDataPath.................................................................................................................................. 501FontDataPath .......................................................................................................................................... 501

[ilats] Section........................................................................................................................................................ 501


Table of Contents16

Optional Sections ................................................................................................................................................. 501[ActivityLog] Section................................................................................................................................ 501[Preferences] Section.............................................................................................................................. 503


17

Chapter 1Introduction

Welcome to the xPression CompuSet Reference, a guide to the interface between the CompuSet composition engine and xPression.

When you publish to CompuSet, xPression uses the CompuSet composition engine to produce output. In order for CompuSet to compose your output correctly, you must supply a few different CompuSet configuration files. These files pass information to CompuSet about your job and the output you want to produce. The xPression CompuSet Reference contains the information you need to create and configure these files, as well as information on the tools and utilities that are available to you to help you create CompuSet output.

Topics included in this chapter:

• Who Should Read This Book

• Icons and Revision Bars

• Solution Support


Chapter 1 - Introduction18

Who Should Read This BookYou should read this book if you are planning on using the publish to CompuSet feature of xPression to create your output. If you are a current CompuSet user, this guide provides the reference information necessary to refresh yourself on how to configure the files, as well as information about new tools that you can use with xPression (such as the Image Utility). If you have never used CompuSet, this reference provides all the necessary information for you to configure CompuSet, and get your CompuSet xPression jobs publishing correctly.

Icons and Revision BarsWhen one of the following icons appears in the left margin of a page, it alerts you to special information.

Caution: The warning cautions you that a fatal error, unsatisfactory output, or loss of data may occur if you do not follow the directions carefully.

Tip: A tip offers suggestions to simplify a task or describes a useful shortcut. They may also describe an alternate way to use the techniques described in the text.

Lock: The lock icon identifies features that Document Sciences licenses individually. If you have not obtained a license, you cannot access the identified feature. For more information, contact your Document Sciences sales representative.

Note: A note offers information that emphasizes or supplements important points of the main text.

Other icons appear to identify a process or button described in the text.

Revision bars help you locate new or changed information. Look for these revision bars in the right margin of each affected page.


Chapter 1 - Introduction19

Solution SupportFor more information or to solve a problem, you can contact Document Sciences Solution Support in one of the following ways:

Telephone (760) 602-1500

Fax (760) 602-1515

World Wide Web http://support.docscience.com

Email [email protected]


http://support.docscience.com

20

Chapter 2Configuring CompuSet

When you publish to CompuSet from xPression Design, xPression uses the CompuSet composition engine to perform composition functions. Publishing pulls together your document’s content, format, and layout and creates the final output.

Before you publish to CompuSet using xPression, you must first configure the required files for CompuSet. These files provide important information to CompuSet and xPression, such as font information and output format options.

This chapter describes these topics:

• What is CompuSet’s Role in xPression?

• Preparing CompuSet Files

• Job Control Files

• Using Two Pass Functionality with xPression


Chapter 2 - Configuring CompuSet21

What is CompuSet’s Role in xPression?The CompuSet publishing engine consists of CompuSet, the output processing engine, and the output formatters. When you publish to CompuSet, CompuSet processes the output produced by xPression Assemble to create your desired output formats. The output processing engine performs partitioning, sorting, merging and other output management tasks. The output formatters create print data streams for use with a large variety of laser printers, Adobe Acrobat Reader, e-mail, fax and archive solutions. You can then distribute the output through the various xPression distribution components, as shown in Figure 1.

Figure 1. xPression Architecture



After you design your document in xPression Design, and create the layout and develop your content, you pull all the pieces together and produce the final output through an xPression publishing engine. When you publish to CompuSet, CompuSet performs page layout and formatting for your target output device. You can then use various distribution profiles and output profiles defined in xPression Admin to create your final output. This way you can send the same output to different output devices.

For more information about xPression Design, see Getting Started with xPression Design. For more information about xPression Admin, see the xPression System Administrator’s Guide.

CompuSet Composition Engine ModesThis section describes the differences in the methods the CompuSet composition engine uses to compose your documents. Once you know how the engine works you will be able to set the correct NOLD command parameters to direct which composition mode the engine uses.

The topics in this section describe:

• CompuSet Regular Mode vs. Linked Emitter Mode

• Can I Direct Which CompuSet Mode xPression Uses?

• How Do I Know Which Mode Was Used?

CompuSet Regular Mode vs. Linked Emitter ModeCompuSet composes documents either in regular mode or in linked emitter mode. This section describes the differences in the way the engine modes work.

Basically, CompuSet and all the emitters are stored in one library (or program) called cmpcal32.dll. xPression delivers a CompuSet tagged text file, an options file, and function calls to CompuSet in order to retrieve an instantiated document. The tagged text, options, and functions are configured based on the conversion options and output profile parameters set up in xPression Admin.



In regular mode, CompuSet produces an intermediate CCF file that the emitter step reads into the CCF file to produce a print file. This method causes the emitter to make two passes through the input CCF file (not to be confused with the CompuSet two-pass mode) that first pre-scans in read mode to collect data, and follows that with a second pass that creates the print file. The necessary font list and shading requirements of the document are determined during the scan.

The linked emitter mode is the most efficient method because information passed from the CompuSet step to the emitter step is done one record at a time, but there are restrictions with this mode. Because only one pass is made through the emitter, fonts to be downloaded must be identified with NOLD commands and certain shadings cannot be done.

For example, if you are publishing to PCL and want to download fonts, you would set the NOLD parameters as follows:

• For regular mode: p2=0

• For linked emitter mode: p2=4

Can I Direct Which CompuSet Mode xPression Uses?The short answer to this question is: No.

In most cases, the job complexity determines which mode the composition engine uses. A simple job, such as a single print to file job, automatically uses the linked emitter mode; all other jobs and jobs requiring multiple output streams, or other output options like file splitting, bar codes, and recipient processing are better served using the regular mode.

How Do I Know Which Mode Was Used?When the composition engine uses the regular mode to produce the documents, two log files are created with similar names, one of which includes the word “emit” in its name. If the engine has used the linked emitter mode, only one log file is produced that contains information for both the CompuSet and the emitter steps.



Preparing CompuSet FilesBefore you begin publishing to CompuSet with xPression, you must set up the required CompuSet files. The following sections outline the steps you need to perform before you publish to CompuSet.

This section describes these topics:

• Step 1: Create Your Font Database and Widths Files

• Step 2: Create Your PDEF Files

• Step 3: Create Your Font Map Files

• Step 4: Define Your Font Definitions and Format Definitions

Step 1: Create Your Font Database and Widths FilesA font database is a random access file that resides on the host and contains all the font information necessary to create CompuSet output. You use the Font Data Base (FDB) utility to create your font database using the font files you get from your vendor. For more information, see Creating a Font Database.

A Widths file contains all the information contained in your Configuration file (composition fonts and font maps, processing environment information, and character codes) as well as the information about the width of every character in every font identified in the Configuration file. CompuSet uses a Widths file to compose the document with the correct font metrics for the output device. You create a Widths file by supplying the Configuration file and your font database and running a batch file (xxxFWids.bat, where xxx is the name of the output formatter, such as AFP).

AFP Full Color Output

If you are producing AFP full color output, with full color data driven graphics, you need to have a secondary Widths file along with the one you create for regular AFP output. CompuSet uses the AFP Include Object (IOB) structured field to encapsulate a PostScript EPS file it generates for each data



driven graphic in your job. The encapsulated object passes through the output data stream intact to print successfully on the IBM full color printer. You can also use this technique to embed externally-created EPS files into your AFP output. Because CompuSet is passing an EPS through the output stream, it requires a secondary PostScript Widths file to manage the PostScript images.

Step 2: Create Your PDEF FilesA Page Definition (PDEF) file contains device-specific information used by an output formatter to create a print data stream to send to a printer, or other output device. You can use the Output Format Tools to create or update a PDEF file. Some common PDEF file options are:

• Page size

• Page orientation

• Tray pulls

• Multiple imposition (booklet creation or duplicate side-by-side printing)

• Multiple file output

• Document and image merging

• Document and image saving

• Color selection and mapping

• Shading selection

• Fonts

• Proofing setup

Not all options are supported for every output type. The Output Format Tool for your output type contains all the supported options. For more information, see Configuring Your PDEF File.



Step 3: Create Your Font Map FilesA font mapping object maps your input fonts to CompuSet font numbers. The font mapping object contains the location of the Widths file that defines the widths of all the fonts. The font mapping object also contains the location of the Font database that contains all the necessary font information.

The Font Mapping Utility

CompuSet supports AFP, metacode, PCL, PDF, and PostScript fonts. You can use the Font Mapping Utility to map the Windows fonts you use in your xPression design to the CompuSet fonts you use for production.

To map your fonts:

1. Double-click the CompuSet Tools desktop icon. The xPression CompuSet Tools appear.

Note: If you do not have the CompuSet Tools installed, you can install them from the installation CD. Click Custom for the install type, and select CompuSet Tools.

2. Double-click CompuSet Font Mapping Utility. The Browse for Folder dialog box appears.

3. Browse to locate the directory where you want to store your font mapping file. Click OK. The CompuSet Font Mappings dialog box appears, as shown in Figure 2 on page 27.



4. Select a Page Definition Language. CompuSet supports AFP, metacode, PCL, PDF, and PostScript.

5. Browse to locate the CompuSet Widths (.wids) file you want to use with this font mapping profile.

6. Select the CompuSet font that xPression should use when it finds an unmapped font. The default setting is none (a blank field).

Figure 2. CompuSet Font Mappings



7. Map your Windows design fonts to corresponding CompuSet production fonts:

– Click in the Available CompuSet fonts list for the Windows font that you want to map.

– Select a CompuSet font from the drop-down list.

8. Repeat Step 7 until you map all of your fonts.

9. Click OK.

Step 4: Define Your Font Definitions and Format DefinitionsIn xPression, your font information is defined at the administrative level. You need to use xPression Admin to define your font definitions and your format definitions.

A font definition contains the name of your font database if you have one (must be located on the server), the names of your primary and optional secondary Widths files (also located on the server), and the name of the font map (which can be located anywhere).

The xPression format definition contains all the information related to format, fonts, font mappings for a specific device, as well as other device-specific information. When you create a format definition using xPression Admin, you select the format of your output, the location of the PDEF file, and the name of a font mapping object.

xPression supports these output formats:

• MSOHTML

• HTML

• PDF

• PostScript

• AFP

• Metacode

• PCL



You may have multiple format definitions that define the same format (such as AFP). Each definition may differ in such things as font mappings, for example, because they are intended for different printers, which require different fonts.

Job Control FilesCompuSet uses job control files to perform many functions. When you publish to CompuSet with xPression, job control files are used to create your font databases and your Widths files. Before you run any job control files, it is important to initialize your environment variables. Each platform has a file designed to do this for you. On a Windows platform, you run the Cset32.bat file, on a UNIX platform, you run Csetinit.sh.

Windows PlatformsWhen you run the Cset32.bat file, it:

• Sets the following environment variables:

– CSET (high-level xPression CompuSet directory)

– OSYS (operating system)

– WRDTYP (word type)

– TEMP (temporary file directory)

• Adds the \\xPression\CompuSet\Run directory to the path.

Note: The installation program modifies Cset32.bat to contain the correct drive letter for the xPression CompuSet directory. For example, C:\Program Files\xPression\CompuSet.

Since the system variables reset themselves when you exit the command prompt, you should modify your Windows environment to include these variables. On Windows 2000, you can set the environment variables from the control panel.



All your batch files can be found on your client machine in \\Program Files\xPression\CompuSet\Run. There are also some job command files on the server, in the \\xPression\CompuSet directory.

As the input parameters for batch files vary, you should verify what parameters are required by viewing the batch file. Some batch files require only a file name, while others expect a file name and extension. It is always a good idea to read the header of a batch file for important information before you run it.

UNIX PlatformsWhen you run the Csetinit.sh file, it:

• Sets the following environment variables:

– CSET (high-level xPression CompuSet directory)

– OSYS (operating system)

– WRDTYP (word type)

– TEMP (temporary file directory)

• Adds the //xPression/CompuSet/Run directory to the path.

• Sets aliases for CompuSet.

CompuSet shell scripts are written in C shell, but you can readily modify them for Korn/Bourne shell use. The //xPression/CompuSet directory on your server contains the necessary shell scripts for use with xPression.

Logical Unit NumbersAll files referred to in job control files are specified by what are called logical unit numbers. These numbers provide the name and paths for both the input and output files required by CompuSet. The numbers vary by platform.



For example, in the following batch file excerpt:

echo FILE 2, %CSET%\system\%WRDTYP%\afp.wid,output widths file >>%TEMP%\afpf.tmpecho FILE 3, %CSET%\system\afpi.cnf,input config file >>%TEMP%\afpf.tmpecho FILE 7, %CSET%\system\afp.cnf ,output config file >>%TEMP%\afpf.tmpecho FILE 9, %CSET%\system\%WRDTYP%\afpi.wid ,input widths file >>%TEMP%\afpf.tmpecho FILE 10, %CSET%\system\%WRDTYP%\afp.fdb ,new/current FDB file >>%TEMP%\afpf.tmpecho FILE 11, %CSET%\system\%WRDTYP%\afpi.fdb ,old FDB file >>%TEMP%\afpf.tmpecho FILE 13, %TEMP%\fdb.tmp ,FDB scratch file >>%TEMP%\afpf.tmpecho FILE 25, %CSET%\system\%WRDTYP%\xicsmsg.mdb ,CompuSet mdb >>%TEMP%\afpf.tmp

File 2 specifies the output Widths file and File 10 specifies the new or current font database.

The following sections describe the logical unit numbers for the files found in the font database and Widths file related job control files.

FDB/Widths Processor Logical Unit Numbers

The following table contains the logical unit numbers used in the font database and the Widths file job control files.

Function Unit Name

UNIX/Windows

I/O

9700/2700/APS Input Font Tape SLUN 1 RO

New Widths File Output OLUN 2 R/W

Standard Input LUNI 5 RO

Standard Output/Log LOGU 6 WR

Config File Input FLUN 3 RO

Old Widths File Input XLUN 9 RO

Message Data Base MDBLUN 25 RO



WDPORT Processor Logical Unit NumbersThe following table contains the logical unit numbers used in the WDPORT job control files.

New Config File Output DLUN 7 WR

Postscript AFM Widths Input WLUN 8 RO

Typesetter Source Widths Input WLUN 8 RO

New/Current Font Data Base FNLUN 10 R/W

Old Font Data Base Input FILUN 11 RO

Font Load Output FJLUN 12 WR

9700/2700 Disk Font Input FHLUN 14 RO

9700/2700 Font Tape Output FTLUN 1 WR

9700/2700 Font Disk Output FDLUN 1 WR

AFP Font Input (non MVS) FHLUN 14 RO

FDB Scratch File FXLUN 13 R/W

PCL Font Scratch File FPLUN 15 RO

Function Unit Name

UNIX/Windows

I/O

Input Portable Widths Tape SLUN 1 RO

Input Portable Widths Disk SCLUN 13 RO

Input/Output Widths File FWDLUN 14 R/W

Function Unit Name

UNIX/Windows

I/O



File NamesJob control files follow a specific naming convention. Each file begins with a three letter output format designator. The designators are shown in the following table.

Font database job command files have their own naming convention. Along with the three letter output format designator, they also include fyyyy in the file name. The “f” denotes a function, and the yyyy names the function. For example, the Metfload file loads metacode fonts, the Afpfwids file creates an AFP Widths file, and the Pclflist file lists a PCL font database.

Output Portable Widths Tape OLUN 2 WR

Output Portable Widths Disk ONLUN 4 WR

Config File Output FLUN 3 WR

Standard Input LUNI 5 RO

Standard Output/Log LOGU 6 WR

Message Data Base MDBLUN 25 RO

Designator Output Format

Afp AFP

Met Metacode

Pcl PCL

Pdf PDF

Pst PostScript

Function Unit Name

UNIX/Windows

I/O



Using Job Control FilesYou may need to add parameters to a job control file before you actually run it.

To edit a job control file:

1. Open the file in a text editor (such as Notepad).

2. Add or change any necessary parameters.

3. Save the file.

4. Close the file.

After you configure the file for your job, you need to run it.

To run a batch file:

1. Click Start and Run. The Run dialog box appears.

2. Type cmd and click OK. The Windows command window appears.

Figure 3. Opening the Windows Command Window



3. Navigate to the \\xPression\CompuSet\Run directory. If you have not initialized your environment variables, run Cset32.bat.

4. Type your batch file name (with extension) and press ENTER. If don’t navigate to the batch file’s directory, you can type the path and the bath file name to run it.

Figure 4. Running Cset32.bat



Using Two Pass Functionality with xPressionYou can use CompuSet two pass functionality (the TWOP command) with xPression, but there are some things you need to know about how xPression supports it. Two pass functionality is enabled at the category level. By default, two pass is enabled for every category (and therefore, all the documents in the category). To turn two pass off, select the Generate only single-pass CompuSet commands (disables N of M) CompuSet conversion option for the category in xPression Admin.

You can’t control the size of the two pass buffers, as they are preset by xPression and unchangeable. Buffer 1 is full word size (4 bytes) and there are 1024 entries (elements) in it. Buffer 1 is reserved for page n of m numbering in Microsoft Word (the HTML to CompuSet conversion program uses this buffer). In addition, buffers 9 and 10 are set the same as buffer 1, and are available when embedding two pass PUTVAL and GETVAL commands in a document, using the insert custom CompuSet command function in xPression Design.

Two pass processing in xPression is done on a document by document basis. That is, xPression doesn’t make two passes of the entire job, but of each document as it's processed, so that limits the information you can gather with two pass to the content contained within the document boundary. That means that through xPression two pass processing, you can know, for example, the total number of pages in a document, but you can’t know the total number of pages in the entire job.


37

Chapter 3Creating Your Font Files

The CompuSet composition engine uses the font information found in a font database and Widths files to compose your xPression documents.

You must have your font databases and Widths files created and in place before you publish your document to CompuSet in xPression Design.


• How to Create and Configure Your Font Files

• Creating a Font Database

• Adding Fonts for AFP Output

• Adding Fonts for Metacode Output

• Adding Fonts for PCL Output

• Adding Fonts for PDF Output

• Adding Fonts for PostScript Output

• Moving Your Widths Files


Chapter 3 - Creating Your Font Files38

How to Create and Configure Your Font FilesCreating and configuring your font files is a multi-step process.

1. First, you must create your font database.

A font database is a random access file that resides on your xPression server and contains the fonts used to create your xPression documents. The font database file is platform-dependant, and therefore, not portable. You must recreate your font database on the new platform if you want to change platforms. A font database is required if you are embedding PDF fonts or downloading PCL, AFP, or PostScript fonts. A font database is required for all types of output if you are creating a new Widths file, or you are adding fonts to an existing Widths file.

For instructions on creating your font database, see Creating a Font Database.

2. Next, add fonts and configure your configuration files.

The FDB utility uses the Configuration file, a text file that can be viewed or edited, to create the Configuration/Widths file (or just Widths file). The Widths file contains the same information as the Configuration file, only in binary format for processing by CompuSet and the output formatters, as well as information about the width of every character in every font that is identified in the Configuration file. The Widths file contains all the information CompuSet and the output formatter needs for normal processing.

Document Sciences provides standard Configuration and Widths files that you can use as a starting point. You can add more fonts to the standard files, or you can use the Configuration files as-is to create your Widths files. These files are located on your client computer, in the \\Program Files\xPression\CompuSet\Font Definition directory.

Each output type has a different set of instructions for this step:

• Adding Fonts for AFP Output

• Adding Fonts for Metacode Output

• Adding Fonts for PCL Output



• Adding Fonts for PDF Output

• Adding Fonts for PostScript Output

Caution: You should exercise extreme caution when converting TrueType fonts for use with any of the supported emitters. If the widths or font metrics of the converted font do not match the information in the widths file, you may experience character alignment problems in your output.

Creating a Font DatabaseThe first step is to initialize your font database using the xxxfinit job. The xxx in the file name is the three character code for the desired output stream:

• Afpfinit creates an AFP font database

• Metfinit creates a metacode font database

• Pclfinit creates a PCL font database

• Pdffinit creates a PDF font database

• Pstfinit creates a PostScript font database

These job files are located in the \\Program Files\xPression\CompuSet\Run directory on your client machine. We also provide sample PCL and PDF font databases (.fdb) that you can use as a starting point when creating your own. They are also located on your client machine in the \\Program Files\xPression\CompuSet\Font Definition directory.

Run the xxxfinit job for your output type.

Next, open and review the xxxfinit.log file. The xxx in the file name is the three character code for the desired output stream. This file is located in following directory:\\Program Files\xPression\CompuSet\Log

Ensure that all of the operations were successful and that the initialization job created an empty file.



Adding Fonts for AFP OutputThe standard AFP Configuration and Widths files, AFP.cnf and AFP.wid, are located on both your server and client xPression directories.

Step One: Backup Existing Configuration and Widths FilesMake a backup of the existing Configuration and Widths files and rename the backup copy as follows:

• Rename the AFP.cnf backup copy to AFPi.cnf

• Rename the AFP.wid backup copy to AFPi.wid

These files are located in both your server and client directories. These configuration and widths files must eventually be placed on the server, so Document Sciences recommends working with the server version of these files. On the client, you can find these files at the following location: \\Program Files\xPression\CompuSet\Font Definition\

On the server, you can find these files at the following location: <xPressionHome>\xPression\CompuSet\Font Definition\

Caution: Always make your configuration changes in the copy of file with the "I" (input) appended to the original file name. Never change or edit the original files.

Step Two: Edit Configuration FileYou need to add fonts to your configuration file. Open AFPi.cnf for editing and add the MFNT Entries, EFNT Entries, and SIZE Entries. When you’ve added all your entries, save the file. This may seem like a lot of work, but it will go faster after you see the pattern of how every EFNT and MFNT has or references an index number.

Note: When updating your font database, keep in mind that font name entries are case sensitive.



MFNT Entries

Find the section in AFPi.cnf that starts with MFNT. After you have found this section, go to the last MFNT entry. It should look like this:

MFNT 324,X04510JC,T1V10500,C04500J0,20.00

Start adding fonts after this entry. Enter the coded font name, code page, character set and point size for any fonts that you would like to add. Provide an MFNT index number for each of these names. Since MFNT 324 is the last index number used, the next index number will be 325. For the complete syntax and list of parameters for MFNT, see MFNT - Machine Font Definition.

Create an MFNT entry for each point size you want to add. Usually start with the smallest size that you want to add and work to the largest for every font family. The point sizes that can be added are controlled by the SIZE command that is found near the top of the Configuration file. There can be a maximum of 16 different point sizes in any Configuration file.

Example

To add a 10-point font with a coded font name of X0C12804, the next line of the MFNT section in the Configuration file would look like this:

MFNT 325, X0C12804,T1C112804,C0C12804, 10.0, 0

Where:

• X0C12804 is the coded font name.

• T1C12804 is the code page.

• C0C12804 is the character set.

• 10.00 is the point size.

• 0 is the type (0=bounded box, 1=unbounded).



FNAM Entries

You will also need to add an FNAM comment. The FNAM comment is used to display the font family name when you set up your font mapping within the CompuSet font mapping utility. Each font family defined needs to have an FNAM command. Use the number that you specified in the MFNT/FONT command for p1 of each new FNAM entry. The third parameter is used to indicate if the font is a serif font (0) or a sans serif font (1).

Each font family defined needs to have an FNAM command.

Example

FNAM 8, 'Courier' ,1,FNAM 9, 'font name' ,0,

EFNT Entries

You must also add the EFNT entries to Afpi.cnf. These entries are found near the top of the file. Look for the following section:

EFNT 8, 7, 301, 302, 303, 304, , CourierEFNT 8, 10, 309, 310, 311, 312, ,EFNT 8, 12, 313, 314, 315, 316, ,EFNT 8, 14, 317, 318, 319, 320, ,EFNT 8, 20, 321, 322, 323, 324, ,

Add a group of EFNT entries for each font family. In the example above, the font family Courier has been assigned to EFNT number 8. For the complete syntax and list of parameters for EFNT, see EFNT - Define Raster Font Correlation.



Example

To add a new font family to EFNT number 9:

* XXXXX FONT (An " * " followed by three spaces denotes a comment)* EFNT 9, 10, 325,325,325,325,, 128 Bar-code

Notice the point size (10) is indicated after the 9. The other numbers, 325 in this case, have to do with the MFNT index numbers that you added for each point size. Notice that 325 is in all four locations. This may not be your case. In this example, there are no Bold, Italic, or Bold Italic fonts, so you apply Regular in each case.

If there were different specific fonts for each type, the line might look like this:

EFNT 9, 10, 326,327,328,329,,, 128 Garamond

EFNT is set up as follows:

EFNT font #, point size, MFNT # for light roman, MFNT # for light italic, MFNT # for bold roman, MFNT # for bold italic,comment

You would then add additional EFNT entries as needed for each point size.

SIZE Entries

For each font you add to Afpi.cnf, there must be an entry for that font size in the SIZE command. The SIZE command is near the top of the file and is limited to 16 parameters. Therefore, for each Configuration file, only 16 font sizes are allowed. If a new font is added using the above steps, the SIZE command will need to reflect this addition if the point size does not currently exist. For the complete syntax and list of parameters for SIZE, see SIZE - Point Sizes Available.



Example

To add a 16-point font, the SIZE command would change from:

SIZE 4, 5, 6, 7, 8, 9, 10, 11, 12, 14, 18, 24,

To:

SIZE 4, 5, 6, 7, 8, 9, 10, 11, 12, 14, 16, 18, 24,

FNSZ Entries

If you are using unbounded fonts, you also need to add FNSZ Entries to Afpi.cnf. Unbounded fonts require separate fonts for each different character rotation, and the FNSZ command provides this information in the Configuration file. Because all the core fonts are bounded box, the default Configuration file does not contain FNSZ entries. If you are using bounded box fonts, proceed to the next step.

An FNSZ entry has the following format:

FNSZ 1,X1CR59, X2CR59, , X4CR59,

The portrait font name (X1CR59) for FNSZ 1 should match the portrait font name for MFNT 1. These index numbers should always match. In the above example, MFNT 1 might look like this:

MFNT 1, X1CR59, T1V10500, C1S0CR15, 8.00, 1,

In addition to adding the portrait font name to the FNSZ 1 line, add the landscape and inverse landscape font names, if they are available. For the complete syntax and list of parameters for FNSZ, see FNSZ - Font Number, Size and Orientation.



Note: The inverse portrait rotation does not exist for unbounded fonts.

The format of the line and an example follow:

FNSZ index #, portrait name, landscape, , inverse landscape

FNSZ 1,X1CR59, X2CR59, , X4CR59,

Where:

• X1CR59 is the portrait name

• X2CR59 is the landscape name

• X3CR59 is the inverse landscape name

You will have to add an FNSZ for each unbounded box MFNT that you added.

Step Three: Edit Font LoaderEdit Afpfload.bat (.sh for UNIX or Linux) by making the necessary changes to reflect the location of the files you are trying to access by changing paths where appropriate. Submit a set of commands for updating files like the following:

UPDT -666, UPDATING EXISTING FDBMACH 13, MACHINE = AFPAEXT ,,.CS3,SPECIFY EXTENSION (FOR 300 DPI CHARACTER SETS)“APTH %CSET%\fonts\afp”, AFP FONTS DIRECTORYLOAD 1,1,,,, LOAD FONT FROM DISK FILELIST 0,, LIST ALL FONTS IN FDB

This will load the fonts from the disk file and update the current FDB (and produce a log file with a listing of the fonts that were loaded).



Make sure the path in the APTH command is surrounded by double quotes if there are spaces in the path name. Ensure you place double-quotes (“) around the path specified in the APTH command.

Step Four: Run Font LoaderFirst, make a backup copy of Afp.fdb.

Next, run the Afpfload job file to load fonts into your font data base. When completed, check the Afpfload.log file located in \\Program Files\xPression\CompuSet\Log

Step Five: Edit Afpfwids.batChange the options section of Afpfwids.bat (.sh for UNIX or Linux) as shown here:

MACH 13, MACHINE=AFPWIDS 0,1,1,GENERATE NEW WIDTHS FILECONF 0,GENERATE NEW CONFIG FILE

Step Six: Run Afpfwids.batRun the Afpfwids.bat (.sh for UNIX or Linux) job file. When completed, check the Afpfwids.log file located in \\Program Files\xPression\CompuSet\Log

Step Seven: Verify ChangesCheck the new configuration file to verify that the fonts you defined were added to the Widths file.

Adding Fonts for Metacode OutputThe standard Metacode Configuration and Widths files, x9700M.cnf and x9700M.wid, are located on both your server and client xPression directories.



Step One: Backup Existing Configuration and Widths Files

Make a backup of the existing Configuration and Widths files and rename the backup copy as follows:

• Rename the x9700M.cnf backup copy to x9700i.cnf

• Rename the x9700M.wid backup copy to x9700i.wid



Caution: Always work in the copy of file with the "I" (input) appended to the original file name. Never change or edit the original files.

Step Two: Edit Configuration FileEdit the X9700Mi.cnf file to add fonts to your Configuration file. You will need to add MFNT Entries, FNSZ Entries, EFNT Entries, FNAM Entries, and SIZE Entries to the file. When you have added all the entries, save the file. This may seem like a lot of work, but it will go faster after you see the pattern of how every EFNT, MFNT, FNSZ has or references an index number.

MFNT Entries

Find the section in X9700Mi.cnf that starts with MFNT. After you have found this section, go to the last MFNT entry. It should look like this:

MFNT 265,AB4FOP, 24.0, 83, 33, 1, 116, 13, 13, 11, 11,



Start adding fonts after this entry. Enter the portrait font name and point size for any fonts that you would like to add. Provide a MFNT index number for each of these names. Since MFNT 265 is the last index number used, the next index number will be 266. For the complete syntax and list of parameters for MFNT, see MFNT - Machine Font Definition.

Follow these steps for every point size and portrait font that you want to add. Usually start with the smallest size that you want to add and work to the largest for every font family. The point sizes that can be added are controlled by the SIZE command that is found near the top of the Configuration file. There can be a maximum of 16 different point sizes in any Configuration file.

Example

To add a 10-point font with a portrait name of Z299PP, the next line of the MFNT section in the Configuration file would look like this:

MFNT 266, Z299PP, 10.0,

You do not need to worry about any of the additional numbers appearing after the point sizes. These are system-generated numbers that you will not have to add. The Configuration file would now look like this:

MFNT 265, AB4FOP, 24.0, 83, 33, 1, 116, 13, 13, 11, 11,MFNT 266, Z299PP, 10.0,

FNSZ Entries

After adding all of the MFNT entries you want to X9700Mi.cnf, move to the bottom of the file and start on the FNSZ entries. Look for the following line:

FNSZ 265,AB4FOP,AB4FOL,AB4FOI,AB4FOJ, 207.44, 226.97, 200.04, 239.88,

Notice that the portrait font name (AB4FOP) for FNSZ 265 matches the portrait font name for MFNT 265. These index numbers should always match. For the complete syntax and list of parameters for FNSZ, see FNSZ - Font Number, Size and Orientation.



In the above example, because MFNT 266 has been added, a line for FNSZ 266 needs to be added. It will look like this:

FNSZ 266, Z299PP,

In addition to adding the portrait font name to the FNSZ 266 line, add the landscape, inverse portrait, and inverse landscape font names, if they are available. The format of the line and an example follow:

FNSZ index #,portrait name, landscape, inverse portrait, inverse landscape

FNSZ 266, Z299PP,Z299PL,Z299PI,Z299PJ,

As with the MFNT commands, additional parameters to FNSZ are system generated. You will have to add an FNSZ for every MFNT that you added. If you do not have all of the rotations of the font, leave a blank parameter for the rotation that you are missing.

EFNT Entries

The next step is to add the EFNT entries to X9700Mi.cnf. These entries are found near the top of the file. Look for the following section:

* OPTIMAEFNT 22, 6, 214, 227, 240, 253, , 6 POINTEFNT 22, 7, 215, 228, 241, 254, , 7 POlNTEFNT 22, 8, 216, 229, 242, 255, , 8 POINT

Add a group of EFNT entries for each font family. In the example above, the font family Optima has been assigned to EFNT number 22. Add additional EFNT entries as needed for each point size. For the complete syntax and list of parameters for EFNT, see EFNT - Logical User Font.



EFNT is set up as follows:

EFNT font #,point size, MFNT # for light roman, MFNT # for light italic, MFNT # for bold roman, MFNT # for bold italic,,comment

Example

*XXXXX FONT (* equals text that follows is a comment)*EFNT 23, 10, 266,266,266,266,,, 10 POINT

Notice the point size (10) is indicated after the 23, as well as commented at the end. The other numbers, 266 in this case, have to do with the MFNT index numbers that you added for each point size. Notice that 266 is in all four locations. This may not be your case. In this example, there are no fonts specifically for Bold, Italic, or Bold Italic, so Regular is applied in each case. If there were different specific fonts for each type, the line might look like this:

EFNT 23, 10, 266,267,268,269,,, 10 POINT

FNAM Entries


You will need to add an FNAM command for each font family defined in X9700i.cnf.

Example

FNAM 22, 'Optima', 0FNAM 23, 'font name' ,0,



For the complete syntax and list of parameters for FNAM, see FNAM - Font Names for Viewing.

Some of the fonts may be subsetted. That is, the size of the font, in printer memory, is too large to fit on one printer memory board. Therefore, the font is split. What you get is some of the letters of a particular point size of a font in one font name and the remaining letters of the same point size in another font name. When this happens, use the CMAP tables that are in the Configuration file. Please check with your font supplier to see if any of the fonts that you are adding are subsetted. If they are, contact your Document Sciences Representative.

SIZE Entries

For each font added in X9700i.cnf, there must be an entry for that font size in the SIZE command. The SIZE command is near the top of the file and is limited to 16 parameters. Therefore, for each Configuration file, only 16 font sizes are allowed. If a new font is added using the above procedures, the SIZE command will need to reflect this addition if the point size does not currently exist. For the complete syntax and list of parameters for SIZE, see SIZE - Point Sizes Available.

Example

To add a 16-point font, the SIZE command would change from:

SIZE 4, 5, 6, 7, 8, 9, 10, 11, 12, 14, 18, 24,

to:

SIZE 4, 5, 6, 7, 8, 9, 10, 11, 12, 14, 16, 18, 24,

Step Three: Run Font LoaderFirst, make a backup copy of x9700.fdb.

Next, run the Metfload job file to load fonts into your font data base. When completed, ensure the fonts were loaded by checking the Metfload.log file located in \\Program Files\xPression\CompuSet\Log



Step Four: Run Metfwids.batUpdate the Widths file and create a new Configuration file by running the metfwids.bat (.sh for UNIX or Linux) job file. When completed, ensure the fonts were successfully added to the widths file by checking the metfwids.log file located in \\Program Files\xPression\CompuSet\Log

Step Five: Verify ChangesCheck the new configuration file to verify that the fonts you defined were added to the Widths file. When viewing the new Configuration file, the same entries as those entered in the input version for MFNT and FNSZ commands will have additional parameters added.

Adding Fonts for PCL OutputThe standard PCL Configuration and Widths files, Pcl.cnf and Pcl.wid, are located on both your server and client xPression directories.

Do I need to use the Font Converter?If you plan to add a non-printer-resident font to your PCL Widths file, then you will need to use the Document Sciences-provided Font Converter to generate a tagged font metric (.tfm) and soft font (.sft or .sfs) version of your Intellifont (.typ) or TrueType (.ttf) font. The tagged font metric file is used by FDB for font information to be placed in the Widths file. The soft font is the printer-recognizable font which is downloaded to the printer and used for output when a non-printer-resident font is called in a job. For more information, see PCL Font Converter.

If you plan to add a printer-resident font to your PCL Widths file, then you do not need to use the Font Converter; you should already have the HP-supplied tagged font metric files for the fonts on your printer.





• Rename the Pcl.cnf backup copy to Pcli.cnf

• Rename the Pcl.wid backup copy to Pcli.wid




Step Two: Create Font ListCreate a list of fonts to be added to the font database.

If adding non-printer-resident fonts:

1. Copy your tagged font metric and soft font files into \\Program Files\xPression\Fonts.

2. Open the command prompt. Type the following to redirect the names of the tagged font metric and soft font files to a file called fonts.lst (specified in the Pclfload and Pclfloudu job command files):cd \Program Files\xPression\Fontsdir /b *.tfm > fonts.lstdir /b *.sf? >> fonts.lst



3. Verify that fonts.lst is a listing of only the names of all the tagged font metric and soft font files that were generated by the Font Converter.

If adding printer-resident fonts:

1. Copy your tagged font metric files into \\Program Files\xPression\Fonts.

2. Open the command prompt and type:cd \Program Files\xPression\Fontsdir /b *.tfm > fonts.lst

If you installed to a directory other than the default directory, your paths may differ from the ones specified above.

Step Three: Edit Configuration FileEdit the Pcli.cnf file to add fonts to your Configuration file. You will need to add MFNT Entries, NOLD Entries, FONT Entries, FNAM Entries, and SIZE Entries to the file. When you have added all the entries, save the file. This may seem like a lot of work, but it will go faster after you see the pattern of how every EFNT, MFNT, FNSZ has or references an index number.

When updating your font database, keep in mind that font name entries are case sensitive.

MFNT Entries

Find the section in Pcli.cnf that starts with MFNT. After you have found this section, go to the last MFNT entry. It should look like this:

MFNT 62,MCourierNewBdIt,19U ,16387, 120,1,0,1,0,0,

There must be an MFNT entry for each physical font available for the typeface. Only p1-p3 of the MFNT command need to be specified; p4-p10 are generated by the system during the FDB run to create the new Widths file. Use the next logical number in the sequence for p1; for printer-resident fonts, use the



HP-given name of the printer font for p2 and p3. PCL fonts are scalable, so you do not need to add font names for each point size. Simply add one font name for each font family. For the complete syntax and list of parameters for MFNT, see MFNT - Machine Font.

Example

To add a 10-point font with a portrait name of ArialNarrow, the next line of the MFNT section in the Configuration file would look like this:

MFNT 63, ArialNarrow, 19U,

NOLD Entries

Make a NOLD entry for each MFNT added to specify whether the font is printer-resident or it is to be downloaded. For the complete syntax and list of parameters for NOLD, see NOLD - Font Location (Resident or Downloaded).

Example

NOLD 5, 1,

FONT Entries

FONT entries define all the typesetter physical fonts that comprise a typeface as one user-level font to be accessed in CompuSet by a single user font index. A user font consists of all the physical fonts required to make up all the subsets, size ranges, and stresses (light, italic, bold, bold italic) for a single typeface. Use the next logical number in the sequence for p1 of each new FONT entry. p2-p5 correspond to the MFNT entries made above. For the complete syntax and list of parameters for FONT, see FONT - Define User Font Correlation.



Example

FONT 5, 1, 2, 3, 4, , M ARIAL

Note: If you have one font for a font family, use the same font index for parameters 2-5 to avoid getting a system error message when you call for a face which is not defined. You will not get all four faces, you will get only the face you actually have.

FNAM Entries


You will need to add an FNAM command for each font family defined in Pcli.cnf. Use the next logical number in the sequence for p1 of each new FNAM entry.

Example

FNAM 22, 'Optima', 0FNAM 23, 'font name' ,0,

For the complete syntax and list of parameters for FNAM, see FNAM - Font Names for Viewing.

SIZE Entries

The SIZE command represents the maximum point size supported by CompuSet. For the complete syntax and list of parameters for SIZE, see SIZE - Point Sizes Available.

Example

SIZE 327, , , , , ,



Step Four: Edit Font LoaderEdit the paths in the Pclfload.bat (.sh for UNIX or Linux) file as needed. For example, you may want to define the location of the log file. Make sure that the pclfload file points to the fonts.lst file that you created earlier listing the fonts to be added, and that the APTH command in the .bat file points to the directory where the font files reside. APTH is the path to the font files that are listed in the file you created. Ensure you place double-quotes (“) around the paths specified in the APTH command.

Step Five: Run Font LoaderFirst, make a backup copy of Pcl.fdb.

Next, run the Pclfload job file to load fonts into your font data base. When completed, ensure the fonts were loaded by checking the Pclfload.log file located in \\Program Files\xPression\CompuSet\Log

Step Six: Run Pclfwids.batUpdate the Widths file and create a new Configuration file by running the pclfwids.bat (.sh for UNIX or Linux) job file. When completed, ensure the fonts were successfully added to the widths file by checking the pclfwids.log file located in \\Program Files\xPression\CompuSet\Log

Step Seven: Verify ChangesCheck the new configuration file to verify that the fonts you defined were added to the Widths file. When viewing the new Configuration file, the same entries as those entered in the input version for MFNT commands will have additional parameters added.

Adding Fonts for PDF OutputThe standard PDF Configuration and Widths files, Pdfiso.cnf and Pdfiso.wid, are located on both your server and client xPression directories.





• Rename the Pdfiso.cnf backup copy to Pdfisoi.cnf

• Rename the Pdfiso.wid backup copy to Pdfisoi.wid




Step Two: Edit Configuration FileEdit the Pdfi.cnf file to add fonts to your Configuration file. You will need to add MFNT Entries, FONT Entries, and FNAM Entries to the file. When you have added all the entries, save the file.

MFNT Entries

Find the section in Pdfi.cnf that starts with MFNT. After you have found this section, go to the last MFNT entry. It should look similar to this:

MFNT 39, ZapfDingbats1, 0, 0, 0, 0, 0

Start adding fonts after this entry. Enter the font name, which is different for each face, while providing an MFNT index number for each of these names. Enter the font type (italic or roman) and the character



layout index. (Fill in parameters 1-4 and 7-8 for this command, parameters 5-6 will be filled in by the system.) For the complete syntax and list of parameters for MFNT, see MFNT - Machine Font Definition.

Example

To add the GARAMOND font, the next lines of the MFNT section in the configuration file would look like this, if you are using all four font faces:

MFNT 40, Garamond-Light, 1, 1,,,0,1,,MFNT 41, Garamond-Light Italic , 0, 1,,,0,1,,MFNT 42, Garamond-Bold, 1, 1,,,0,1,,MFNT 43, Garamond-Bold Italic , 0, 1,,,0,1,,

Parameter 8 must be set to option 1 if you are going to embed the font in the PDF.

Note: Each face is a separate font.

FONT Entries

Find the DEFINE USER FONTS section in Pdfisoi.cnf, which starts with FONT.

FONT entries define all the typesetter physical fonts that comprise a typeface as one user-level font to be accessed in CompuSet by a single user font index. A user font consists of all the physical fonts required to make up all the subsets, size ranges, and stresses (light, italic, bold, bold italic) for a single typeface. For the complete syntax and list of parameters for FONT, see FONT - Define Font Correlation.

Go to the last FONT entry. It should look like this:

FONT 20, 37, 37, 37, 37,,SYMBOL

Add a FONT entry for each family of four faces. For the above example you would have:

FONT 21, 40, 41, 42, 43,,GARAMOND



In the previous example, the Garamond font family has been assigned to the FONT number 21, with 40,41,42,43 corresponding to the different font faces defined by the MFNT's above.

Note: If you have one font for a font family, use the same font index for parameters 2-5 to avoid getting a system error message when you call for a face which is not defined. You will not get all four faces, you will get only the face you actually have.

Example

If you have only one font (face=light), then you would enter:

FONT 21, 40, 40, 40, 40,GARAMOND

FNAM Entries


Add an FNAM entry for each font in Pdfisoi.cnf. The FNAM entries can be found in the ASSIGN NAMES TO FONT ENTRIES FOR PC PROOFER section. This command maps the Windows font to the actual font (font number to the font name). For the complete syntax and list of parameters for FNAM, see FNAM - Font Names for Viewing.

Go to the last FNAM entry which should look like this:

FNAM 20,'SYMBOL',0,



For our example, you would need to add:

FNAM 21,'ITC-GARAMOND',0,

Note: The third parameter is used to indicate if the font is a serif font (0) or a sans serif font (1).

Step Three: Create Font ListIn order to embed fonts in your PDF, you will need to use the following method of loading fonts.

1. Create a file named list.txt in the following directory: \\Program Files\xPression\Fonts\PDF\

2. In this file, create a list of all of the fonts that you want to load into the font database. The list will look something like this:

0, U003003T.AFM

0, U003004T.AFM

0, U003006T.AFM

0, U003008T.AFM

2, U003003T.PFB

2, U003004T.PFB

2, U003006T.PFB

2, U003008T.PFB

2, HIERC___.PFB

0, HIERC___.AFM

2, HIERD___.PFB

0, HIERD___.AFM

2, HIERP___.PFB

0, HIERP___.AFM



The first parameter is the type of file; the second parameter is the filename. The file types defined in the created input file are:

– 0 = A text file with Adobe font Metrics (AFM). Use AFM if you are embedding your fonts.

– 1 = A text file with Adobe Type 1 fonts (PFA)

– 2 = A binary sequential file with Adobe Type 1 fonts in PFB format

– 3 = A binary sequential file with PostScript font metrics in PFM. Do not use PFM if you are embedding your fonts.

Note: Note: If you are embedding the font, then you will need both the font metrics (afm or pfm) and the font itself (pfb or pfa). If you are not embedding the font, then you will need only the font metrics.

Caution: PFM files do not contain bounding box information. If you load PFM files into the font database instead of AFM files, you may get errors when opening a document in Acrobat Reader such as the following: The font ‘name of font’ contains a bad /BBox. To avoid such errors, load AFM files into FDB.

Step Four: Edit Font LoaderEdit Pdffload.bat (.sh for UNIX or Linux). Make sure that the paths and filenames are correct. The commands, for Pdffload.bat (.sh for UNIX or Linux), should look something like this:

UPDT -666,,, IN-PLACE UPDATEMACH 14, MACHINE = PDF/POSTSCRIPTAPTH “%CSET%\fonts\pdf”LOAD 1,2,,,1,, LOAD FONT METRICS INTO FDBLIST 0,, LIST ALL FONTS IN FDB

Parameter 2 of the LOAD command should be a 1 if the font is not going to be embedded and it should be a 2 if the font is an ISO Latin 1 font. If you are not embedding, but still need to access an ISO Latin 1 font, use p2=2. p2=2 should be the default for all customers. Use the MFNTs in your configuration file to choose which character set you want to access.



APTH is the path to the font files that are listed in the file you created. There can be multiple paths. Use APTH commands if the fonts are not all in the same directory. Ensure you place double-quotes (“) around the paths specified in the APTH command.

Step Five: Run Font LoaderFirst, make a backup copy of Pdf.fdb.

Next, run Pdffload.bat (.sh for UNIX or Linux) to load fonts into your font database.

To ensure the fonts were loaded properly, check the log file for errors.

Step Six: Load Fonts Into the Width/Configuration FileEdit Pdffwids.bat (.sh for UNIX or Linux). Make sure that the paths and filenames are correct. The commands should look something like this:

MACH 14, MACHINE = PDF/POSTSCRIPTWIDS 0,1,1, GENERATE NEW WIDTHS FILECONF 0, GENERATE NEW CONFIG FILE

Run Pdffwids.bat.




Three Issues with PDF OutputPlease ensure you are familiar with the following issues:

1. You may need to enter multiple FONT and MFNT entries to handle all of the standard and Iso-Latin characters.

2. If you plan to embed Iso-latin character sets in a PDF document, you may want to use only the MFNT entries for the Iso-latin characters in your FONT commands for this family. You may experience problems with mixing character types.

3. You need to set the MFNT p7 parameter differently for standard PostScript encoding or Iso-Latin encoding. Please see MFNT - Machine Font Definition for more information.

Adding Fonts for PostScript OutputThe standard postscript Configuration and Widths files, Postiso.cnf and Postiso.wid, are located on both your server and client xPression directories.



• Rename the Postiso.cnf backup copy to Postisoi.cnf

• Rename the Postiso.wid backup copy to Postisoi.wid






Step Two: Edit Configuration FileEdit the file Postisoi.cnf to add fonts to your Configuration file. You will need to add MFNT Entries, FONT Entries, and FNAM Entries. to the file. When you have added all the entries, save the file.

MFNT Entries

Find the section in Postisoi.cnf that starts with MFNT. After you have found this section, go to the last MFNT entry. It should look like this:

MFNT 39, ZapfDingbats1, 0, 0, 0,

Start adding MFNT commands after this entry. Enter an MFNT index number each font followed by the font name. A separate MFNT entry must be made for each stress used (light, italic, bold, and bold-italic). Fill in parameters 1-4; parameters 5-6 will be filled in by the system. For the complete syntax and list of parameters for MFNT, see MFNT - Machine Font Definition.

Example

To add the Garamond font, the next lines of the MFNT section in the configuration file would look like this:

MFNT 40, Garamond-Light , 1, 1,,,MFNT 41, Garamond-Lightltalic , 0, 1,,,MFNT 42, Garainond-Bold , 1, 1,,,MFNT 43, Garamond-Boldltalic , 0, 1,,,



FONT Entries

Find the FONT section in Postisoi.cnf. FONT entries correlate to logical user fonts in CompuSet. A user font consists of all the physical fonts required to make up all the subsets, size ranges, and stresses (light, italic, bold, bold italic) for a single typeface. For the complete syntax and list of parameters for FONT, see FONT - Define Font Correlation.

Go to the last FONT entry. It should look like this:

FONT 20, 37, 37, 37, 37,,SYMBOL

Add a FONT entry for each family of four faces. For the above example you would have:

FONT 21, 40, 41, 42, 43,,GARAMOND

The Garamond font family has been assigned to the FONT number 21, with 40,41,42,43 corresponding to the different font faces defined by the MFNT's above.

Note: If you have one font for a font family, use the same font index for parameters 2-5 to avoid getting a system error message when you call for a face which is not defined. You will not get all four faces, you will get only the face you actually have. For example, if you have only one font (face=light), then you would enter:

FONT 21, 40, 40, 40, 40,GARAMOND

FNAM Entries




Add an FNAM entry for each font in Post.cnf. FNAM entries can be found in the ASSIGN NAMES TO FONT ENTRIES FOR PC PROOFER section. This command allows the user to map the actual font (font number to the font name) to a Windows font for proofing. For the complete syntax and list of parameters for FNAM, see FNAM - Font Names for Viewing.

Go to the last FNAM entry which should look like this:

FNAM 20,'SYMBOL',0,

For our example, you would need to add

FNAM 21,'ITC-GARAMOND',0,

Step Three: Create Font ListFirst, make a backup copy of Post.fdb. In order to embed fonts in your PDF, you will need to use the following method of loading fonts.

1. Create a file named list.txt in the following directory: \\Program Files\xPression\Fonts\Ps\

2. In this file, create a list of all of the fonts that you want to load into the font database. The list will look something like this:

0, U003003T.AFM

0, U003004T.AFM

0, U003006T.AFM

0, U003008T.AFM

2, U003003T.PFB

2, U003004T.PFB

2, U003006T.PFB

2, U003008T.PFB

2, HIERC___.PFB

0, HIERC___.AFM



2, HIERD___.PFB

0, HIERD___.AFM

2, HIERP___.PFB

0, HIERP___.AFM

The first parameter is the type of file; the second parameter is the filename. The file types defined in the created input file are:

– 0 = A text file with Adobe font Metrics (AFM). Use AFM if you are embedding your fonts.

– 1 = A text file with Adobe Type 1 fonts (PFA)

– 2 = A binary sequential file with Adobe Type 1 fonts in PFB format

– 3 = A binary sequential file with PostScript font metrics in PFM. Do not use PFM if you are embedding your fonts.

Note: If you are embedding the font, then you will need both the font metrics (afm or pfm) and the font itself (pfb or pfa). If you are not embedding the font, then you will need only the font metrics.

Step Four: Edit Font LoaderEdit Pstfload.bat (.sh for UNIX or Linux). Make sure that the paths and filenames are correct. The commands, for Pstfload.bat (.sh for UNIX or Linux), should look something like this:

UPDT -666,,, IN-PLACE UPDATEMACH 14, MACHINE = PDF/POSTSCRIPTAPTH %CSET%\fonts\pdfLOAD 1,2,,,1,, LOAD FONT METRICS INTO FDBLIST 0,, LIST ALL FONTS IN FDB

Parameter 2 of the LOAD command should be a 1 if the font is not going to be embedded and it should be a 2 if the font is an ISO Latin 1 font. If you are not embedding, but still need to access an ISO Latin 1 font, use p2=2. p2=2 should be the default for all customers. Use the MFNTs in your configuration file to choose which character set you want to access.



APTH is the path to the font files that are listed in the file you created. There can be multiple paths. Use APTH commands if the fonts are not all in the same directory. Ensure you place double-quotes (“) around the paths specified in the APTH command.

Step Five: Run Font LoaderFirst, make a backup copy of Pst.fdb.

Next, run Pstfload.bat (.sh for UNIX or Linux) to load the fonts into your font database.

Check the log file for errors.

Step Six: Load Fonts Into the Width/Configuration FileEdit Pstfwids.bat (.sh for UNIX or Linux). Make sure that the paths and filenames are correct. The commands should look something like this:

MACH 14, MACHINE = PDF/POSTSCRIPTWIDS 0,1,1, GENERATE NEW WIDTHS FILECONF 0, GENERATE NEW CONFIG FILE

Run Pstfwids.bat.




Three Issues with PDF OutputPlease ensure you are familiar with the following issues:

1. You may need to enter multiple FONT and MFNT entries to handle all of the standard and Iso-Latin characters.

2. You need to set the MFNT p7 parameter differently for standard PostScript encoding or Iso-Latin encoding. Please see MFNT - Machine Font Definition for more information.

Moving Your Widths FilesWidths files are platform dependent, therefore, to move them to a platform different from the one that they were created on, you must use the WDPORT Utility. WDPORT imports and exports Widths files from one platform to another. You can store the file on tape or disk, or use a file transfer process to copy the file to the destination host.

You must have the WDPORT Utility installed on both the source and the destination host. WDPORT runs on the source host to export a Widths file to an output file. WDPORT runs on the destination host to import the new file and convert it into a Widths file that is compatible with that host.

For example, you may want the Widths file located on your Windows platform, where you will be designing your document, but the Widths file currently resides on the production platform.

To move the Widths file from the production platform to your Windows platform:

1. Export the Widths file on the production platform by running the Wdexport job file to create a portable, platform-independent version of the Widths file.

2. Binary FTP the file to your Windows platform.Import the portable Widths file on the Windows platform by running Wdimport.bat (.sh for UNIX or Linux). Wdimport also creates a Configuration file while importing the Widths file.


71

Chapter 4Configuring Your PDEF File

When you publish to CompuSet, xPression uses PDEF files to determine the format and other specific characteristics of your output. PDEF files define such characteristics as page size, what type of color is to be used (no color, highlight color, or full color), and whether the document is to be produced in a booklet format.

Before you publish your document to CompuSet, you must configure a PDEF file with your output options. The Output Format Tool enables you edit or create a PDEF file to specify those characteristics as output options for your job.

This chapter includes these topics:

• What Can I Specify in my PDEF File? • Fonts

• The Output Format Tool • Proofing

• Page Setup • PDF Encryption Setup

• Index Settings • Output Options

• Special Document Type • Print Job Reporting

• Document Merge • Printer-Specific Settings

• Document Save • Emitter Log

• Content Repository Setup • Embedding Tag Logical Elements (TLEs) in Your AFP Output File

• Color


Chapter 4 - Configuring Your PDEF File72

What Can I Specify in my PDEF File?Output format options are stored in the PDEF file, and are printer-specific. This means you can create a PDEF file for each printer you use, and then select the appropriate PDEF file by selecting the Format Definition that contains it. For more information, see Step 4: Define Your Font Definitions and Format Definitions.

There are many options that you can define to control the way your output looks. The available options vary between the different output types. The following table shows what is supported for each output type. To select these options, see The Output Format Tool.

Option AFP Metacode PCL PDF PostScript

AFP Indexing Yes No No No No

Booklets

Booklet layout Yes Yes Yes No Yes

Booklet offset Yes Yes No No Yes

Last page options Yes Yes Yes No Yes

Printing order Yes Yes No No Yes

Color

Color mapping Yes No No Yes Yes

Color selection No Yes No Yes Yes

Conditional output Yes Yes Yes Yes Yes

Content repository element disposition Yes Yes Yes Yes Yes

Document merging

Merging from the content repository Yes Yes Yes Yes Yes

Merging from memory Yes Yes Yes Yes Yes



Document saving

Saving to the content repository Yes Yes Yes Yes Yes

Saving to memory Yes Yes Yes No Yes

Duplicate page side-by-side printing

Logical page placement Yes Yes No No Yes

Side-by-side printing layout Yes Yes No No Yes

Font list for printing Yes Yes No No No

Message log setup

Content repository and memory options Yes Yes Yes Yes Yes

Customized error messages Yes Yes Yes Yes Yes

Message format Yes Yes Yes Yes Yes

Multi-file output Yes Yes No No Yes

Output file comments Yes No No No Yes

Output file format

Block size No Yes No No No

Character code No No No No Yes

Compression accuracy No No No Yes Yes

File type No Yes Yes No Yes

Image compression Yes No No Yes Yes

Line ending sequence No No No No Yes

Printer carriage control byte No No No No Yes




Record format Yes No Yes No No

Record size No Yes Yes No Yes

Text compression No No No Yes No

Output job setup

AFPC comments Yes No No No No

Bookmarks No No No Yes No

Collating No Yes No No Yes

Copies No Yes Yes No Yes

Cover options No Yes No No No

Duplex/simplex selection No Yes Yes No Yes

Hyperlink options No No No Yes No

Image format Yes No No No No

Offset in output bin No Yes No No Yes

Page overlay options Yes No No No No

Page range Yes Yes Yes Yes Yes

Page segments Yes No No No No

Repetitive merge element mapping Yes No No No No

Shading selection No No No Yes Yes

Shading type Yes No No No No

View orientation No No No Yes No




Page setup

AFP Medium maps Yes No No No No

Page offset Yes Yes Yes Yes Yes

Paper size Yes Yes Yes Yes Yes

Tray selection No Yes Yes No Yes

Printer connection

Spur options No Yes No No No

Type of connection No Yes No No No

Printer-specific settings No No No No Yes

Print job reporting

Accounting information No Yes No No No

Console messages No Yes No No No

Print processing options

DJDE setup No Yes No No No

Interword spacing No Yes No No No

Merge text check No Yes No No No

Page optimization No Yes No No No

Proofing

Font mapping Yes Yes Yes Yes Yes

Font translation table Yes Yes Yes Yes Yes




The Output Format ToolThe xPression CompuSet Tools application contains the Output Format Tools that help you select your output format options. There is a tool for each supported output type, except for PCL. For more information, see Are You Creating PCL Output?.

The Output Format Tool assigns default or, in some cases, recommended values for all of the output settings. When creating a PDEF file, you can generally use the default values set by the Output Format Tool and customize the output settings that are specific to your application. For example, when creating a PDEF file for a catalog, you may want to use the Output Format Tool default values, but specify side-by-side printing. In this case, you need to make only minor adjustments to the settings already assigned by the tool.

• Here are some common options and the location in the tool where you can set those options:

• If you are using a paper size other then 8 1/2 x 11-inch, be sure to specify the correct paper size on the Paper Size tab in the Page Setup dialog box (see Paper Size).

• If you are merging an image or document, ensure that you specify merging options in the Document Merge dialog box (see Document Merge).

Proofing justification Yes Yes Yes Yes Yes

Proofing selection Yes Yes Yes Yes Yes




• If you are printing a landscape multiple imposition document, choose Booklet on the Select Document Type tab (see Select Document Type) and specify the booklet options on the tabs (see Booklet Options). Also, ensure that you specify the following options on the Paper Size tab in the Page Setup dialog box (see Paper Size):

– Landscape orientation– The binding method you want to use (head-to-head booklet or head-to-toe tablet)– The paper size

• If you want to print more than one logical page on the physical page, and then cut the paper after printing, specify Duplicate Page Side-by-Side Printing on the Select Document Type tab (see Select Document Type).

Are You Creating PCL Output?If you are creating PCL output, you can still define your output options, but you’ll have to add them to your PDEF file in a text editor using PCL output format commands. We have provided a default PDEF file that you can use as a starting point. The default files are located on your server in the \\xPression\CompuSet\Format definition directory. All the supported PCL output format commands are described in PCL Output Formatter Commands.

Launching an Output Format ToolThere are four Output Format Tools provided with the xPression CompuSet Tools that enable you to define output options for these output types:

• AFP

• Metacode

• PDF

• PostScript



To launch an Output Format Tool:


2. Double-click the Output Format Tool for the output type you are producing. For example, if you are producing PDF output, you would click Output Format Tool - PDF. The Output Format Tool main window appears, as shown in Figure 5 on page 79.


The Output Format Tool InterfaceEach version of the Output Format Tool has the same interface and works in the same way. Each tool displays a main window with a Tree view and a Summary view.

Note: In xPression, the concept of a Merge library has been replaced with the content repository. In the Output Format Tools, you will see the term Merge library used. The actions associated with these Merge library options are actually taking place in the content repository, not the Merge library. The descriptions and steps in this chapter refer to the content repository (even though the tool may say “Merge library”), since that is where the actions are taking place.

The Main Window

When you open the Output Format Tool, it displays the main window as shown in Figure 5 on page 79, which contains a Tree view in the left pane, and a Summary view in the right pane. The Tree view contains folders that each represent a category of output options you can define. The PDEF file updates automatically as you select options on the tabs. The Summary view contains the contents of the PDEF file either in a text or code format, depending on your selection.



Tree View

The Tree view, shown in Figure 6 on page 80, displays the output options for the selected output device in a tree structure in the left pane of the main window. Each folder has a dialog box associated with it, which contains related tabs that allow you to set specific options.

Figure 5. Output Format Tool Main Window



You can do any of the following tasks in the Tree view:

• Click a folder to display the associated dialog box.

• Expand a folder to display elements that represent the individual tabs contained in the associated dialog box.

• Click an element to display a dialog box that contains only the associated tab.

• Expand an element to list the output formatter codes generated by the tab.

Summary View

The main window Summary view in the right pane displays the output options selected in the output options file. When you open a new file, the summary displays the default output options for the selected output device. You can switch between the Text Summary view, shown in Figure 5 on page 79, and the

Figure 6. Tree View



Code Summary view. On the View menu, click Code Summary or Text Summary to switch between the two views.

The Text Summary view lists a brief text description of the most relevant commands used in the file. These commands are the settings for the output options selected in the file. From the Text Summary view, you can double-click an option, such as Page Setup, to display the dialog box where you can make changes. For example, if you specify US Letter paper size in the Page Setup dialog box, the summary displays the following information:

Page SetupPaper Size - US Letter

Figure 7. Code Summary View



If you want to change the page size to Legal, double-click Paper Size - US Letter in the Text Summary view to display a dialog box containing only the Paper Size tab. When you change the setting in the dialog box and click OK, the text displayed in the Summary view updates with the new information. To display the Page Setup dialog box with all the tabs, double-click Page Setup in the text Summary view.

The Code Summary view, shown in Figure 7 on page 81, lists all the output formatter commands for the output options in the file. Along with these commands, the Code Summary view also lists the parameters for each command. Use this summary to verify that you supplied the correct commands to the output formatter.

Selecting OptionsYou can select output options from the Tree view in the main window. The output options are logically grouped into folders. Click any folder to display the corresponding dialog box.

For example, the folder called Emitter Log accesses the Emitter Log dialog box, which contains the three tabs shown Figure 9 on page 83 as elements in the folder: Message Log, Customize Error Messages, and Message Format. You can enter values for any field in this dialog box, or you can use the default values. After you change a value in the dialog box, click Apply to accept the change and apply it to the output options file. Click OK to close the dialog box, accept all the changes made on the tabs, and apply them to the output options file.

Figure 8. Tree View



Clicking Cancel after clicking Apply does not cancel any changes or selections. Once you click Apply, the options cannot be canceled. When you open a new PDEF file for the first time, the Output Format Tool selects default output options. You can click Default on any tab to return the options to their defaults. The default value may not always be the recommended value. Generally, the Output Format Tool notes exceptions on the dialog box next to the option or you can look for the description of the option in this book. When you first open a new file, the text summary lists the default values currently selected.

Figure 9. Emitter Log Dialog Box



Setting User Options

You can select global options for the Output Format Tool user environment. On the View menu, select Options to display the Options dialog box. From the Options dialog box you can select unit, line-ending sequence, and save options.

Note: The Options dialog box is unavailable if a tabbed dialog box is currently open.

To customize your options:

1. Select the units of measure: points, inches, or centimeters.

2. Select the line-ending sequence: only carriage returns, only line feeds, or both.

3. Select your save options.

Figure 10. Options Dialog Box



Editing the PDEF FileThe Output Format Tool enables you to edit the PDEF file that the tool creates, or an existing PDEF file. This feature opens the PDEF file with a text editor, where you can edit the entries. When you open the file with the text editor by selecting the Manual edit option, the Output Format Tool automatically saves the file. Any changes you made in the file are saved and cannot be reversed.

Caution: This option is recommended only for those users who have experience with PDEF files. Altering entries in the file may cause unpredictable results.

To edit the PDEF file:

1. Click Manual Edit, or on the Tools menu, click Manual Edit. The text editor opens the PDEF file for editing.

2. Click OK to save any changes you make and close the text editor to return to the Output Format Tool. Click Cancel to close the editor without saving any changes. When you close the editor, the Output Format Tool validates the PDEF file. If any errors occur, an entry appears in the message log file.

Page SetupThe Page Setup dialog box enables you to customize the page setup for your job. You can specify size of the paper, any tray options, and page offset from this dialog box. This includes changing the paper size and orientation, as well as defining your trays (for supported output types). Output types differ in their page setup options. Not all output types have all of the tabs and options described in the following sections.

Paper SizeThe Paper Size tab enables you to customize the size of your page by defining the various parameters that specify paper size and orientation for your job. Refer to the graphic in the Preview area of the tab for an illustration of the options you select.



The Paper Size tab is generally the same for each output type, any differences are noted in the steps.

To customize your page size:

1. Select the paper size for your job. If you are creating AFP output and your job contains multiple paper sizes, skip to Step 3.

2. If you choose Custom as the paper size, type the custom page width and height in the appropriate boxes.

3. Select either Portrait or Landscape orientation.

Figure 11. Paper Size Tab — AFP and PostScript



4. If you choose Landscape, you can also select the Force rotation on all text check box, which causes all the text on the page to print in landscape orientation.

Note: The Force rotation on all text option, and the following binding options are not available if you are creating PDF output.

5. Select either Head-to-head (booklet) or Head-to-toe (tablet) for your binding option.

6. Define the unprintable area on the page. This is the margin around the logical page where the printer cannot print. Type the left and right margins and the top and bottom margins in the appropriate areas in user-specified units (points, centimeters, inches).

Note: The unprintable area options are not available if you are creating metacode output.

Tray SelectionThe Tray Selection tab, shown in Figure 12 on page 88, enables you to customize your metacode printer tray setup. You can define how your paper trays are assigned.



Note: The Tray Selection tab is available only if you are creating metacode output.

To customize your tray setup:

1. Select the Enable Printer Tray Select check box to enable printer tray selection. If you clear the check box, the options on the dialog box are unavailable.

2. Select the Same paper size in all trays check box if all trays use the same paper size. Clear this check box to use different paper sizes in the trays. If this check box is selected, the JDE and JDL columns in the table are unavailable.

Figure 12. Metacode Tray Select Tab



Note: If you select Same paper size in all trays, the output formatter ignores all tray options in the PDEF file.

3. Click Add to add a row to the table. The tray number is automatically entered and incremented by one with each new row added.

4. Select the paper size for the tray. If you select the Same paper size in all trays check box, the only available option is the page size you selected on the Page Size tab.

5. Enter a cluster name (1–6 characters) that defines a group of trays with the same paper size.

6. Enter a JDE (Job Descriptor Entry) name (1–6 characters) that is defined in the JDL (Job Descriptor Language) on the printer. If you select Same paper size in all trays, this option is unavailable.

7. Enter a JDL name (1–6 characters) that contains the JDE. If you select Same paper size in all trays, this option is unavailable.

Tip: You can add custom Cluster, JDE, and JDL names in the Xrxint.ini file so that they always appear in the corresponding drop-down lists in the table. To add custom names, open the Xrxint.ini file, located in \\Program Files\xPression\Bin, in a text editor. Under the section [TraySelect], add custom names using this format:

[TraySelect]Cluster1=MainCluster2=AUXJDE1=DFLTJDL1=XICSONJDL2=XICSOFF

Tray SetupThe Tray Setup tab enables you to customize your PostScript printer tray selections. You can define how your paper trays are to be assigned. Depending on the type of printer you are using, this can include paper size, paper color, paper type, number of holes drilled, and repetitive tabs for all of the paper trays specified for your output device. There are several Tray Setup tabs that vary depending on the type of printer you select. These tabs are described in the following sections.



Note: The Tray Setup tab is available only if you are creating PostScript output.

DocuPrint/DocuTech

The Tray Setup tab enables you to customize the tray setup for a Xerox DocuPrint or DocuTech printer.

To customize your DocuPrint or DocuTech tray setup:

1. Click Add to add a row to the table. The Tray number is automatically entered and incremented by one with each row added. You can add up to five trays for a DocuTech and six trays for a DocuPrint, with tray 1 designated to be the main or default tray.

2. Choose the paper size for each tray from the Paper Size drop-down list.

Figure 13. PostScript Tray Setup Tab — DocuPrint/DocuTech



3. Choose the color of the paper from the Paper Color list, or type a different color, for each tray. Select Clear for transparencies.

4. Choose the paper type from the Paper Type list that includes the following: standard or plain, full cut tab (one tab the full length of the page), or pre-cut tabs (multiple tab stops).

5. Specify if there are three holes drilled or no holes drilled (0) in the paper in the # Holes Drilled column for each tray.

6. Type the number of non-repetitive tab positions (1–100) in the Tabs column.

Lexmark

The Tray Setup tab enables you to customize the tray options for a Lexmark printer.

Figure 14. PostScript Tray Setup Tab — Lexmark



To customize your Lexmark tray setup:

1. Select the number of input trays from the following options:

– Three input trays: the upper tray (Tray 1), the lower tray (Tray 2), and the envelope, high capacity feeder (HCF), or 100-sheet auxiliary feeder tray (Tray 3).

– Four input trays: the upper tray (Tray 1), the lower tray (Tray 2), the envelope, HCF, or 100-sheet auxiliary feeder (Tray 3), and the manual feed tray (Tray 4).

– Five input trays: the upper tray (Tray 1), the lower tray (Tray 2), the envelope, HCF, or 100-sheet auxiliary feeder tray (Tray 3), the manual feed tray (Tray 4), and the manual envelope feed tray (Tray 5).

2. Select the default input tray from one of the following:

– 1 Upper tray

– 2 Lower tray

– 3 High capacity feeder

– 4 Manual feeder

– 5 Envelope

3. Select a paper size for each paper tray listed in the Tray column.



Xerox 4700

The Tray Setup tab enables you to customize tray setup options for a Xerox 4700 printer.

To customize your Xerox 4700 tray setup:

1. Choose two or three input paper trays from the Number of input trays list.

2. Select the default input tray: 1 Top tray, 2 Bottom tray, 3 High capacity feeder (available only if you specify three input trays).

3. Choose the paper size for each tray listed in the Tray column.

Figure 15. PostScript Tray Setup Tab — Xerox 4700



PostScript Level 2 or DocuColor Models

The PostScript Level 2 Tray Setup tab enables you to customize setup options for a PostScript Level 2 or DocuColor series printer. You can select Standard Options and Advanced Options. The Tray Setup tab enables you to configure the standard options for a PostScript Level 2 or DocuColor printer.

To customize your standard options for a PostScript Level 2 or DocuColor printer:

1. Select Standard Options.

2. Choose the paper size from the Paper Size list for each tray.

Figure 16. PostScript Tray Setup Tab — Standard Options



3. Type the paper color for each tray (1–15 characters).

4. Type the paper weight for each tray (1–3 numeric characters).

The Tray Setup tab shown here enables you to configure the advanced options for a PostScript Level 2 or DocuColor printer.

To customize your advanced options for a PostScript Level 2 or DocuColor printer:

1. Select Advanced Options.

2. Type the media type for each tray (1–15 characters).

Figure 17. PostScript Tray Setup Tab — Advanced Options



3. Click in the Tray Command column to generate a PostScript command that identifies the tray number specified in the Tray column, or choose Do not generate command and use the options on this tab to identify the tray.

4. Select a feed option for each tray from the following options: Auto feed if not default, Auto feed if default, Manual feed if not default, Manual feed if default.

Tray Setup PoliciesThe Tray Setup Policies tab enables you to define what you want the PostScript Level 2 or DocuColor printer to do when certain paper tray error conditions occur. For each condition, select the action you want the printer to take when the condition occurs.

Figure 18. PostScript Tray Policies Tab



Note: The Tray Setup Policies tab is available only when you choose PostScript output and select PostScript Level 2 or DocuColor Series on the Select Printer Model dialog box.

To customize your tray setup policies for a PostScript Level 2 or DocuColor printer:

1. Choose one of the following actions if the requested paper size is not available on the printer:

– Terminate the job.

– Ignore the requested paper size.

– Interact with the operator.

– Select the nearest paper size and adjust the page to fit.

– Select the next larger paper size and adjust the page to fit.

– Select the nearest paper size and do not adjust the page to fit.

– Select the next larger size and do not adjust the page to fit.

2. Choose whether to terminate the job, ignore the requested paper color, or interact with the operator if the requested paper color is not available on the printer.

3. Choose whether to terminate the job, ignore the requested paper weight, or interact with the operator if the requested paper weight is not available on the printer.

4. Choose whether to terminate the job, ignore the requested media type, or interact with the operator if the requested media type is not available on the printer.



Page OffsetThe Page Offset tab enables you to define the placement of the logical page on the physical sheet of paper. The logical page is the printable area that fits onto the physical sheet of paper. The unprintable area margins defined on the Page Size tab (refer to Step 6 on page 87) specify the logical page size. Refer to the graphic in the Preview area for an illustration of the options you select.

Figure 19. Page Offset Tab



To customize your page offset options:

1. Choose whether to center the logical page on the physical page or position the logical page on the physical page.

2. If you choose to position the logical page, you can specify one of these options:

– Offset the page horizontally and vertically as specified. Type the horizontal and vertical values in the appropriate areas. Negative values move the text left or up and positive values move the text right or down.

– Offset the page horizontally as specified and center it vertically. Type the horizontal value in the Horizontal (x offset) box. Negative values move the text left and positive values move the text right.

– Offset the page vertically as specified and center it horizontally. Type the vertical value in the Vertical (y offset) box. Negative values move the text up and positive values move the text down.

3. Select the type of page inversion to apply from the Consecutive Page Inversion list. Page inversion switches the fixed offsets from side to side on alternate pages. This is particularly useful when duplex printing to maintain a fixed inside margin for binding.

Medium MapsThe Medium Maps tab, shown in Figure 20 on page 100, enables you to define the attributes of the medium maps used for your job. You can specify the map number and name, your duplex choice, the paper size, the number of copies, which paper tray to pull from, a page overlay and your offset stacking choice for each map.



Note: The Medium Maps tab is available only if you are creating AFP output.

To customize your medium map options:

1. Click Add to add a new row to the table.

2. Select a number from the list or type the medium map number (from 1 to 127) in the Map # column.

3. Type the name of the medium map in the Name column. The name can be 1 to 8 alphanumeric characters.

4. Select to print the job in normal duplex mode, tumble duplex mode, or in simplex (no duplex).

Figure 20. AFP Medium Maps Tab



5. Select a paper size for each medium map.

6. Type the number of copies to print of each page. You can specify from 0 to 254 copies.

7. Type the ID for the paper tray used for each medium map. If you type 0, that specifies no tray selection. You can type a number up to 255.

8. Type the name of the page overlay to be merged on every page. The name can be 1 to 8 alphanumeric characters.

9. Select whether you want offset stacking in the output bin or no action.

Index SettingsThe Index Settings dialog box enables you to customize your AFP index properties. You can specify options for each index you want to include in the output formatter run. The Index settings dialog box is available only if you are creating AFP output.

Note: If you want to embed Tag Logical Elements (TLEs) in your AFP output file, you must follow the steps located in Embedding Tag Logical Elements (TLEs) in Your AFP Output File.



Index SetupThe Index Setup tab enables you to define the settings for each index. You can define the Index ID and name, key fields, as well as the page range of the index.

To customize your index settings:

1. Click Add to add a row to the table.

2. Select the index ID for each index file.

Figure 21. AFP Index Setup Tab



3. Type, in the Active Key Fields column, the index field numbers that are to form the key in the index member. Each value must be from 1 to 10 and separated from the next by a comma. You can also use a dash (–) to show a range of numbers, for example you can type: 1–3,5.

4. Type the name of the index member that will display in the viewer. The name can be up to 40 alphanumeric characters long.

5. Select Multiple pages to specify a page range from the page number of the COMPUSET index entry up to (by not including) the page number of the next COMPUSET entry. Select One page to specify a page range of one page based on the page in the COMPUSET index entry.

Special Document TypeThe Special Document Type dialog box enables you to customize the document type of your job. You can specify booklet layout and offset options for printing booklets or specify side-by-side printing layout and logical page placement options for printing duplicate pages side-by-side.

Note: The Special Document Type options are not available if you are creating PDF output.



Select Document TypeThe Select Document Type tab enables you to define which type of special document you want to produce. The available tabs on the Special Document Type dialog box change depending on the option selected on this tab.

Figure 22. Select Document Type Tab



To specify a special document type:

• Select Normal to print one logical page for each physical sheet of paper output. There are no special settings for this document type. This is the default value.

• Select Booklet to print two logical pages on each side of a sheet of paper (physical page). You can fold the output into a booklet and staple it. Pages are arranged so that when you fold the entire document along a center line, you have a booklet in which the pages appear in sequential order (multiple imposition). For more information about specifying booklet options, see Booklet Options.

Tip: If the booklet is too thick to fold, you can specify duplicate side-by-side printing and print two booklet pages on each physical page, then cut the printed pages in half to produce two booklets.

Note: For booklets, you do not have to define multiple imposition options.

• Select Duplicate Page Side-by-Side Printing to print two or more copies of the same logical page on one physical page by dividing the page symmetrically. This is useful when you want to print the same page many times. This is also called n-up printing. You can also use duplicate page side-by-side printing for booklets if the booklet is too thick to fold. This allows you to print two duplicate pages on each physical page and then cut the pages to form two booklets. For more information about side-by-side printing options, see Duplicate Page Side-By-Side Printing.

Note: (1) For side-by-side printing, you must use also define n-up printing. (2) Booklet and side-by-side printing are mutually exclusive; therefore, you cannot select both at the same time. If you select booklet, side-by-side printing options are unavailable, and the reverse is true.

Booklet OptionsWhen you select Booklet as your special document type, the Booklet Layout, Booklet Offset, and Booklet Options tabs appear in the Special Document Type dialog box. Use these tabs to select booklet options.



Booklet Layout

The Booklet Layout tab enables you to define the way the booklet is folded and to specify binding margin options (gutter width).

To customize your booklet layout:

1. Choose to fold the booklet along the short edge of the physical page (in landscape, head-to-toe format), or along the long edge (in landscape, head-to-head format).

2. Select the Allow different text and image rotation check box to print text and images in different rotations on the same page.

Figure 23. Booklet Layout Tab



3. Choose whether to center each logical page on its half of the physical page, or to position both left and right logical pages on a single physical page.

4. If you choose to position the page, you can select a gutter width option from the following:

– Fixed gutter width for all pages: Specify a minimum gutter width between the left and right logical pages printed on a single physical page.

– Variable gutter width between the outer pages: Specify a minimum and a maximum width between left and right logical pages printed on a single physical page. The minimum and maximum gutter width together create a variable gutter space that allows for the increasing width required between the outer pages of a booklet, due to the fold. The gutter decreases on every page in even increments from the maximum width at the outside of the booklet to the minimum width at the center of the booklet.



Booklet Offset

The Booklet Offset tab enables you to define whether you want to center or position the logical page on the physical sheet of paper.

Figure 24. Booklet Offset Tab



To customize your booklet offset:

1. Choose whether to center the logical page on the physical page, or position the logical page on the physical page.

2. If you choose to position the logical page, specify whether to:

– Offset the page horizontally and vertically as specified. Type the horizontal and vertical values in the appropriate areas. Negative values move the text left or up and positive values move the text right or down.

– Offset the page horizontally as specified and center it vertically. Type the horizontal value in the Horizontal (x offset) box. Negative values move the text left and positive values move the text right.

– Offset the page vertically as specified and center it horizontally. Type the vertical value in the Vertical (y offset) box. Negative values move the text up and positive values move the text down.



Booklet Options

The Booklet Options tab enables you to define output options for printing your booklet. Refer to the graphic on the right side of the tab for an illustration of the option currently selected.

Figure 25. Booklet Options Tab



To customize your booklet options:

1. Select how you want the last page of the document to be printed:

– Set logical pages in normal sequence with blank pages left at the end. This option leaves enough pages at the end to fill out to a multiple of four logical pages (one physical sheet).

– Insert blank logical pages so last logical page appears on the back cover. This option leaves enough pages at the end for the last page to print on the back cover of the folded output.

– Insert blank logical pages so last two logical pages appear on inside and outside of back cover. This option leaves enough pages at the end for the last two pages to print on the inside and outside of the back cover of the folded output.

2. Choose how you want the last page imposed: using the COMPUSET IMPO command to start and stop imposition, no special action for imposition, or do not impose the last page.

If you do not impose the last page, the last logical page of the intermediate file is not included in the imposition sequence, but it is formatted as a separate physical page. You can use this option in online installations where the last page is a trailer page (IBM JES banner page).

3. Choose whether to print pages normally (first to last) or print pages in reverse order (last to first).

Duplicate Page Side-By-Side PrintingWhen you select Duplicate Page Side-By-Side Printing as your special document type, the Side-By-Side Printing Layout and Logical Page Placement tabs appear in the Special Document Type dialog box. Use these tabs to specify side-by-side printing options.



Side-By-Side Printing Layout

The Side-by-Side Printing Layout tab enables you to define options for duplicate page side-by-side printing.

To customize your side-by-side printing layout:

1. Choose whether to print three or more duplicate pages (all logical pages on the same physical page have the same rotation) or two duplicate pages.

2. If you choose to print two duplicate pages, you can select the Both in upright rotations check box to have the pages cut on the long edge and both of the pages printed in the upright orientation. If you select this check box, the rest of the options are unavailable. To select the other options, clear this check box.

Figure 26. Side-by-Side Printing Layout Tab



3. Choose whether to cut parallel to the short edge or the long edge of the physical sheet of paper.

4. Choose the rotations you want to apply. The available rotations vary based on the selection in the Cut parallel to box.

Logical Page Placement

The Logical Page Placement tab enables you to define the horizontal and vertical margins for side-by-side printing. Refer to the graphic for an illustration of the options you select.

Figure 27. Logical Page Placement Tab



To customize your logical page placement options:

1. Choose whether to center each page vertically or offset the top edge of the logical page from the top edge of the physical page.

2. If you choose to offset the top edge of the page, you can type the amount of vertical offset you want in the Vertical offset box. You should measure from the top edge of the physical page to the top edge of the uppermost logical page. You do not need to specify a bottom margin.

3. Choose whether to center each logical page horizontally or offset the left edge of the logical page from the left edge of the physical page.

4. If you choose to offset the left edge of the page, you can type the amount of horizontal offset you want in the Horizontal offset box. You should measure from the left edge of the physical page to the left edge of the leftmost logical page. You do not need to specify the right margin.

Document MergeThe Document Merge dialog box enables you to customize the document merging options for your job. You can specify options for merging images or documents from the content repository or from memory.



Merging from the Content RepositoryThe Merging from Merge library tab enables you to define options for how the output formatter accesses the content repository as well as the action the output formatter takes if is does not locate a content repository resource.

To customize your document merging options:

1. Select the Enable Merging from the Merge library check box to enable merging documents or images from the content repository. If you do not select this check box, the remaining options on this tab are unavailable.

Figure 28. Merging from the Merge Library Tab



2. Select the search type from the following options:

– Off. Loads no names into the memory merge buffer; loads them into a fixed-size buffer.

– Binary. Loads the binary search names for the content repository into memory.

– All. Loads all the names of the content repository entries into memory.

3. Specify the maximum percentage of the memory merge buffer used to load content repository elements, such as a logo appearing on every page, in the Percentage of memory merge buffer used to store names box. This option is unavailable if you select Off in the Search column. When you store an image in a memory buffer, the output formatter has to read it into memory only once from the content repository. This improves output formatter performance by reducing the number of input/output (I/O) operations.

4. Choose the action from the Action Upon Failure to Locate Merge Element list that you want the output formatter to take if it cannot locate the content repository resource you are requesting to merge. You can continue with the run or stop the run if certain types of elements (images, documents, or both) are not found.

5. Select the Ignore offsets and center merge page check box to rotate the merged page. If the rotation of the page differs from the current rotation, the merged document can be rotated if it fits on the output page. Clear this check box to merge the document as it is. The imported document is saved in the content repository with no specified rotation. The output formatter is free to select a rotation that prints the document satisfactorily. If possible, the output formatter selects the current page rotation.

6. If you select Duplicate Page Side-by-Side Printing on the Select Document Type tab, choose from the With Side-by-Side Printing list how you want the output formatter to extract documents from the content repository into a document with side-by-side printing. You can either merge all the pages of the saved document into the side-by-side printed document, or merge only the first page of a saved document.



Merging from MemoryThe Merging from Memory tab enables you to define options for merging elements from memory.

To customize your memory merging options:

1. Select the Enable Merging from Memory check box to enable memory merge. If you clear this check box, the remaining options on this tab are unavailable.

2. Type a value in the Storage buffer size box to set the storage buffer size in 32-bit (4-byte) words.

Caution: It is recommended that you do not change the storage buffer size value unless you have a thorough understanding of how the buffer works.

Figure 29. Merging from Memory Tab



3. Choose whether to merge documents from the content repository or memory during the output formatter run.

4. If you choose memory merging for documents, select one of the follow types of memory merge:

– Use the COMPUSET DMRG command to determine the memory option.

– Reuse memory as needed. Temporarily stores all the documents to be merged in memory.

– Maintain the document in memory for the duration of the emitter run. Permanently stores all documents to be merged in memory.

– Use the DOCUTL MMRG command to determine the memory option. Stores all documents to be merged according to the merge flag set by the DOCUTL MMRG command.

5. Choose whether to merge images from the content repository or memory during the output formatter run.

6. If you choose to use memory merge for images, select one of the follow types of memory merge:

– Use the COMPUSET IMG command to determine the memory option.

– Reuse memory as needed. Temporarily stores all the images to be merged in memory.

– Maintain the image in memory for the duration of the emitter run. Permanently stores all images to be merged in memory.

Document SaveThe Document Save dialog box enables you to specify document saving options for your job. You can specify options for saving to the content repository or for saving to memory.



Saving to Content RepositoryThe Saving to Merge Library tab enables you to define options for saving resources to the content repository. Each output type supports saving to the content repository, but there are differences in the available options. The differences are noted in the following steps.

To customize your document saving options:

1. Select the Enable Saving to the Merge Library check box to save documents or images to the content repository. If you clear this check box, the remaining options on this tab are unavailable.

2. Select the Save document in upright and inverse orientation check box to save the document in both upright and inverse orientations. Clear this check box to save it in its original orientation.

Figure 30. Metacode Saving to Content Repository Tab



Note: Saving documents in upright and inverse orientation is available only if you are creating metacode or AFP output.

3. Select the Save each FEED DJDE check box to save each FEED DJDE command. Clear this check box to omit saving the FEED DJDE command if it appears on the last page of the saved document.

Note: Saving FEED DJDE commands is available only if you are creating metacode output.

4. Choose whether to ignore the save command or replace the existing document if a document of the same name exists in the content repository.

5. If you choose to replace the existing document, you can specify whether to replace the document only if it is a specific type (AFP, metacode, PDF, or PostScript), or regardless of its type.

6. If you choose to replace the existing document, you can also specify to delete or save existing VMF references in the document.

7. Select the Save empty documents check box to save blank (empty) documents in the content repository. Clear this check box to delete empty documents.

8. Select the Save booklet (imposed) documents check box if you want to save imposed documents. Clear this check box to disregard imposed documents. Imposed documents cannot be saved in two orientations and cannot be imposed a second time.

Note: Saving imposed documents is not available if you are creating PDF output.



Saving to MemoryThe Saving to Memory tab enables you to define options for saving documents to memory.

To customize your saving to memory options:

1. Select the Enable Saving to Memory check box to save documents to memory. If you clear this check box, the remaining options on this tab are unavailable.

2. Type a value in the Storage buffer size box to set the storage buffer size in 32-bit (4-byte) words.

Figure 31. Saving to Memory Tab



Caution: It is recommended that you do not change the storage buffer size value unless you have a thorough understanding of how the buffer works.

3. Choose whether you want to save documents in the content repository only, or in memory as well.

4. If you choose to save documents to memory, you can also select whether to save the document in its current orientation or to save it in the current and inverse orientations (portrait and inverse portrait, or landscape and inverse landscape).

Content Repository SetupThe Merge Library Setup dialog box enables you to customize resource disposition for your content repository.



Content Repository Resource DispositionThe Merge Library Element Disposition tab enables you to delete or rename content repository resources. These resources are renamed or deleted at the end of the run.

To delete or rename content repository resources:


2. Select Delete or Rename from the Action column.

Figure 32. Merge Library Element Disposition Tab



3. Select the name of the resource that you want to delete or rename from the list in the Name column. This is a list of resources currently in the content repository.

4. Type the new name of the resource in the New Name column if you are renaming a resource. If you are deleting a resource, this column is unavailable.

5. Repeat the previous steps for each resource you want to rename or delete during the run.

ColorThe Color dialog box enables you to customize color for your job. The available tabs in this dialog box vary depending on the type of output you are creating. You can select and map colors for color printers. Remember, when using highlight color for all output types except metacode, you must specify the color index numbers in the Color Mapping Setup tab. Regardless of the highlight color requested, the printer must have color capability; otherwise, black is substituted whenever color is specified. For text output, all non-black colors are converted to the specified highlight color. It is the operator’s responsibility to perform color substitution if necessary.

For metacode output, this dialog box is available only if you select the Xerox 4850 or 4890 color printers on the Select Printer Model dialog box. For AFP output, this dialog box is only available if you select highlight color for your specified printer on the Select Printer Model dialog box.

Color SelectionThe Color Selection tab is available for metacode, PDF, and PostScript output, but the options on the tab differ depending on the output type. The Color Selection tab is not available for AFP output. The following sections describe the tabs.



Metacode Output

The metacode Color Selection tab enables you to define color printing options for the Xerox 4850 and 4890 color printers.

To customize your color selection:

1. Choose a highlight color. The normal ink color used for printing on the specified printer is displayed next to Normal ink color.

2. If you select Custom, type the name of the custom color. The name must be 1–32 characters long, and must currently reside on the printer.

Figure 33. Metacode Color Selection Tab



3. Type the name of the ink catalog to be used as the default. The name must be 1–6 alphanumeric characters in length, with no blanks.

4. Type the name of the palette to be used as a default. The name must be 1–32 alphanumeric characters in length, contain at least one alphabetic character, and may contain blanks.

PDF and PostScript Output

The PDF and PostScript Color Selection tab enables you to define color printer options.

Figure 34. PDF and PostScript Color Selection Tab



To customize your color selection:

1. Choose whether you are printing to a black and white printer (no color), a full color printer, or a specific highlight color printer (red, green or blue).

If you select the DocuPrint 350-HC (Xerox 4850) printer in the Select Printer Model dialog box, the Color Selection tab also contains the DocuPrint color options shown in Figure 35.

2. If you are using a DocuPrint 350-HC printer, choose no action or to substitute the highlight color for a specific color when a full color image prints.

3. If you are using a DocuPrint 350-HC printer, choose no action if the highlight color is not available, use the current color, hold the job, or cancel the job.

Color Mapping SetupThe Color Mapping Setup tab shown in Figure 36 on page 128 enables you to match a color specified by the RGB model to a named ink on a highlight color printer.

Figure 35. DocuPrint Color Options



Note: The Color Mapping Setup tab is not available if you are creating metacode output.

To customize your color mapping setup:


2. Type the index number in the Color Index column that corresponds to the CompuSet color(0 through 511).

Figure 36. PostScript Color Mapping Setup Tab



3. Click in the Color Selection column to display the color palette where you can select a basic color or define a custom color. The color you select appears in this cell of the table.

4. The % Red, % Green, and % Blue columns display the RGB red, green, or blue value for the color you selected. You can edit this value to make changes, which are reflected in the color displayed in the Color Selection cell. The RGB value must be a real number between 0.0 and 100.0.

Note: If the intermediate file set of RGB values is within 10% of the values set here, the output formatter assumes the colors match and uses the values you specify as the ink index. If no match is found, or you do not specify any values here, black is substituted. If each RGB value is within 10% of the maximum (100) or 10% of the minimum (0), black is substituted. If all three RGB values are almost identical (within 5% of each other), the output formatter substitutes black. Otherwise, the highlight color is used.

FontsThe Fonts dialog box enables you to customize your font selections for each output type. Font options are usually defined in the Widths file, but you can override the options for a specific run in the PDEF file.

The tabs available in this dialog box differ depending on the type of output you are creating. The following sections describe the different tabs.

Font OptionsThe Font Options tab shown in Figure 37 on page 130 enables you to define font mapping options. You need to specify character types within a font to identify floating accents and uppercase and lowercase characters.



Note: The Font Options tab is available only if you select PDF or PostScript output.

To customize your font options:


2. Type a value (1–10) in the Table Index column that indicates where the character types specified by the remaining fields are to be stored. This value must correspond to the table index specified in the MFNT command in the Widths file.

3. Choose either normal, uppercase characters, or floating accents for the character type in the Character Type column.

Figure 37. Font Options Tab



4. In the First Character Code column, type the physical font character code ID of the first character in the range of characters defined by the Character Type field. The decimal value should be 0–255.

5. In the Last Character Code column, type the physical font character code ID of the last character in the range of characters defined by the Character Type column. The decimal value of 0–255 must be equal to or greater than the value of the First Character field.

Font List for PrintingThe Font List for Printing tab is available for both AFP and metacode output, but the options on the tab differ depending on the output type. The following sections describe the AFP and metacode tabs.

AFP Output

The Font List for Printing tab enables you to define options for creating printer font lists.

Figure 38. AFP Font List for Printing Tab



To customize your font list options:

1. Choose whether you want to create a font list by scanning the input files, or by manually entering the information. If you choose to create a font list by scanning input files, click OK.

If you choose to create a fonts list manually, follow the rest of the steps.


3. Type the MFNT (machine font identification) number for the AFP font as listed in the Widths file in the MFNT # column.

4. Type the font list index number of the portrait version of the font in the Portrait # column.

5. Type the font list index number of the landscape version of the font in the Landscape # column.

6. Type the font list index number of the inverse portrait version of the font in the Inverse Portrait # column.

7. Type the font list number of the inverse landscape version of the font in the Inverse Landscape # column.

Note: When specifying the location of a font in the font list, count from 1 to n, where n is the number of fonts in the list.



Metacode Output

The Font List for Printing tab enables you to define options for creating printer font lists.

To customize your font list options:

1. Select the Create font list check box to create a font list.

2. Choose whether you want to create a font list by scanning the input files, or by manually entering the information.If you choose to create a font list by scanning input files, click OK. If you choose to create a fonts list manually, follow the rest of the steps.


Figure 39. Metacode Font List for Printing Tab



4. Type the Xerox LPS machine font number as listed in the Widths file in the MFNT # column.

5. Type the line number of the portrait version of the font in the Xerox LPS PDE fonts list in the Portrait # column.

6. Type the line number of the landscape version of the font in the Xerox LPS PDE font list in the Landscape # column.

7. Type the line number of the inverse portrait version of the font in the Xerox LPS PDE font list in the Inverse Portrait # column.

8. Type the line number of the inverse landscape version of the font in the Xerox LPS PDE font list in the Inverse Landscape # column.

ProofingThe Proofing dialog box enables you to customize your proofing options. You can identify your output proofing device, set up the proof fonts, and map them to CompuSet fonts.

Note: The Proofing dialog box is available only if you are creating PDF and PostScript output.



Proofing SelectionThe Proofing Selection tab enables you to define the Configuration files used by the output device and the proofing device.

To customize your proofing selection options:

1. Select the Enable Proofing check box to enable proofing, or clear it to disable proofing. The remaining options on the tab are available only when you enable proofing.

2. Browse in the Final Output Device (CNF) box to locate and select the Configuration file (.cnf) for the production printer. The Proofing Device (CNF) box displays the Configuration file (.cnf) for the PostScript proofing device.

Figure 40. PDF/PostScript Proofing Selection Tab



3. Select the Use Templates check box to use a template while proofing.

4. Browse to locate and select the template. The selected file name appears.

Font Mapping SetupThe Font Mapping Setup tab enables you to define font mapping from the output device font name to the proofing device font name.

Figure 41. PDF/PostScript Font Mapping Setup Tab



To customize your font mapping setup:

1. Select a proof font in the Proof Font Name column to map to each final font name listed in the Final Font Name column.

2. Repeat until all the necessary fonts are mapped.

Proofing Font Translation TableThe Proofing Font Translation Table tab enables you to define a translation from the printer character code to the host computer character code for proofing output. This is necessary only for those character codes that are not the same as ASCII.

Figure 42. PDF/PostScript Proofing Font Translation Table Tab



To customize your proofing font translations:


2. Type the decimal value of the output device character code in the Output Code column.

3. Type the ASCII code used by the output formatter to represent the character in the proof output in the ASCII Code column.

4. Type the decimal value of the output subset index in the Subset Index column.

Proofing JustificationThe Proofing Justification tab enables you to specify how justified text fits into a column when the text exceeds the column width.

Figure 43. PDF/PostScript Proofing Justification Tab



To customize your proofing justification, select either of the following justification options:

• Force into the current column width by reducing interword space. Attempts to force horizontally-justified text records into the column by reducing the number of spaces between words.

• Convert into left justified text when it does not fit current column width. Converts horizontally justified text records to quad left text records when the text does not fit into the column width.

PDF Encryption SetupYou can encrypt your PDF to enable or prohibit the recipient of the PDF from performing certain functions with the file. For example, you can enable the user to save the PDF or prohibit them from printing the PDF. Encrypted PDFs prompt the user for a password to access the PDF.

Note: Autograph 9.3 does not support 128-bit AES (Advanced Encryption Standard) encryption. This encryption is supported in Acrobat Reader version 7.0 and later.



PDF Encryption TabThe PDF Encryption tab enables you to activate PDF encryption.

To enable PDF encryption, select the Enable 128-bit standard PDF Encryption option.

You can also set the compatibility level of your output PDF to Acrobat Reader 5.0, 6.0 or 7.0 or later.

Figure 44. PDF Encryption Tab



Document Permissions TabThere are two levels of users for PDF encryption:

• Owner: The owner has all permissions and rights for the PDF.

• User: The user has only those permission granted in the Permissions box.

For the Owner Password: The value of OwnerKey is a string for owner password, it is also case sensitive. The password should not be more than 32 characters in length. If the password is longer than 32 characters, the Adobe PDF library will truncate the password to 32 characters.

For the User password: Define a case-sensitive user password. The PDF prompts the user for this password while accessing the PDF. The password should not be more than 32 characters in length. If

Figure 45. Document Permissions Tab



the password is longer than 32 characters, the Adobe PDF library will truncate the password to 32 characters.

You can grant the following permissions to the User.

Permission Definition

Printing You can choose disable, allow high resolution printing, or allow low resolution printing.

When disabled, the Print option is not available from the File menu.

Enable copying of text and graphics

Enables text and graphics copying in a document.

Enable edit content Enable document modification, except what is controlled by the following three permissions: Enable add/edit comments and form fields, Enable form fields fill-in, Enable page insertion, rotation, deletion, bookmark, creation, thumbnail image creation.

Enable add/edit comments and form fields

Enables annotation addition and modification, and the filling of interactive form fields.

Enable form fields fill-in Enables the filling of existing interactive form fields.

Enable page insertion, rotation, deletion, bookmark, creation, thumbnail image creation

Enable the assembly of the document (insert, rotate or delete pages, and create bookmarks or thumbnail images).



Information DirectoryPDFs can contain an information directory that displays the author’s name and document title. If you want to add this information to your output PDF, specify that information here.

Output OptionsEach output type has specific output options you can specify. The following sections describe the Output Options dialog box and its tabs for each output type.

Figure 46. Information Directory Tab



AFPThe Output Options dialog box enables you to customize your output job setup, output file format and comments, conditional output options, as well as your shading and line options.

Output Job Setup

The AFP Output Job Setup tab enables you to define image format, page overlay, page range, and page segment options.

Figure 47. AFP Output Job Setup Tab



To customize your output job setup options:

1. Select IOCA or IM1 as the image format for the job. 2. Select the Output text first, then images check box to force the output formatter to output the text

on the page before the images. If you clear this check box, the output formatter outputs the text and images in the order they appear in the input file.

3. Choose whether to output a regular AFPDS document or a page overlay.

4. If you choose to output a page overlay:

– Type the name of the page overlay in the Page overlay name box.

– Type the page number of the page that the overlay appears on in the Page number of overlay box.

If you select this option, the page range options are unavailable.

5. Choose whether to print all the pages or a range of pages. This option is unavailable if you choose to output a page overlay. To select a page range option, you must select Output regular AFPDS document in the Page Overlay Options.

6. If you choose to print only a selected range of pages, type the first and last page numbers in the range in the corresponding boxes.

7. Choose whether to process or ignore page segments.

8. Choose whether to process or ignore page overlay requests and AFPC comments. If you select Ignore, the output formatter ignores page overlay requests and processes AFPC comments as regular comments.

9. Select the Map only repetitive merge elements check box to map only the page segments that are for use as repetitive merge elements. This option is available only if you select Process for both Page Segments and Overlay and AFPC comments.



Output Options

The AFP Output Options tab enables you to define conditional output options and select multi-file output.

To customize your conditional and multi-file output options:

1. Choose whether you want to transfer the final document normally to the selected output device, to suppress the document if the output formatter encounters a fatal error, or to save the document in its output format to a disk without transferring the document to the printer or viewer.

2. Select the Enable multiple print files check box to produce multiple output files as specified in the input file.

Figure 48. AFP Output Options Tab



Output File Comments

The AFP Output File Comments tab enables you to define up to five AFP comments.

To customize your AFP file comments, type any comments you want to appear in the comment lines that are inserted after the first line of the AFP header.

You do not need to insert quotes around the comments; the Output Format Tool does this automatically. Up to five AFP comments can be entered (up to 65 characters each) that are output in the same order as you enter them. The AFP output formatter does not verify any user comments. It simply echoes the text to the output file, preceded by %%.

Figure 49. AFP Output File Comments Tab



Output File Format

The AFP Output File Format tab enables you to define the format of the AFP records that are output by the AFP output formatter and enables you to select image compression.

Caution: It is recommended that you do not change options on this tab unless you are very experienced at creating PDEF files. Use the default values instead of overriding any of the options on this tab.

Figure 50. AFP Output File Format Tab



To customize your output file format options:

1. Select printer-formatted output, punch-formatted output, or IBM variable block records from the Output format list.

2. Type the maximum output record (block) size in bytes (includes the record and block length fields). For punch- or printer-formatted records, this value cannot exceed 8205. For IBM variable block formatted records, this value cannot exceed 8213. You can achieve the fastest throughput on the printer by using the maximum record size allowed.

3. Type the maximum number of bytes in each output block in the Maximum block size box.

4. Select the Enable compression of images check box to compress images that are stored in the content repository and in the AFP output files. The images are compressed into the CCITT G.4 format (binary) before they are converted into the ASCII85 format. The output formatter requires the ASCII85 format to print the files.



Shading and Line Options

The AFP Shading and Line Options tab enables you to define shading and line settings for AFP output.

To customize your shading and line options:

1. Select the type of shading you want to use: – IBM shading: Produces light, medium, and bold shading patterns similar to those generated by

the IBM Overlay Generation Language (OGL).

– Other shading: Produces light, medium, and bold shading patterns similar to those produced on a Xerox printer.

Figure 51. AFP Shading and Line Options Tab



2. Select your dotted and dashed line setting:

– Use emitter default values for line weight: Produces a light line weight of 0.5 points, a medium line weight of 1.0 points, and a bold line weight of 2.0 points.

– Use line weight value in tagged text: Produces line weights using the values defined in your CompuSet document.

Note: xPression always produces solid and shaded lines using the line weight specified in your CompuSet document.

MetacodeThe Output Options dialog box enables you to customize your metacode output file format, output job setup, and print processing options, as well as select a printer interface.



Output Job Setup

The metacode Output Job Setup tab enables you to define the number of copies, the page range, collate options, simplex or duplex printing, offset output, and cover options.


1. Choose whether you want CompuSet to control the copy count or whether you want to specify the number of copies to be printed here.

2. If you choose to specify the number of copies here, type the number (up to 32,766) in the Number of copies box.

Figure 52. Metacode Output Job Setup Tab



3. Choose whether to print all the pages or a range of pages.

4. If you choose to print only a selected range of pages, type the first and last page numbers in the range in the corresponding boxes.

5. Choose no collating action, collated, or uncollated printed pages.

6. Choose whether to have no duplex action, print simplex, print duplex, or print simplex without printing generated blank pages.

7. Choose whether to perform no offsetting action, to have no offset in the output bin, or to offset the job in the output bin. Select Offset the job in the output bin to stagger the output left to right in stacks like the bin of a copy machine.

8. Choose your cover option: no cover selection, pull the front cover from the Aux tray, pull the back cover from the Aux tray, or pull both covers from the Aux tray.



Print Processing Options

The metacode Print Processing Options tab enables you to define document merging, text placement accuracy, page optimization, and printer options.

To customize your print processing options:

1. Select the Verify that the text of a merged document is on the page check box to instruct the output formatter to verify that the text of a merged document fits on the page. Clearing this check box assumes that the text fits, and doesn’t need to be verified.

Figure 53. Metacode Print Processing Options Tab



Note: If you are setting a border of rules or shading around the edges of imposed pages, clear the Verify that the text of a merge document is on the page check box.

2. Choose how the output formatter should handle interword spacing: by using move commands, by using spaces when possible and move commands otherwise, or by always using spaces (used for CCF file printing when the Configuration/Widths file is omitted).

– Move commands are values that are used for spacing between words. These values are calculated from the Configuration/Widths file, and are variable based on the placement of the text, which is useful for justified text.

– When the output formatter inserts spaces between words it produces smaller output files, but not necessarily accurate placement of text. The size of a space is set by the font and therefore does not change as long as that same font is used.

– When the output formatter determines whether or not to use move commands, it measures the area between the words, and if that area is the same width as a space, then it uses a space. If it is not the same width, then it uses a move command, which is larger and slows down processing.

3. Select the Page Optimization check box to enable page optimization. The output formatter uses a sort procedure to optimize the way it presents data to the printer, which reduces the number of records and the chance of overflow. Only records on requested pages are sorted. The sorting process increases processing and execution time. Use only when necessary.

4. If you enable page optimization, you can also select whether it applies to inverse pages only or all pages.

5. Select the Separate DJDEs with END parameters check box to use the format where page-orientated DJDEs are separated from one another with END parameters and blank records. Clear this check box to use the format where page-orientated DJDEs are grouped together with a single END parameter.



Output File Format

The metacode Output File Format tab enables you to define record length and block size of the metacode output print file.

Caution: It is recommended that you do not change options on this tab unless you are very experienced at creating PDEF files. Use the default values instead of any option overrides.

Figure 54. Metacode Output File Format Tab



To customize your output file format:

1. Choose whether the output file format is variable length tape records (blocked and formatted like IBM VB tapes) or unformatted tape blocks.

2. Type the maximum record length (66–2140) for the output file in the Size of the largest online output record box. The recommended value is 214. This option is available only if you select Online in the Select Printer Model dialog box.

3. Type the maximum record length in bytes (66–300) for the output file in the Size of the largest offline output record box. The recommended value is 300. This option is available only if you select Offline in the Select Printer Model dialog box.

Tip: The fastest throughput on the printer occurs when you specify the maximum record size allowed.

4. Type the maximum block size for the output file in bytes (1032–11784). The maximum block length is the maximum number of 8-bit bytes (not words) allowed in each block. For offline printers, the recommended value is 8200. The maximum block size must be a multiple of four, and four bytes larger than the size of the record. This option is unavailable if you select Online in the Select Printer Model dialog box.



Printer Interface

The metacode Printer Interface tab enables you to define the interface used on the destination printer. This option is available only for online printing applications.

To select your printer interface:

1. Select the Choose Printer Connection Hardware check box to choose your printer interface. The Output Format Tool selects the type of output format based on the type of hardware (or black box) connecting the printer to the host computer.

Figure 55. Metacode Printer Interface Tab



2. Choose the brand of interface (or black box) used on the destination printer.

If you select Spur, continue with the following steps.

If you select any other interface, you can click OK and exit the dialog box.

3. Choose whether the Spur output format type (or black box type) is 8-bit transparent, 7-bit ASCII hex with or without a counter, or EBCDIC hex without a counter.

4. Select the Insert ASCII carriage control check box to insert an ASCII carriage control preceding each record.

5. Type the decimal value of the control escape character you want to precede each record transmitted in transparent mode. The default setting of 31 generally applies.

6. Type the decimal value of the control operation code character that immediately follows the transparent control escape character at the start of each record. This option is usually left at the default setting.



Output Options

The metacode Output Options tab enables you to define conditional output options as well as specify multi-file output.

If you select Output normally for your conditional output option, the following list of error conditions can cause the suppression of the output. The program ceases output to the printer at the point that the error occurred. An attempt is made to suppress the output, but on some systems this is impossible.

• The metacode job requests fonts that are not defined in the PDEF file that is specified in the job.

• The same PDE list font location is assigned in the PDEF file to two different fonts.

• A read/write error was encountered during document saving or merging.

Figure 56. Metacode Output Options Tab



• Commands are not complete for an online job. The record format was not listed for the DJDE in the Configuration file command, or a JDE or JDL was omitted in the PDEF file.

• An error occurred in DJDE, RAUX, ROFF, or RSTK definitions.

• The data overflows the page because there are too many text characters in the page.

To customize your output options:

1. Choose whether to output normally, suppress the output when a fatal error is reported, or suppress the output and save it to a file.

2. Select the Enable multiple print files check box to enable multiple print files. An OUTF command must appear in the tagged text file, and you must enable multiple print files in the PDEF file.

PDFThe PDF Output Options dialog box enables you to select your hyperlink, bookmark, shading and line, compression, and conditional output options.



Output Job Setup

The PDF Output Job Setup tab enables you to define your hyperlink and bookmark options, as well as your select your page range.


1. Select the Enable hyperlinks check box to use hyperlinks in your PDF output. If you clear this check box, skip to Step 6.

2. Select the Draw outline around link check box to instruct the output formatter to draw a box around the link text in the output file. If you clear this check box, skip to Step 6.

3. Choose whether the outline is a solid or dashed line.

Figure 57. PDF Output Job Setup Tab



4. Select the outline color by typing the red, green, and blue values in the appropriate boxes, or by clicking Color to select the color from the Color dialog box.

5. Select whether the matching of link sources with their destinations is case dependent or independent.

6. Select the Enable Bookmarks check box to use bookmarks in you PDF output. If you clear this check box, skip to Step 8.

7. Select whether to open the top level of the bookmarks, or open at a level you specify. If you choose to open at a specific level, type the level number in the box.

8. Choose whether to print all the pages or a range of pages. If you choose to print only a selected range of pages, type the first and last page numbers in the range in the corresponding boxes.

9. Choose how you want your document to view in PDF. Select:

– No rotation if you want the document to view in the same rotation in which you created the that pages.

– Head-to-head pages if your document is landscape, but you want it to view in PDF in portrait orientation.

– Head-to-toe pages if your document is landscape and inverse landscape, but you want it to view in PDF in portrait orientation.

– All pages if your document has both landscape and portrait pages, but you want to view all pages in portrait orientation.




The PDF Shading and Line Options tab enables you to define the number of passes through the input file for shading of text, shading percentages, and line settings.

Figure 58. PDF Shading and Line Options Tab



To customize your shading options:

1. Choose whether to make one or two passes of the input file shading commands.

Keep in mind that specifying only one pass increases the processing speed; however, two passes may be more desirable for your output.

Two passes are made through the input file to ensure that the shading prints first. Then, the text is imposed over the printed shading on the second pass. Unless you specify this method, text overwritten with shading disappears rather than being printed over the shading.

2. (Two passes only) Select whether to isolate only the light, medium, and bold shading commands, or to isolate all the rule commands.

3. Define the percentage of shading you want for your rules. You can specify a percentage for light, medium, and dark rules.







Output File Compression

The PDF Output File Compression tab enables you to define image compression and specifies accuracy or size emphasis.

To customize your output file compression options:

1. Select the Enable compression of images check box to compress images that are stored in the content repository and in the PDF output files. The images are compressed into the CCITT G.4 format (binary) before they are converted into the ASCII85 format (required by the output formatter).

Figure 59. PDF Output File Compression Tab



2. Select the Enable Text Compression check box to compress the text in the PDF output file. Enter the amount of compression in the box. The compression value can be an integer from 1-9. One is the least amount of compression and nine is the highest amount of compression. The default is 6.

3. Choose whether the output formatter should always use absolute move commands for accuracy in justified text, or use spaces when possible for a smaller, faster output file.

– Absolute move commands are values that are used for spacing between words. These values are calculated from the Configuration/Widths file, and are variable based on the placement of the text, which is useful for justified text.




Output Options

The PDF Output Options tab enables you to define conditional output options.

To customize your conditional and multiple file output options, choose whether you want the output formatter to:

• Transfer the final document normally to the selected output device.

• Suppress the document if a fatal error occurs.

• Save the document in its output format to a disk without transferring the document to the printer or viewer.

Figure 60. PDF Output Options Tab



PostScriptThe PostScript Output Options dialog box enables you to customize your output file format, compression, and comments, as well as conditional output and shading and line options.

Output Job Setup

The PostScript Output Job Setup tab enables you to define options for the number of copies, page range, collating, simplex or duplex printing, and offset output.

Figure 61. PostScript Output Job Setup Tab




1. Choose whether you want CompuSet to control the copy count or whether you want to specify the number of copies to print here.

2. If you choose to specify the number of copies here, type the number (up to 9,999 for DocuTech or DocuPrint models and 999 for all other printers) in the Number of copies box.

3. Choose whether to print all the pages or a range of pages. If you choose to print only a selected range of pages, type the first and last page numbers in the range in the corresponding boxes.

4. Choose no collating action, collated, or uncollated printed pages.

5. Choose whether you want to print simplex or duplex and whether you want duplex with short side binding or long side binding.

6. Choose whether to perform no offsetting action, to have no offset in the output bin, or to offset the job in the output bin. Choose Offset the job in the output bin to stagger the output left to right in stacks like the bin of a copy machine.




The PostScript Shading and Line Options tab enables you to define the number of passes through the input file for shading of text, as well as line settings.

Figure 62. PostScript Shading Options Tab



To customize your shading options:

1. Choose whether to make one or two passes of the input file shading commands.

Keep in mind that specifying only one pass increases the processing speed; however, two passes may be more desirable for your output.

Two passes are made through the input file to ensure that the shading prints first. Then, the text is imposed over the printed shading on the second pass. Unless you specify this method, text overwritten with shading disappears rather than being printed over the shading.

2. (Two passes only) Select whether to isolate only the light, medium, and bold shading commands, or to isolate all the rule commands.

3. Define the percentage of shading you want for your rules. You can specify a percentage for light, medium, and dark rules.







Output File Compression

The PostScript Output File Compression tab enables you to define image compression and specifies accuracy or size emphasis.

Figure 63. PostScript Output File Compression Tab



To customize your output file compression options:

1. Select the Enable compression of images check box to compress images that are stored in the content repository and in the PostScript output files. The images are compressed into the CCITT G.4 format (binary) before they are converted into the ASCII85 format. The output formatter requires the ASCII85 format to print the files.

2. Choose whether the output formatter should always use absolute move commands for accuracy in justified text, or use spaces when possible for a smaller, faster output file.

– Absolute move commands are values which are used for spacing between words. These values are calculated from the Configuration/Widths file, and are variable based on the placement of the text, which is useful for justified text.




Output Options

The PostScript Output Options tab enables you to define conditional output options as well as specify multiple file output.

To customize your conditional and multiple file output options:

1. Choose whether you want to transfer the final document normally to the selected output device, suppress the document if a fatal error occurs, or save the document in its output format to a disk without transferring the document to the printer or viewer.

2. Select the Enable multiple print files check box to produce multiple output files as specified in the input file.

Figure 64. PostScript Output Options Tab



Output File Comments

The PostScript Output File Comments tab enables you to define the text you want to display in the PostScript creator comment line, and up to five PostScript comments.

Figure 65. PostScript Output File Comments Tab



To customize your PostScript file comments:

1. Type the text you want to replace the default creator comment CompuSet version xxx in the PostScript comment header that begins each PostScript document. The comment can be from 1 to 65 characters in length.

2. Type any comments you want to appear in the comment lines that are inserted after the first line of the PostScript header. You do not need to insert quotes around the comments; the PostScript Output Format Tool does this automatically. Up to five PostScript comments can be entered (up to 65 characters each) and are output in the same order as you enter them here. The PostScript output formatter does not verify any user comments. It simply echoes the text to the output file, preceded by %%.

Output File Format

The PostScript Output File Format tab, shown in Figure 66 on page 178, enables you to define the format of PostScript records to be output by the PostScript output formatter and identifies print job specifications.



Caution: It is recommended that you do not change options on this tab unless you are very experienced at creating PDEF files. Use the default values instead of overriding any of the options on this tab.

To customize your output file format options:

1. Choose printer formatted output or punch formatted output from the Output type list.

2. Choose whether the output file has variable length records or fixed length records padded with blanks.

3. Type the maximum record length (60 to 255 bytes) in the Maximum record length box.

Figure 66. PostScript Output File Format Tab



4. Choose whether to omit any line ending sequence, append carriage returns and line feeds (Windows), append only carriage returns (Mac), append only line feeds (UNIX), or append a hex value. If you choose to append a hex value, type the value in the Customized line ending sequence (hex value) box.

5. Select the output file character code to be one of the following options:

– ASCII 7 bit with characters above 127 in octal

– ASCII 8 bit

– EBCDIC

– ASCII double byte encoded to EBCDIC

– EBCDIC double byte encoded to EBCDIC

6. Choose whether to omit PCC bytes, whether a overprint (plus sign) is a PCC byte, or whether a print and space 1 (blank) is a PCC byte.

Print Job ReportingThe Print Job Reporting dialog box enables you to customize your printer message reporting and accounting options.

Note: The Print Job Reporting dialog box is available only if you are creating metacode output.



Messages and AccountingThe Messages and Accounting tab enables you to define the cost center to charge for the job and the messages to appear to the operator on the printer console.

To customize your message text and specify a cost center:

1. Type the name of the department or cost center you want to be charged for the job. The name can be up to 31 characters, and should not be enclosed in quotes. The Output Format Tool automatically converts lowercase text to uppercase text as you type. A report can be produced at the printer detailing the printer usage for each cost center. The cost center or department name must be entered at the printer console before it will be recognized by the output formatter.

Figure 67. Metacode Messages and Accounting Tab



2. Select the Display Console Messages check box to display console messages. Clear it to suppress all messages.


4. Choose whether the message should appear before the job, after the job, or before a specific copy prints.

5. Enter the number of the copy you want print after the message appears (up to 32,765 copies). This option is only available when you select Before copy in the Type of Message column.

6. Type the message text you want to appear on the printer console.

7. Choose whether you want the message to appear without stopping the printer, or whether you want the printer to stop when the message appears.

Printer-Specific SettingsThe Printer-Specific Settings dialog box enables you to specify printer options, features, and any special finishing options that apply for the selected printer type. This dialog box is not available if you select Generic PostScript in the Select Printer Model dialog box.

Note: The Printer-Specific Settings dialog box is available only if you are creating PostScript output.

Printer FeaturesThe Printer Features tab appears for all printer models, but the information on the tab varies depending on the type of printer you have specified. Read the following sections for information about these tabs.



DocuTech/DocuPrint

The Printer Features tab enables you to send PostScript output to a DocuTech or DocuPrint printer

To customize DocuTech or DocuPrint printer features:

1. Choose whether you want to print the output and not save it on a server, save the output on a sever but not print it, or print the output and save it on a server.

2. Type the corresponding names or messages for the following categories:

– Job Name

– Sender Name

– Recipient Name

Figure 68. PostScript Printer Features Tab — DocuTech/DocuPrint



– Account Name

– Banner Message

– Operator Message

– File name on Network Server

– File name for Decomp Services

3. Choose whether you want images placed relative to the illustration area, or relative to the page.

Lexmark

The Printer Features tab enables you to send PostScript output to a Lexmark Optra printer.

Figure 69. PostScript Printer Features Tab — Lexmark



To customize printer features for a Lexmark printer:

1. Choose 600 or 300 dpi (dots per inch) for the printer resolution. Choose 300 dpi when the printing speed of is more important than the resolution.

2. Select the Display operator messages on printer panel check box to show operator messages on the Lexmark printer panel.

PostScript Level 2 or DocuColor Models

The Printer Features tab enables you to send PostScript output to a PostScript Level 2 or DocuColor printer.

Figure 70. PostScript Printer Features Tab — PostScript Level 2/DocuColor



To customize your printer features for a PostScript Level 2 or DocuColor printer:

1. Choose a standard printer resolution or a specific resolution.

2. If you choose to select a resolution, select either 300 or 600 dpi (dots per inch).

Xerox 4700

The Printer Features tab enables you to send PostScript output to a Xerox 4700 Color Document Printer (CDP).

Figure 71. PostScript Printer Features Tab — Xerox 4700 CDP



To customize printer features for a Xerox 4700 CDP printer:

1. Choose whether to output standard PostScript output, or to insert the =MCK= EMULATE/Postscript/END command at the start of the job and the =MCK= RESET/END command at the end of the file.

2. Type the name of the job to appear in the %XRXJob: comment line.

3. Select the First page is a banner page check box if the first page of the job is a PostScript banner page that is not part of the print job. A PostScript banner page is different from (and usually an addition to) an operating system banner page.

Printer FinishingThe Printer Finishing tab shown in Figure 72 on page 187 enables you to define a variety of printer features that determine how your output is finished on a DocuTech printer. Some of these options may not be supported by all PostScript printers.



Note: This tab is available only if you select a DocuTech or DocuPrint printer.

To customize your DocuTech finishing features, select one of the printer finishing options. Any options that are not supported by the selected printer are unavailable. You can refer to the graphic on the right side of the Printer Finishing tab to see an illustration of the finishing option you have selected.

Note: If you specify Booklet as the special document type, the Booklet maker job, Signature job, and Booklet maker and signature job options on this dialog box are unavailable.

Figure 72. PostScript Printer Finishing Tab



Variable Print Specification The Variable Print Specification (VPS) tab enables you to specify that you want your PostScript job to use VPS output.

Note: This tab is available only if you select a DocuColor printer.

Figure 73. PostScript Variable Print Specification (VPS) Tab



To define VPS options:

1. Select the Enable VPS check box.

2. Type the name of the VPS job. The name can be 1-60 characters long and contain letters, numbers, and the underscore (_).

Do not include a file extension or specify a path as part of the file name. The controller operator specifies the path, which may be based on the print queue used to print the job or may be assigned to an individual job.

3. Select the Enable VPS Booklet and Side-by-Side printing check box to enable the controller to manage multiple imposition and n-up printing instead of using CompuSet imposition and n-up commands.

Emitter LogThe Emitter Log dialog box enables you to set content repository and memory log options, severity levels, and message date and time format options.



Message LogThe Message Log tab enables you to define content repository and memory log options for the output formatter message log file.

To customize your message log options:

1. Choose whether to log successful content repository and memory merges.

2. Choose whether to log successful content repository and memory saves.

Figure 74. Message Log Tab



3. Choose whether to list content repository resources (images, forms, documents) in the log file. You can list resources after renaming and deleting (and before processing any COMPUSET commands), after all processing, or before and after processing.

4. Type your page count sentinel in the Page number label box. This sentinel prints with the page count accumulator in the batch job log file and provides a uniform string of characters for locating page count accumulator numbers using automatic searching routines. If you use the page number label, you must have page numbers in your input.

Customize Error MessagesThe Customize Error Messages tab enables you to define an override for preset condition codes. This override resets the error code produced, on a message by message basis, when the output formatter encounters an error during execution.

Figure 75. Customize Error Messages Tab



To customize your error messages:

1. Select, from the Change message severity level list, the maximum severity level to generate an error condition when the output formatter encounters a problem during execution. This enables you to identify the types of problems that generate error conditions. The following options are available:

– Warning, Error to Information. Warnings and errors are changed to a severity of Information.

– Fatal to Error. Fatal errors are changed to a severity of Error.

– Fatal, Error to Warning. Errors and Fatal errors are changed to a severity of Warning.

– Fatal, Error, Warning to Information. Fatal, Error, and Warning errors are changed to a severity of Information.

– Use program default severity levels. Makes no changes to the severity levels and uses the program default values.

– Specify custom severity levels below. Changes specified messages to specific condition codes.

2. If you choose to specify custom severity levels, click Add to add a new row to the table.

3. Choose the new severity (information, warning, error, or fatal) that you want to apply to specific message numbers. This changes the severities of the messages listed in the Messages column to the new severity you specify.

4. Type the message numbers (separated by commas) to be changed to the new selected severity. You can type up to 72 characters in the Messages column for each row.



Message FormatThe Message Format tab enables you to define the date and language format for error messages.

To customize your message format:

1. Choose the date and time format for the output formatter log.

2. Choose a language for the output formatter log file.

Figure 76. Message Format Tab



Embedding Tag Logical Elements (TLEs) in Your AFP Output FileIf you want to embed TLEs in your AFP output file, you will need to complete a few configuration steps:

• Setup CompuSet Indexing for AFP

• Configure Settings in ofp.properties

• Ensure All Settings Match

To determine if TLEs should be embedded, xPression checks for two conditions before running the AFP emitter. First, it checks for is the existence of valid index files for your document. Secondly, it checks for TLE commands in your ofp.properties file that correspond to one or more of your index files.

If both conditions are met, xPression adds the TLE commands from your ofp.properties file to the automatically generated .emitopt (PDEF) file and calls the AFP emitter. The AFP emitter uses the settings in the .emitopt file to create your TLEs.

Additionaly, the linked emitter must be disabled if you want to embed TLEs. The linked emitter functionality is disabled when any output processing functionality (for example, multiple output streams) is used.

Setup CompuSet Indexing for AFPTLEs can only be embedded if CompuSet indexing is configured for your AFP output. You must associate each TLE that you want to embed with a valid index file.

Your index files will be named with the following format: nnnnnnnnnnnn-<index_number>.inx

Where n is a system generated number and <index_number> is the number of your index. There can be up to 12 indexes, so your index files can have any number between 1 and 12. For example:

1121466318387-1.inx



Configure Settings in ofp.propertiesLocate and open your ofp.properties file in your xPressionHome directory. By default, this directory is C:\xPression or /opt/xPression.

Place the commands to create your TLEs in this file as follows:

AFPIFLD<index_number>=IFLD 1,1,1,1,1,1,1,1,1,1,1,,,,,,,,,,,,,,, AFP INDEX

AFPINDX<index_number>=INDX 1,1,'Identifier',,,,,,,,,,,,,,,,,,,,,,,

where <index_number> is the number of the index file you are associating with this TLE.

For a description of these parameters, reference the CompuSet IFLD and INDX commands.

Ensure All Settings MatchEnsure that the index number(s) in ofp.properties file matches the index number(s) of your index file(s).

To demonstrate, the following example show a set of matching index file settings and TLE commands.

Index File: 1121466318387-1.inxIndex Tag: <IN,1,1,1,6,4,0,0,2,0/sk>

<I,1,1/sk>{POLICY.CONTRACTNUMBER}

TLE Commands: AFPIFLD1=IFLD 1,1,1,1,1,1,1,1,1,1,1,,,,,,,,,,,,,,, AFP INDEXAFPINDX1=INDX 1,1,'PolNumber',,,,,,,,,,,,,,,,,,,,,,,


196

Chapter 5Working With the Image Utility

xPression enables you to add images and precomposed documents to your content. All your images and precomposed documents are stored in the content repository.

You can use the xPression Image Utility to add, delete, and manage the images, precomposed documents, and Variable Merge Frames (VMFs) contained in your content repository.

This chapter discusses only the resources related to CompuSet, the content repository holds much more than what is discussed here. The information in this chapter includes not only instructions on using the Image Utility, but also specifications and formats for the resources.

This chapter includes the following topics:

• When Do I Use the Image Utility?

• What CompuSet Resources Can I Manage with This Utility?

• Using the Image Utility

For a full discussion of the content repository, see the xPression System Administrator’s Guide.


Chapter 5 - Working With the Image Utility197

When Do I Use the Image Utility?The Image Utility is not the only way you can add or update resources in the content repository. xPression Design enables you to update the content repository while you are creating your document in Microsoft Word. In most cases, you should update and manage your resources while in xPression Design. You should use Image Utility in the following cases:

• You have resources that you do not want other users to have access to. For example, logos or signatures.

• You want to edit Variable Merge Frames (VMFs).

• You want to import IMG files into the content repository.

• You want to import images, precomposed documents or VMFs from existing Merge libraries into the content repository.

• You want to import an entire Merge library into the content repository.

What CompuSet Resources Can I Manage with This Utility?The content repository holds all the images, precomposed documents, and VMFs that you use in your xPression jobs. This is a common container available to all the jobs run at your site. With the Image Utility, you can add or manage any precomposed documents (metacode, PostScript (including EPS), PCL) or forms. You can also add or manage these image formats:

• Xerox IMG (.img)

• TIFF (.tif or .tiff)

• JPEG (.jpeg, .jpg, .jfif, or .jpe)

Note: The Image Utility does not support importing externally-created AFP or PDF documents.



Resource Specifications and FormatsThe resources managed through the Image Utility should be formatted according to the CompuSet recommendations and specifications when they are created so that you get the best possible results in xPression. This section describes the specifications and formats for the resources supported by xPression.

PostScript Specifications

This section describes how PostScript documents function, what the document structuring conventions are, and how to work with the conventions and variable format frames.

• PostScript Documents. PostScript is a powerful page-description language that is also a programming language. You can define and call subroutines in a PostScript print file. When you create and call subroutines, you have really defined your own set of commands. These application-dependent commands can contain important printing functions, such as font selection or the command to print a page and advance to a new page. Because these important printing instructions are embedded in application-dependent command definitions, which may or may not be used, it is very difficult to detect which fonts are selected or where page breaks are invoked.

• When CompuSet attempts to import a PostScript document or image, there are two different sets of application-dependent commands: one for CompuSet and one for the imported document or image. Document and image merging begins with CompuSet commands to identify the Merge library element. If you define them, Variable Merge Frames (VMFs) that are associated with the imported document are also supported with CompuSet commands. The imported document to be merged has its own embedded PostScript formatting commands. Therefore, two print environments are created and the PostScript emitter must be able to differentiate between the two and make all relevant print command definitions available to the destination printer. If the PostScript emitter interprets only CompuSet print commands, the embedded command definitions in the imported document can be lost or ignored.

• Document Structuring Conventions. To help import one PostScript document into another PostScript document, Adobe Systems (the creator of PostScript) has proposed PostScript language standards, known as Document Structuring Conventions. These standards are conventions only



and are not part of the PostScript language. Compliance is voluntary; they are suggestions and not language requirements.

PostScript output for documents that follow these conventions consists of two parts, the prologue and the script. The prologue contains the definitions for all the application-dependent commands. The script describes how to print the pages in the document using these commands. The prologue has three parts that are described in the following list. When the document conforms to these prologue conventions, comments indicate where you can find the beginning and end of the header, command definitions, document setup, and each page.

• Header. Consists of a series of comments that describe some of the global properties of the document, such as the number of pages, paper size, and required fonts.

• Command Definitions. All application-dependent commands must be defined in the prologue; no commands can be defined in the script. The page descriptions in a multiple-page document must be self-contained to ensure that pages can be printed in any order after the prologue.

• Document Setup Commands. Each page must begin with the comment:

%%Page:nn

where nn is the page number.

• Conforming to Conventions. PostScript documents must conform to the Adobe Document Structuring Conventions (ADSC) if the document is to have page independence and portability. The degree of compliance depends on the PostScript printer driver for the individual application. Many Microsoft Windows and Apple Macintosh applications are improved when you substitute the Adobe PostScript printer driver for the one supplied by Microsoft or Apple.

A typical application error is to format variable data on a page, such as a header or footer and merge an imported PostScript document. When the document prints, the variable data is missing. This error occurs because some PostScript documents issue non-conforming commands that erase the page before printing the document. If you edit the PostScript document produced by the PostScript emitter, you can find the variable data, but it is erased by the merged document.



Because the PostScript emitter follows Adobe conventions, merged documents and images that adhere to these standards produce conforming documents. If you import a Postscript document or image that does not conform to these standards into a Merge library, every job that merges this document becomes non-conforming. If you merge conforming documents, or documents generated by COMPUSET and the PostScript emitter, the result is always a document that conforms to ADSC conventions. For information about repairing non-conforming PostScript files, refer to the Adobe Web site at http://www.adobe.com.

• Conventions and Variable Merge Frames. CompuSet requires imported PostScript documents that are to be used with VMFs to fully conform to the ADSC. If these conventions are used partially, or omitted, in the imported document, CompuSet imports the document and stores it in a Merge library; however, when it is merged, variable data can be included only on the first page of the document and no VMFs are permitted. Successful importing and merging of PostScript documents depends on the degree of compliance with the conventions in the imported document. Ultimately, trial and error will determine the degree of compliance with individual imported documents.

JPEG Image Formats

The following are recommended specifications for a JPEG image that you want to import:

• You can generate JPEG images with standard graphics programs; however, the image should be in the JPEG File Interchange Format (JFIF), with one image per file.

• Specify only RGB color.

• Specify standard compression, instead of progressive compression, for maximum compatibility with PDF and Adobe Acrobat Reader.

• The Tiff Importer recognizes only portrait orientation where the color pixels are scanned from top to bottom and left to right.

• Generate the JPEG image with 8-bit color for each pixel.

• Generate the JPEG image with one frame and one scan per image.


http://www.adobe.com


• The TIFF Importer will not import JPEG images embedded in a TIFF file, or JPEG images, created in the Still Picture File Format (SPIFF).

• All versions of Adobe Acrobat Reader support JPEG images using standard compression and RGB color.

• The PDF emitter does not support JPEG images that use CMYK color values.

• The AFP emitter can now merge JPEG images from a Merge Library and output the JPEG to AFP."

• You can use any of these graphics programs to generate JFIF-compliant images:

– Adobe Illustrator

– Photoshop

– CorelDRAW

– Corel PHOTO-PAINT

– Paint Shop Pro

To determine if other graphics programs will produce satisfactory results, create a test image and import it into a Merge library.

TIFF and IMG Image Formats

CompuSet supports importing and merging TIFF (Tagged Image File) files and JPEG images into a CompuSet Merge library using the TIFF Importer. The TIFF Importer stores TIFF format one-bit black and white bitmap files in a CompuSet Merge library by converting them into Xerox IMG format. It can reverse the process by extracting IMG format images from a CompuSet Merge library and converting them into TIFF one-bit black and white bitmap images. The TIFF Importer stores JPEG images in a CompuSet Merge library in the JFIF file format.

CompuSet can handle only black and white TIFF images directly. A third party graphics editor can be used to convert color and gray scale TIFF images into black and white images, or to edit images that are to be stored in a CompuSet Merge Library. Also, the Visual CompuSet Viewer can be used to view images in a CompuSet Merge library, or to convert color to black and white TIFF images.



CompuSet handles only JPEG images in the JFIF file format. The TIFF Importer does not import JPEG images saved in the SPIFF file format or images embedded in a TIFF file.

The TIFF Importer executes on these operating system platforms:

• IBM z/OS

• All supported UNIX platforms

• All supported Windows platforms

On a Windows host, the TIFF Importer can generate proof bitmaps for the Visual CompuSet Viewer in batch mode.

Naming Your ResourcesYou can have multiple resources in the content repository with the same name, as long as they are different object types. For example, you can a have a PostScript precomposed document and a PDF precomposed document that have the same name, because they are different formats. You can also have an IMG image and a JPEG image that have the same name, or a PostScript precomposed document and a JPEG image with the same name.

You can’t have two resources that are the same object type with the same name in the content repository. For example, you can’t have two PDF precomposed documents called “CoverLetter”, or two IMG images called “Signature”.

What About My Merge Libraries?xPression does not use Merge libraries to hold document components; it uses the more robust content repository instead. If you have existing Merge libraries, you need to move the contents of those libraries into the content repository.

You can use the Image Utility to import existing images into the content repository that you previously exported from a Merge library. You can also open an existing Merge library in the Image Utility and copy and paste, or drag and drop resources into the content repository.



You can also place copies of all the Merge library images and precomposed documents referenced in your products into the content repository during the upgrade process. For assistance with upgrading, please contact your Document Sciences representative.

Using the Image UtilityThe content repository stores images, precomposed documents, and VMFs that you can merge into your xPression jobs. This section describes how you can use the Image Utility to access the content repository to view and update CompuSet resources, import and export those resources, and perform a variety of other tasks.

This section discusses these topics:

• Launching the Image Utility

• The Main Window

• Working with CompuSet Resources

• Copying Resources From a Merge Library

• Converting Images to xPression Publish Images

• Importing Resources

• Exporting Resources

• Viewing an Image

• Rotating an Image

• Combining Images

• Viewing Properties

• Searching for a Resource

• Variable Merge Frames



Launching the Image UtilityThe Image Utility is one of the tools provided with the xPression CompuSet Tools application.

To launch the Image Utility:


2. Double-click Image Utility. The Connect to xPression dialog box appears.

3. Select your xPression server from the drop-down list.

4. Type your user name and password. Click OK. The Image Utility main window appears, as shown in Figure 78 on page 205.


Figure 77. Connecting to xPression



The Main WindowThe Image Utility main window is divided into two panes. The Tree view displays folders that contain the images, precomposed documents, and VMFs in the content repository. The Resource Information view displays detailed information about each resource in the selected folder. As you select resources in the Tree view, the Resource Information view shows the detail for that resource.

Figure 78. Image Utility Main Window



Tree View

All the images, precomposed documents, and VMFs located in the content repository display in the Tree view. The Image Utility groups these resources into folders according to resource type. The following table describes each resource type.

You can double-click images and precomposed documents in the Tree view to view them. Double-clicking an image displays its proof image, and double-clicking a precomposed document opens it with the Merge Document Viewer. For more information, see Using the Merge Document Viewer.

Resource Information View

The Resource Information view displays resource properties, such as the name, date, number of pages, and fonts. The information that displays in the Resource Information view depends on which type of resource you select in the Tree view.

Resource Type Attributes

Precomposed Documents

Can be in Xerox metacode, PostScript, PCL, AFP, or EPS format. Precomposed documents can also be relocatable (fragments) or non-relocatable (single or multi-page).

VMFs Defined using CompuSet commands or by working with merge frames on the precomposed document. VMFs enable you to define the position of the tagged data and its formatting attributes for placement onto a precomposed form.

Images Imported from any compatible drawing package. Accepted formats are IMG, TIFF, and JPEG. Color images may only be EPS format, including full color data driven graphics.



Working with CompuSet ResourcesYou can use the Image Utility to import images and precomposed documents, as described in Importing Resources, and you can delete or rename an image or precomposed document. After you perform any of these actions, you can use Undo to reverse the changes, as long as you have not closed the tool. Once you close the tool, you cannot undo any changes.

To delete an element, do one of the following:

• Select the element you want to delete and, on the Edit menu, click Delete.

• Right-click the element and click Delete.

Caution: The Image Utility does not check to see if a resource is being used before deleting. Therefore, it is possible to delete a resource that is currently being used in production.

To rename an element:

1. Select the element you want to rename, and on the Edit menu, click Rename or right-click the element and click Rename.

2. Type the new name.

3. Press Enter to accept the new name.

Caution: Other objects reference image and precomposed document names during design. If you rename an image or precomposed document, you’ll need to update any references to it. If the xPression document has already been approved, this will cause problems. Rename an image or precomposed document only if you are absolutely certain it will not affect anything.



Copying Resources From a Merge LibraryYou can open a Merge library in the Image Utility and copy its resources into the content repository. The Merge library opens in a separate window so you can copy and paste or drag and drop resources.

To copy a resource from a Merge library:

1. On the File menu, click Open Merge Library. The Open dialog box appears..

2. Locate the Merge library you want to open and click Open. The Merge library opens in a new window, on top of the Image Utility window. You can have several Merge libraries open at a time.

Figure 79. Open Dialog Box



3. Drag the new window so you can see both the Merge library window and the content repository window.

Figure 80. An Open Merge Library



4. Copy a resource using one of these methods:– Right-click the Merge library resource you want to copy and click Copy. Right-click the

appropriate container folder in the content repository and click Paste.

– Click the Merge library resource you want to copy and, on the Edit menu, click Copy. Click the appropriate container folder in the content repository and, on the Edit menu, click Paste.

– Click the Merge library resource you want to copy and “drag” it into the content repository window and “drop” it in the container folder.

Converting Images to xPression Publish ImagesCompuSet images are not compatible with xPression Publish documents; therefore, if you convert a CompuSet document to an xPression Publish document, you must also convert any images used in that document to xPression Publish images. The Image Utility enables you to convert any of the CompuSet images you have stored in the content repository. When you convert an image, xPression makes a copy of that image in the xPression content repository, and formats it for xPression Publish output.

To convert an image to xPression Publish format:

1. Select the image.2. Select Convert to Publish from the File menu, or right-click and select Convert to Publish from

the shortcut menu. The Convert Image dialog box appears.

3. Specify the name for the new xPression Publish image.

Figure 81. Convert Image Dialog Box



4. Click OK. When the conversion is complete a confirmation message appears.

5. Click OK to complete the conversion.

Importing ResourcesYou can import images and precomposed documents into the content repository using the Image Utility. These formats are supported:

• PostScript (.ps)

• Encapsulated PostScript (.eps)

• Metacode document (.xrx)

• Metacode offline document (.xof)

• Xerox image format (.img)

• TIFF image format (.tif)

• PCL document (.prn, .pcl)

• JPEG (.jpeg, .jpg, .jfif, or .jpe)

Note: The Image Utility does not import VMFs, but you can use the Image Utility to copy them into the content repository from an existing Merge library. For more information, see Variable Merge Frames.



To import an image or precomposed document into the content repository:

1. On the File menu, click Import. The Import dialog box appears.

2. Select the type of image or precomposed document you want to import from the Files of type drop-down list.

3. Locate the file you want to import. Click Open. A message displays in the status bar to verify that the resource imported successfully.

For metacode, PCL, or PostScript precomposed documents, or IMG or TIFF images, a dialog box appears after you click Open, where you can specify import options. The following sections describe the import options for each format type.

Figure 82. Import Dialog Box



Metacode Import Options

When you import a metacode (.xrx) precomposed document into the content repository, the Import Metacode Options dialog box appears. You can:

• Leave the options set as they are.

• Click Default to set the options to their default values.

• Click Suggest to set the options to their recommended values.

• Select new values for individual options.

Figure 83. Importing Metacode Precomposed Documents



You can define these options:

• Page size. Type the page width and depth in points. If you don’t specify any values, the default width is 612 points (8.5 inches), and the default depth is 792 points (11 inches).

• PCC Byte. Type the value for the Printer Carriage Control (PCC) byte.

• Input type flag. Select whether:

– The printer is online or offline.

– To spool to a printer that accepts ASCII or EBCDIC carriage control bytes.

– To strip the carriage control byte.

– The DJDE header packet is ASCII or EBCDIC.

• Orientation. Select how you want the imported precomposed document oriented.

• Blocked/unblocked flag. Select from these options:

– Disk, Unblocked. Input disk file is unblocked for online LPS printing.

– Disk, Blocked, non-CompuSet. Input disk file is blocked for offline printing.

– Disk, Blocked, CompuSet. Input disk file was produced by CompuSet and is blocked in IBM VB format.

– Tape, Blocked, CompuSet. Input tape file was produced by CompuSet and is blocked in IBM VB format.

• Zero length record flag for blocked data. Select this check box to specify that a record length of zero indicated that end of tape or disk bock in a variable blocked formatted file. Clear this check box to process a record length of zero normally.

You can also define advanced options for importing a metacode precomposed document. Click Advanced to display the Advanced Meta Options dialog box. The Advanced Meta Options dialog box displays the selected parameters for the DOCUTL commands used to import metacode precomposed



documents. You can enter additional parameters for the commands, or specify a Configuration file that contains the parameter information.

On the Advanced Meta Options dialog box, you can:

• Enter or edit the parameters for the following commands:

– MRAX. Recognizes RAUX commands in the input file.

– MROF. Recognizes ROFFSET commands in the input file.

– MRST. Recognizes RSTACK records in the metacode input file.

– MDJD. Defines the DJDE record structure.

– MALN. Defines physical page size.

– META. Imports a metacode print file into the content repository.

• Enter a Configuration file path and name, or click Browse to select a file.

Figure 84. Advanced Metacode Import Options



PCL Import Options

When you import a PCL (.pcl or .prn) precomposed document into the content repository, the Import PCL Options dialog box appears. You can:






• Page. Type the page width and depth in points. If you don’t specify any values, the default width is 612 points (8.5 inches), and the default depth is 792 points (11 inches).

• Record length. Specify the maximum record length in bytes. The default it 80 bytes.

Figure 85. Importing PCL Precomposed Documents



PostScript Import Options

When you import a PostScript (.ps or .eps) precomposed document into the content repository, the Import PostScript Options dialog box appears. You can:




Figure 86. Importing PostScript Precomposed Documents





• Page. Select the Define Size check box to define a page size. Type the page width and depth in points. If you don’t specify any values, the default width is 612 points (8.5 inches), and the default depth is 792 points (11 inches).

• Line ending sequence flag. If you are using z/OS, select a line ending sequence flag. if you choose Use hex value, type the value, which can be 1–8 hexadecimal digits.

• Character code. Select the character code of the input file. The default is ASCII.

• PCC byte. Select the Printer Carriage Control (PCC) byte.

• Multiple documents in the input file. Select this check box to indicate that multiple documents are concatenated together in the same file. Clear this check box to treat the entire input file as one document.

• Type of PostScript document. Select the type of PostScript document. An Encapsulated Postscript (EPS) page fragment can be a text fragment or an image.

You can also define advanced options for importing a PostScript precomposed document. Click Advanced to display the Advanced Import PostScript Options dialog box. The Advanced PostScript Options dialog box displays the selected parameters for the DOCUTL command used to import PostScript precomposed documents. You can enter additional parameters for the POST command, or specify a Configuration file that contains the parameter information.

Figure 87. Advanced Import PostScript Options



On the Advanced PostScript Options dialog box, you can:

• Enter or edit the parameters for the POST command. The POST command converts PostScript to content repository format.


IMG Import Options

When you import an IMG (.img) image into the content repository, the Import IMG Options dialog box appears. You can:




Figure 88. Importing IMG Images




• Orientation. Select how you want the imported image oriented.

• Image file has a header. Select this check box if the image file has a header. Clear this check box if the image file does not have a header.

• Source of the image. Select whether the source is a centralized printer labeled magnetic tape, or a centralized printer disk file in HOSTCOPY format.

• Extended label flag. Select to use the printer file name as the content repository name, or use the full content repository name of the image.

TIFF Import Options

When you import a TIFF (.tif or .tiff) image into the content repository, the Import TIFF Options dialog box, shown in Figure 89 on page 221, appears. You can:







• Rotation of the image. Select how you want the imported image rotated (or oriented).

• Rotation(s) to store. Select one or more rotations (orientations) for storing the image. You can store multiple rotations.

• Resolution to store. Select the resolution for the stored image.

Figure 89. Importing TIFF Images



• Scaling to apply. Select a scaling option:

– Do not Scale. Does not attempt to scale the image.

– Maintain the size. Scales the image if the input resolution is different from the content repository resolution, This option ensures the image remains the same size as the original.

– Scale to fit. Scales the image to fit the specified size in the Width and Height fields.

• Cropping to apply. Select which edges you want to crop to fit the dimensions specified in the Width and Height fields.

• Size, in points. Specify the width and height of the converted image, in points. Define values here only if you are scaling or cropping the image.

• Generate PC proof version of the imported image. Select this check box to generate a proof of the converted image.

• Replace the existing component with the same name. Select this check box to replace any image of the same name in the content repository.

Note: If you do not request image scaling when importing an image, the Image Utility stores the image bit-for-bit using the specified resolutions, For example, if you store a 600 dpi image at 300 dpi, the stored image is four times the size of the original when it displays.

Exporting ResourcesYou can export resources using the Image Utility. This can be useful if you want to use a resource outside of xPression. For example, someone who does not have access to xPression or the content repository may need to update an image or precomposed document. Certain resource types require options to be selected before the resource can be exported. However, the first few steps for exporting are the same regardless of the format you are exporting.



To export a resource:

1. Select the image or precomposed document that you want to export in the Tree view.

2. On the File menu, click Export. The Export Image dialog box appears.

3. Locate the directory where you want to export the file.

4. (Optional) Type a new name in the File name text box.

5. Click Save.

For PostScript precomposed documents, and IMG and TIFF images, a dialog box appears where you can specify export options. The following sections describe the export options for each resource type.

Figure 90. Export Image Dialog Box



PostScript Export Options

When you export a PostScript (.ps or .eps) precomposed document from the content repository, the Export PostScript Options dialog box appears. You can:





• Output file format. Select the record format of the file.

• Output character code. Select the type of character code.

• PCC byte. Select the type of Printer Carriage Control (PCC) byte.

Figure 91. Exporting PostScript Precomposed Documents



• Record length. Type the maximum record length, in bytes. This value must be less than 255. The default value is 132 bytes for printer formatted records, and 80 bytes for punch formatted records.

• Record length type. Select the type of record length.

• Line ending sequence flag. Select the line ending sequence flag. If you select Append hex value, type the value, which can be 2–8 hexadecimal digits.

You can also define advanced options for exporting a PostScript precomposed document. Click Advanced to display the Advanced PostScript Options dialog box. The Advanced Export PostScript Options dialog box displays the selected parameters for the DOCUTL commands used to import PostScript precomposed documents. You can enter additional parameters for each command, or specify a Configuration file that contains the parameter information.

On the Advanced Export PostScript Options dialog box, you can:

• Enter or edit the parameters for these commands:

– POUT. Defines PostScript output parameters.

– DOCL. Produces an export sample of a document from the content repository in a format that is ready for printing.


Figure 92. Advanced Export PostScript Options



IMG Export Options

When you export an IMG (.img) image from the content repository, the Export IMG Options dialog box appears. You can:





• Image orientation. Select the how you want the exported image oriented. If you select All orientations, the export utility replaces the last letter of the file name with the letter P for portrait, L for landscape, I for inverse portrait, or J for inverse landscape.

• Output type. Select how you want to output the image.

Figure 93. Exporting an IMG Image



• Extended label flag. Select the type of Xerox 9700 tape labels you want to generate.

• Image type. Select the type of image you want to export.

TIFF Export Options

When you export a TIFF (.tif or .tiff) image from the content repository, the TIFF Export Options dialog box appears. You can:





• Rotation to extract. Select the rotation of the TIFF image that you want to export.

• Rotation to output. Select the rotation of the exported TIFF image.

• Compression. Select the type of compression for the exported TIFF image.

Figure 94. Exporting a TIFF Image



Viewing an ImageYou can use the Image Utility to view images in the content repository by doing one of the following:

• Select the image and click the View button on the toolbar.

• Select the image and, on the View menu, click Image.

• Right-click the image and click View.

• Double-click the image.

Note: When you view a two-color image, only the black portion (plane) displays. If you want to view the image in color, you must first compose the document.

Rotating an ImageYou can change the rotation of an image in the content repository to portrait, landscape, inverse portrait, or inverse landscape. This enables you to store the image in the rotation you will use it.

To rotate an image:

1. Select the image in the Tree view.

2. On the Options menu, click Rotate Image. The Rotate Image dialog box, shown in Figure 95 on page 229, appears with the current rotation of the image selected in the From section.



3. Select the new rotation in the To area.

4. Click OK to change the rotation.

Combining ImagesThe Image Utility enables you to combine two .img files of the same size into one file for use in highlight color printing. Using this option, you can combine a black and white image with a highlight color image to create a black and white image with highlight color.

Figure 95. Rotate Image Dialog Box



To combine images:

1. On the Options menu, click Combine Images. The Combine Images dialog box appears.

2. Type the name of the new combined image.

3. Select the black image that you want to combine.

4. Select the highlight color image you want to combine.

5. Select the Delete both source images after the combination check box to delete both the original .img files after the Image Utility combines the two images.

6. Click OK to combine the selected images.

Figure 96. Combine Images Dialog Box



Viewing PropertiesWhen you want to view information about a resource within the content repository, you can display the Properties dialog box. The Properties dialog box enables you to view information about the selected image, precomposed document, or VMF. The information that displays in the Properties dialog box varies depending on the type of resource selected.

To access the Properties dialog box, select the resource and select Properties in the View menu or click the Properties toolbar button.

For more information about viewing resource properties, see the xPression Image Utility Help.

Searching for a ResourceYou can search the content repository for a specific resource. To search for an resource:

1. Click Search and then Find or click the Search button on the toolbar to open the Find dialog box

2. Select the resource you want to find from the drop-down list.

3. Choose whether to search through all the resources or only a specific type of resource.

Figure 97. Find Dialog Box



4. Choose whether to look up or down through the content repository.

5. Click Find Next to search the content repository for the resource. The Image Utility highlights the resource in the main window.

Variable Merge FramesA VMF is a flexible method for merging data onto precomposed forms or documents. It is a collection of information that allocates space and defines placement coordinates and formatting attributes for variable data that is to be merged on a precomposed form or document. You can use the Merge Document Viewer to create, open, delete, or save VMFs. You can also rename a VMF or view VMF properties.

Copying VMF References

Using the Image Utility, you can copy VMF references from one precomposed document located in the content repository into another. This prevents you from having to recreate references that are the same in two precomposed documents. For example, you may have two letters in which the variable data is same (such as customer name and address), is located in the same area, and formatted the same. You can easily copy the references from the first letter into the second letter using the Copy References option.



To copy VMF references:

1. On the Options menu, click Copy References. The Copy references dialog box, shown below, appears.

2. Select the precomposed document that contains the VMFs to be copied in the From document column.

3. Select the precomposed document destination for the VMF references in the To document column.

4. Click OK.

Using the Merge Document Viewer

The Image Utility uses the Merge Document Viewer to display precomposed documents in the content repository. To view a document, double-click the document in the Tree view. You can navigate through the document using the arrows on the Merge Document Viewer toolbar. You can also use the Merge Document Viewer to examine other aspects of your document.

Figure 98. Copy References Dialog Box



Creating a New VMF

To create a new VMF in a precomposed document:

1. In the Image Utility main window, double-click the precomposed document you want to view. The Merge Document Viewer opens and displays the precomposed document.

2. On the Merge Document Viewer View menu, click Merge frames.

Figure 99. Merge Document Viewer



3. Right-click anywhere in the precomposed document and click New variable merge frame. The cursor becomes a cross.

4. Draw a rectangle over the area where you want to place the VMF.

5. Click inside the VMF rectangle to select it.

6. Right-click inside the VMF rectangle and click Variable Merge Frame Properties. The Merge Frame Properties dialog box, shown below, appears.

Figure 100. Selected Variable Merge Frame

Figure 101. Merge Frame Properties Dialog Box



7. Specify the properties for the VMF in the dialog box. The Merge Document Viewer automates much of the VMF definition for you, depending on the placement and size of your VMF on the current precomposed document. You can modify this information as needed in the Merge Frame Properties dialog box.

8. Click Save As to save the VMF properties. The Save Variable Merge Frame dialog box appears.

9. Browse to the location where you want to save the VMF.

10. Type the name of the VMF in the Variable Merge Frame Name text box.

11. Click Save to return to the Merge Document Viewer.

12. Close the Merge Document Viewer and save your changes when prompted.

Figure 102. Save Variable Merge Frame Dialog Box



Opening a VMF

To open an existing VMF in the precomposed document you are viewing:

1. On the View menu, click Merge frames.

2. Right-click anywhere in the precomposed document and click Open variable merge frame. The Select Variable Merge Frame Definition dialog box appears.

Figure 103. Select Variable Merge Frame Definition Dialog Box



3. Select a VMF and click Details. The Variable Merge Frame Definition dialog box appears.

4. Click OK to return to the Select Variable Merge Frame Definition dialog box and select a different VMF.

Or, click Open to open the currently selected VMF. If you click Open, skip Step 5.

5. Select the VMF you want to open from the Select Variable Merge Frame Definition dialog box and click Open.

Point the mouse where you want to place the frame and click. The VMF is placed on the precomposed document.

Figure 104. Variable Merge Frame Definition Dialog Box


239

Chapter 6PCL Font Converter

Before publishing to CompuSet and creating PCL output for xPression, you may want to convert TrueType fonts you want to use in your job to PCL fonts.

The PCL Font Converter converts TrueType fonts to PCL fonts by creating the soft font and TFM files that you can load into the font database.


• Launching the PCL Font Converter

• Converting A Font

• Finding the Best Symbol Set

• Tips for Converting Fonts

• Symbol Sets

• Font Converter Error Messages


Chapter 6 - PCL Font Converter240

Launching the PCL Font ConverterThe Font Converter is one of the tools provided with the xPression CompuSet Tools application. To launch the Font Converter:


2. Double-click PCL Font Converter to open the PCL Font Converter, shown in Figure 105 on page 241.

Note: If you do not have the CompuSet Tools installed, you can install them from the installation CD. Click Custom for the install type and select CompuSet Tools.



Converting A FontThe PCL Font converter makes it easy to convert a TrueType font into a PCL font. We recommend that you use the converted font for development of your application only, and not for production. A converted PCL font does not have the same quality as an original PCL font.

To convert a TrueType font into a PCL font:

1. Click Choose fonts to convert and browse to locate and select the fonts you want to convert. You can multi-select fonts (hold the SHIFT key while selecting) to convert more than one font at a time.

Tip: If you have trouble selecting a font that is located in the \\Windows\Fonts directory, copy the font to another directory and then select it for conversion.

Figure 105. Font Converter



2. Select a symbol set from the drop-down list. The list contains all the available PCL symbol sets within the Font Converter. Each PCL symbol set has an associated code. For a list of symbol sets and codes, see Symbol Sets.

Tip: To select the best symbol set for a specific font, click Analyze Fonts/Symbol Sets. For more information, see Finding the Best Symbol Set.

3. Click Choose destination directory and browse to the directory where you want to store the converted fonts.

4. Click Start Conversion (to stop the conversion, click Stop Conversion). If the name of the font that you are converting is more than 16 characters long, the Font Converter displays the following message.

Click OK, and the Rename Font dialog box appears.

Figure 106. Font Converter Font Name Message

Figure 107. Font Converter Rename Font Dialog Box



Type a new unique name for the font that contains 16 characters or less and click OK. Since the Font Converter truncates font names to 16 characters during the conversion, if you don’t rename the font, you may end up with duplicate font names.

5. Click OK on the “Conversion complete” message.

6. (Optional) Click View Log. The File viewer dialog box appears. It displays the contents of the conversion log, which shows the one-to-one mapping results between the characters in the TrueType font and the codes of the PCL symbol set.

Finding the Best Symbol SetBefore you convert a True Type font, you should analyze the font to ensure that you select a PCL symbol set that will get you the most successful character matches. For a list of all the symbol sets, see Symbol Sets.

Figure 108. Log File Viewer



To analyze a True Type font:

1. Click Analyze Fonts/Symbol Sets. The Font Analysis dialog box appears.

2. Click Choose Font and browse to locate the TrueType font (.ttf) that you want to analyze. Select the font and click Open.

– The Character codes in font list displays the number of character codes in the selected TrueType font and lists the actual codes. This list is for display purposes only.

– The Symbol Set column shows a list of available PCL symbol sets.

Figure 109. Font Analysis Dialog Box



– The Characters mapped column shows the number of successful matches between the TrueType characters and the PCL characters for each symbol set.

– The Characters not mapped column lists the codes for the TrueType characters that do not successfully map for each symbol set.

3. Select a symbol set from the list and click Print Test Page to print a character map test page that shows the mapping scheme between a TrueType font and a PCL symbol set. You can select the PCL printer you want to use to print the test page.

4. Click Close when you are done analyzing fonts.

Tips for Converting FontsThe following suggestions are guidelines for successfully converting fonts to PCL 5 format and loading these fonts into the font database.

• When you are loading a non-symbol font, generally, you should be able to use the Windows 3.1 Latin symbol set (19U) without problems.

• The file names that the Font Converter assigns to a specific font are different for soft font and TFM files.

• Special fonts such as Wingdings, Zapf Dingbats, and Symbols require special symbol sets. Refer to the Symbol Set Reference Table on page 246 for information about valid symbol sets to use.

Symbol SetsA symbol set is a unique group of characters designed to meet the requirements of specific languages and occupations. Symbol sets can consist of characters that are alphabetic, numeric, punctuation, or special symbols. When you are loading fonts, it is important to choose a symbol set that corresponds with the font you are loading.



The Symbol Set Reference table can help you choose the appropriate symbol set. This table gives you the symbol set name and description, along with the corresponding Font Converter and PCL output formatter codes for each symbol set.

The Font Converter code appears in the Select symbol set list. The PCL output formatter code is used in the Widths file.

Symbol Set Name/Usage Font Converter Code

PCL Output Formatter Code

ATM Type 1 AT 32T

ISO 14:JIS ASCII 0K 0K

ISO 8859/1 Latin 1 (EC94) E1 0N

ISO 8859/2 Latin 2 E2 2N

ISO 8859/9 Latin 5 E5 5N

Macintosh MC 12J

Microsoft Publishing PB 6J

PC-8, Code Page 437 (IBM-8) PC 10U

PC-8 Denmark/Norway, Code Page 437N PD 11U

PC-852 Latin 2 PE 17U

Pi Font PI 15U

PC-8 TK, Code Page 437T PT 9T

Roman-8 R8 8U

PS Text TS 10J

ISO 6: ANSI ASCII US 0U

Ventura US VU 14J



Windows 3.1 Latin 1 W1 19U

Windows 3.1 Latin 2 WE 9E

Windows WN 9U

Windows 3.0 Latin 1 WO 9U

Windows 3.1 Latin 5 WT 5T

ISO French 0F 0F

ISO 69: French FR 1F

HP German 0G 0G

ISO 21: German GR 1G

HP Spanish 1S 1S

ISO 85: Spanish 6S 6S

ISO 17: Spanish SP 2S

ISO 57: Chinese 2K 2K

ISO 2: International Reference Version 2U 2U

ISO 10: Swedish 3S 3S

ISO 11: Swedish SW 0S

ISO 61: Norwegian 2 1D 1D

ISO Danish/Norwegian DN 0D

ISO 16: Portuguese 4S 4S





ISO 84: Portuguese 5S 5S

ISO 15L Italian IT 0I

PC-850 Multilingual PM 12U

ISO 4: United Kingdom UK 1E

Ventura International VI 13J

ITC Zapf Dingbats/100 D1 11L



PS ITC Zapf Dingbats DS 10L

Wingdings WD/L$ 579L

Desktop DT

Windows Symbols AS

Legal LG 1U

Math-8 M8 8M

PS Math MS 5M

Symbols SY 19M

Ventura Math VM 6M





Font Converter Error MessagesThis section contains a list of the error messages that you may encounter when using the Font Converter. These messages are grouped by category in numeric order.

1–49: Tagged Font Metric Error MessagesAll of the error messages in this section are related to insufficient memory. To check the amount of memory, type the MEM command at the MS-DOS prompt. At least 512 KB bytes of free memory is recommended. To correct these errors, increase the amount of available memory.

Error Number

Meaning

1 Insufficient memory for CG-MSL conversion list.

2 Insufficient memory for bit-mapped font header.

3 Insufficient memory for bitmapped character header.

4 Insufficient memory for character metrics.

5 Insufficient memory for bitmapped data segment.

6 Insufficient memory for temporary data segment.

7 Insufficient memory for attribute file header.

8 Insufficient memory for font alias header.

9 Insufficient memory for font header.

10 Insufficient memory for attribute header.

11 Insufficient memory for typeface header.

12 Insufficient memory for identifier segment.

13 Insufficient memory for descriptor set segment.



14 Insufficient memory for complement header.

15 Insufficient memory for character segment.

16 Insufficient memory for textkern header.

17 Insufficient memory for sector segment for textkern.

18 Insufficient memory for trackkern header.

19 Insufficient memory for compound character header.

20 Insufficient memory for compound character ID header.

21 Insufficient memory for compound character metrics header.

22 Insufficient memory for file header.

23 Insufficient memory for display header.

24 Insufficient memory for hqdata header.

25 Insufficient memory for character metrics from file.

26 Insufficient memory for segment directory.

27 Insufficient memory for library file segment.

28 Insufficient memory for face header.

29 Insufficient memory for face character header.

30 Insufficient memory for global directory segment.

31 Insufficient memory for library copyright header.

32 Insufficient memory for symbol set data segment.

Error Number

Meaning



50–69: File Management Error MessagesAll of the messages in this section are related to file management problems. When file management problems occur, some general suggestions are:

• Check to see if there are File Allocation Table (FAT) errors on your hard drive.

• Reinstall the Font Converter program.

• Reload the font to ensure that the original font file is not corrupt.

33 Insufficient memory for temporary tag data variable.

34 Insufficient memory for offset data in WT-TFM.C program.

35 Insufficient memory for pair kern segment.

Error Number

Meaning Action

50 Unable to open library file. The Intellifont library file cannot be opened, implying that your SOURCE path is wrong.

Reselect the font or reinstall the font on your system.

52 Unable to open .SYM file. The *.sym symbol set mapping file could not be found. The SYMBOLSET path is wrong or the *.sym file is corrupted.

Change the symbol set path in the Options field. If this fails, reinstall the Font Converter from diskette.

53 Unable to open FAIS attribute file. A necessary file is missing from the installed FAIS Intellifonts.

Install the missing font from the original FAIS Intellifont diskette.

54 Unable to open FAIS descriptor file. A necessary file is missing from the installed FAIS Intellifonts.

Install the missing font from the original FAIS Intellifont diskette.

Error Number

Meaning



55 Unable to open PLUGIN.TYQ file. The necessary Plugin.tyq cannot be found. The Plugin path is wrong or the file is corrupt.

Change the Plugin path in the Directory field. If this does not work, you may need to reinstall the Font Converter.

56 Unable to write to temporary file. You do not have enough disk space.

You must have at least 1 MB of free disk space.

57 Unable to open TD.KRN file. The necessary TD.krn cannot be found. Either the Plug-in path is wrong or the file has been corrupted.

Change the Plug-in path in the Directory field. If this does not work, you may need to reinstall the Font Converter.

58 Incorrect path name for finding .SYM files. The *.sym symbol set mapping file could not be found. The symbol set path is wrong or the *.sym file is corrupt.

Change the symbol set path in the Options field. If this does not work, you may need to reinstall the Font Converter.

59 Unable to open PARAMET.ERS for parameter list. The necessary Paramet.ers can not be found. The Plug-in path is wrong or the file is corrupt.


60 Unable to open RESULTS.TAG for conversion. The necessary Results.tag file cannot be found. The Plug-in path is wrong or the file is corrupt.


61 Unable to write to output file. You do not have enough free disk space.


62 No disk space available. You do not have enough free disk space.


Error Number

Meaning Action



70–99: Invalid Font FilesAll of the messages in this section are related to defective font files. When defective files are identified, some general suggestions are:• Install the font again or obtain a new copy.

• Check to see if there are File Allocation Table (FAT) errors on your hard drive.

Error Number

Meaning

70 Invalid (or missing) font alias header.

71 Invalid (or missing) attribute file header.

72 Invalid (or missing) font header.

73 Invalid (or missing) attribute header.

74 Invalid (or missing) typeface header.

75 Invalid (or missing) identifier segment

76 Invalid (or missing) descriptor set segment.

77 Invalid (or missing) complement header.

78 Invalid (or missing) character segment.

79 Invalid (or missing) textkern header.

80 Invalid (or missing) sector segment for textkern.

81 Invalid (or missing) buffer segment.

82 Invalid (or missing) trackkern header.

83 Invalid (or missing) compound character header.

84 Invalid (or missing) compound character ID header.



88 Invalid (or missing) compound character metrics header.

89 Invalid (or missing) file header.

90 Invalid (or missing) display header.

91 Invalid (or missing) hqdata header.

92 Invalid (or missing) character metrics from file.

93 Invalid (or missing) word for character metrics.

94 Invalid (or missing) metric offset for character metrics.

95 Invalid (or missing) nkey for hqdata header.

96 Invalid (or missing) number of compound characters.

97 Invalid (or missing) bitmapped character header.

98 Invalid (or missing) byte.

99 Invalid (or missing) bitmapped font header.

Error Number

Meaning



100–299Two action codes may be associated with an error: A or B. Error A means that a file operations error has occurred. Check the integrity of the File Allocation Table. Error B means that the font file is defective. Reload the font file, or check the integrity of the File Allocation Table on your hard drive.

Error Number

Meaning

100 Error A: Error opening output font file.Error B: Invalid (or missing) segment directory.

101 Error A: Write to file or printer failed. The printer may be offline or invalid. Error B: Invalid (or missing) library file segment.

102 Error A: Error opening IF library file.Error B: Invalid, or missing, face header.

103 Error A: Invalid library type selected. Reselect library.Error B: Invalid (or missing) face character header

104 Error B: Error reading segment keyword.Error B: Invalid (or missing) global directory segment.

105 Error B: Improper keyname encountered.Error B: Invalid (or missing) ccheader for library compound characters.

106 Error A: File directory segment seek error.Error B: Invalid (or missing) characters for library compound characters.

107 Error B: File directory segment read error.Invalid (or missing) number of characters for Plugin.tyq file.



108 Error A: Face header segment seek error.Error B: Invalid (or missing) library copyright header.

109 Error A: Face header segment read error.Error B: No line present.

110 Error B: Character directory segment allocation error.Error B: Segment size is larger than expected size.

111 Error A: Character directory segment read error.Error B: File segment directory not found.

112 Error A: TF global segment seek error.Error A: Library file is not a disk file.

113 Error A: TF global segment read error.Error B: More than one typeface in the Font alias table.

114 Error B: Error reading segment key.

115 Error B: Error reading segment offset.

116 Error B: Error reading segment length.

117 Error B: Segment not present error.

118 Error B: Global IF segment allocate error.

119 Error B: Global IF data segment seek error.

120 Error B: Global IF data segment read error.

121 Error B: Raster parameter segment missing.

122 Error B: Raster parameter segment seek error.

123 Error B: Raster parameter segment allocation error.

Error Number

Meaning



124 Error B: Raster parameter segment read error

125 Error B: Font attribute segment missing.

126 Font attribute segment seek error.

127 Font attribute segment allocation error.

128 Font attribute segment read error.

129 Display header segment missing.

130 Display header segment seek error.

130 Invalid file type.

131 Display header segment allocation error.

131 Unable to open CG-MSL.exh file.

132 Display header segment read error.

132 Invalid byte order in file.

133 Font alias table segment missing.

133 No tags found in the file.

134 Font alias table segment seek error.

134 Asterisk expected, but another character was found.

135 Font alias table segment allocate.

136 Missing data type tag.

136 Font alias table segment read error.

Error Number

Meaning



137 Copyright segment allocation error.

138 Copyright segment seek error.

139 Copyright segment read error.

140 Maximum character size exceeded.

141 Character data segment seek error.

142 Character data segment read error.

143 Error allocating character buffer.

144 Maximum symbol set character count exceeded.

145 Compound character segment seek error.

146 Compound character segment read error.

147 Character definition segment allocation error.

148 Character directory segment seek error.

149 PCLeo must be symbol set bound.

150 File name exceeds MAXPATH length.

151 Invalid test argument passed.

200 Error A: Cannot open TrueType file.

201 Source symbol set not found. It could be an inappropriate choice of symbol set for the font or not available for that font.Error B: Cannot read TrueType table directory

Error Number

Meaning



202 Invalid command line argument. The Font Converter was run with an invalid command line argument.Error B: Cannot read TrueType head table.

203 Error A: Error opening source font file.Error B: Cannot read TrueType post table.

204 Error B: Font HDR access error.Cannot read TrueType head table.

205 OS/2 table not found.Cannot read TrueType MAXP table.

206 Font directory access error.Cannot read TrueType HMTX table.

207 Output buffer write error.Cannot read TrueType Name table.

208 Improper command response.Cannot read TrueType PCLT table.

209 Error creating output file.Cannot read TrueType OS/2 table.

210 Error building Offset table.Cannot read TrueType CMAP directory.

211 Source copyright not found.Cannot read TrueType CMAP sub-table.

212 Error allocating PANOSE table.Cannot build character metrics array.

Error Number

Meaning



300–399

213 Error accessing glyph table.Cannot open TrueType Universal file.

214 Compound-compound error.

215 PCLT/OS2 font tables missing.

216 Error getting CMAP suitable.

217 Symbol set not compatible with font.

218 Error accessing Head table.

219 Error accessing HMTX table.

Error Number

Meaning

300 Error scanning type-1 file.

301 Error scanning for type-1 matrix.

302 Error reading type-1 binary header.

303 Error scanning for type-1 private.

304 Error scanning for type-1 LenIV.

305 Error scanning for type-1 StdVW.

306 Error scanning for type-1 StdHW.

307 Error scanning for type-1 blues.

Error Number

Meaning



308 Error scanning for type-1 other blues.

309 Error scanning for type-1 blue scale.

310 Error scanning for type-1 blue shift.

311 Error scanning for type-1 encoding.

312 Error scanning for type-1 subroutines.

313 Type-1 Subroutine number too high.

314 Error scanning for type-1 character strings.

315 Type-1 character string number too high.

316 Error allocating type-1 subroutine array.

317 Error allocating type-1 subroutine data memory.

318 Error allocating type-1 character string array.

319 Error allocating type-1 character name memory.

320 Error allocating type-1 character data memory.

321 Error allocating type-1 encoding array memory.

322 Error allocating type-1 encoding name memo.

323 Name not found in character strings

324 Error opening type-1 file.

325 Error reading type-1 font.

326 Piece of compound character missing.

Error Number

Meaning



327 Hint structure overflow.

328 Working buffer overflow.

329 Expand buffer overflow.

330 Scale factor overflow.

331 Error scanning for bounding box.

332 Error scanning for type-1 bluefuzz.

333 Error scanning for type-1 blues

334 Error scanning for type-1 blues.

335 Error scanning for stemsnap.

336 Error scanning for stemsnap.

337 Error allocating PSCHAR memory.

338 Error opening file.

339 Destination file exists.

340 Error reading file.

341 Error seeking to desired position.

342 Error setting up tables.

343 Out of range or invalid subroutine number.

344 Cannot do unbound PS pcleos.

345 General memory allocation error.

Error Number

Meaning



400–499: Warnings

346 Error parsing command line argument.

347 Error writing to file.

348 Error opening font file.

349 Error opening soft font file.

350 Error opening psname configuration file.

351 Error opening INF file.

352 Error opening AFM file.

Error Number

Meaning Action

400 Source symbol set not found. Perhaps the set is not available for this font—try another set.

450 Converted soft font will not contain all the characters requested for the symbol set. If you print the incomplete soft font, some characters will not print. This is because the font file does not contain all the characters requested for that symbol set.

Not all fonts contain all the characters for every symbol set. A few characters may be missing; or, you may have made a poor choice of symbol set, and many characters are missing. Running the PCL output formatter using the job file Grid.txt can produce a grid indicating which characters are available for this font.

Error Number

Meaning



500–599Two action codes may be associated with an error: A or B. Error A means that a file operations error has occurred. Check the integrity of the File Allocation Table. Error B means that the font file is defective. Reload the font file, or check the integrity of the File Allocation Table on your hard drive.

Error Number

Meaning Action

501 Memory error. A memory error probably means you need more free memory. Review the suggestions at the beginning of this Appendix.

502 Command line argument error. The Font Converter ran with invalid command line arguments; correct them.

503 Error accessing specified type file.

504 Error A: Error accessing specified font file.

505 Error A: Error determining file statistics.

506 Error A: Unable to rename file. Verify that a file by that name does not exist already.

507 Error A: Unable to create file. Verify that the hard drive is not full.

508 Error A: Error opening backup file. Verify that the hard drive is not full.

509 Error A: Error reading backup file.

510 Error A: Error writing to Glue.txt file. Verify that the Glue.txt file has not been corrupted.

511 Error A: Unable to open Glue.txt file.

512 Error B: Unable to find SYMSET class.

513 Error B: Used to delimit GW error codes.



600–699These errors are related to insufficient memory. It is recommended that you have at least 512 K of free memory.

Error Number

Meaning Action

601 Insufficient memory for CG-MSL conversion list.

602 Insufficient memory for bitmapped font header.

603 Insufficient memory for bitmapped character header.

604 Insufficient memory for character metrics.

605 Insufficient memory for bitmapped data segment.

606 Insufficient memory for temporary data segment.

607 Insufficient memory for attribute file header.

608 Insufficient memory for font alias header.

609 Insufficient memory for font header.

610 Insufficient memory for attribute header.

611 Insufficient memory for typeface header.

612 Insufficient memory for identifier segment.



613 Insufficient memory for descriptor set segment.

614 Insufficient memory for complement header.

615 Insufficient memory for character segment.

616 Insufficient memory for textkern header.

617 Insufficient memory for sector segment for textkern.

618 Insufficient memory for trackkern header.

619 Insufficient memory for compound character header.

620 Insufficient memory for compound character ID header.

621 Insufficient memory for compound character metric header.

622 Insufficient memory for file header.

623 Insufficient memory for display header.

624 Insufficient memory for hqdata header.

625 Insufficient memory for character metrics from file.

626 Insufficient memory for segment directory.

Error Number

Meaning Action



627 Insufficient memory for library file segment.

628 Insufficient memory for face header.

629 Insufficient memory for face character header.

630 Insufficient memory for global directory segment.

631 Insufficient memory for library copyright header.

632 Insufficient memory for symbol set data segment.

633 Insufficient memory for temporary tag data variable.

634 Insufficient memory for offset data in wt-tfm.c program.

635 Insufficient memory for pair kern segment.

650 Unable to open library file. The Intellifont library file cannot be open. Your source path may be incorrect.

Reselect the font or reinstall the font on your system.

652 Unable to open .SYM file. The *.sym symbol set mapping file could not be found. The symbol set path is wrong or the *.sym is corrupted.

Change the symbol set path in the options field. If this does not work, you may need to reinstall the Font Converter from diskette.

Error Number

Meaning Action



653 Unable to open FAIS attribute file. A necessary file is missing when install FAIS Intellifonts.

Install the font from the original FAIS Intellifont diskette.

654 Unable to open FAIS descriptor file. A necessary file is missing when install FAIS Intellifonts.

Install the font from the original FAIS Intellifont diskette.

655 Unable to open PLUGIN.TYQ file. The necessary Plugin.tyq file cannot be found. The Plugin path is wrong or the file is corrupt.

Change the Plugin path in the Directory field. If all else fails, you may need to reinstall the Font Converter.

656 Unable to write to temporary file. You do not have enough disk space.


657 Unable to open TD.KRN file. The necessary TD.krn file cannot be found. The Plugin path is wrong or the file is corrupt.


658 Incorrect path name for finding .SYM files. The *.sym symbol set mapping file could not be found. The symbol set path is wrong or the *.sym file is corrupt.

Change the symbol set path in the Options field. If all else fails, you may need to reinstall the Font Converter.

659 Unable to open PARAMET.ERS for parameter list. The necessary Parameters cannot be found. The Plugin path is wrong or the file is corrupt.


Error Number

Meaning Action



660 Unable to open the RESULTS.TAG file for conversion. The necessary Results.tag file cannot be found. The Plugin path is wrong or the file is corrupt.


661 Unable to write to output file

662 No disk space available error. You do not have enough free disk space.


663 Bad FSEEK command. There is a general Font Converter error.

Reinstall the Font Converter from the original diskette.

664 Bad FSCANF command. There is a general Font Converter error.

Reinstall the Font Converter from the original diskette.

670 Invalid (or missing) font alias header.

671 Invalid (or missing) attribute file header.

672 Invalid (or missing) font header.

673 Invalid (or missing) attribute header.

674 Invalid (or missing) typeface header.

675 Invalid (or missing) identifier segment.

676 Invalid (or missing) descriptor set segment.

677 Invalid (or missing) complement header.

678 Invalid (or missing) character segment.

679 Invalid (or missing) textkern header.

Error Number

Meaning Action



680 Invalid (or missing) sector segment for textkern.

681 Invalid (or missing) buffer segment.

682 Invalid (or missing) trackkern header.

683 Invalid (or missing) compound character header.

684 Invalid (or missing) compound character ID header.

688 Invalid (or missing) compound character metrics header.

689 Invalid (or missing) file header.

690 Invalid (or missing) display header.

691 Invalid (or missing) hqdata header.

692 Invalid (or missing) character metrics from file.

693 Invalid (or missing) word for character metrics.

694 Invalid (or missing) metric offset for character metrics.

695 Invalid (or missing) key for hqdata header.

696 Invalid (or missing) number of compound characters.

Error Number

Meaning Action



700–799

697 Invalid (or missing) bitmapped character header.

698 Invalid (or missing) byte.

699 Invalid (or missing) bitmapped font header.

Error Number

Meaning

700 Invalid (or missing) segment directory.

701 Invalid (or missing) library file segment.

702 Invalid (or missing) face header.

703 Invalid (or missing) face character header.

704 Invalid (or missing) global directory segment.

705 Invalid (or missing) ccheader for library compound characters.

706 Invalid (or missing) characters for library compound characters.

707 Invalid (or missing) number of characters for Plugin.tyq file.

708 Invalid (or missing) library copyright header.

709 No line present.

710 Segment size is larger than expected size.

711 File segment directory not found.

Error Number

Meaning Action



800–899

712 Library file is not a disk file.

713 More than one typeface in the font alias table.

730 Invalid file type.

731 Unable to open CG-MSL.exh file.

732 Invalid byte order in file 733. No tags found in the file.

734 Asterisk expected, but another character was found.

735 Missing font tag.

736 Improper input to test routine.

737 Error during search for symbol set file.

738 Error during search for TD.krn file.

739 Missing Panose.if file.

Error Number

Meaning

800 Cannot open TrueType file.

801 Cannot read TrueType table directory.

802 Cannot read TrueType HEAD table.

803 Cannot read TrueType POST table.

804 Cannot read TrueType HHEA table.

Error Number

Meaning



900–999

805 Cannot read TrueType MAXP table.

806 Cannot read TrueType HMTX table.

807 Cannot read TrueType NAME table.

808 Cannot read TrueType PCLT table.

809 Cannot read TrueType OS/2 table.

810 Cannot read TrueType CMAP directory.

811 Cannot read TrueType CMAP subtable.

812 Cannot build character metrics array.

813 Cannot open TrueType Universal file.

Error Number

Meaning

900 Unable to open PFM file.

901 Unable to allocate memory for PFM struct.

902 Unable to allocate memory for PFM header.

903 Unable to allocate memory for PFM extension.

904 Unable to allocate memory for extended text metric.

905 Unable to allocate memory for pair kern table.

906 Unable to allocate memory for track kern table.

Error Number

Meaning



907 Unable to allocate memory for extent table.

908 Error reading PFM header.

909 Error reading PFM extension.

910 Error reading extended text metric.

911 Error reading pair kern table.

912 Error reading track kern table.

913 Error reading extent table.

914 Error seeking to desired position.

915 Error reading PS font name from PFM file.

916 Error loading selected symbol set.

917 Unable to open character metrics data file.

Error Number

Meaning


275

Appendix AFDB Utility Commands

This appendix contains information on the general format of the Font Database Utility commands, as well as the syntax and parameters that make up each command.


Appendix A - FDB Utility Commands276

FDB Utility CommandsFDB utility commands have this format:

command p1,p2,p3,...pn

where command is the four-character command name, and p1 – pn are the parameter values.

The command format requirements are:

• The command name must be the first four characters in the line.

• There must be at least one blank between the name and the parameter list.

• All parameter values are separated by commas.

• If the last parameter is followed by a comma, the remainder of the line can be used for comments.

• Comment lines begin with an asterisk (*) followed by three blanks. Comment lines are for documentation only and are ignored for execution.

• FDB commands can be specified in any order; however, if you use the INIT or UPDT commands, they must appear first.

File and Path NamesWhen you are working on a host with a supported UNIX or Windows operating system, you can specify FDB Job Command file paths with environment variables, or you can specify these paths explicitly. CompuSet supports path names up to 320 bytes if you choose to define them explicitly.



Sample FDB JobThe following sample job for all supported Windows platforms shows how to load fonts into a font database for a Xerox centralized printer.

@echo offremrem Batch file to run FDB to load fonts into a Xerox centralized printerrem font database. Syntax is:remrem metfload fontnameremrem where %CSET%\fonts\fontname.fnt is the font file (FILE 14) to load.remrem *** WARNING: YOU SHOULD HAVE A BACKUP COPY OF THE FONT DATABASE ***rem *** BEFORE UPDATING THE CURRENT FDB. ***rem *** FAILURE TO DO SO COULD PERMANENTLY DESTROY YOUR FILE. ***remif "%1" == "" goto errorremecho Running FDB - Run log saved in %CSET%\syslog\metfload.log . . .echo %CSET%\system\%OSYS%\fdbx >%CSET%\syslog\metfload.logecho * >%TEMP%\fdbl.tmpecho * FILE DEFINITIONS FOR FDB >>%TEMP%\fdbl.tmpecho * >>%TEMP%\fdbl.tmpecho FILE 10, %CSET%\system\%WRDTYP%\x9700.fdb,current FDB file>>%TEMP%\fdbl.tmpecho FILE 13, %TEMP%\fdb.tmp ,FDB scratch file >>%TEMP%\fdbl.tmp

echo FILE 14, %CSET%\fonts\met\%1.fnt,hostcopy font input (LOAD p4=1)>>%TEMP%\fdbl.tmp

echo FILE 25, %CSET%\system\%WRDTYP%\xicsmsg.mdb ,CompuSet mdba>>%TEMP%\fdbl.tmp

echo // END OF FILE DEFINITIONS >>%TEMP%\fdbl.tmp

echo * >>%TEMP%\fdbl.tmp

echo * COMMANDS FOR FDB >>%TEMP%\fdbl.tmp



echo * >>%TEMP%\fdbl.tmp

echo UPDT -666,,,IN-PLACE UPDATE >>%TEMP%\fdbl.tmp

echo MACH 2, MACHINE = XEROX CENTRALIZED LPS >>%TEMP%\fdbl.tmp

echo LOAD 1,,,1,LOAD FONT METRICS (FROM DISK) INTO FDB >>%TEMP%\fdbl.tmp

echo LIST 0,, LIST ALL FONTS IN FDB >>%TEMP%\fdbl.tmp

echo // END OF COMMANDS >>%TEMP%\fdbl.tmp

rem -- run WIN32 version if OSYS is NOT set...

if "%OSYS%"=="" goto WIN32

if "%OSYS%"=="WIN32" goto WIN32

:WIN32

%CSET%\system\%OSYS%\fdbx < %TEMP%\fdbl.tmp >> %CSET%\syslog\metfload.log

goto cleanup

:cleanup

del %TEMP%\fdbl.tmp > nul

goto end

:error

echo Please re-run batch file with proper parameter(s) specified.

goto end

:end

echo Done.



AEXT - Specify Extension (AFP, PCL, PostScript)The AEXT command enables you to specify a standard extension to be added to the file names for each of the three types of AFP font files: coded font, code page, and character sets. For PCL, CompuSet allows only the tagged font metric extension. For PostScript, CompuSet allows only PostScript font file extensions. CompuSet adds the extension you specify when the FDB utility searches for the font files on disk.

Syntax AEXT p1,p2,p3

Parameters

p1

Extension to be added to the names of the coded font files.

p2

Extension to be added to the names of the code page files.

p3

Extension to be added to the names of the character set files.

Note: The following notes apply to the AEXT command:

• The extension should include the leading period, if desired, and should not contain embedded blanks or commas. It is not necessary to delimit the extension with quotes.

• AFP font files are specified in the Configuration file by eight-character names. These names refer to files which are often located in multiple disk directories.

• Each extension can be up to 12 characters long, although the host operating system may impose other limitations.



• Use the AEXT command on these host systems:

– All supported Windows platforms

– All supported UNIX platforms

• On UNIX and Windows platforms, the AEXT command specifies an extension to be added to the end of each file name. The default is to specify no extensions, and no extensions are possible on IBM z/OS systems.

• PCL and PostScript use only the first parameter as the file extension.



APTH - Directory Name (AFP, PCL, and PostScript)The APTH command specifies a directory to add to the search path to find AFP (coded font, code page, and character set), PCL (tagged font metric and downloadable fonts), and PostScript font files.

Syntax APTH p1

Parameters

p1

Name of the directory on the host machine to add to the path list (up to 68 characters).

Default: Required

Note: The following notes apply to the APTH command:

• AFP font files are specified in the Configuration file by eight-character names. These names refer to files that are often located in multiple disk directories.

• When searching for a font file, the FDB utility first looks in the current directory, then in the directories specified by the APTH statements in the order in which they have been entered.

• The p1 parameter should be specified in the form native to the host on which the program is running. The trailing / or \ character (UNIX or Windows) is optional. Embedded blanks or commas are not allowed. It is not necessary to delimit the directory name with quotes.

• Up to 25 directories can be added to the path list.

• Use the APTH command only on UNIX and Windows hosts. On IBM z/OS systems, the FDB utility searches for font files in up to three partitioned data sets, which are specified in the job control language (JCL) that runs the job.



ExampleOn a UNIX machine, the following commands will cause the FDB utility to look first in the current directory, and then in the three directories subsequently listed, in order, for the font files.

APTH /AFP/corefonts/codepage/primaryAPTH /AFP/corefonts/latin1/charset/helveticaAPTH /AFP/corefonts/latin1/codefont/helvetica

Equivalent directories on a Windows host would be:

APTH d:\corefonts\codepage\primaryAPTH d:\AFP\corefonts\latin1\charset\helveticAPTH d:\AFP\corefonts\latin1\codefont\helvetic



CCOD - Override Condition CodeThe CCOD command overrides preset condition codes and resets the condition code that is produced when an error is encountered during execution on a message-by-message basis.

Syntax CCOD p1,p2,...pn

Parameters

p1

Maximum severity level.

-3 — No fatal errors.

-2 — No errors or fatal errors.

-1 — No warnings.

0 — Use program default seveity levels.

>0 — Severity level for the message numbers specified by the parameters p2, p3, and so on.

Default: 0

p2 - pn

Message numbers to be assigned the severity level specified by parameter p1 > 0 (numbers, separated by commas, must fit into a record of 72 characters or less).

Note: The following notes apply to the CCOD command:

• Message numbers can be any valid CompuSet message from 1001 to 99999. Non-existent message numbers are not flagged as errors, but are simply ignored.

• If p1 is less than or equal to 0, no other parameters are required.

• If p1 is less than 0, messages can be logged with different severity levels, but none higher than the maximum specified by p1.



• If p1 < 1, the p1 value applies to all messages; parameters p2 and so on are ignored.

• If p1 > 0, multiple CCOD commands can be entered to list all the message numbers whose severity is to be changed; however, only the first 1000 message numbers specified are actually used during execution.

Condition Code ValuesFor the following operating systems, CompuSet generates non-zero condition codes when a serious error, such as an attempt to merge a non-existent document or image from a Merge library, is detected. The operating systems are:

• IBM z/OS



These condition codes can be monitored by the Job Command files executing each CompuSet program.

Each program log message is assigned a specific level of error severity. The condition codes for the IBM z/OS operating system and their meanings are:

• 0 = No errors

• 4 = Warning

• 8 = Error

• 12 = Fatal error

For the UNIX and Windows operating systems, the condition codes and their meanings are:

• 0 = No errors

• 1 = Warning

• 2 = Error

• 3 = Fatal error



CONF - Generate Configuration FileThe CONF command creates a Configuration text file from the information in a Configuration/Widths file. The Configuration text file generated by this command can be edited and used for Configuration input in the next execution of the FDB utility.

Syntax CONF p1

Parameters

p1

Include comments in the Configuration text file.

0 — Include comment lines in the created Configuration text file.

1 — Do not include comments in the created Configuration text file.

Default: 0

Note: Occasionally, it is necessary to generate a Configuration file from the information in a Configuration/Widths file. This can occur if the original Configuration text file that created the Widths file is lost or if the user cannot determine which of many versions of a Widths file is being used.

ExampleThe following example illustrates use of the CONF command to create a Configuration text file from a CompuSet Configuration/Widths file for some Xerox Centralized printers.

>FDB: MACH 2FDB050012-I: XEROX 8700/9700/4050 SELECTED.FDB: CONFCompuSet CONFIGURATION FILE GENERATED FOR THE XEROX 9700FDB050021-I: XEROX 8700/9700/4050 CONFIGURATION FILE CREATED.>



DELE - Delete FontThe DELE command deletes a font from the font database.

Syntax DELE p1

Parameters

p1

Name of the font to be deleted.

Default: Required

Note: To use the DELE command, the FDB utility must be in initialization (INIT) or update (UPDT) mode, and output device selection (MACH) must be made prior to deleting a font.

ExampleThe following example shows how the DELE command can remove fonts from a font database.

FDB050345-I: ENGLISH LANGUAGE MESSAGES SELECTED.>FDB: UPDT -666FDB050008-I: FONT DATA BASE OPENED FOR IN-PLACE UPDATE.FDB050009-I: ERRORS COULD PERMANENTLY DESTROY YOUR FILE.FDB050010-I: PROCEED WITH CAUTION!>FDB: MACH 8FDB050012-I: XEROX 2700/3700/4045 SELECTED.>FDB: DELE XCP14-PFDB050029-I: XEROX 2700/3700/4045 FONT ’XCP14-P’ DELETED.>



FDB: DELE XCP14-LFDB050029-I: XEROX 2700/3700/4045 FONT ’XCP14-L’ DELETED.>FDB: MACH 2FDB050012-I: XEROX 8700/9700/4050/4090/4650 SELECTED.>FDB: DELE AB1AJPFDB050029-I: XEROX 8700/9700/4050/4090/4650 FONT ’AB1AJP’ DELETED.>

FDB: DELE UN104BFDB050029-I: XEROX 8700/9700/4050/4090/4650 FONT ’UN104B’ DELETED.>



EDIT - Edit FontThe EDIT command modifies the font most recently specified in a FONT command. Several EDIT commands can be invoked successively on the same font. The effect is cumulative. Currently, only Xerox Centralized and Decentralized fonts can be edited.

EDIT can produce customized fonts for special applications or requirements. Fonts can be subsetted to reduce memory requirements and prevent font memory overflow.

Syntax EDIT p1,p2,p3

Parameters

p1

Edit function to be performed.

1 — Unused.

2 — Unused.

3 — Unused.

4 — Change all character widths to zero and toggle the physical orientation of the font.

5 — Convert the font to metrics only by discarding the bitmap portion of the font. (The result of this operation is

identical to having loaded the font with p2 of the LOAD command specified as 1).

6 — Relocate characters to new character code locations in the font based upon the current definition of the

character mapping table.

7 — Change the ISO (International Standards Organization) compatibility and floating accent attributes of the

font. Applies to Xerox Decentralized printer fonts. See the 3700 Laser Printing System Management

Guide, publication 600P87276-A. (Not available to Rank Xerox customers).

8 — Delete specified characters from the font (retain all other characters).



9 — Retain specified characters in the font (delete all other characters).

10 — Duplicate a specified character in the font so that it can be accessed at more than one character location.

Default: Required

p2

Edit parameters. Ignored if p1 = 1 – 6. If p1 = 7, specify settings for the ISO and floating accent attributes.

0 — Clear both the ISO and floating accent attributes.

1 — Let the ISO attribute; clear the floating accent attribute.

2 — Set both the ISO and floating accent attributes.

Default: Required only if p1 = 7, 8, 9, or 10.

p3

Hexadecimal character code identifier of the new location for the duplicated character specified in p2 (the character currently in this location will be deleted from the font).

Default: Required only if p1 = 10.

Caution: Editing fonts with the ISO-compatibility attribute can render them incompatible with the ISO6937 standard and potentially unusable. Set or clear the ISO or floating accent attributes following other editing operations performed on ISO fonts.

Note: The following notes apply to the EDIT command:

• For p2, if p1 = 8 or 9, specify the hexadecimal locations of the characters to delete or retain. Multiple specifications must be separated by commas. Specify sequential locations by separating the first and last locations with a dash. See the notes for examples. If p1 = 10, specify the hexadecimal location of the character to be duplicated (location 20 cannot be specified).

• For p3, location 20 (the space character) cannot be specified. Regardless of the edit function and parameters specified, the space character is never removed from a font.



Saving the ChangesWhen EDIT is invoked, the font is copied non-destructively into the scratch file for editing. The original font in the font database remains unchanged. To retain the modified font in the font database, you must explicitly save it with the SAVE command, which writes it back into the font database. Unless you specifically instruct the FDB utility to replace a font in the font database with its edited version, the original font remains unaltered in the font database.

RenamingRenaming (see “RENM - Rename Font” on page 331) reduces confusion when there are several customized versions of the same font. Edited and renamed fonts can also be used to construct a font Job Command file for downloading without the need for storing the fonts in the permanent font database. The following examples show how to customize a font.

ExamplesThe following example shows how the Xerox Decentralized font Titan10-P can be edited to remove all uppercase characters except A, E, I, O, and U, while retaining all other characters in the font.

>FDB: MACH 8FDB050012-I: XEROX 2700/3700/4045 SELECTED.>FDB: FONT Titan10-PFDB050044-I: XEROX 2700/3700/4045 FONT ’Titan10-P’ SELECTED.>FDB: EDIT 8, 42-44, 46-48, 4A-4E, 50-54, 56-5AFDB050034-I: XEROX 2700/3700/4045 FONT ’Titan10-P’ EDITED.

The next example shows how to edit the Xerox Decentralized font Titan10-P so that the question mark (?) character in location X´3F´ can be accessed from locations X´3F´ and X´5F´.



>FDB: MACH 8FDB050012-I: XEROX 2700/3700/4045 SELECTED>FDB: FONT Titan10-PFDB050044-I: XEROX 2700/3700/4045 FONT ’Titan10-P SELECTED.>FDB: EDIT 10, 3F, 5FFDB050034-I: XEROX 2700/3700/4045 FONT ’Titan10-P EDITED>



FJOB - Create Font Job Command File (Xerox LPS and PCL 5) The FJOB command creates a font Job Command file for downloading fonts to Xerox Decentralized and PCL 5 laser printers.

The FJOB command in the Configuration file must be preceded by:

• A MACH command to define the output device, clear the names of fonts previously specified in FONT commands, and clear the contents of the Scratch file.

• One or more FONT commands to specify the fonts to be included in the font file.

FJOB must be executed prior to any other MACH command to ensure that the fonts are written to the Font Job file.

Syntax FJOB p1,p2,p3,p4,p5,p6,p7,p8

Parameters

p1

Character format for writing the font Job Command file.

0 — Create font Job Command file commands and font encoding in host native character set.

1 — Create font Job Command file commands and font encoding in ASCII.

2 — Write font download commands in host native code and font encoding in ASCII.

3 — Create font Job Command file commands and font encoding in EBCDIC.

Default: 0



p2

Clear the font memory of the output device before loading the fonts present in the Font Job file.

0 — Generate a font job that clears the output device font memory before loading the specified fonts.

1 — Generate a font job that appends the specified fonts to those already residing in the output device font

memory.

Default: 0

p3

Escape character in the font job. The escape character is generally used to distinguish printer commands from font information in the font job (character is not translated on output, regardless of the value of p1).

A´x´ — x represents an ASCII character.

E´x´ — x represents an EBCDIC character.

X´x´ — x represents a hexadecimal value.

Default: X´1B´ on ASCII hosts and X´27´ on EBCDIC hosts.

p4

Filler character when padding output records to constant length; must be a character that is completely ignored by the printer when received (character is not translated on output, regardless of the value of p1).




Default: X´08´ on ASCII hosts and X´16´ on EBCDIC hosts.



p5

String of 1 – 10 characters as a record line-ending sequence (characters are not translated on output, regardless of the value of p1).




Default: X´0D0A´ on ASCII hosts and X´0D25´ on EBCDIC hosts. Both values correspond to a carriage return or linefeed sequence.

p6

Write the end-of-file sentinel to the font Job Command file following the font data.

0 — Do not write an end-of-file sentinel. This permits other data to be concatenated to the file.

1 — Write an end-of-file sentinel

Default: 0

p7

Status page showing the names of the downloaded fonts.

0 — Do not generate a status page.

1 — Generate a status page.

Default: 0

p8

Output a PCC byte.

0 — Output no PCC byte.

1 — Use a plus sign (+) as a PCC byte. A plus sign causes the printer to overprint the line.

2 — Use a space character ( ) as a PCC byte. A space character causes the printer to skip a line and print

Default: 0



Note: The following notes apply to the FJOB command:

• On most host systems, the default values are appropriate. Computer configurations that employ special communications controllers, or non-standard protocols may require parameter values other than the defaults. Due to the wide variety of configurations possible, specific parameter values cannot be suggested here.

• A font job can consist of a maximum of 40 fonts before a new FJOB command must be issued.

• The content of the scratch file and the list of specified fonts is cleared following processing of the FJOB command.

PCL Printers For a PCL 5 laser printer, specify MACH 15 and values for the FJOB p2 and p6 parameters. The p2 = 0 value deletes all soft fonts from printer memory. To retain soft fonts, or for a second occurrence of FJOB in a print stream, specify p2 = 1 to append new fonts to existing fonts.

For a series of FJOB commands in a multi-step job, use p6 = 0 to ensure that new fonts are appended to the file of existing fonts; the final FJOB command should specify p6 = 1 to write an end-of-file sentinel. If the job has only one FJOB command, specify p6 = 1.

PCC Byte If p8 = 1 or 2:

• The PCC byte is always the first byte in each record, and only ANSI carriage control is used.

• For downloading a font job, the records are fixed-length 81-byte records.

This parameter is most useful when a spooler, such as IBM VM RSCS, assumes that a file to be transmitted has a PCC/VFU byte in the first character position in each record, which the spooler discards. Now a PCC/VFU byte can be added for the spooler to discard before transmission of the fonts and text to the printer.



Example The example following creates a Font Job Command file for a Xerox Decentralized printer using four fonts stored in a font database. In the process of creating the font Job Command file (and for this sole purpose), the name of font OCRA10-P changes to OCRA10-SUBSET-P. All lowercase characters are deleted from the font. The changed font is not stored in the permanent font database.

>FDB: MACH 8FDB050012-I: XEROX 2700/3700/4045 SELECTED.>FDB: FONT Titan10-PFDB050044-I: XEROX 2700/3700/4045 FONT ’Titan10-P’ SELECTED.>FDB: FONT XCP14-PFDB050044-I: XEROX 2700/3700/4045 FONT ’XCP14-P’ SELECTED.>FDB: FONT OCRA10-PFDB050044-I: XEROX 2700/3700/4045 FONT ’OCRA10-P’ SELECTED.>FDB: RENM OCRA10-SUBSET-PFDB050077-I: XEROX 2700/3700/4045 FONT RENAMED TO ’OCRA10-SUBSET-P’.>FDB: EDIT 8, 61-7AFDB050034-I: XEROX 2700/3700/4045 FONT ’OCRA10-SUBSET-P’ EDITED.>FDB: FONT Kosmos10-PFDB050044-I: XEROX 2700/3700/4045 FONT ’Kosmos10-P’ SELECTED.>FDB: FJOB

FONT NAME CHARS BYTES



Titan10-P 190 12,484XCP14-P 190 6,946OCRA10-SUBSET-P177 9,396Kosmos10-P 190 10,320

4 FONTS 747 39,146FDB050039-I: XEROX 2700/3700/4045 FONT JOB FILE CREATED.>



FONT - Specify FontThe FONT command specifies the name of a font to be edited or renamed. To use the FONT command, you must first specify MACH to select an output device.

Syntax FONT p1

Parameters

p1

Name of the font to be edited or renamed.

Default: Required

Note: The following notes apply to the FONT command:

• The FONT command can also specify the names of fonts to use in the creation of a font Job Command file. For more information, see the section about downloading fonts.

• Issuing a MACH command clears the names of fonts previously specified in FONT commands.

Example The following example illustrates how a font is selected for subsequent processing.

>FDB: MACH 8FDB050012-I: XEROX 2700/3700/4045 SELECTED.>FDB: FONT Titan10-PFDB050044-I: XEROX 2700/3700/4045 FONT ’Titan10-P’ SELECTED.



FTAP - Write Font to Tape or DiskThe FTAP command generates font tapes or host disk files for selected laser printers from fonts in the font database. Currently, font tape creation is supported for all Centralized and Decentralized Xerox LPS.

Several fonts can be written to the same font tape or disk file by invoking the FTAP command repeatedly, once for each font. Only fonts in the font database can be written to tape or disk. Fonts located in the scratch file cannot be copied.

Syntax FTAP p1,p2,p3,p4,p5

Parameters

p1

Name of font to copy from the FDB; enter an asterisk (*) to specify all fonts for this machine.

Default: Required

p2

Output is to disk or tape. If tape, whether to rewind to the loadpoint before writing the fonts.

0 — Do not rewind the tape.

1 — Rewind the tape.

2 — Output to disk.

Default: 0

p3

Rewind tape to loadpoint after fonts are written.

0 — Do not rewind the tape.

1 — Rewind the tape.

Default: 0



p4

Character code for the font data (ASCII or EBCDIC). This parameter is meaningful for Xerox Decentralized fonts only and is ignored for other printers.

0 — ASCII-encoded font.

1 — EBCDIC-encoded font.

Default: 0

p5

Block size in bytes for writing the font tape or disk file. If this parameter is omitted or zero, the default block size for the output device is used. For Xerox Decentralized font tapes, values from 0 to 2048 that are integral multiples of either 80 or 128 are valid. For Xerox Centralized font tapes, values from 0 to 8192 that are integral multiples of 512 are valid. For Centralized disk files p5 is ignored.

Default: 2048 for Decentralized printers or 512 for Centralized printers.

Note: The following notes apply to the FTAP command:

• To create a font tape, you must first specify MACH to select the output device.

• The p3 parameter does not apply if p2 = -1.

• For Centralized printers, the disk file format is the same as that required for using HOSTCOPY to download the fonts to an online printer using an IBM channel interface, (for example, the font data, including font file tape labels are stored as a series of 128-byte fixed length records). For Decentralized printers, the data file format is fixed length records with a record length selected by the user.

• The creation of font tapes is subject to Xerox licensing restrictions.



Block and Record SizeFor disk file output, Centralized printer fonts are stored as 128-byte fixed length records. The data for each font is preceded by a 128-byte record containing a Centralized printer file tape label, and the data that follows consists of four (4) 128-byte records for each Centralized printer 512-byte disk block. The disk file can also be read back into a font database by specifying a LOAD command for input from disk.

Decentralized printer fonts are output to disk in fixed length records whose length is determined by p3. This disk file can be read back into a font database by specifying a LOAD command for input from disk. If a font download file for a Decentralized printer is required, use the FJOB command.

Multiple FontsWhen output to disk, multiple fonts can be output either by specifying individual fonts with separate FTAP commands or by outputting all fonts in the data base by specifying p1 = *.

After an FTAP command has been issued that selects either disk or tape as the font destination, all subsequent FTAP commands issued during the same execution of the FDB utility are output to the same destination as the initial command, regardless of the value given to p2. For example, if a font is output by the command FTAP UN104B,-1, at the beginning of an FDB run, the command FTAP UN210E,0, appearing later in the same run also outputs to the host disk file.

Disk File SpecificationsThe disk file used to output laser printer fonts is specified on individual hosts as shown in the following table.

Host Definition

IBM z/OS DD statement with DDNAME of CSS09.

Windows and UNIX The file specified by FILE 1 in the shell script for the FDB utility.



ExampleIn the following example, Xerox Centralized fonts in the font database are written to magnetic tape. The tape is rewound before and after the fonts are written.

>FDB: MACH 2FDB050012-I: XEROX 8700/9700/4050 SELECTED.>FDB: FTAP *,1,1FDB050214-I: XEROX 8700/9700/4050 FONT ’AA1AJP’COPIED TO TAPE.FDB050214-I: XEROX 8700/9700/4050 FONT ’AA1AJL’COPIED TO TAPE.FDB050214-I: XEROX 8700/9700/4050 FONT ’AA1AJI’COPIED TO TAPE.FDB050214-I: XEROX 8700/9700/4050 FONT ’AA1AJJ’COPIED TO TAPE.FDB050214-I: XEROX 8700/9700/4050 FONT ’AB1AJP’COPIED TO TAPE.FDB050214-I: XEROX 8700/9700/4050 FONT ’AB1AJL’COPIED TO TAPE.FDB050214-I: XEROX 8700/9700/4050 FONT ’AB1AJI’COPIED TO TAPE.FDB050214-I: XEROX 8700/9700/4050 FONT ’AB1AJJ’COPIED TO TAPE.FDB050049-I: XEROX 8700/9700/4050 FONT TAPE WRITTEN.>



GETC - Map Characters from a Source FontThe GETC command retrieves characters from a source font to map to new locations in a destination font. GETC modifies the character mapping table by assembling characters from specified locations (which can be scattered) in a source font.

Syntax GETC p1,p2...pn

Parameters

p1

Hexadecimal identifier of the new location in the destination font. If more than one character is being moved with a single GETC, the new location specifies the first in a sequence of consecutive locations where the characters are to be placed. If the new location = 0, no character can be mapped and the characters currently in the locations specified by p2 are removed or discarded.

Default: 0

p2 – pn

Hexadecimal identifier of the original location in the source font of the character to be moved. If more than one character is to be moved to a sequence of consecutive locations, several old locations can be specified, separated by commas. Multiple consecutive old locations can be specified by separating the first and last location with a dash, to eliminate the need to specify them all individually.

Default: Required

Note: The GETC command only defines the character mapping table. To relocate characters in a font, an EDIT 6 (relocate) command or a MAKE command must be executed.



Special FunctionsIf both new location and old location are specified as 0, the character mapping table is reset to one-to-one mapping.

If new location is specified as -1, the current character mapping for the specified old location(s) is displayed. Consequently GETC, using a value of -1, can determine the new locations from the specified old locations.

If new location is specified as -1 and old location is specified as 0, the entire character mapping table is displayed in sequence by ascending old location value.

ExampleRefer to the font PressRoman11B-P, which is displayed in Appendix F, “Character Charts”. To create a new font, PressRoman11BX-P is identical, except for exchanging the locations of the # and ^r characters (in locations 23 and B9, respectively) and for moving the characters ~X and ~3 in locations A0 and CE to locations 5E and 5F.

>FDB: MOVC 23, B9FDB050245-I: CHARACTER 23 (HEX) IS MAPPED TO LOCATION B9 (HEX).>FDB: MOVC B9, 23FDB050245-I: CHARACTER B9 (HEX) IS MAPPED TO LOCATION 23 (HEX).>FDB: GETC 5E, A0, CEFDB050245-I: CHARACTER A0 (HEX) IS MAPPED TO LOCATION 5E (HEX).FDB050245-I: CHARACTER CE (HEX) IS MAPPED TO LOCATION 5F (HEX).>FDB: GETC -1, 0FDB050244-I: CHARACTER MAPPING IS ONE-TO-ONE WITH THE FOLLOWING EXCEPTIONS:FDB050245-I: CHARACTER 23 (HEX) IS MAPPED TO LOCATION B9 (HEX).



FDB050245-I: CHARACTER 5E (HEX) IS MAPPED TO LOCATION 00 (HEX).FDB050245-I: CHARACTER 5F (HEX) IS MAPPED TO LOCATION 00 (HEX).FDB050245-I: CHARACTER A0 (HEX) IS MAPPED TO LOCATION 5E (HEX).FDB050245-I: CHARACTER B9 (HEX) IS MAPPED TO LOCATION 23 (HEX).FDB050245-I: CHARACTER CE (HEX) IS MAPPED TO LOCATION 5F (HEX).>FDB: MOVC -1, 0FDB050244-I: CHARACTER MAPPING IS ONE-TO-ONE WITH THE FOLLOWING EXCEPTIONS: FDB050245-I: CHARACTER B9 (HEX) IS MAPPED TO LOCATION 23 (HEX).FDB050245-I: CHARACTER A0 (HEX) IS MAPPED TO LOCATION 5E (HEX).FDB050245-I: CHARACTER CE (HEX) IS MAPPED TO LOCATION 5F (HEX).FDB050245-I: CHARACTER 00 (HEX) IS MAPPED TO LOCATION A0 (HEX).FDB050245-I: CHARACTER 23 (HEX) IS MAPPED TO LOCATION B9 (HEX).FDB050245-I: CHARACTER 00 (HEX) IS MAPPED TO LOCATION CE (HEX).>FDB: MACH 8FDB050012-I: XEROX 2700/3700/4045 SELECTED.>FDB: FONT PressRoman11B-PFDB050044-I: XEROX 2700/3700/4045 FONT ’PressRoman11B-P’ SELECTED.>FDB: EDIT 6 FDB050034-I: XEROX 2700/3700/4045 FONT ’PressRoman11B-P’ EDITED.>FDB: RENM PressRoman11BX-PFDB050077-I: XEROX 2700/3700/4045 FONT RENAMED TO ’PressRoman11BX-P’.>FDB: SAVEFDB050059-I: DUPLICATE FONTS WILL NOT BE REPLACED.FDB050155-I: XEROX 2700/3700/4045 FONT ’PressRoman11BX-P’ SAVED.



INFF - Define INFO FontThe INFF command defines the name of the permanent portrait font on a Xerox Decentralized printer. This font is required to display the font information generated by the INFO and SAMP commands.

Syntax INFF p1

Parameters

p1

Name of the permanent portrait font on a Xerox Decentralized printer.

Default: Required

Note: The following notes apply to the INFF command:

• The default font name is Titan10iso-P, which is the permanent portrait font in the United States but not in Europe, where Titan10-P is sometimes used.

• If required, INFF must precede any INFO or SAMP commands.

ExampleThe following example shows how to use the INFF command.

>

INFF Titan10iso-PINFO UNI04B>



INFO - Display Font DataThe INFO command displays font data for Decentralized fonts contained in the font database. The font data is displayed in the Log file. To use the INFO command, the MACH command must first be set to value 8 for the Xerox Decentralized printers.

Syntax INFO p1

Parameters

p1

Name of font to be displayed.

Default: Required

Note: The following notes apply to the INFO command:

• The font to be displayed must reside in the font database. Font data sheets cannot be generated for fonts located in the scratch file.

• Depending upon the load of your host computer, the INFO command can take up to several minutes to process; some font data sheet information requires a bit-by-bit analysis of a font bitmap.

ExampleThis example shows the generation and appearance of a font data sheet.

> FDB: MACH 8FDB050012-I: XEROX 2700/3700/4045 SELECTED.>FDB: INFO Titan10iso-P

XEROX 2700/3700/4045 FONT DATA SHEETFONT ID NAME: Titan10iso-P



PART NUMBER: 22501REVISION NUMBER: 6

FONT TYPE ORIENTATION: PORTRAITPITCH: FIXEDFONT POSSESSES ISO ATTRIBUTEFONT CONTAINS FLOATING ACCENTSFONT DOES NOT CONTAIN KERNING INFORMATION

SCOPE NUMBER OF PRINTABLE CHARACTERS: 195NUMBER OF SPACE CHARACTERS: 1BEGINNING/ENDING CHARACTER: 20/FF (HEX)

VERTICAL NOMINAL LINE SPACING: 50 BITS (12 POINTS) SPACING FONT HEIGHT: 60 BITS (14 POINTS)

HIGHEST/LOWEST BIT IN FONT (ABOVE BASELINE): 46/-14MAXIMUM ALPHA ASCENDER (ABOVE BASELINE): 34 BITSMAXIMUM ALPHA DESCENDER (ABOVE BASELINE): -10 BITSCAP HEIGHT: 30 BITS LOWERCASE ’X’ HEIGHT: 23 BITS

HORIZONTAL AVERAGE CHARACTER WIDTH: 30.00000 BITSSPACINGAVERAGE FIGURE WIDTH: 30.0 BITS

NUMBER OF CHARACTERS PER INCH: 10.00000LOWER CASE ALPHABET LENGTH: 15.6 PICASUPPER CASE ALPHABET LENGTH: 15.6 PICAS

OTHER UNDERLINE OFFSET (ABOVE BASELINE): -10 BITSMETRICSUNDERLINE THICKNESS: 4 BITS

STRIKEOUT OFFSET (ABOVE BASELINE): 13 BITSSTRIKEOUT THICKNESS: 5 BITS SUPERSCRIPT OFFSET (ABOVE BASELINE): 18 BITSSUBSCRIPT OFFSET (ABOVE BASELINE): -12 BITS

FILE SIZEDECODED: 22,092 BYTES ENCODED: 29,456 BYTES



CHARACTERCHARACTER CHARACTER LEFT/RIGHT HIGH/LOWMETRICS CODE WIDTH SIDE BEARING (ABOVE

(HEX) BITS) (NEG = KERN) BASELINE)

20 30 0/ 30 0/ 021 30 10/ 10 31/ -122 30 7/ 7 33/ 023 30 4/ 4 33/ -524 30 0/ 0 30/ 025 30 4/ 4 32/ -226 30 4/ 5 27/ -227 30 12/ 12 33/ 028 30 10/ 10 31/ -829 30 9/ 10 31/ -92A 30 5/ 5 33/ 02B 30 3/ 3 29/ 0

:::

F8 30 4/ 4 32/ 0F9 30 1/ 2 28/ -5FA 30 0/ 0 24/ -1FB 30 2/ 2 32/ -1FC 30 2/ 1 30/ -10FD 30 3/ 4 31/ -1FE 30 3/ 5 24/ -10

** UNASSIGNED CHARACTER LOCATION>



INIT - Initialize New Font DatabaseThe INIT command creates a new font database file or reinitializes (destroys and recreates) an existing font database.

Syntax INIT p1

Parameters

p1

Maximum number of blocks for font database expansion (range 100 – 32000). Guidelines for determining appropriate values for the size parameter can be found in this chapter.

Default: Required

Note: The following notes apply to the INIT command:

• INIT must be the first command in the file (aside from comments) to invoke the initialization mode.

• On IBM z/OS systems, one block is 1020 words (4080 bytes). On all other systems, one block is 512 words (the number of bytes depends upon the word size of the particular host). The size value is used primarily by host systems that require files and space to be allocated prior to use.

• The size specified in the INIT command must correspond to the preallocated space. For hosts that do not require file pre-allocation, the size value on the INIT command can be specified as any value sufficient to contain the fonts to be loaded into the data base or, alternatively, 32,000.

• Following processing of the INIT command, the font database file contains a special file header to mark it as a font database. Further, the data base is placed into update mode so that font information can be added to it. Specifying the LOAD command next to load fonts into the data base is recommended.



ExampleThe following example illustrates use of the INIT command to initialize a new font database. The database is allowed to expand to 2,000 blocks.

FDB050345-I: ENGLISH LANGUAGE MESSAGES SELECTED.>FDB: INIT 2000FDB050004-I: FONT DATA BASE FILE INITIALIZED.>



LANG - Language SelectionThe LANG command selects the language to display FDB utility messages. Because the FDB utility is designed to be used in many countries throughout the world, it supports multi-national message displays. The FDB utility program retrieves messages from the Message Data Base file and displays them in the language of choice.

LANG can be issued any time you want to change the message display language. There is no limit on the number of times it can be issued in one execution of the FDB utility.

Syntax LANG p1

Parameters

p1

Language for messages.

0 — Site-specific default

1 — English

2 — French

3 — German

4 — Spanish

5 — Italian

6 — Dutch

7 — Swedish

8 — Norwegian

9 — Danish

10 — Portuguese

11 — Finnish

Default: 0



Note: The following notes apply to the LANG command:

• When the FDB utility is invoked, the site-specific default language is automatically selected by the utility program and identified in the log file. This default is selected and specified during software installation when the Message Data Base Utility (MDBUTL) is run.

• When building the message database file at your site, you can exclude one or more languages from the database in order to reduce the disk space required for the message database file. Consequently, not all of the languages listed above may be available on your system.

• For US customers, message text is delivered in the English language only. In other countries, languages available for message text may vary.

ExampleThe following example illustrates use of the LANG command to select a language for subsequent FDB utility messages.

FDB050345-I: ENGLISH LANGUAGE MESSAGES SELECTED.>FDB: LANG 2FDB050344-I: SELECTING FRENCH LANGUAGE MESSAGES.FDB050345-I: FRANCAIS CHOISI POUR LES MESSAGES.>FDB: UPDT -666FDB050008-I: BASE DE DONNEES POLICES OUVERTE POUR UNE MI E A JOUR ’EN PLACE’.FDB050009-I: DES ERREURS PERMENENTES RISQUENT DE DETRUIRE VOTRE FICHIER.FDB050010-I: PROCEDER AVEC PRECAUTION!>



LIST - Display Font ListThe LIST command enables you to display the contents of the font database.

Syntax LIST p1

Parameters

p1

Output device:

0 — List all fonts in data base.

2 — Xerox Centralized printers.

8 — Xerox Decentralized printers.

12 — Xerox 4650

13 — AFP

14 — PostScript

15 — HP PCL

Output device most recently specified by the MACH command. If no output device is currently specified, all fonts in the data base are listed.

Note: The following notes apply to the LIST command:

• The meaning of the coded indicators in the FLAGS column of the listing are:

E — Font has been edited by the EDIT command.

L — This is a logo (Xerox Centralized printers only).

M — Font was created with the MAKE command.

R — Font has been renamed with the RENM command.

W — Font contains metric (widths) information only.

Z — All character widths in this font are zero; font has been edited with edit function 4 of the EDIT command.



• Font databases created by some early versions of the FDB utility program did not record the time of data base creation and, therefore, display "00:00:00" as the creation time.

• The p1 values of 1, 3 – 7, and 9 – 11 are supported for backward compatibility but should not be selected for new applications.

ExampleThis is an example of an FDB log.

FDB: LISTFDB050002-I: FONT DATA BASE OPENED FOR READ-ONLY ACCESS.

FONT DATA BASE CREATED AT 00:00:00 ON TUESDAY, DECEMBER XX, 19XXLAST UPDATED AT 13:23:07 ON WEDNESDAY, JANUARY XX, 19XX

2,500 BLOCKS AUTHORIZED 183 BLOCKS USED 7.3% FULL 11 FONTS

PACKING WOULD RECOVER 53 BLOCKS

MACH PHY LOG BLOCK DATECODE FONT NAME ROT ROT FLAGS COUNT INSERTED

2 AB1AJP P P W 3 12/09/862 AB1AJL L L W 3 12/09/862 AB1AJI IP IP W 3 12/09/862 AB1AJJ IL IL W 3 12/09/868 Kosmos 10-L L L 17 01/21/878 LetterGothic12-PP P 16 01/21/878 LetterGothic12-LL L 17 01/21/878 Titan10-L L L 20 01/21/878 Mercury P P R 17 01/21/878 Venus P P RE 15 01/21/878 Kosmos 10-P l P Z 14 01/21/87



LOAD - Load Fonts into the Font DatabaseThe LOAD command copies fonts and font metrics into the font database. Depending on the machine selection, the FDB utility attempts to read a font tape, disk file, or a font source file.

Syntax LOAD p1,p2,p3,p4,p5

Parameters

p1

Replace existing fonts in the font database with fonts of the same name from the font tape or font source file.

0 — Do not replace existing fonts.

1 — Replace existing fonts.

Default: 0

p2

Load the entire font into the font database or just the font metrics.

0 — Load entire font (including bitmap, if present).

1 — Load only the font metrics.

2 — Load both Standard and ISO Latin 1 characters for PostScript.

Default: 0

p3

Size, in bytes, of the tape block or file record containing Xerox Decentralized fonts. If this parameter is omitted or zero, default record size for the machine (MACH) applies. This parameter applies only to a Xerox Decentralized Printer font tape or disk file. Values from 0 to 2048 that are integral multiples of either 80 or 128 are valid.

Default: 2048 for input from tape; 12 for input from disk.



p4

Source of fonts to be loaded (Xerox Centralized and Decentralized Printer fonts only).

0 — Load fonts from a printer font magnetic tape.

1 — Load fonts from a disk file.

Default: 0

p5

Type of input file flag. Specify only for PostScript.

0 — Input file is a text file with Adobe Font Metrics (AFM).

1 — Input file is a text file with a list of input file types and input file names. The file names are for fonts and font

metrics.

Note: The following notes apply to the LOAD command:

• Generally, fonts to be downloaded to printers (Xerox Decentralized fonts, for example) must be loaded into the database in their entirety to permit font Job Command files to be created for the output device.

• Fonts that are not to be downloaded to an output device (Xerox Centralized fonts, for example) need only have their metrics loaded into the font database. Loading only metrics into the font database, when appropriate, can significantly reduce the amount of disk space required on the host computer to maintain the fonts.

• If p5 is set to one, the FDB utility reads a separately created text file that defines a variety of input AFM, PFA, PFB or PFM font metrics files that reside in different directories.

• The file types defined in the created input file are:

– 0 = A text file with Adobe Font Metrics (AFM).

– 1 = A text file with Adobe Type 1 fonts (PFA).



– 2 = A binary sequential file with Adobe Type 1 fonts in PFB format.

– 3 = A binary sequential file with PostScript font metrics in PFM format.

Block and Record SizeXerox Centralized printer fonts to be loaded from disk must be stored in the same format as required when using HOSTCOPY to download the fonts through an IBM printer channel. This means that the fonts must be stored as 128-byte fixed length records. The data for each font is preceded by a 128-byte record containing a Centralized printer tape label, and the data that follows consists of four 128-byte records for each Centralized printer 512-byte disk block.

Xerox Decentralized printer fonts to be loaded from disk must be stored in disk records where each disk record is a copy of the equivalent record on the printer font tape. The tape block length and printer record length can have any value from 80 to 2048, which is an integer multiple of 80 or 128.

Multiple FontsMultiple fonts can be included in both Xerox Centralized and Decentralized font files on disk. The load procedure uses information in the font header to determine where the next font in the file starts. Each font must start at the beginning of a new record. On IBM z/OS systems, you can also use data set concatenation to load multiple fonts during a single load operation.

Disk File SpecificationsThe disk file font loading for Xerox Centralized and Decentralized printers is specified on individual hosts as shown in the following table.

Host Specification

IBM z/OS DD statement with DDNAME of CSS04.

Windows and UNIX The file specified by FILE 14 in the shell procedure for the FDB utility.



Using the LOAD CommandTo use the LOAD command, your font database must be in either INIT or UPDT mode. Further, the output device selection (MACH) must be specified prior to loading fonts.

PostScript ISO Latin1 Character EncodingThe PostScript output formatter, the FDB utility program, and the Postscript Configuration text file (Postiso.cnf) have enhancements that make it easy for CompuSet and the PostScript output formatter to switch from one encoding scheme to the other within a single job, either Standard encoding or Latin1 encoding. Use the p2 parameter of the FDB LOAD command to specify that both encoding schemes are to be used.

ExampleThe following example illustrates a sequence of commands that load a tape of Xerox Decentralized printer fonts into an existing font database.

FDB050345-I: ENGLISH LANGUAGE MESSAGES SELECTED.>FDB: UPDT 5000FDB050006-I: FONT DATA BASE OPENED FOR UPDATE.>FDB: MACH 8 FDB050012-I: XEROX 2700/3700/4045 SELECTED.>FDB: LOAD FDB050059-I: DUPLICATE FONTS WILL NOT BE REPLACED.FDB050175-I: XEROX 2700/3700/4045 FONT ’Kosmos10-P’ LOADED.FDB050175-I: XEROX 2700/3700/4045 FONT ’Kosmos10-L’ LOADED.FDB050175-I: XEROX 2700/3700/4045 FONT ’LetterGothic12-P’ LOADED.FDB050175-I: XEROX 2700/3700/4045 FONT ’LetterGothic12-L’ LOADED.FDB050175-I: XEROX 2700/3700/4045 FONT ’Titan10-P’ LOADED.FDB050175-I: XEROX 2700/3700/4045 FONT ’Titan10-L’ LOADED.FDB050175-I: XEROX 2700/3700/4045 FONT ’XCP14-P’ LOADED.



FDB050175-I: XEROX 2700/3700/4045 FONT ’XCP14-L’ LOADED.FDB050175-I: XEROX 2700/3700/4045 FONT ’OCRA10-P’ LOADED.FDB050175-I: XEROX 2700/3700/4045 FONT ’OCRA10-L’ LOADED.FDB050061-I: XEROX 2700/3700/4045 FONT DATA LOADED.



MACH - Identify Output DeviceThe MACH command specifies the output device for the fonts to be accessed. A single font database can contain fonts for several different output devices. After establishing access to a FDB but before dealing with fonts, you must designate the output device to select the fonts to be manipulated by the FDB utility.

Syntax MACH p1

Parameters

p1

Output device.

0 — None selected.

2 — Xerox Centralized printers.

8 — Xerox Decentralized printers.

12 — Xerox 4650

13 — AFP

14 — PostScript

15 — HP PCL

Default: MACH clears the names of fonts previously specified by FONT commands.

Note: The following notes apply to the MACH command:

• The MACH command can be issued many times in one FDB file. It is possible to work with the fonts for several different output devices simply by changing the machine code with the MACH command.

• MACH clears the scratch file of any fonts previously specified by FONT commands. Any fonts that were edited, renamed, or made must be saved or downloaded using the SAVE or FJOB commands before a new MACH is specified.

• The p1 values of 1, 3 – 7, and 9 – 11 are supported for backward compatibility but should not be selected for new applications.



ExampleThe following example uses the MACH command to select the Xerox Centralized printer font for subsequent processing.

>FDB: MACH 2FDB050012-I: XEROX 8700/9700/4050 SELECTED.>



MAKE - Convert FontThe MAKE command creates a new font for a Xerox Centralized LPS font and stores it in a scratch file.

Syntax MAKE p1,p2,p3,p4

Parameters

p1

Name of the Xerox Centralized font to convert.

Default: Required

p2

Location where the new font is to be placed.

0 — Place the newly created font in the scratch file. This permist the font to be renamed or edited prior to

saving it in the font database or permist it to be used as part of a font job without keeping it permanently.

Fonts placed in the scratch file must be explicitly saved using the SAVE command if they are to be

retained in the font database.

1 — Save the newly created font directly in the font database.

Default: 0

p3

Delete the original font.

0 — Do not delete the Xerox Centralized printer font.

1 — Delete the Xerox Centralized font from the font database after the new font has been created.

Default: 0



p4

Settings for the ISO (International Standards Organization) compatibility and floating accent attributes of the created font. These attributes apply to Xerox Decentralized fonts and are fully described in the 3700 Laser Printing System Management Guide. (Not available to Rank Xerox customers).

0 — Rename both the ISO and floating accent attributes.

1 — Set the ISO attribute; remove the floating accent attribute.

2 — Set both the ISO and floating accent attributes. High and low accent definitions are set to the ISO

standard.

3 — Set both the ISO and floating accent attributes. High and low accent definitions are set to the CompuSet

standard.

Default: 0

Note: The creation of fonts is subject to Xerox licensing restrictions. Font creation is supported only for the Xerox Decentralized LPS.

ExampleIn the following example, the Xerox Decentralized font Century10-P is created from the Centralized font AA1AJP and saved in the font database. In the process of creating the font, the characters in locations 10 through 1F are relocated to character locations A0 through AF.

>FDB: MOVC 10, A0-AFFDB050245-I: CHARACTER 10(HEX)IS MAPPED TO LOCATION A0(HEX).FDB050245-I: CHARACTER 11(HEX)IS MAPPED TO LOCATION A1(HEX).FDB050245-I: CHARACTER 12(HEX)IS MAPPED TO LOCATION A2(HEX).FDB050245-I: CHARACTER 13(HEX)IS MAPPED TO LOCATION A3(HEX).FDB050245-I: CHARACTER 14(HEX)IS MAPPED TO LOCATION A4(HEX).FDB050245-I: CHARACTER 15(HEX)IS MAPPED TO LOCATION A5(HEX).



FDB050245-I: CHARACTER 16(HEX)IS MAPPED TO LOCATION A6(HEX).FDB050245-I: CHARACTER 17(HEX)IS MAPPED TO LOCATION A7(HEX).FDB050245-I: CHARACTER 18(HEX)IS MAPPED TO LOCATION A8(HEX).FDB050245-I: CHARACTER 19(HEX)IS MAPPED TO LOCATION A9(HEX).FDB050245-I: CHARACTER 1A(HEX)IS MAPPED TO LOCATION AA(HEX).FDB050245-I: CHARACTER 1B(HEX)IS MAPPED TO LOCATION AB(HEX).FDB050245-I: CHARACTER 1C(HEX)IS MAPPED TO LOCATION AC(HEX).FDB050245-I: CHARACTER 1D(HEX)IS MAPPED TO LOCATION AD(HEX).FDB050245-I: CHARACTER 1E(HEX)IS MAPPED TO LOCATION AE(HEX).FDB050245-I: CHARACTER 1F(HEX)IS MAPPED TO LOCATION AF(HEX).>FDB: MACH 8FDB050012-I: XEROX 2700/3700/4045 SELECTED.>FDB: MAKE AA1AJPFDB050070-I: XEROX 2700/3700/4045 FONT ’AA1AJP’ CREATED.>

>FDB: RENM Century10-PFDB050077-I: XEROX 2700/3700/4045 FONT RENAMED TO ’Century10-P’.>

>FDB: SAVEFDB050059-I: DUPLICATE FONTS WILL NOT BE REPLACED.FDB050155-I: XEROX 2700/3700/4045 FONT ’Century10-P’ SAVED.>



MOVC - Map Characters to FontThe MOVC command modifies the character mapping table by moving characters from sequential locations in a source font to assigned locations (which can be scattered) in a destination font.

Syntax MOVC p1,p2,...pn

Parameters

p1

Original hexadecimal location in the source font from which a character is to be moved. Valid values are 0 through FF, inclusive. If more than one character is being moved with a single MOVC command, the old location specifies the first in a sequence of consecutive locations from which the characters are to be moved. If the old location = 0, the character location(s) specified by new location have nothing mapped into them in the destination font, so they are removed or discarded.

Default: 0

p2 – pn

Hexadecimal location in the destination font to which the character in old location is to be moved. Valid values are 1 through FF, inclusive. If more than one character is to be moved from a sequence of consecutive locations, several new locations can be specified provided that they are separated by commas. More than one consecutive new location can be specified by separating the first and last locations with a dash, to eliminate the need to specify them all individually. See the notes for examples.

Default: One or more values must be specified for new location.

Note: The MOVC command defines only the character mapping table. To relocate characters in a font, an EDIT 6 (relocate) command or a MAKE command must be executed.



Special FunctionsIf both old location and new location are specified as zero, the character mapping table is reset to one-to-one mapping.

If old location is specified as -1, the character mapping for the new location is displayed. MOVC -1 can then determine which old location maps to the specified new location.

If old location is specified as -1 and new location is specified as 0, the entire character mapping table is displayed in sequence by ascending new location value.

ExampleTo create a new font, PressRoman11BX-P is identical, except for exchanging the locations of the # and ^r characters (in locations 23 and B9, respectively) and for moving the characters ~X and ~3 in locations A0 and CE to locations 5E and 5F.

>FDB: MOVC 23, B9FDB050245-I: CHARACTER 23(HEX) IS MAPPED TO LOCATION B9(HEX).>FDB: MOVC B9, 23FDB050245-I: CHARACTER B9(HEX) IS MAPPED TO LOCATION 23(HEX).>FDB: GETC 5E, A0, CEFDB050245-I: CHARACTER A0(HEX) IS MAPPED TO LOCATION 5E(HEX).FDB050245-I: CHARACTER CE(HEX) IS MAPPED TO LOCATION 5F(HEX).>FDB: GETC -1, 0FDB050244-I: CHARACTER MAPPING IS ONE-TO-ONE WITH THE FOLLOWING EXCEPTIONS:FDB050245-I: CHARACTER 23(HEX) IS MAPPED TO LOCATION B9(HEX).FDB050245-I: CHARACTER 5E(HEX) IS MAPPED TO LOCATION 00(HEX).FDB050245-I: CHARACTER 5F(HEX) IS MAPPED TO LOCATION 00(HEX).



FDB050245-I: CHARACTER A0(HEX) IS MAPPED TO LOCATION 5E(HEX).FDB050245-I: CHARACTER B9(HEX) IS MAPPED TO LOCATION 23(HEX).FDB050245-I: CHARACTER CE(HEX) IS MAPPED TO LOCATION 5F(HEX).>FDB: MOVC -1, 0FDB050244-I: CHARACTER MAPPING IS ONE-TO-ONE WITH THE FOLLOWING EXCEPTIONS:FDB050245-I: CHARACTER B9(HEX) IS MAPPED TO LOCATION 23(HEX).FDB050245-I: CHARACTER A0(HEX) IS MAPPED TO LOCATION 5E(HEX).FDB050245-I: CHARACTER CE(HEX) IS MAPPED TO LOCATION 5F(HEX).FDB050245-I: CHARACTER 00(HEX) IS MAPPED TO LOCATION A0(HEX).FDB050245-I: CHARACTER 23(HEX) IS MAPPED TO LOCATION B9(HEX).FDB050245-I: CHARACTER 00(HEX) IS MAPPED TO LOCATION CE(HEX).>FDB: MACH 8FDB050012-I: XEROX 2700/3700/4045 SELECTED.>FDB: FONT PressRoman11B-PFDB050044-I: XEROX 2700/3700/4045 FONT ’PressRoman11B-P’ SELECTED.>FDB: EDIT 6FDB050034-I: XEROX 2700/3700/4045 FONT ’PressRoman11B-P’ EDITED.>FDB: RENM PressRoman11BX-PFDB050077-I: XEROX 2700/3700/4045 FONT RENAMED TO ’PressRoman11BX-P’.>FDB: SAVEFDB050059-I: DUPLICATE FONTS WILL NOT BE REPLACED.FDB050155-I: XEROX 2700/3700/4045 FONT ’PressRoman11BX-P’ SAVED.



PACK - Compress Font DatabaseThe PACK command compresses the font database file to eliminate unusable space. As fonts are added, modified, and deleted from the font database, the file can become fragmented with small areas of empty space. Compressing the file creates a single area of usable space. The INIT or UPDT command must also be specified to compress the file.

Syntax PACK

Caution: The PACK command, once invoked, must be allowed to run to completion. Interrupting the file compression results in destruction of the font database. The time required to compress a font database varies with the amount of fragmentation, the size and number of fonts in the database, the speed of the host CPU and disk device, and the load on the system. Under normal circumstances, a typical compression can take 1 to 10 minutes.

Note: When compressing a font database, do not exceed user, job, or other computer system resource limits that might abort the process before it is completed.

ExampleThe following example shows how to use the PACK command.

>

FDB: PACK

FDB050172-I: ’PACK’ MUST RUN TO COMPLETION. INTERRUPTING IT WILL RESULT IN THE DESTRUCTION OF

THIS DATA BASE.

FDB050073-I: FONT DATA BASE FILE PACKED -- 53 BLOCKS RECOVERED.

>



QUIT - Terminate FDBThe QUIT command terminates the FDB utility in an orderly fashion. If the font database is accessed in initialization mode or update mode, the termination process updates and rewrites the font database file header to reflect any changes made. Failure to terminate properly can leave the font database in an unstable state or inaccessible in the future.

The FDB utility can be terminated in two ways. Either can be used; however, if your computer system recognizes special “/” input lines (some IBM systems), use the QUIT command to terminate the program.

Syntax QUIT

/

Note: The second form of the command consists of a slash (in column 1) followed by anything in the other columns.

Example The following example shows the job log when you use the QUIT command.

>FDB: QUITFDB050305-I: END OF RUN AT 12:56:28 ON WEDNESDAY, JANUARY XX,19XX.



RENM - Rename FontThe RENM command changes the name of the font specified in the most recent FONT command. When RENM is invoked, the font is copied non-destructively into the scratch file and the copy is renamed. The original font in the font database remains unchanged. The RENM command can be interspersed with EDIT commands, and they can be invoked successively on the same font. The effect is cumulative. Currently, only Xerox Centralized and Decentralized LPS fonts can be renamed.

Syntax RENM ’p1’

Parameters

´p1´

New font name (in single quotes).

Default: Required

Note: The following notes apply to the RENM command:

• Valid names for Xerox Centralized fonts are composed of 1 to 6 uppercase alphanumeric characters. No punctuation or special characters are allowed.

• By convention, the last letter of the font name indicates the font’s orientation: P (portrait), L (landscape), I (inverse portrait), J (inverse landscape). Adherence to the convention is suggested but not required.

• Valid names for Xerox Decentralized fonts are composed of 1 to 20 characters. The font name can consist of uppercase and lowercase alphabetic characters, numbers and special characters, including punctuation. By convention, the font names end with -P for portrait fonts and -L for landscape fonts.



ExampleThe following example shows how how to rename the Xerox Decentralized font Titan10-P to Saturn-P.

>FDB: MACH 8FDB050012-I: XEROX 2700/3700/4045 SELECTED.>FDB: FONT Titan10-PFDB050044-I: XEROX 2700/3700/4045 FONT ’Titan10-P’ SELECTED.>FDB: RENM Saturn-PFDB050077-I: XEROX 2700/3700/4045 FONT RENAMED TO ’Saturn-P’. >



SAMP - Create Font Sample Display (Decentralized LPS)The SAMP command generates a file of downloaded fonts and commands that display a font sample when processed by an output device. The font sample displays every character in a font on a numbered grid. The output produced by the SAMP command is written to the font Job Command file. Currently, font sample files can be generated for the Xerox Decentralized laser printers.

To generate a sample font file, first select the output device with the MACH command. One or more SAMP commands can be issued to write the samples to the font Job Command file. After exiting from the FDB utility, the font sample can be printed by transmitting the Font Job file to the output device.

Syntax SAMP p1,p2,p3,p4,p5,p6,p7

Parameters

p1

Name of the font to be sampled.

Default: Required

p2

Precede font sample with a font data sheet. The font data sheet is identical to that displayed by the INFO command except that it is written to the sample font file instead of the Log file.

0 — Generate the font sample only.

1 — Generate a font data sheet followed by the font sample.

Default: 0



p3

Character code format for writing the sample font file.

0 — Write sample file commands, font data sheet text, and font encoding in host native code.

1 — Write sample file commands, font data sheet text, and font encoding in ASCII.

2 — Write sample file commands and font data sheet text in host native code and font encoding in ASCII.

3 — Write sample file commands, font data sheet text, and font encoding in EBCDIC.

Default: 0

p4

Single text character for the escape character in the sample job file. The escape character is generally used to distinguish printer commands from font information in the file; it is not translated upon output regardless of the value of p3.




Default: X´1B´ on ASCII hosts and X´27´ on EBCDIC hosts.

p5

Single character for filler when padding output records to constant length. The character chosen must be one that is completely ignored by the printer when received; it is not translated upon output regardless of the value of p3.




Default: X´08´ on ASCII hosts and X´16´ on EBCDIC hosts.



p6

String of 1 – 10 characters to be used as a record line-ending sequence. These characters are not translated on output regardless of the value of p3.




Default: X'0D0A' on ASCII hosts and X'0D25' on EBCDIC hosts. Both of these values correspond to a carriage return/linefeed sequence.

p7

PCC byte.

0 — Output no PCC byte.

1 — Use a plus sign (+) as a PCC byte. A plus sign causes the printer to overprint the line.

2 — Use a space character ( ) as a PCC byte. A space character causes the printer to skip a line and print.

Default: 0.

Note: The following notes apply to the SAMP command:

• The font being sampled must reside in the font database file. Font samples cannot be generated for fonts located in the scratch file.

• The content of the scratch file and the list of specified font names by the FONT command are cleared before processing SAMP.

• Several SAMP commands can be processed in one invocation of the FDB utility. The resulting font samples are concatenated in the font Job Command file, which prints each sample sequentially.

• On most host computers, the default values are appropriate. Computer configurations consisting of equipment that employs special communications controllers or non-standard protocols may require



parameter values other than the defaults. Due to the wide variety of configurations possible, specific parameter values cannot be suggested here.

• SAMP temporarily constructs, downloads, and deletes three special fonts for each font sampled. This is necessary to correctly display the characters in every cell of the specified font on the wide variety of host computers supported by the font database. The three temporary fonts are given names that are created by inserting a prefix of “a”, “b”, and “c” before the specified font name. For example, if the font Titan10-P is sampled, the three temporary fonts would be named aTitan10-P, bTitan10-P, and cTitan10-P. During the generation of the font sample, these names are displayed in the log file when the fonts are written to the font Job Command file.

• On the Xerox 2700 and 4045 printers, the three temporary fonts are downloaded, used, and then deleted from the printer font memory. On the Xerox 3700 and 4235, however, the temporary fonts are stored on the printer’s internal disk and must be deleted at the printer’s keyboard and display screen. If many font samples are generated, periodically delete these temporary fonts from the Xerox 3700 or 4235 disk or it eventually fills and disrupts printing operations.

• Depending upon your host computer’s load, the SAMP command can take up to several minutes to process.

PCC ByteIf p7 = 1 or 2:

• The PCC byte is always the first byte in each record, and only the ANSI carriage control is used.

• The records are fixed-length 81-byte records for downloading a font job.

The records are variable-length records for a font sample.

This feature is most useful when a spooler, such as IBM VM RSCS, assumes that a file to be transmitted has a PCC/VFU byte in the first character position in each record, which the spooler discards. With this feature, a PCC/VFU byte can be added for the spooler to discard before transmission of the fonts and text to the printer.



ExampleCreate a Xerox Decentralized font data sheet and font sample sheet for two fonts stored in a font database.

>FDB: MACH 8FDB050012-I: XEROX 2700/3700/4045 SELECTED.>FDB: SAMP Titan10-P,1

FONT NAME CHARS BYTES

a Titan10-P 113 9,836b Titan10-P 110 3,002c Titan10-P 33 332

3 FONTS 256 13,170>FDB: SAMP XCP 14 - P,1FONT NAME CHARS BYTES a XCP14-P 113 5,354b XCP14-P 110 1,966 c XCP14-P 33 332 3 FONTS 256 7,652 >



SAVE - Save Temporary FontThe SAVE command copies the fonts in the scratch file to the font database. Fonts that have been edited and/or renamed are stored in the scratch file. If you want to retain the modified font in the font database, you must explicitly save it by writing it back into the font database. Because the saving of fonts requires a modification to the font database, the INIT or UPDT command must be specified or SAVE is ignored.

Syntax SAVE p1

Parameters

p1

Replace existing fonts in the font database with fonts of the same name from the scratch file.

0 — Do not replace existing fonts.

1 — Replace existing fonts.

Default: 0

Note: The following notes apply to the SAVE command:

• The scratch file holds a maximum of 40 fonts. This means that no more than 40 fonts can be edited and/or renamed before doing a SAVE.

• The content of the scratch file and the list of specified fonts using the FONT command are cleared following processing of the SAVE command.

• Issuing a MACH command clears the font database of fonts previously specified by FONT commands, and clears the content of the Scratch file. Any fonts that were edited or renamed must be saved before specifying MACH if they are to remain in the font database.



ExampleThe following example illustrates use of the SAVE command to store a number of edited fonts into the permanent font database.

FDB050345-I: ENGLISH LANGUAGE MESSAGES SELECTED.>FDB: UPDT 2500FDB050006-I: FONT DATA BASE OPENED FOR UPDATE.>FDB: MACH 8FDB050012-I: XEROX 2700/3700/4045 SELECTED.>FDB: FONT Titan10-PFDB050044-I: XEROX 2700/3700/4045 FONT ’Titan10-P’ SELECTED.>FDB: RENM MercuryFDB050077-I: XEROX 2700/3700/4045 FONT RENAMED TO ’Mercury’.>FDB: FONT LetterGothic12-PFDB050044-I: XEROX 2700/3700/4045 FONT ’LetterGothic12-P’ SELECTED.>FDB: RENM VenusFDB050077-I: XEROX 2700/3700/4045 FONT RENAMED TO ’Venus’.>FDB: EDIT 8, 61-7AFDB050034-I: XEROX 2700/3700/4045 FONT ’Venus’ EDITED.>FDB: FONT Kosmos10-PFDB050044-I: XEROX 2700/3700/4045 FONT ’Kosmos10-P’ SELECTED.>FDB: EDIT 4FDB050034-I: XEROX 2700/3700/4045 FONT ’Kosmos10-P’ EDITED.>



FDB: SAVE 1FDB050060-I: DUPLICATE FONTS WILL BE REPLACED.FDB050155-I: XEROX 2700/3700/4045 FONT ’Mercury’ SAVED.FDB050155-I: XEROX 2700/3700/4045 FONT ’Venus’ SAVED.FDB050153-I: XEROX 2700/3700/4045 FONT ’Kosmos10-P’ IS BEING REPLACED.FDB050155-I: XEROX 2700/3700/4045 FONT ’Kosmos10-P’ SAVED.>



UPDT - Update Font DatabaseThe UPDT command defines the FDB update mode to modify an existing font database by adding, changing, or deleting fonts. UPDT must be the first FDB command in the Font Job Command file to specify update mode.

Syntax UPDT p1

Parameters

p1

Number of blocks to which the new font database can be expanded (range 100 – 32000). The value specified can be larger or smaller than the number of blocks in the old font database, but must be at least large enough to contain all the fonts from the old font database. For systems that require preliminary file space allocation, the size on the UPDT command must correspond to the size allocated in the Job Command file for the new font database.

Default: Required

Note: The following notes apply to the UPDT command:

• Guidelines for determining appropriate values for the size parameter can be found in the disk requirements section of this chapter.

• Update mode operates by initializing a new font database, copying the entire content of the old font database file to it, and allowing modifications to be made to the new file. The purpose of the copy operation is to provide a backup database (the old font database) in case of system failure. Although not recommended, an existing font database can be placed directly in update mode without performing the copy operation. This in-place update is the faster method because the copy operation is not performed; however, it exposes the database to unrecoverable corruption. If your system has limited disk space, you may have to use in-place update.



• To use the in-place update mode (without the copy operation), specify a size of -666.

• To convert a font database from 16- to 32-bit, specify UPDT 32000, If the input font database is a 16-bit font database, this command causes the 6.4 version of the FDB utility to convert it to a 32-bit font database. This command is not printer-dependent; it converts all types of font data bases.

The following examples show how to use the UPDT command to update a font database.

Examples The first example illustrates use of the UPDT command to establish update access to a font database. The data base is allowed to expand to 2,500 blocks.

FDB050345-I: ENGLISH LANGUAGE MESSAGES SELECTED.>FDB: UPDT 2500FDB050006-I: FONT DATA BASE OPENED FOR UPDATE.

The following example shows how the UPDT command can establish in-place update access to a font database.

FDB050345-I: ENGLISH LANGUAGE MESSAGES SELECTED.>FDB: UPDT -666FDB050008-I: FONT DATA BASE OPENED FOR IN-PLACE UPDATE.FDB050009-I: ERRORS COULD PERMANENTLY DESTROY YOUR FILE.FDB050010-I: PROCEED WITH CAUTION!>



WIDS - Create Configuration/Widths FileThe WIDS command creates a Configuration/Widths file from information in the Configuration text file, the old Configuration/Widths file, and the font database. A Configuration text file is always required and the old Configuration/Widths file is optional. If present, the old Configuration/Widths file is copied to the new Configuration/Widths file and updated to reflect the information in the Configuration text file and the font database.

Regardless of which input files are available, the WIDS command always creates a random access Configuration/Widths file.

Syntax WIDS p1,p2,p3,p4

Parameters

p1

Type of Configuration/Widths file to create.

0 — Create a Configuration/Widths file usable by both CompuSet and HFDL.

1 — Create a Configuration/Widths file for HFDL only.

Default: 0

p2

How to handle the Configuration text file.

-1 — Read and edit the Configuration text file for syntax errors, but do not generate a Configuration/Widths file.

0 — Do no process a Configuration text file.

1 — Read and process a Configuration text file during Configuration/Wiedths file generation. Required when

p1 = 0.

Default: 0 for p1 = 1. When p1 = 0, specify 1 or -1.



p3

Font information source.

0 — Take as much font information as possible from the old Configuration/Widths file. Information is to be taken

from the font database only if a font is not present in the old Configuration/Widths file.

1 — Take as much font information as possible from the font database. Information is to be taken from the old

Configuration/Widths file only if a font is not present in the font database.

Default: 0

p4

True Type rounding dpi value.

0 — Accept 600 dpi True Type rounding.

600 — True Type rounding to 600 dpi.

800 — Omit True Type rounding and use 300 dpi.

n — Customized True Type rounding value.

Default: 0

Note: The following notes apply to the WIDS command:

• The font metrics for every font named in the Configuration text file must be present in the old Configuration/Widths file or the font database for the Configuration/Widths file generation to be effective.

• Specifying the font information source (p3 = 0) will significantly speed the creation of the Configuration/Widths file by eliminating many unnecessary accesses to font database. If any existing fonts in the font database have been updated with newer fonts of the same name, a value of 1 must be specified for p3.



• When using a Configuration/Widths file that is created with the FDB utility with CompuSet, if the Configuration text file is edited for any reason, a new Configuration/Widths file must be generated by the FDB utility using the WIDS command. This must be done even where system font information is not modified—such as changing graphic memory size or changing a user font number. Failure to generate a new Configuration/Widths file requires CompuSet to use obsolete configuration information because it gets its configuration data from the Configuration/Widths file.

• CompuSet programs require that a Configuration text file be specified, although configuration information is contained in the Configuration/Widths file. You can substitute a dummy Configuration file as long as a valid Configuration/Widths file is also specified. If you specify an actual Configuration file in the Job Command files instead of a dummy Configuration file, these Configuration file commands override the same commands in the Configuration/Widths file.

PCL PrintingThe p4 parameter enables you to specify a dpi value to be used when True Type font widths are rounded internally. This value does not necessarily coincide with the dpi rating of the target printer. The FDB utility uses the p4 parameter only when you also specify MACH 15 to identify a PCL printer.

You can ignore the p4 parameter, or specify a zero value, if you are using Intellifonts with the PCL output formatter or a different output formatter.

Choose the following values, depending on your printer:

The effect of specifying 300 or 600 dpi may be subtle unless you are printing a special effect, like dot leadering. You may need to experiment with the p4 value to produce satisfactory output.

p4 Value Printer Model

p4 = 600 HP LaserJet 4

p4 = 300 HP LaserJet 5


346

Appendix BWDPORT Commands

File Export/Import Program (WDPORT) is a utility program that runs on all CompuSet-supported platforms. It enables CompuSet Configuration/Widths files to be transferred from one host to another. To transfer Configuration/Widths files successfully, WDPORT and CompuSet must be running on both the source and destination machines.

WDPORT executes on the source host to export a CompuSet Configuration/Widths file to an output file. WDPORT executes on the destination host to import the new file and convert it into a Configuration/Widths file that is compatible with CompuSet on that host.

WDPORT exports and imports Widths files, but it does not copy or transfer a file from one host to another. The files are transferred by storing them on offline media (disk or tape), or by using a File Transfer Protocol (FTP) process.


Appendix B - WDPORT Commands347

Command FormatWDPORT commands have this format:

command p1,p2,p3,...pn

where command is the four-character command name, and p1 – pn are the parameter values. The command format requirements are:






• WDPORT commands can be specified in any order.



CCOD - Override Condition CodeThe CCOD command overrides preset condition codes and resets the condition code that is produced when an error is encountered during execution on a message-by-message basis. CCOD can appear in the Job Command file.


Parameters

p1


-4 — Only fatal errors are reported.



-1 — No warnings, errors, or fatal errors.

0 — Use program default severity levels.


Default: 0

p2 – pn

Message numbers to be assigned the severity level specified by parameter p1 > 0 (numbers, separated by commas, must fit into a record with a maximum length of 72 characters).



• If p1 is less than or equal to zero, no other parameters are required.



• If p1 is less than zero, messages can be logged with different severity levels, but none higher than the maximum specified by p1.

• If p1 is less than one, then the p1 value applies to all messages; parameters p2 – pn are ignored.

• If p1 > 0, multiple CCOD commands can be entered to list all the message numbers whose severity is to be changed; however, only the first 1000 message numbers specified are actually used during execution.

Condition Code ValuesFor the following operating systems, CompuSet generates non-zero condition codes when a serious error, such as an attempt to merge a non-existent document or image from a Merge library, is detected.

The operating systems are:

• IBM z/OS





• 0 = No errors

• 4 = Warning

• 8 = Error





• 0 = No errors

• 1 = Warning

• 2 = Error

• 3 = Fatal error



CONF - Output a Configuration FileThe CONF command creates a Configuration file from the Configuration data in the Configuration/Widths file that is being imported. The output Configuration file is a text file that may be printed or edited. CONF can appear in the Job Command file.

Syntax CONF p1

Parameters

p1

Configuration file creation flag.

0 — No output Configuration file is requested.

1 — Create a Configuration file with comment lines.

2 — Create a Configuration file without comment lines. This is not recommended and intended only for

debugging.

Default: 0

Note: The CONF command is ignored when WDPORT produces a Configuration/Widths file to be exported to another host. The CONF command executes only when WDPORT imports a Configuration/Widths file. This command is similar to the CONF command in the FDB utility program.



LANG - Language SelectionThe LANG command specifies the language for messages in the execution log files and the format for printing the system time and date. LANG can appear in the Job Command file.

Syntax LANG p1,p2

Parameters

p1

Select language.

0 — Site-specified default.

1 — English

2 — French

3 — German

4 — Spanish

5 — Italian

6 — Dutch

7 — Swedish

8 — Norwegian

9 — Danish

10 — Portuguese

11 — Finnish

Default: 0



p2

Log file time and date format.

0 — MM/DD/YY for date and HH:MM:SS for time


2 — DD/MM/YY for date and HH:MM:SS for time

3 — DD.MM.YY for date and HH.MM.SS for time

4 — DD-MM-YY for date and HH:MM:SS for time

5 — DD.MM.YY for date and HH:MM:SS for time


7 — YY-MM-DD for date and HH:MM:SS for time





Default: 0


• If LANG is omitted, the default language defined in the message database at installation time is used.

• LANG specifies the language in which messages are written; it does not provide the text of those messages. The message text is contained in the message database.

• For U.S. customers, message text in the message database is delivered in the English language only. In other countries, languages available for message text may vary.



ExampleThe arrangement of values in p1 and p2 is designed to match languages to the time and date formats common in that language. This command provides the date and time in a format commonly used in Spanish-speaking countries:

LANG 4,4

However, any value of p1 can be paired with any value of p2 at your discretion.



WCVT - Export or Import a Configuration/Widths FileThe WCVT command specifies whether to export or import a Configuration/Widths file, and specifies the format of the input or output file. WCVT can appear in the Job Command file.

Syntax WCVT p1,p2,p3,p4,p5,p6,p7

Parameters

p1

Widths file export or import flag.

0 — Write a portable Configuration/Widths file to disk.

1 — Write a portable Configuration/Widths file to tape in IBM variable blocked tape format.

2 — Write a portable Configuration/Widths file to punch in IBM punch format.

3 — Read a portable Configuration/Widths file from disk and convert it to a host system Configuration/Widths

file.

4 — Read a portable Configuration/Widths file from tape and convert it to a host system Configuration/Widths

file.

Default: 0



p2

Maximum number of bytes per input or output tape block. This value should be a multiple of 128 bytes and less than or equal to 1024 bytes. This parameter is used only for tape and is ignored for disk or punch.

Default: 0

p3

Maximum number of bytes in an input or output record. This value should be a multiple of 128 bytes.

Default: 0

p4

Character code used for the input or output Configuration/Widths file.

0 — Binary encoded data

1 — Binary encoded data

2 — Double byte hexadecimal encoded to ASCII

3 — Double byte hexadecimal encoded to EBCDIC

Default: 0

p5

Type of PCC (Printer Carriage Control) byte. The PCC byte, if used, is always the first byte in each record.

0 — No PCC byte

1 — Records begin with an overprint ("+")

2 — Records begin with a space

Default: 0



p6

Type of line ending sequence that is to be appended to each record by WDPORT.

0 — No line ending sequence

1 — Append a carriage return/line feed combination to each record

2 — Append a carriage return to each record

3 — Append a line feed to each record

4 — Append the hexadecimal line-ending dequence specified by p7

Default: 0

p7

User-defined line-ending sequence of up to 20 hexadecimal digits: X'xx xx xx xx xx xx xx xx xx xx'.

Default: 0s Note: The following notes apply to the WCVT command:

• If you specify p2 = 0, the default value is 1024 bytes for each tape block.

• If you specify p3 = 0, the default value is 128 bytes for each record, which is the recommended value.


358

Appendix CFont Commands

This appendix contains the complete syntax and parameter list for the font commands that you use to add fonts to your Configuration files.


Appendix C - Font Commands359

EFNT - Define Raster Font CorrelationThe EFNT command correlates CompuSet logical user fonts with physical bounded and unbounded AFP fonts. Fonts are grouped into families, each representing a single style face in multiple point sizes. The font is further grouped by point size, where each point size is available in any of four stresses.

The maximum number of distinct EFNT logical font identification numbers varies with the host computer system. The maximum is 100 for these operating systems: IBM z/OS, all supported Microsoft Windows platforms, and all supported UNIX platforms.

Syntax EFNT p1,p2,p3,p4,p5,p6,p7

Parameters

p1

User font identification number representing a font family, such as Helvetica. This identification number is the logical user font number assigned by the first parameter of the COMPUSET F command.

Default: Required.

p2

Point size of the font (must equal one of the values specified in the SIZE command). This number corresponds to the first parameter in the COMPUSET PT command.

Default: Required



p3

Machine font identification number for light Roman.

Default: 0

p4

Machine font identification number for light italic.

Default: 0

p5

Machine font identification number for bold Roman.

Default: 0

p6

Machine font identification number for bold italic.

Default: 0

p7

Character mapping identification.

0 — Use default character mapping.

n — Specify the character mapping table to be used (n is an integer from 1 to 10; see the CMAP command).

Default: 0



Note: The following notes apply to the AFP EFNT command:

• When a stress and slant is unavailable in a given point size, more than one EFNT parameter can reference the same MFNT number. For example:

EFNT 1, 11, 3, 3, 5, 5, 0, 11 POINT PRESS ROMAN

• The point size specified in the EFNT command must match that specified in the corresponding MFNT command. Failure to observe this constraint causes character widths to be computed incorrectly. The FDB utility issues a warning message if it detects such a mismatch.

• EFNT commands for bounded and unbounded fonts and FONT commands for outline fonts are mutually exclusive. Do not specify the same machine font identification number in an EFNT and a FONT command. You can mix EFNT and FONT commands within the same font family as long as each has unique machine font identification numbers.



FNSZ - Font Number, Size and OrientationThe FNSZ command describes font characteristics. It is required for Widths file creation when you use unbounded-box fonts.

Syntax FNSZ p1,p2,p3,p4,p5

Parameters

p1

Machine font identification number.

Default: Required

p2

Coded font name of the portrait font.

Default: Required

p3

Coded font name of the landscape font.

Default: Required

p4

Coded font name of the inverse portrait font.

Default: Required



p5

Coded font name of the inverse landscape font.

Default: Required

Note: The following notes apply to the AFP FNSZ command

• The font names must be from three to eight characters in length. If no machine font name exists for an orientation, leave the corresponding name blank.

• You must supply the correct font name for each FNSZ command.



MFNT - Machine Font DefinitionThe MFNT command identifies a physical machine font and specifies its name, size, and system parameters.

Syntax MFNT p1,p2,p3,p4,p5,p6

Parameters

p1

Physical machine font identification number that is referenced by EFNT commands. Each MFNT command must have a unique machine font number.

Default: Required

p2

Coded font name (up to eight characters).

Default: Optional

p3

Code page name (up to eight characters).

Default: Optional if coded font name is given. Otherwise, required.

p4

Character set name (up to eight characters).

Default: Optional if coded font name is given. Otherwise, required.



p5

Point size (integer).

Default: Required

p6

Font type.

0 — Bounded singly-byte font.

1 — Unbounded single-byte font.

2 — Outline single-byte font.

Default: 0

Note: The following notes apply to the AFP MFNT command:

• If the coded font name is given, the code page and character set names are optional. If the coded font name is not specified, both the code page and character set names are required. If the coded font name is specified, the code page and character set names in the MFNT statement are not used.

• The point size specified in any MFNT command must match the value specified in the corresponding EFNT command.

• The maximum number of MFNT commands permitted in a Configuration file varies with the host operating system. The maximum is 2,000 for these operating systems: IBM z/OS, all supported Microsoft Windows platforms, and all supported UNIX platforms.

• Bounded and unbounded fonts are bitmap fonts. Outline fonts are scalable fonts, which means that one font can be used to print in all point sizes.

• If you specify p6 = 1 for an unbounded-box font, define a corresponding FNSZ command.

• The point size for an outline font should be zero.

• You must specify the point size in p5 as an integer value.



SIZE - Point Sizes AvailableThe SIZE command defines up to 16 fixed point sizes supported by CompuSet. These become the valid point sizes to be used as size values in both the EFNT and MFNT commands.

Syntax SIZE p1,...p16

Parameters

p1–p16

Point sizes specified in ascending order from the smallest point size to the largest.

Default: Required



EFNT - Logical User FontThe EFNT command correlates CompuSet logical user fonts with physical Xerox fonts. Fonts are grouped into families, each representing a single style face in multiple point sizes. The font is further grouped by point size, where each point size is available in any of four stresses.

The maximum number of distinct EFNT logical font identification numbers varies with the host computer system. The maximum is 100 for these operating systems: IBM z/OS, Microsoft Windows, and all supported UNIX platforms.

Syntax EFNT p1,p2,p3,p4,p5,p6,p7

Parameters

p1

User font identification number representing a font family, such as Helvetica. This identification number is the logical user font number assigned by the first parameter of the COMPUSET F command.

Default: Required

p2

Point size of the font (must equal one of the values specified in the SIZE command). This number corresponds to the first parameter in the COMPUSET PT command.

Default: Required

p3

Machine font identification number for light Roman.

Default: 0

p4

Machine font identification number for light italic.

Default: 0



p5

Machine font identification number for bold Roman.

Default: 0

p6

Machine font identification number for bold italic.

Default: 0

p7

Character mapping identification.

0 — Use default character mapping.

n — Specify the character mapping table to be used (n is an integer from 1 to 10).

Default: 0

Note: The following notes apply to the metacode EFNT command:

• When a stress and slant is unavailable in a given point size, more than one EFNT parameter can reference the same MFNT number. For example:

EFNT 1, 11, 3, 3, 5, 5, 0, 11 POINT PRESS ROMAN

• The point size specified in the EFNT command must match that specified in the corresponding MFNT command. Failure to observe this constraint causes character widths to be computed incorrectly. The FDB program issues a warning message if it detects such a mismatch.

• Logos can be used on the Xerox LPS, but are not supported by CompuSet. If the logos exist as font characters, they can be added to the Configuration/Widths files and referenced with a corresponding font call.



FNAM - Font Names for ViewingThe FNAM command defines the names of the fonts that are displayed when you select a pop-up menu of the available fonts for a particular printer.

Syntax FNAM p1,’p2’,p3

Parameters

p1

FONT identification number for the font family. This font number is used by the COMPUSET F command.

Default: Required

‘p2’

The name of the font family that is displayed in a font list pop-up menu. The name must be enclosed in single quotation marks and can be up to 20 characters long.

Default: Required

p3

Serif/sans-serif font flag.

0 — Serif font

1 — Sans-serif font

Default: 0



Note: The following notes apply to the metacode FNAM command:

• The format for the FNAM output formatter command is the same for every output formatter and every printer.

• On the pop-up menu for the font list, only p2 displays; p1 or p3 do not display.

• There should be a one-to-one correspondence between each font family in the Configuration file and each FNAM command. For each group of FONT or EFNT commands with the same first parameter, there should be one FNAM command with that same first parameter.



FNSZ - Font Number, Size and OrientationThe FNSZ command describes font characteristics. It is required for widths file creation.

Syntax FNSZ p1,p2,p3,p4,p5,p6,p7,p8,p9

Parameters

p1

Machine font identification number.

Default: Required

p2

Name of the portrait font.

Default: 0

p3

Name of the landscape font.

Default: 0

p4

Name of the inverse portrait font.

Default: 0

p5

Name of the inverse landscape font.

Default: 0



p6

Size, in kilobits, of the portrait font.

Default: 0

p7

Size, in kilobits, of the landscape font.

Default: 0

p8

Size, in kilobits, of the inverse portrait font.

Default: 0

p9

Size, in kilobits, of the inverse landscape font.

Default: 0

Note: The following notes apply to the metacode FNSZ command:

• The names must be from one to six characters in length and must not include the .FNT extension. If no machine font name exists for an orientation, leave the corresponding name blank.

• Users must supply the correct font name for each FNSZ command. The FDB program generates the correct size of each font specified in the FNSZ command.




Syntax MFNT p1,p2,p3,p4,p5,p6,p7,p8,p9,p10,p11

Parameters

p1

Physical machine font identification number that is referenced by EFNT commands. Each MFNT command must have a unique machine font number.

Default: Required

p2

Font name on the printer. All Xerox Centralized font names consist of six alphanumeric characters.

Default: Required

p3

Point size of the font (must be equal to a value specified in the SIZE command, and also must match the nominal point size in associated EFNT commands).

Default: Required

p4–p11

System parameters that adjust character baselines and horizontal positioning (calculated by the FDB when constructing the Configuration/Widths file and entered into the Configuration file).

Default: Supplied by system.



Note: The following notes apply to the metacode MFNT command:

• The maximum number of MFNT commands permitted in a Configuration file varies with the host operating system. The maximum is 2,000 for these operating systems: IBM z/OS, Microsoft Windows, and all supported UNIX platforms.

• The point size specified in any MFNT command must match the value specified in the corresponding EFNT command.



SIZE - Point Sizes AvailableThe SIZE command defines up to 16 fixed point sizes supported by CompuSet. These become the valid point sizes to be used as size values in both the EFNT and MFNT commands.

Syntax SIZE p1,...p16

Parameters

p1–p16

Point sizes specified in ascending order from the smallest point size to the largest.

Default: Required



FNAM - Font Names for ViewingThe FNAM command defines the names of the fonts that are displayed when you select a pop-up menu of the available fonts for a particular printer.

Syntax FNAM p1,‘p2’,p3

Parameters

p1


Default: Required

‘p2’

The name of the font family that is displayed to the user in a font list pop-up menu. The name must be enclosed in single quote marks and can be up to 20 characters long.

Default: Required

p3


0 — Serif font


Default: Required



Note: The following notes apply to the PCL FNAM command:

• The format for FNAM is the same for every output formatter and every printer.

• On the pop-up menu for the font list, only p2 is displayed, not p1 or p3.

• There should be a one-to-one correspondence between each font family in the Configuration file and each FNAM command. For each group of FONT commands with the same first parameter, there should be one FNAM command with that same first parameter.



FONT - Define User Font CorrelationThe FONT command defines all the physical fonts that comprise a typeface as one font to be referenced by CompuSet with a single font index number. The referenced font consists of all the physical fonts required to make up all the subsets, size ranges, and stresses (light, italic, bold, bold italic) for a single typeface.

Syntax FONT p1,p2,...p6

Parameters

p1

Font index number that is used by the COMPUSET F command to call the font.

Default: Required

p2–p5

Font numbers. Define the four possible physical fonts that can comprise a subset of a COMPUSET logical font in the following order:

p2 — MFNT font for light

p3 — MFNT font for light italic

p4 — MFNT font for bold

p5 — MFNT font for bold italic

These numbers correspond to p1 of MFNT. A value of zero indicates the physical font does not exist.

Default: 0,0,0,0

p6

Index to the character-mapping table that applies to this user font.

Default: 0



Note: The following notes apply to the PCL FONT command:

• The FONT command combined with MFNT commands correlates COMPUSET logical fonts to PCL physical fonts. A physical font number of zero specifies that the font does not exist and a COMPUSET error message is generated.

• When a stress or font size is unavailable in a given font, more than one FONT parameter can reference the same physical font.

• If p6 > 0 is specified by the first FONT command for a given font index, it indicates that the font can be subsetted. In this case, more than one FONT command can be specified for the same user font index. The first FONT command for a particular index specifies the physical fonts that comprise subset 0 of the font, the second FONT command for the same user index specifies the physical fonts in subset 1, and so on. In this circumstance, the CMAP character-mapping table indexes for the FONT command specify how the entire user font is subsetted.



MFNT - Machine FontThe MFNT command identifies a physical machine font and specifies its positioning characteristics.

Syntax MFNT p1,p2,p3,p4,p5,p6,p7,p8,p9,p10

Parameters

p1

Physical machine font identification number (referenced by FONT commands). Each MFNT command must have a unique machine font number.

Default: Required

p2

Font name (maximum 20 characters with no blanks).

Default: Required

p3

PCL symbol set identification string.

Default: Required

p4

PCL typeface number.

Default: The correct value is automatically entered in this field by FDB when you create a Configuration and/or Widths file.



p5

Pitch.

0 — Proportional font

Other — The product of the pitch and the point size


p6

Slant.

0 — Roman

1 — Italic


p7

Appearance.

0 — Normal

1 — Condensed

2 — Expanded




p8

Stroke weight.

0 — Light

1 — Bold


p9

Type of font.

0 — TrueType

1 — Intellifont


p10

Font resolution.

0 — 300 dpi


Note: The following notes apply to the PCL MFNT command:

• For purposes of standardization, use the portrait font name in the p2 parameter when a choice between portrait and landscape exists.

• The maximum number of MFNTs allowed in a Configuration file varies with the host computer system. The maximum is 2,000 for these operating systems: IBM z/OS, Microsoft Windows, and all supported UNIX platforms.



NOLD - Font Location (Resident or Downloaded)The NOLD command identifies the fonts that are resident on the printer as well as those fonts that are to be downloaded by the PCL output formatter to the printer.

Syntax NOLD p1,p2

Parameters

p1

MFNT number of downloaded font.

Default: Required

p2

Font type.

0 — Font is to be downloaded to the printer.

1 — Font is resident on the printer or it is a cartridge font.

2 — Unused.

3 — Font is not to be downloaded to the printer because it is permanently resident on the printer.

4 — Font is to be downloaded to the printer for linked output formatter processing.

Default: 0

Note: The following notes apply to the PCL NOLD command:

• Enter NOLD into the Configuration file to identify both the permanent fonts on the printer and any fonts loaded on cartridges for the printer (cartridge fonts are specified as permanent fonts).

• The p2 = 0 value indicates that soft fonts are to be downloaded to the printer by the PCL output formatter or with the FJOB FDB command.



• If you specify p2 = 1 or 2, the output formatter does not distinguish between resident or cartridge fonts.

• Specify p2 = 4 and FNLD p1 = 2 if you are using linked output formatter processing.

• PDEF commands take precedence over NOLD commands.

• If every font needed for printing a document has already been downloaded, FNLD can disable font downloading.



CHDF - Define Character LayoutThe CHDF command specifies the character types within a physical font that identify floating accents and uppercase and lowercase characters. This enables the PDF output formatter to position floating accents for uppercase and lowercase characters.

Syntax CHDF p1,p2,p3,p4

Parameters

p1

Font layout map index (1–10) where the character types specified by the p2–p4 parameters are to be stored. The p1 value must correspond to the p4 parameter of the MFNT command.

Default: Required

p2

Character type within the range specified by p3 and p4.

0 — Characters are not uppercase or floating accents.

1 — Characters are uppercase.

2 — Characters are floating accents.

Default: 0

p3

Physical font character code of the first in the range of characters defined by the character type specified by p2 (decimal value 0–255).

Default: 0



p4

Physical font character code of the last in the range of characters defined by the character type specified by p2 (decimal value 0–255, which must be equal to or greater than the value of p3).

Default: 0

Note: The following notes apply to the PDF CHDF command:

• All layout tables defined by CHDF are set up initially with all characters of type 0. CHDF statements are needed only to define type 1 and type 2 characters.

• Use multiple CHDF commands that specify the same font layout map index to construct an entire table.

• Up to 10 font layout maps can be created with CHDF commands.

• Font layout maps are identified by a numeric index. They can be associated with a particular font by specifying the index value as p4 of the MFNT command.



FNAM - Font Names for ViewingFNAM defines the names of the fonts that are displayed.

Syntax FNAM p1,’p2’,p3

Parameters

p1

FONT identification number for the font family. The font number is assigned to the COMPUSET F command.

Default: Required

‘p2’

Name of the font family that is displayed in a font list pop-up menu. The name must be enclosed in single quote marks and can be up to 20 characters long.

Default: Required

p3

Serif or sans-serif font flag.

0 — Serif font


Default: 0

Note: The following notes apply to the PDF FNAM command:





FONT - Define Font CorrelationDefines all the physical fonts that comprise a typeface as a single font to be accessed in CompuSet by a single font index number. A single font consists of all the physical fonts required to make up all the subsets, size ranges, and stresses (light, italic, bold, bold italic) for a single typeface.


Parameters

p1

Font index number used by the COMPUSET F command to call the font.

Default: Required

p2 – p5

Font numbers (define in the following order the four possible physical subsets of a COMPUSET logical font).

p2 — MFNT number for light type.

p3 — MFNT number for light italic type.

p4 — MFNT number for bold type.

p5 — MFNT number for bold italic type. These numbers correspond to p1 of MFNT. A value of zero indicates that

the physical font does not exist.

Default: 0,0,0,0

p6

Index to the character mapping table that applies to this user font.

Default: 0



Note: The following notes apply to the PDF FONT command:

• The FONT command combined with MFNT commands correlates COMPUSET logical fonts to PDF physical fonts. A physical font number of zero specifies that the font does not exist and a COMPUSET error message is generated.


• If p6 > 0 is specified by the first FONT command for a given font index, it indicates that the font can be subsetted. In this case, more than one FONT command can be specified for the same user font index. The first FONT command for a particular index specifies the physical fonts that comprise subset 0 of the user font, the second FONT command for the same user index specifies the physical fonts in subset 1, and so on. In this circumstance, the CMAP character-mapping table indexes for the FONT command specify how the entire font is subsetted.




Syntax MFNT p1,p2,p3,p4,p5,p6,p7,p8

Parameters

p1

Physical font identification number that is referenced by FONT commands. Each MFNT command must have a unique font number.

Default: Required

p2

PostScript font name. Font names can consist of as many as 64 uppercase and lowercase characters with no embedded blanks. They can contain special characters.

Default: Required

p3

Italic/roman flag.

0 — The font is italic; it may not be oblique.

1 — The font is roman; it may be oblique.

Default: 0



p4

Character layout index.

0 — No layout map applies to this font and the font contains no uppercase characters or floating accents.

n — Index number (1-10) of the font layout map constructed by CHDF.

Default: 0

p5

Vertical displacement for floating accents over uppercase characters.

Default: 0

p6

Vertical displacement for floating accents over characters other than uppercase characters.

Default: 0

p7

Encoding flag.

0 — Standard PostScript encoding.

1 — ISO Latin1 encoding.

Default: 0

p8

Font location.

0 — The font is one of the basic fonts supplied with Adobe Acrobat Reader.

1 — The font must be downloaded to the printer.

Default: 0



Note: The following notes apply to the PDF MFNT command:


• The p5 and p6 parameters are specified in 1/1000 ems and generated automatically when the FDB utility processes the AFM font metric file. A positive value moves the accent up; a negative value moves the accent down.

• Specify p8 = 0 or 1 to indicate whether the font must be embedded into the PDF output file for downloading to the printer. This ensures a faithful reproduction of the document when it is printed.



CHDF - Define Character LayoutThe CHDF command specifies the character types within a physical font to identify floating accents and uppercase and lowercase characters. This enables the PostScript output formatter to position floating accents for uppercase and lowercase characters.

Syntax CHDF p1,p2,p3,p4

Parameters

p1

Font layout map index (1–10) where the character types specified by the p2–p4 parameters are to be stored. The p1 value must correspond to the p4 parameter of the MFNT command.

Default: Required

p2

Character type within the range specified by p3 and p4.

0 — Characters are not uppercase or floating accents.

1 — Characters are uppercase.

2 — Characters are floating accents.

Default: 0

p3

Physical font character code of the first character in the range of characters defined by the character type specified in p2 (decimal value 0–255).

Default: 0



p4

Physical font character code of the last character in the range of characters defined by the character type specified in p2 (decimal value 0–255, which must be equal to or greater than the value of p3).

Default: 0

Note: The following notes apply to the PostScript CHDF command:

• All layout tables defined by CHDF are set up initially with all characters of type 0. CHDF statements are needed only to define type 1 and type 2 characters.

• Use multiple CHDF commands that specify the same font layout map index to construct an entire table.

• Up to 10 font layout maps can be created with CHDF commands.

• Font layout maps are identified by a numeric index. They can be associated with a particular font by specifying the index value as parameter p4 of the MFNT command.



FNAM - Font Names for ViewingFNAM defines the names of the fonts that are displayed when you select a pop-up menu of the available fonts for a particular printer.


Parameters

p1

FONT identification number for the font family. The font number is assigned to the COMPUSET F command.

Default: Required

‘p2’

Name of the font family that is displayed to the user in a font list pop-up menu. The name must be enclosed in single quote marks and can be up to 20 characters long.

Default: Required

p3


0 — Serif font.

1 — Sans-serif font.

Default: 0



Note: The following notes apply to the PostScript FNAM command:






FONT - Define Font CorrelationDefines all the physical fonts that comprise a typeface as one user-level font to be accessed in COMPUSET by a single user font index. A user font consists of all the physical fonts required to make up all the subsets, size ranges, and stresses (light, italic, bold, bold italic) for a single typeface.


Parameters

p1

Font index. Define the number used by the COMPUSET F command to call the font.

Default: Required

p2–p5

Font numbers (define in the following order the four possible physical fonts that can comprise a subset of a COMPUSET logical font).

p2 — MFNT font for light.

p3 — MFNT font for light italic.

p4 — MFNT font for bold.

p5 — MFNT font for bold italic.

These numbers correspond to p1 of MFNT. A value of zero indicates that the physical font does not exist.

Default: 0,0,0,0

p6

Index to the character mapping table that applies to this user font.

Default: 0



Note: The following notes apply to the PostScript FONT command:

• The FONT command combined with MFNT commands correlates COMPUSET logical fonts to PostScript physical fonts. A physical font number of zero specifies that the font does not exist and a COMPUSET error message is generated.


• If p6 > 0 is specified by the first FONT command for a given font index, it indicates that the font can be subsetted. In this case, more than one FONT command can be specified for the same user font index. The first FONT command for a particular index specifies the physical fonts that comprise subset 0 of the user font, the second FONT command for the same user index specifies the physical fonts in subset 1, and so on. In this circumstance, the CMAP character-mapping table indexes for the FONT command specify how the entire font is subsetted.




Syntax MFNT p1,p2,p3,p4,p5,p6,p7,p8

Parameters

p1

Physical machine font identification number that is referenced by FONT commands. Each MFNT command must have a unique machine font number.

Default: Required

p2

PostScript name of the font on the output device Font names can consist of as many as 64 uppercase and lowercase characters with no embedded blanks. They can contain special characters.

Default: Required

p3

Italic/roman flag.

0 — The font is italic; it may not be oblique.

1 — The font is roman; it may be oblique.

Default: 0



p4

Character layout index.

0 — No layout map applies to this font and the font contains no uppercase characters or floating accents.

n — Index number (1-10) of the font layout map constructed by CHDF.

Default: 0

p5

Vertical displacement for floating accents over uppercase characters.

Default: 0

p6

Vertical displacement for floating accents over characters other than uppercase characters.

Default: 0

p7

Encoding flag.

0 — Standard PostScript encoding

1 — ISO Latin-1 encoding.

Default: 0

p8

Font location.

0 — The font is resident on the printer.

1 — The font must be downloaded to the printer.

Default: 0



Note: The following notes apply to the PostScript MFNT command:


• The p5 and p6 parameters are specified in 1/1000 ems and generated automatically when the FDB utility processes the AFM font metric file. A positive value moves the accent up; a negative value moves the accent down.

• Specify p8 = 0 or 1 to indicate whether the font must be embedded into the PostScript output file for downloading to the printer. This ensures a faithful reproduction of the document when it is printed.


402

Appendix DINDRPR Commands

This chapter describes the how to produce indexes using the index post-processing utility, INDRPR. See the CompuSet Command Reference for descriptions of each index command.

INDRPR processes index extraction files created during execution of CompuSet. The extracted index records from a composed document are inserted in a temporary intermediate file that is incompatible with a CompuSet input text file. The tags that are added to the extracted text are described in the following section.

INDRPR reformats this file by deleting trailing unused fields (any key or label fields higher than the highest used field) and by arranging standard tags.


Appendix D - INDRPR Commands403

Format of Index RecordsAfter INDRPR processing, an index file has this format:

<50>primary key<50A><51>secondary key<51A><52>label "1"<52A><56>label "2"<56A><53>page number<53A>

If a series of records with identical primary keys and different secondary keys is produced, the subsequent records in the series are output to be the processed file in this format:


If a series of records with identical primary and secondary keys is produced, subsequent records in the series are output in this format:




If a series of records with identical primary keys, secondary keys, and label 1, but a different label 2 is produced, subsequent records in the series are output in this format:


If a series of records with an identical primary key, secondary key, and label 1 is produced, subsequent records in the series are output in this format:

<70>primary key<70A><71>secondary key<71A><72>label "1"<72A><63>page number<63A>

The second and subsequent records of a series of duplicate records are output in the form:


Duplicate keys and records can be deleted by defining <70=SK>, <71=SK>, and so on. Differing secondary keys belonging to the same primary key can be grouped by definition of <61> as a tag. Similarly, other groupings can be achieved by definition of <62>, <63>, and so on.



Index Tags for Duplicate RecordsThe following list shows how the system changes standard tags on second and subsequent (2+) records:

<50>Key 1 modifies to <70> on a duplicate<51>Key 2 modifies on 2+ record to <61> and <71> on duplicate<5U>Key 3 modifies on 2+ record to <6U> and <7U> on duplicate<5V>Key 4 modifies on 2+ record to <6V> and <7V> on duplicate<5W>Key 5 modifies on 2+ record to <6W> and <7W> on duplicate<5X>Key 6 modifies on 2+ record to <6X> and <7X> on duplicate<5K>Key 7 modifies on 2+ record to <6K> and <7K> on duplicate<5L>Key 8 modifies on 2+ record to <6L> and <7L> on duplicate<5M>Key 9 modifies on 2+ record to <6M> and <7M> on duplicate<5N>Key 10 modifies on 2+ record to <6N> and <7N> on duplicate<52>Label 1 modifies on 2+ record to <62> and <72> on duplicate<56>Label 2 modifies on 2+ record to <66> and <76> on duplicate<5Y>Label 3 modifies on 2+ record to <6Y> and <7Y> on duplicate<5Z>Label 4 modifies on 2+ record to <6Z> and <7Z> on duplicate<5O>Label 5 modifies on 2+ record to <6O> and <7O> on duplicate<5P>Label 6 modifies on 2+ record to <6P> and <7P> on duplicate<5Q>Label 7 modifies on 2+ record to <6Q> and <7Q> on duplicate<5R>Label 8 modifies on 2+ record to <6R> and <7R> on duplicate<5S>Label 9 modifies on 2+ record to <6S> and <7S> on duplicate<53>Page Number modifies on 2+ record to <63> and <73> on duplicate

When a change in the first character of the primary key is detected, a record of the form <54> character <55> is output preceding the first record containing that change. This provides an optional method of separating or labeling the output where a change in the first character occurs.



INDRPR also appends an extra tag to the end of every index item as shown by the <50A>, <51A>, and <53A>. This can be used for setting rules or for formatting the index pages.

<50>String One<50A><51>String Two<51A><53>Page Number<53A>

File and Path NamesWhen you are working on a host with a UNIX or Windows operating system, INDRPR Job Command file paths can be specified with environment variables, or these paths can be specified explicitly. CompuSet supports path names up to 320 bytes if you choose to define them explicitly.

INDRPR Sample JobThe example below shows how to run an INDRPR job.

@echo offremrem Batch file to run INDRPR (Index Post-processor). Syntax is:remrem indrpr filenameremrem where 'filename' is the name of a raw index file (without extension)rem generated from a composition run.remif "%1" == "" goto errorremecho Running INDRPR - Run log saved to .\log\indrpr.log . . .echo %CSET%\system\%OSYS%\indrprx > .\log\indrpr.log



echo * >%TEMP%\indr.tmpecho * FILE DEFINITIONS FOR INDRPR >>%TEMP%\indr.tmpecho * >>%TEMP%\indr.tmpecho FILE 1, .\index\%1.inx,index file generated from CompuSet >>%TEMP%\indr.tmpecho FILE 2, %1.txt ,processed index file >>%TEMP%\indr.tmpecho FILE 25, %CSET%\system\%WRDTYP%\xicsmsg.mdb ,CompuSet mdb >>%TEMP%\indr.tmpecho // END OF FILE DEFINITIONS >>%TEMP%\indr.tmpecho * >>%TEMP%\indr.tmpecho * OPTIONS FOR INDRPR >>%TEMP%\indr.tmpecho * >>%TEMP%\indr.tmpecho *(NOTE THAT IF USING VERSION 6.1.01 OR LATER, INDRPR WILL >>%TEMP%\indr.tmpecho * AUTOMATICALLY DETECT THE FORMAT OF A CSET-GENERATED INDEX >>%TEMP%\indr.tmpecho * FILE; THEREFORE, NO DIRECTIVES ARE REQUIRED.) >>%TEMP%\indr.tmpecho * >>%TEMP%\indr.tmpecho // END OF OPTIONS >>%TEMP%\indr.tmp

rem -- run WIN32 version if OSYS is NOT set...

if "%OSYS%"=="" goto WIN32if "%OSYS%"=="WIN32" goto WIN32

:WIN32%CSET%\system\%OSYS%\indrprx < %TEMP%\indr.tmp > .\log\indrpr.loggoto cleanup

:cleanupdel %TEMP%\indr.tmp > nulgoto end

:errorecho Please re-run batch file with proper parameter(s) specified.goto end

:endecho Done



Command FormatINDRPR commands have this format:

command p1,p2,p3,. . . pn

where command is the four-character command name, and p1 – pn are the parameter values. The command format requirements are:






• INDRPR commands can be specified in any order.

Caution: Do not attempt to bypass the INDRPR utility and run an index file that has not been post-processed. You will not get correct output. All index files must be processed through the INDRPR utility.

Note: The following notes apply to INDRPR commands:

• All INDRPR commands are specified in the Job Command file. A default Job Command file to execute INDRPR at your site is supplied with the full CompuSet installation. The only required INDRPR command is the FLDS command.

• To execute INDRPR, make the file assignments required by the Job Command file, define the FLDS command, and execute the program.



• INDRPR verifies that the format descriptions in the IOPT, FLDS, and IFMT commands match the structure of the index file. If not, the index file is not processed and the discrepancy is reported in the batch job log.

• INDRPR processes only one index at a time. If multiple indexes have been produced by COMPUSET, multiple INDRPR runs are necessary, one for each index file. Change file assignments for each run.



CCOD - Override Condition CodeThe CCOD command enables you to override pre-set condition codes. It resets the condition code produced when an error is encountered during execution on a message-by-message basis.

On IBM z/OS, UNIX and Windows hosts, non-zero condition codes are generated when a serious error, such as a missing input file, is detected. These condition codes can be monitored by the Job Command files that execute COMPUSET.

Each CompuSet log message is assigned a specific level of error detection. On IBM z/OS systems, information, warning, error and fatal error messages produce condition codes of 0, 4, 8, and 12, respectively. CCOD appears in the Job Command file.


Parameters

p1

Maximum severity level:

-4 — Only fatal errors are reported.






Default: 0.

p2 – pn

Message numbers to be assigned the severity level specified by parameter p1 > 0 (numbers, separated by commas, must fit into a record of 72 characters or less).




• Message numbers can be any valid COMPUSET message from 1001 to 99999. Non-existent message numbers are not flagged as errors, but are simply ignored.

• If p1 is less than one, the p1 value applies to all messages and parameters p2 and greater are ignored.

• If p1 is less than or equal to zero, then no other parameters are required.


• If p1 > 0, multiple CCOD commands can be entered to list all the message numbers whose severity is to be changed; but only the first 1000 message numbers specified are actually used during execution.

Condition Code ValuesFor the following operating systems, CompuSet generates non-zero condition codes when a serious error, such as an attempt to merge a non-existent document or image from a Merge library, is detected. The operating systems are:

• IBM z/OS• All supported UNIX platforms• All supported Windows platforms



• 0 = No errors

• 4 = Warning



• 8 = Error



• 0 = No errors

• 1 = Warning

• 2 = Error

• 3 = Fatal error



FLDS - Key and Label FieldsThe FLDS command specifies the number of key/label fields in the index record (up to 10 total). FLDS must be specified in the Job Command file.

Syntax FLDS p1,p2

Parameters

p1

Number of key fields (maximum of 10). A zero (0) or negative number is treated as 1.

Default: 6.

p2

Number of labels (0 – 9).

Default: 4.

Caution: The number of key fields and the number of labels cannot total more than 10. If more than 10 are specified, INDRPR reduces the number to 10.

Note: The following notes apply to the FLDS command:

• Key fields and label fields are required by INDRPR to generate the output records.

• If sorting is required, key/label fields are helpful in determining the parameters for the sort program. Sorting is necessary for producing an alphabetical index such as a word index at the end of a document. compuset has no index sorting utility. Sorting must be accomplished through the host computer sort utility.



IFMT - Field SizeThe IFMT command describes the size of the page number, key, and label fields in an index record. IFMT appears in the Job Command file; however, it is invoked only if p1 = 2 on the IOPT command. Otherwise, IFMT is ignored.

Syntax IFMT p1,p2,...pn

Parameters

p1

Number of composite page number subfields present in the page number field of the index record. The value of p1 must equal the value of p2 of the COMPUSET IFMT command in the input file.

Default: 1.

p2

Length (in characters) of the first extraction key/label field in the index record. COMPUSET automatically generates the field’s leading tag; the p2 parameters must include four character spaces for that tags.

The value of p2 must equal the value of p3 on the COMPUSET IFMT command in the input file.

Default: 64.

p3–pn

Length (in characters) of the last extraction key/label field in the index record. COMPUSET automatically generates the field’s leading tag; pn must include four character spaces for that tags.

The value of pn must equal the value of the comparable pn of the COMPUSET IFMT command in the input file.

Default: 64.



Note: The number of possible key/label fields in a record is equal to the sum of p4 and p5 of the COMPUSET IN command for that index file in the CompuSet input file. A maximum of 10 key/label fields can be defined.



IOPT - Index File FormatThe IOPT command specifies:

• Whether the index file to be processed was formatted prior to version 5.3.1 or not.

• What to do with key and label fields that are completely blank.

IOPT appears only in the Job Command file.

Syntax IOPT p1,p2

Parameters

p1

Version of the index file to be processed:

1 — Pre-v5.3.1 index file format

2 — Current index file format

Default: 2.

p2

Disposition of completely blank fields in index records:

0 — Discard any trailing empty fields (pre-v5.3.1 method)

1 — Discard all empty fields

2 — Retain all empty fields

Default: 0.

Note: If p2 = 2, it invokes the IFMT command.



ExampleIn this example, the index record contains the following:

If p2 = 0, the following output is generated.

<54><55><50><50A><51>key field 2 text<51A><52><52A><56>label field 2 text<56A><53>page number<53A>


<54><55><51>key field 2 text<51A><56>label field 2 text<56A><53>page number<53A>

Key field 1 blanks

Key field 2 text for key field 2

Key field 3 blanks

Label field 1 blanks

Label field 2 text for label field 2

Label field 3 blanks




<54><55><50><50A><51>key field 2 text<51A><5U><5UA><52><52A><56>label field 2 text<56A><5Y><5YA><53>page number<53A>



LANG - Language SelectionThe LANG command specifies the language for messages in the log file, and the format for printing the system time and date. LANG appears only in the Job Command file.

Syntax LANG p1,p2

Parameters

p1

Select language:

0 — Site-specified default

1 — English

2 — French

3 — German

4 — Spanish

5 — Italian

6 — Dutch

7 — Swedish

8 — Norwegian

9 — Danish

10 — Portuguese

11 — Finnish

Default: 0.



p2

Log file time and date format:

0 — MM/DD/YY for date, HH:MM:SS for time

1 — MM/DD/YY for date, HH:MM:SS for time

2 — DD/MM/YY for date, HH:MM:SS for time

3 — DD.MM.YY for date, HH.MM.SS for time

4 — DD-MM-YY for date, HH:MM:SS for time

5 — DD.MM.YY for date, HH:MM:SS for time


7 — YY-MM-DD for date, HH:MM:SS for time





Default: 0.


• If the LANG command is omitted, the default language defined for the Message Data Base installation is used.

• The LANG command specifies the language for messages; it does not provide the text of those messages. Message text is contained in the message database. For U.S. customers, message text in the message database is delivered in the English language only. In other countries, languages available for message text may vary.

• The arrangement of values in p1 and p2 is designed to match languages to the time and date formats common in that language. For example, LANG 4,4 provides the date and time in a format commonly used in Spanish-speaking countries.

• Any value of p1 can be paired with any value of p2.



LINK - Generate COMPUSET LINK CommandsThe INDRPR LINK command causes a COMPUSET LINK command to be generated as needed when INDRPR processes each index record. The identifier on the generated COMPUSET LINK command matches the identifier specified by name on the COMPUSET DESTIX command.

Syntax LINK p1,p2

Parameters

p1

Defines a prefix to be added to the COMPUSET LINK identifiers. If the prefix contains embedded blanks, it should be enclosed in single or double quotation marks.

Default: No prefix generated.

p2

Specifies when to output COMPUSET LINK commands.

0 — Output COMPUSET LINK commands only when the page number changes from one index record to the

next.

1 — Output COMPUSET LINK commands before each index record.

Default: 0.

Note: The following notes apply to the LINK command:

• The link identifier is an eight-digit decimal number representing the physical page number where the index item appears. For the INDRPR LINK command to work, the index file must be generated with a physical page number. For more information, see the COMPUSET IN command.

• If an INDRPR LINK command is issued and the index file to be processed does not contain physical page numbers, an error message appears and no COMPUSET LINK command is inserted in the output.



• The COMPUSET LINK commands inserted in the index output precede the index records to which they apply. By including COMPUSET HBOX commands in the standard index tags, any part of the index record may be defined as a hyperlink source to the destination defined by the LINK command.

ExampleIf the COMPUSET output contains link identifiers generated by the following COMPUSET command:

<DESTIX>my dest

The INDPR LINK command should be:

LINK my dest

The COMPUSET identifiers and the INDPR links generated by these commands look like this:

my dest00000001my dest00000002my destnnnnnnnnn



OFMT - Variable- or Fixed-Length RecordsThe OFMT command specifies that INDRPR is to output fixed-length records for host systems with text editors that require them. OFMT appears only in the Job Command file.

Syntax OFMT p1

Parameters

p1

Length of the output text record created by INDRPR.

0 — Variable length records.

n — Length (in bytes) of the fixed-length text records.

Default: 0.

ExampleIf the output record length is less than n, the record is padded with spaces to equal the value of n. If the output record length is greater than n, the record is split into two or more records, with each padded to equal the value of n.


424

Appendix EPCL Output Formatter Commands

This appendix contains information on the general format of PCL output formatter commands, as well as the syntax and parameters that make up each command.


Appendix E - PCL Output Formatter Commands425

Command FormatPCL output formatter commands have this format:

command p1,p2,p3,. . . pn,

where command is the four-character command name, and p1–pn are the parameter values. Configuration, PDEF and Job Command files require the same command format:





• If you omit a parameter to accept the default value, there must be a placeholder comma for each of these default values. Otherwise, comments may be interpreted as parameter values.


• PCL output formatter commands can be specified in any order.



AMAC - Page OffsetThe AMAC command provides flexibility in positioning output pages anywhere on the physical sheet of paper. All offsets are measured in points. AMAC appears in the PDEF or Job Command file.

Syntax AMAC p1,p2,p3,p4,p5

Parameters

p1

Offset flag.

0 — Center page.

1 — Offset according to p2 and p3.

Default: 0

p2

x offset (in points) from the left edge of logical page to the left edge of physical page when you view the page in portrait orientation. A positive x value offsets the page to the right; a negative x value offsets the page to the left.

Default: 0

p3

y offset (in points) from the bottom of the logical page to the bottom of the physical page when you view the page in portrait orientation. A positive y value moves the logical page up; a negative y value moves the logical page down.

Default: 0



p4

Offsets applied.

0 — Both x and y.

1 — Only x. The page is centered in the y direction.

2 — Only y. The page is centered in the x direction.

Default: 0

p5

Invert flag (switch the fixed offsets from side to side on alternate pages; particularly useful on duplex pages to maintain a fixed inside margin for binding).

0 — No alternation.

1 — Alternate fixed x offset from left to right on consecutive pages.

2 — Alternate fixed y offset from top to bottom on consecutive pages.

3 — Alternate both fixed x and y offsets on consecutive pages.

Default: 0

Note: The following notes apply to the AMAC command:

• The value for the COMPUSET PW and PD commands must be smaller than the physical dimensions of the paper if horizontal and vertical offsetting is to occur.

• Set parameters p2 and p3 so that the logical page does not extend beyond the physical page. If it does, the system reduces the offsets specified in p2 and p3 so that the edge of the logical page is placed at the edge of the physical page.

The offsets specified in parameters p2 and p3 are applied relative to the bottom left corner of the page when you view the page in portrait orientation. The orientation that you select does not affect the application of these offsets.



• Parameter p5 lets you switch the fixed offsets from side to side on alternate pages. It is particularly useful on duplex pages to maintain a fixed inside margin for binding.

• If fixed offsets are selected, they are absolute and not added to the offset derived from centering the page.

If multiple imposition is selected, fixed offsets can be applied to move the page in a direction parallel to the booklet fold axis, but not perpendicular to it.



CCOD - Condition Code OverrideThe CCOD command overrides preset condition codes. It resets the condition code produced when an error is encountered during execution on a message by message basis. CCOD appears in the PDEF or Job Command file.


Parameters

p1






1-4 — Severity level for the message numbers specified by the parameters p2-pn.

5 — Do not print message numbers specified by the parameters p2-pn.

Default: 0

p2–pn

Message numbers you want assigned the severity level specified by parameter p1 = 1–4, or messages numbers that you do not want to be printed in the log if p1 = 5. The p2–pn parameters should contain numbers, separated by commas, and must fit into a record with a maximum length of 72 characters.


• You cannot add comments to the end of a CCOD command; the output formatter tries to process the comments as parameters since the number of parameters can vary. If the output formatter



attempts to process a comment as a parameter, it generates an error message such as the following:

PCL002218-E: A PDEF FILE ERROR OCCURRED AT CHARACTER 22 OF LINE 7:CCOD 1,2052,13311, SUPP WARNING MSGS FOR 2056, 13311 (ADD AS NEEDED)

You can work around this limitation by placing the comment on a separate line. For example:

* SUPP WARNING MSGS FOR 2056, 13311 (ADD AS NEEDED)CCOD 1,25056,13311,



• If p1 is less than 1, the p1 value applies to all messages; parameters p2–pn are ignored.

• If p1 = 1–4, multiple CCOD commands can be entered to list all the message numbers whose severity is to be changed; however, only the first 1000 message numbers specified are actually used during execution.



CMAP - Character MappingThe CMAP command specifies a font character-mapping table for subsetting logical user fonts. CMAP appears in the Configuration file. This command is used only by COMPUSET, not by the output formatter.

Syntax CMAP p1,p2,p3,p4

Parameters

p1

Identifying number (an integer from 1–10) of this character-mapping table (same as p6 in the FONT command).

Default: 0

p2

Initial standard output code to be mapped (integer, 0–255). This output code is obtained after the application of the XLAT character translation.

Default: 0

p3

Font subset index (integer, 0–255).

Default: 0

p4

Final output code to print the character (integer, 0–255).

Default: 0



Note: The following notes apply to the CMAP command:

• All character-mapping tables are initialized to select subset 0 (zero) and to specify no translation. Therefore, it is necessary to supply CMAP commands only for those output codes that are different from the default.

• The subset index and subset code are ordered pairs. There must be at least one ordered pair and a maximum of 10 ordered pairs defined in one CMAP command. Each of these commands can have a maximum of 72 characters.

• Ordered pairs must be provided for each consecutive output code, beginning with the output code identified by the second parameter of the command. If a pair is specified as 0,0, the character-mapping table uses the default for that pair.

• Multiple CMAP commands that reference the same character-mapping table ID can be used to construct a table. However, all CMAP commands with the same table ID must appear consecutively in the Configuration file. All commands out of order are ignored.



COPY - Number of CopiesThe COPY command specifies the number of copies of the job to be printed. COPY appears in the PDEF or Job Command file.

Syntax COPY p1

Parameters

p1

Number of copies to be printed (maximum is 999). A positive value results in non-collated printout. A negative value results in collated printout.

Default: 1

Note: The following notes apply to the COPY command:

• If you set the number of copies (p1) to zero, the printer defaults to one copy.

• If you enter a positive value for p1, the copy function is executed by your printer, and your printed output is not collated.

• If you enter a negative value for p1, the copy function is done at a software level within the output formatter. The print stream (minus any font downloads) is written multiple times. This method is slower and results in much larger PCL files, but has the advantage of producing collated output.

• If COPY is not specified, one copy is produced.



DELE - Delete Merge Library EntryThe DELE command deletes named documents, images, or forms from the read/write Merge library. DELE appears in the PDEF or Job Command file.

Syntax DELE ‘p1’

Parameters

‘p1’

Name (in single quotes) of the Merge library element to be deleted.

Only one name can be specified on a DELE command. The output formatter identifies each element that is deleted. If an element is not found, the output formatter issues a diagnostic message.

Default: Required

Note: The following notes apply to the DELE command:

• The DELE command deletes entries only from the read/write Merge library, specified by Merge library 3 in the Job Command file. Setting parameter p2 in the DMRG command (enabling or disabling document saving) does not affect the ability of the DELE command to delete entries from the read/write Merge library.

• Any number of DELE commands can be processed during a single execution of the PCL output formatter. Element deletions are performed before the COMPUSET-generated intermediate file is processed. Only the PCL output formatter executes DELE commands; they are not executed by COMPUSET.



DJDE - Dynamic Job Descriptor EntryThe DJDE command is used by the PCL output formatter to determine how COMPUSET DJDE commands are to be processed. DJDE can appear in the Configuration, PDEF, or Job Command file.

Syntax DJDE p1

Parameters

p1

Process COMPUSET DJDE commands.

0 — Ignore all COMPUSET DJDE commands.

1 — Transfer all COMPUSET DJDE commands to the printer.

2 — Transfer any COMPUSET DJDE commands to the printer only when it begins with a decimal value of 14,

15, or 27; or it can begin with a hexadecimal value of X’0E’, X’0F’, or X’1B’. All other DJDE commands are

assumed to be metacode printer commands and are ignored.

Default: 0

Note: The following notes apply to the DJDE command:

• Specify p1 = 0 when the original text file is prepared for a metacode printer and you do not want to alter the original file.

• Specify p1 = 1 when all DJDE commands are to be processed by the destination printer.

• Specify p1 = 2 when the source text file is to be printed on a metacode printer and a PCL printer. The PCL printer will ignore all metacode DJDE commands.



DLBL - Merge Library Block LengthThe DLBL command specifies the length of each block of a Merge library. Each Merge library is a random access file with fixed-length data blocks. However, the length of each data block in a Merge library can be changed with the DLBL command. DLBL appears in the Configuration, PDEF, or Job Command file.

Syntax DLBL p1,p2,p3

Parameters

p1

Number of words in each data block (at least 512).

Default: 2048

p2

Number of blocks allowed.

Default: 1500

p3

Search method for finding Merge library elements.

0 — Case dependent search.

1 — Case independent search.

2 — Case independent search, with the ability to recognize extended ASCII characters, those above 128 ASCII

(decimal).

Default: 0



Caution: DLBL alters the number of words read from or written to every block in all Merge libraries. If several Merge library files exist, each with a different block length, using these files in the same execution of the PCL output formatter creates I/O errors. The PCL output formatter is unable to access (read from or write to) any Merge library files whose block lengths differ from the length specified by DLBL.

Note: On most platforms, p2 is not required because the operating system specifies the number of blocks.



DMRG - Merging and Saving DocumentsThe DMRG command enables documents, images, and forms to be saved in Merge libraries and the saved elements to be merged into other documents. DMRG appears in the PDEF or Job Command file.

Syntax DMRG p1,p2,p3,p4,p5,p6,p7

Parameters

p1

Merge flag.

0 — Do not permit document or image merging.

1 — Enable merging (assuming one Merge library is assigned in the Job Command file from which the merged

documents or images can be extracted).

2 — Enable merging (assuming two Merge libraries are assigned in the Job Command file from which the

merged documents or images can be extracted). The document or image to be merged can be extracted

from either Merge library.

3 — Enable merging (assuming three Merge libraries are assigned in the Job Command file from which the

merged documents or images can be extracted). The document or image to be merged can be extracted

from any one of the three Merge libraries.

Default: 0

p2

Document saving.

0 — Do no permit saving.

1 — Enable saving (each document is saved into a Merge library in its original orientation).

2 — Enable saving (each document is saved in a Merge library in both the upright and inverse orientation).



3 — Open the Merge library as read-only at start time. If an attempt is made to save a document, the emitter

closes the library and reopens it as a write library. If this operation fails, the emitter generates a document

save failure. Each document is saved in the Merge library in its original orientation.

4 — Open the Merge library as read-only at start time. If an attempt is made to save a document, the emitter

closes the library and reopens it as a write library. If this operation fails, the emitter generates a document

save failure. Each document is saved in the Merge library in both the upright and inverse orientations.

Default: 0

p3

Output formatter log file list.

0 — Do not list all images, forms, and documents in each Merge library.

1 — Generate a list before processing any COMPUSET DSAV or DMRG commands, but after performing the

delete and rename functions provided by the DELE and RENM commands

2 — Generate a list after all processing is complete.

3 — Generate a list both before and after processing

Default: 0

p4

Document replacing.

0 — Ignore any command to save documents where the name of the document to be saved already exists in

the save Merge library.

1 — Replace an existing document in the save Merge library with a new document that has the same name

only if both documents are in PCL output format. Delete any VMF references in the old document.

2 — Replace an existing document in the save Merge library with a new document that has the same name,

regardless of the format of the existing document. Delete any VMF references in the old document.



3 — Replace an existing document in the save Merge library with a new document that has the same name

only if both documents are in PCL output format. Save any existing VMF references and associate them

with the new document.

4 — Replace an existing document in the save Merge library with a new document that has the same name,

regardless of the format of the existing document. Save any existing VMF references and associate them

with the new document.

Default: 0

p5

Null documents.

0 — Save null documents.

1 — Delete null documents.

Default: 0

p6

Merge log.

0 — Write a message into the log file each time a document is merged.

1 — Suppress merge log messages.

Default: 0

p7

Save log.

0 — Write a message into the log file each time a document is saved.

1 — Suppress save log messages.

Default: 0



Note: The following notes apply to the DMRG command:

• This command does not perform in-core memory saving and merging.

• If both the p1 and p2 = 0, p3 is ignored.

• A Merge library may contain more than one resource with the same name; therefore, the output formatter uses a selection profile to determine the correct document or image to be merged.

• Specify p2 = 3 or 4 to open Merge library 3 as a read-only library, until the output formatter encounters a document save, at which time, the output formatter closes the library and reopens it as a write library. This enables Windows and UNIX jobs that are waiting for a Merge library to become available to be paused, instead of aborted.



DUPL - Duplex PrintingThe DUPL command enables duplex printing for the PCL printer when duplex mode is supported by the device. DUPL appears in the PDEF or Job Command file.

Syntax DUPL p1

Parameters

p1

Enable/disable duplex printing.

0 — No action; use the current set up on the printer

1 — Set printer to simplex.

2 — Set printer to head-to-head duplex mode.

3 — Set printer to head-to-toe duplex mode.

4 — Set printer to simplex, and treat all NPR and NPV commands as NP commands.

Default: 0

Note: The following notes apply to the DUPL command:

• If you use this command with a printer that does not support duplex printing, problems may occur with the printed output, such as offsetting the page incorrectly.

• If p1 = 3 for head-to-toe duplex, set OPTN p1 = 0 and MIMP p1 = -1. If these OPTN and MIMP settings are not specified, the system automatically resets p1 to a value of 2 (head-to-head).

• Duplex head-to-head printing with OPTN p1 = 0 outputs duplex portrait pages head-to-head, and outputs duplex landscape pages head-to-toe.

• To honor all NPR and NPV commands in the CompuSet input file, specify p1 = 1. To treat any NPR and NPV commands in the input file as NP commands (to ensure that there are no blank pages), specify p1 = 4.



FNAM - Font Names for ViewingThe FNAM command defines the names of the fonts that are displayed by CompuBuild, CompuSpec, and CompuSeries when you select a pop-up menu of the available fonts for a particular printer. FNAM appears in the Configuration file. It is used only by COMPUSET, not by the output formatter.


Parameters

p1


Default: Required

‘p2’

The name of the font family that is displayed to the user in a font list pop-up menu. The name must be enclosed in single quote marks and can be up to 20 characters long.

Default: Required

p3


0 — Serif font.

1 — Sans-serif font.

Default: Required

Note: The following notes apply to the FNAM command:





• There should be a one-to-one correspondence between each font family in the Configuration file and each FNAM command. For each group of FONT commands with the same first parameter, there should be one FNAM command with that same first parameter.



FNLD - Font DownloadingThe FNLD command enables or disables font downloading and lets you specify whether the downloaded fonts are to be retained or deleted. This is especially useful when you are printing many documents that share the same fonts; however, you want to minimize the size of the print stream by downloading these fonts only once. FNLD appears in the PDEF or Job Command file.

Syntax FNLD p1,p2,p3,p4

Parameters

p1

Download fonts.

0 — Disable font downloading. Use the NOLD command to specify printer-resident fonts.

1 — Enable font downloading. The PCL output formatter makes one pass to identify required fonts.

2 — Enable font downloading. Do not scan the CIF for the names of downloaded soft fonts; use the values

specified by PDEF file MFNT commands.

3 — Enable font downloading. The PCL emitter makes two passes to identify required fonts.

Default: 0

p2

Criteria for matching font names in the PDEF and Job Command files.

0 — Font name matching is case dependent.

1 — Font name matching is case independent.

Default: 0



p3

Retain or delete permanent soft fonts.

0 — Retain permanent soft fonts before the PCL job begins; delete temporary soft fonts only.

1 — Delete all permanent and temporary soft fonts before the PCL job begins.

Default: 0

p4

Store soft fonts temporarily or permanently.

0 — Store downloaded soft fonts temporarily.

1 — Store downloaded soft fonts permanently.

2 — Store downloaded soft fonts permanently, and delete all fonts (including permanent fonts) when the job

finishes.

Default: 0

Caution: If you are downloading fonts, the FDB must exist on the host. You cannot port the FDB; therefore, you must rebuild it for each host.

Note: If you specify p4 = 1 on the CompuSet NP command, and you are downloading fonts to a PCL printer, make the fonts resident permanently by also specifying p4 = 1 or 2 on the FNLD output formatter command.



FONT - Define User Font CorrelationThe FONT command defines all the physical fonts that comprise a typeface as one font to be referenced by COMPUSET with a single font index number. The referenced font consists of all the physical fonts required to make up all the subsets, size ranges, and stresses (light, italic, bold, bold italic) for a single typeface. FONT appears in the Configuration file. It is used by COMPUSET, not by the output formatter.


Parameters

p1

Font index number that is used by the COMPUSET F command to call the font.

Default: Required

p2–p5

Font numbers. Define the four possible physical fonts that can comprise a subset of a COMPUSET logical font in the following order:

p2 — MFNT font for light.

p3 — MFNT font for light italic.

p4 — MFNT font for bold.

p5 — MFNT font for bold italic.

These numbers correspond to p1 of MFNT. A value of zero indicates that the physical font does not exist.

Default: 0,0,0,0



p6

Index to the character-mapping table that applies to this user font.

Default: 0

Note: The following notes apply to the FONT command:

• The FONT command combined with MFNT commands correlates COMPUSET logical fonts to PCL physical fonts. A physical font number of zero specifies that the font does not exist and a COMPUSET error message is generated.


• If p6 > 0 is specified by the first FONT command for a given font index, it indicates that the font can be subsetted. In this case, more than one FONT command can be specified for the same user font index. The first FONT command for a particular index specifies the physical fonts that comprise subset 0 of the font, the second FONT command for the same user index specifies the physical fonts in subset 1, and so on. In this circumstance, the CMAP character-mapping table indexes for the FONT command specify how the entire user font is subsetted.



FTYP - Output Device and Scaling FactorThe FTYP command identifies the printer and scaling factor. FTYP appears in the Configuration, PDEF, or Job Command file.

Syntax FTYP p1,p2

Parameters

p1

Device code.

15 — PCL compatible printer.

Default: Required

p2

Scale flag.

0 — Point=1/72 inch.

1 — Point=1/72 inch.

2 — Point=1/72.27 inch.

3 — Point=1/76.564 inch.

Default: 0

Note: Parameter p2 is used by COMPUSET, not by the output formatter.



ILAT - Inverse Translation TableThe ILAT command provides an inverse translation from character code of the output device to ASCII, the internal character code for the PCL output formatter. ILAT is used for proofing. ILAT appears in the Configuration, PDEF, or Job Command file.

Syntax ILAT p1,p2,p3

Parameters

p1

Output code (the least significant 8 bits of a character code for the printer for which the PCL output formatter is proofing).

Default: Required

p2

ASCII code used by the output formatter to represent the character in proof output.

Default: Required

p3

Output subset code.

Default: 0

Note: ILAT is needed only for character codes that are not the same as ASCII.



LANG - Language SelectionThe LANG command specifies the language for messages in the execution log files and the format for printing the system time and date. LANG appears in the Configuration, PDEF, or Job Command file.

Syntax LANG p1,p2

Parameters

p1

Select language.

0 — Site-specified default.

1 — English

2 — French

3 — German

4 — Spanish

5 — Italian

6 — Dutch

7 — Swedish

8 — Norwegian

9 — Danish

10 — Portuguese

11 — Finnish

Default: 0



p2

Log file time and date format.


1 — MM/DD/YY for date and HH:MM:SS for time (same as 0)



4 — DD-MM-YY for date and HH:MM:SS for time

5 — DD.MM.YY for date and HH:MM:SS for time


7 — YY-MM-DD for date and HH:MM:SS for time



10 — DD/MM/YY for date and HH:MM:SS for time (same as 9)


Default: 0


• If the LANG command is omitted, the default language defined during installation of the message database is used.

• The arrangement of values in p1 and p2 is designed to match languages to the time and date formats common in that language.

• LANG specifies the language in which messages are to be written; it does not provide the text of those messages. Message text is contained in the message database. For U.S. customers, message text in the message database is delivered in the English language only. In other countries, languages available for message text may vary.



MFNT - Machine FontThe MFNT command identifies a physical machine font and specifies its positioning characteristics. MFNT appears in the Configuration, PDEF, or Job Command file.

Syntax MFNT p1,p2,p3,p4,p5,p6,p7,p8,p9,p10

Parameters

p1

Physical machine font identification number (referenced by FONT commands). Each MFNT command must have a unique machine font number.

Default: Required

p2

Font name (maximum 20 characters with no blanks).

Default: Required

p3

PCL symbol set identification string.

Default: Required

p4

PCL typeface number.




p5

Pitch.

0 — Proportional font.

Other — The product of the pitch and the point size.


p6

Slant.

0 — Roman.

1 — Italic


p7

Appearance.

0 — Normal

1 — Condensed

2 — Expanded




p8

Stroke weight.

0 — Light

1 — Bold


p9

Type of font.

0 — TrueType

1 — Intellifont


p10

Font resolution.

0 — 300 dpi


Note: The following notes apply to the MFNT command:

• For purposes of standardization, use the portrait font name in the p2 parameter when a choice between portrait and landscape exists.

• The maximum number of MFNTs allowed in a Configuration file varies with the host computer system. The maximum is 2,000 for these operating systems: IBM z/OS, Microsoft Windows, and all supported UNIX platforms.



MIMP - Multiple ImpositionThe MIMP command formats two logical pages on each side of a sheet of paper (physical page) and rearranges pages so that when the entire document is folded along a centerline, it produces a booklet in which the pages appear in sequential order.

There are two ways to fold the paper: along a vertical center line or a horizontal center line. When folded, there are two ways to bind the booklet: the binding can be at the top or at the left side.

Multiple imposition and n-up printing are mutually exclusive. MIMP can appear in the PDEF or Job Command file.

Syntax MIMP p1,p2,p3,p4,p5,p6

Parameters

p1

Page orientation.

-1 — Do not use multiple imposition.

0 — Landscape, head-to-head with the booklet made by folding along the short axis of the page. All text and

images rotate the same way.

1 — Portrait, head-to-head with the booklet made by folding along the long axis of the page. All text and


2 — Landscape, head-to-head (same as 0).

3 — Portrait, head-to-toe, with the booklet made by folding on the short axis of the page. All text and images

rotate the same way.

4 — Landscape, head-to-toe with the booklet made by folding along the long axis of the page. All text and




5 — Portrait, head-to-head with the booklet made by folding along the long axis of the page. Different text and

image rotation on the same page is supported.

6 — Landscape, head-to-head with the booklet made by folding along the short axis of the page. Different text

and image rotation on the same page is supported.

7 — Portrait, head-to-toe, with the booklet made by folding on the short axis of the page. Different text and


8 — Landscape, head-to-toe with the booklet made by folding along the long axis of the page. Different text and


Default: -1

p2

Gutter 1 width.

0 — Center each logical page on its half of the physical page.

n — Minimum width (in points) between left and right logical pages printed on a single physical page.

Default: 0

p3

Cover flag.

0 — Set all logical pages in normal sequence with enough blank logical pages left at the end to fill out to a

multiple of four logical pages (one physical sheet).

1 — Insert blank logical pages so the last logical page appears on the back cover of the folded output.

2 — Insert blank logical pages so the last two logical pages appear on the inside and outside of the back cover

of the folded output.

Default: 0



p4

Last page imposition.

-1 — Enable start/stop imposition as controlled by the user with the COMPUSET IMPO command.

0 — No special action.

1 — Do not include last logical page of the intermediate file in the imposition sequence, but output it last as a

separate physical page (necessary in online installations where the last page is a trailer, such as an IBM

JES banner page).

Default: 0

p5

Gutter 2 width.

0 — Fix gutter width at the value specified by p2.

n — Maximum gutter width (in points) between imposed pages.

Default: 0

p6

Save flag.

0 — Do not save imposed documents regardless of the DMRG command.

1 — Permit saving of imposed documents.

Default: 0

Note: The following notes apply to the MIMP command:

• The recommended values for p1 are 5, 6, 7, or 8.

• Specify p1 = 5 if you are using 11 x 17 paper to create a landscape head-to-head booklet with a short edge fold.



• If p1 = -1, there is no imposition and all other parameters of this command are ignored.

• If p4 = 1, all pages produced in the run, except the last, are imposed as one booklet.

• For p8 and p9, offsets are applied relative to the bottom left corner of the page when it is viewed in portrait orientation. The orientation selected by the user does not affect the application of these offsets. So for p8, negative values move the imposed pages to the left and positive to the right, when viewed in portrait orientation.

• MIMP shifting is similar to that of the AMAC command, but the AMAC shifting applies to text and images on the logical page and occurs before imposition. The MIMP shift moves the logical pages together in unison on the physical paper after imposition. When pages are imposed, The PCL output formatter always assumes that the center fold line for the booklet is in the middle of the physical page. However, the MIMP command can specify to move the center fold line.

• The value chosen for p3 applies to every multiply imposed set of a start/stop imposition run.

• If p4 = 1, all pages produced in the run, except the last, are imposed as one booklet.

• Parameters p2 and p5 together create a variable gutter that allows for the increasing width required for outer pages of the booklet, due to the fold. The gutter is decreased on every page in even increments from p5 at the outside of the booklet to p2 at the center of the booklet.

• If p2 = 0, the p5 parameter is ignored.

• The imposed, saved document cannot be imposed a second time. If it is being merged into a document that is being imposed, multiple imposition must be turned off just before the merge document.

• To save an imposed document, the parameter of DMRG that controls document saving must also be specified.



NOLD - Font Location (Resident or Downloaded)The NOLD command identifies the fonts that are resident on the printer as well as those fonts that are to be downloaded by the PCL output formatter to the printer. NOLD appears in the Configuration, PDEF, or Job Command file.

Syntax NOLD p1,p2

Parameters

p1

MFNT number of downloaded font.

Default: Required

p2

Font type.

0 — Font is to be downloaded to the printer.

1 — Font is resident on the printer or it is a cartridge font.

2 — Unused.

3 — Font is not to be downloaded to the printer because it is permanently resident on the printer.

4 — Font is to be downloaded to the printer for linked output formatter processing.

Default: 0

Note: The following notes apply to the NOLD command:

• Enter NOLD into the Configuration file to identify both the permanent fonts on the printer and any fonts loaded on cartridges for the printer (cartridge fonts are specified as permanent fonts).

• The p2 = 0 value indicates that soft fonts are to be downloaded to the printer by the PCL output formatter or with the FJOB FDB command.



• If you specify p2 = 1 or 2, the output formatter does not distinguish between resident or cartridge fonts.

• Specify p2 = 4 and FNLD p1 = 2 if you are using linked output formatter processing.

• PDEF commands take precedence over NOLD commands.

• If every font needed for printing a document has already been downloaded, FNLD can disable font downloading.



OBFM - Output Record FormatThe OBFM command writes the output file as fixed-length records. OBFM appears in the Configuration, PDEF, or Job Command file.

Syntax OBFM p1,p2

Parameters

p1

Output type.

0 — Printer-formatted output.

Default: 0

p2

Record format.

0 — 132 characters for printer format.

n — Maximum record length (integer between 60 and 512).

Default: 0

Note: The following notes apply to the OBFM command:

• OBFM 0,80 is recommended for IBM operating systems.

• The font download header is always 80 bytes, regardless of the record length specified by p2.

• If you specify a p2 value that is less than 60, a warning is issued and the value defaults to 60.



OPTN - Define OrientationThe OPTN command specifies processing options for the print job. OPTN appears in the PDEF or Job Command file.

Syntax OPTN p1,p2,p3,p4,p5,p6,p7

Parameters

p1

Orientation mode.

0 — For long-edge binding, print the document in head-to-head portrait or head-to-toe landscape orientation.

COMPUSET rotation commands in the text file control the orientation and the output formatter makes no

changes to these rotation commands.

1 — For short-edge binding, print the document in head-to-toe portrait orientation. The output formatter controls

the orientation and ignores any COMPUSET rotation commands in the text file. All text on recto pages is

portrait; all text on verso pages is inverse portrait.

2 — For short-edge binding, print the document in head-to-head landscape orientation. The output formatter

controls the orientation and ignores any COMPUSET rotation commands in the text file. All text on recto

pages is landscape; all text on verso pages is inverse landscape.

11 — For short-edge binding, print the document in head-to-toe portrait orientation. For recto pages, the output

formatter formats all text in the orientation specified by COMPUSET rotation commands. For verso pages,

the output formatter formats all text that is in portrait orientation into inverse portrait orientation; other

COMPUSET rotation commands are unchanged.

12 — For short-edge binding, print the document in head-to-head landscape orientation. For recto pages, the

output formatter formats all text in the orientation specified by COMPUSET rotation commands. For verso

pages, the output formatter formats all text that is in landscape orientation into inverse landscape

orientation; other COMPUSET rotation commands are unchanged.



21 — For short-edge binding, print the document in head-to-toe portrait or head-to-head landscape orientation.

COMPUSET rotation commands control the orientation. These rotation commands are automatically

inverted on verso pages.

31 — For short-edge binding, print the document in head-to-head portrait or head-to-toe landscape orientation.

COMPUSET rotation commands control the orientation. These rotation commands are inverted on verso

pages automatically as needed.

32 — For long-edge binding, print the document in head-to-toe portrait or head-to-head landscape orientation.

COMPUSET rotation commands control the orientation. These rotation commands are inverted on verso

pages automatically as needed.

Default: 0

p2

Physical paper size.

0 — 8.5 X 11 inches (letter).

1 — 8.5 X 11 inches (letter; same as 0 ).

2 — 7.25 X 11.5 inches (executive).

3 — 8.5 X 14 inches (legal).

4 — A4 paper (210 mm by 297 mm).

5 — A3 paper (297 mm by 416 mm).

6 — 11 X 17 inches (ledger).

7 — 3 7/8 X 7.5 inches (monarch letter-sized envelope).

8 — 4 1/8 X 9.5 inches (commercial 10 business-sized envelope).

9 — 110 X 220 mm (international DL).

10 — 162 X 229 mm (international C5).

11 — 176 X 250 mm (international B5).

12 — JIS B5 182 X 257 mm (7.16 X 10.12 inches).



13 — JIS B4 257 X 364 mm (10.12 X 14.33 inches).

14 — JPOSTD 148 X 200 mm (5.83 X 7.87 inches)..

Default: 0

p3

Conditional output flag.

0 — Output normally.

1 — Suppress output when a fatal error is detected.

2 — Suppress output unconditionally.

Default: 0

p4

Proofing justification flag.

0 — Reduce interword spacing to force a horizontally-justified text record into the current column.

1 — convert a horizontally-justified text record to a quad left text record when it does not fit into the current

column width.

Default: 0

p5

Interword spacing.

0 — Always use Move commands between words.

1 — Use spaces between words when possible.

Default: 0



p6

Job separation command switch.

0 — Include the job separation command in the output file.

1 — Suppress the job separation command in the output file (Xerox NPS printers only).

Default: 0

p7

Saving tray selection.

0 — Do not save the tray selection on the first page of a saved document.

1 — Save the tray selection on the first page of a saved document.

Default: 0

Note: The following notes apply to the OPTN command:

• The first parameter of the MIMP output formatter command takes precedence over first parameter of OPTN. As a result, if multiple imposition is on, OPTN p1 is set to 0.

• Use p6 = 1 for Xerox NPS printers. Use the default value for all other printers.



PAGE - Output Formatter Page RangeThe PAGE command defines the range of composed pages to be made ready for output. PAGE allows one page or a selected portion of a file to be output without processing the entire file. PAGE appears in the PDEF or Job Command file.

Syntax PAGE p1,p2

Parameters

p1

First page to be output.

Default: First page of document.

p2

Last page to be output.

Default: Last page of document.

Note: If the PAGE command is not used, COMPUSET output is processed by the output formatter starting at the first page and continuing through the end of the document. If multiple PAGE commands appear in the PDEF file, the last one overrides the others.



PDEF - Print Descriptor Entry FormatThe PDEF command specifies a soft font that is to be downloaded. PDEF can appear in the PDEF or Job Command file.

Syntax PDEF p1

Parameters

p1

MFNT number of the font specified in the Configuration file.

Default: Required

Note: Specify p1 = mfnt_number and FNLD p1 = 2 if you are using linked output formatter processing.



PDFM - Output Printer and Font MemoryThe PDFM command defines printer specifications to the output formatter. PDFM appears in the Configuration, PDEF, or Job Command file.

Syntax PDFM p1,p2

Parameters

p1

Output device type.

3 — HP LaserJet III and compatible printers.

4 — HP LaserJet 4, HP LaserJet 5, and compatible printers.

Default: 4

p2

Printer memory size in Kilobytes (KB).

Default: 1024

Note: If the total size of all fonts downloaded for a job exceeds the printer memory, a message displays. Many PCL printers have memory enhancement features that can allow you to download more fonts than your installed memory value specifies. If the total size of the font download exceeds your installed printer memory, you may find fonts deleted from the printer, depending on the efficiency of the memory-enhancement features.



PFID - Final Output DeviceThe PFID command specifies the final output printer for which the PCL printer is being used as a proofer. This command informs the output formatter that the following PFNT and ILAT commands apply to the printer specified by the device code. The proofing information for all the printers at a site can be included in the same Configuration file. PFID appears in the Configuration, PDEF, or Job Command file.

Syntax PFID p1

Parameters

p1

Device identification code.

2 — Xerox Centralized printer.

8 — Xerox Decentralized printer.

12 — Xerox 4650.

13 — AFP

14 — PostScript

15 — HP PCL

20 — xPression Design viewer. This value must be in the PDEF file for any output profile where output will be

viewed through xPression Design and special characters need to be translated with ILATs. If no special

translations are needed, PFID 20 is not needed. If you are translating special charactors, you also need to

add to your PDEF file any and all ILAT commands that are needed to remap special characters.

Default: Required

Note: The p1 values of 1, 3–7, and 9–11 are supported for backward compatibility but should not be selected for new applications.



PFNT - Proof Font Numbers (Printers)The PFNT command specifies the printer MFNT number that emulates the MFNT font value used in the composition phase of COMPUSET. PFNT appears in the Configuration, PDEF, or Job Command file.

Syntax PFNT p1,p2

Parameters

p1

MFNT number used in the composition phase of CompuSet.

Default: Required

p2

PCL printer MFNT number that emulates the composition MFNT.

Default: Required

Note: A PFNT number is required for each composition MFNT number used. Use this format of PFNT for proofing files composed for other printers.



PGSZ - Output Paper SizeThe PGSZ command selects the paper size for the PCL printer. PGSZ appears in the PDEF or Job Command file.

Syntax PGSZ p1

Parameters

p1

Printer paper size.





4 — A4 paper (210 mm by 297 mm).

5 — A3 paper (297 mm by 416 mm).







12 — JIS B5 182 X 257 mm (7.16 X 10.12 inches).

13 — JIS B4 257 X 364 mm (10.12 X 14.33 inches).


Default: 1



Note: The following notes apply to the PGSZ command:

• The page size value is set when you specify one of these values:

• The p3 parameter of the TRAY output formatter command

• The p1 parameter of the PGSZ output formatter command

• The p2 parameter of the OPTN output formatter command

If you set values for more than one of these commands, the TRAY value supersedes the PGSZ value. The OPTN value has the lowest priority.

• The TRAY command has been enhanced to support a wider range of trays. For the output formatter, the maximum range is now 1–39; however, COMPUSET has a smaller range of 1–15. For now, increase tray ranges to the limit that is acceptable for COMPUSET.



PPNM - Page Count SentinelThe PPNM command identifies a marker or sentinel to be printed with the page count accumulator in the log file. The COMPUSET PPN command allows page numbers to be printed both in the document and in the output log. The sentinel provides a uniform string of characters that facilitate the use of automatic searching routines to locate the page count accumulator. PPNM appears in the PDEF or Job Command file.

Syntax PPNM p1

Parameters

p1

1–4 alphanumeric characters to appear in columns 2–5 of all page number records in the output log. Do not enclose the characters in quotes. A page number record appears in the output log each time the COMPUSET PPN,-4 command is used.

Default: Required



RENM - Merge Library Entry RenameThe RENM command renames an existing document, image, or form in the read/write Merge library. Only one pair of names is allowed for each RENM command. The output formatter identifies each Merge library element that is renamed and issues a diagnostic message if it cannot find the original name, or if the new name already exists in the Merge library. RENM appears in the PDEF or Job Command file.

Syntax RENM ‘p1’,‘p2’

Parameters

‘p1’

Current name (in single quotes) of the element to be renamed.

Default: Required

‘p2’

New name (in single quotes) of the element.

Default: Required

Note: The following notes apply to the RENM command:

• The RENM command affects only the read/write Merge library that is identified in the Job Command file. The p2 parameter value of the DMRG command, which enables or disables document saving does not affect the ability of the RENM command to rename elements in the read/write Merge library.

• Any number of RENM commands can be entered during a single execution of the output formatter. These commands are executed before the COMPUSET-generated intermediate file is processed.



SIZE - Maximum Point SizeThe SIZE command specifies the maximum point size supported by COMPUSET. SIZE appears in the Configuration file. It is used only by COMPUSET, not by the output formatter.

Syntax SIZE p1

Parameters

p1

Maximum point size allowed.

Default: Required



SPHC - Special Hyphenation CharactersThe SPHC command is used only with the enhanced algorithms for the Danish, Dutch, Finnish, French, German, Norwegian and Swedish languages. When making a hyphenation decision, the enhanced hyphenation algorithms can recognize extra characters in addition to the characters A–Z (uppercase and lowercase). Because the character codes corresponding to the extra characters are not standard, SPHC allows these codes to be specified for each of the extra characters.

SPHC permits the site manager to specify the decimal input representations that correspond to the characters listed in parameters p2–p11. The values the site manager must enter for p2–p11 depend on:

• Whether the computer uses ASCII or EBCDIC coding

• The algorithms that are to be used

The number of extended characters, and the extended characters themselves, are dependent on the language algorithm implemented. SPHC appears in the Configuration file. It is used only by COMPUSET, not by the output formatter.

Syntax SPHC p1,p2,p3,p4,p5,p6,p7,p8,p9,p10,p11

Parameters

p1

Language code to which the extended alphabetic characters apply.

2 — French

3 — German

6 — Dutch

7 — Swedish

8 — Norwegian

9 — Danish

11 — Finnish

Default: Required



p2

Decimal value of the uppercase representation of the first extended character (for French, E grave; for German, A umlaut; for Dutch the IJ digraph; for Swedish, Norwegian, Danish and Finnish, A ring).

.p3

Decimal value of the lowercase representation of the first extended character (for French, e grave; for German, a umlaut; for Dutch the ij digraph; for Swedish, Norwegian, Danish and Finnish, a ring).

Default: Language ASCII (ISO) EBCDICFrench 200 208German 196 74Dutch 208 0Swedish 197 91Norwegian 197 91Danish 197 91Finnish 197 91

Default: Language ASCII (ISO) EBCDICFrench 232 208German 228 192Dutch 240 0Swedish 229 208Norwegian 229 208Danish 229 208Finnish 229 208



p4

Decimal value of the uppercase representation of the second extended character (for French, E acute; for German, O umlaut; for Dutch unused; for Swedish, A umlaut; for Norwegian and Danish, the AE digraph; for Finnish, A umlaut).

p5

Decimal value of the lowercase representation of the second extended character (for French, e acute; for German, o umlaut; for Dutch unused; for Swedish, a umlaut; for Norwegian and Danish, the ae digraph; for Finnish, a umlaut).

Default:

Default: Language ASCII (ISO) EBCDICFrench 201 192German 214 224Swedish 196 123Norwegian 196 123Danish 196 123Finnish 196 123




p6

Decimal value of the uppercase representation of the third extended character (for French, O umlaut; for German, U umlaut; for Dutch unused; for Swedish, O umlaut; for Norwegian and Danish, O slash; for Finnish, O umlaut).

p7

Decimal value of the lowercase representation of the third extended character (for French, o umlaut; for German, u umlaut; for Dutch unused; for Swedish, o umlaut; for Norwegian and Danish, o slash; for Finnish, o umlaut).





p8

Decimal value of the uppercase representation of the fourth extended character (for French, unused; for German, s sharp; for Dutch unused; for Swedish, unused; for Norwegian and Danish, A umlaut; for Finnish, U umlaut).

.p9

Decimal value of the lowercase representation of the fourth extended character (for French, unused; for German, unused; for Dutch unused; for Swedish, unused; for Norwegian and Danish, a umlaut; for Finnish, u umlaut).

p10

Decimal value of the uppercase representation of the fifth extended character (for French, unused; for German, unused; for Dutch unused; for Swedish, unused; for Norwegian and Danish, O umlaut; for Finnish, unused).

Default: Language ASCII (ISO) EBCDICGerman 223 161Norwegian 196 123Danish 196 123Finnish 220 161

Default: Language ASCII (ISO) EBCDICNorwegian 228 192Danish 228 192Finnish 252 161

Default: Language ASCII (ISO) EBCDICNorwegian 214 124Danish 214 124



p11

Decimal value of the lowercase representation of the fifth extended character (for French, unused; for German, unused; for Dutch unused; for Swedish, unused; for Norwegian and Danish, o umlaut; for Finnish, unused).

Note: The following notes apply to the SPHC command:

• If a shifted character is used to input one or more of the extended characters, specify p2, p3, p4,... as the decimal value of the unshifted input character, incremented by 256 for a shift-1 character and by 512 for a shift-2 character. Consequently, on an EBCDIC machine, if ¬ is to represent the German A umlaut (assuming ¬ is the shift-1 character), specify p2 in the SPHC command as 449 (193 for EBCDIC A, plus 256).

• If more than one language is in use at the same site, multiple SPHC commands can be included in the Configuration file, each with a different value for p1, to specify the special characters for the languages to be used. If no SPHC commands are included in the Configuration file, all defaults are in effect.

Default: Language ASCII (ISO) EBCDICNorwegian 246 106Danish 246 106



TRAY - Select Input TrayThe TRAY command specifies the printer tray number specified by COMPUSET, maps it to the corresponding printer tray device number, and identifies the paper size. TRAY appears in the PDEF or Job Command file.

Syntax TRAY p1,p2,p3

Parameters

p1

Printer tray ID number specified by COMPUSET NP, NPR, or NPV command.

1 - 15

Default: Required

p2

Printer tray ID to be issued to the printer.

1 — Feed paper from the printer default tray.

2 — Feed paper from manual input.

3 — Feed envelope from manual input.

4 — Feed paper from lower tray.

5 — Feed from an optional paper source which is high-capacity input (HCI) tray number 1.

6 — Feed envelope from an optional envelope feeder; use with a specified envelope paper size..

7 — Autoselect default tray.

8 — Feed from manual input.

20-39— Feed from an optional paper source which are high-capacity input (HCI) trays numbered 2-21.

Default: The value specified by p1.



p3

Physical paper size.





4 — A4 paper (210 mm by 297 mm).

5 — A3 paper (297 mm by 416 mm).







12 — JIS B5 182 X 257 mm (7.16 X 10.12 inches).

13 — JIS B4 257 X 364 mm (10.12 X 14.33 inches).


Default: 0

Note: The following notes apply to the TRAY command:• The p1 value should match the p2 value on COMPUSET NP, NPR, or NPV commands.• HP printers can support as many as 39 paper tray IDs; however, COMPUSET supports a maximum

of 15 trays.



• The p2 parameter enables you to identify the destination printer tray. The p2 values shown identify generic PCL 5 printer tray ID numbers for Hewlett-Packard (HP) printers only. These values may have different meanings for each printer model. For example, the p2 values for HP LaserJet 8100 and 9000 series printers map as follows:

If you change paper sizes, reissue the COMPUSET PW and PD commands in the tagged text file before specifying an NP, NPR, or NPV command.

• The page size value is set when you specify one of these values:

• The p3 parameter of the TRAY output formatter command

• The p1 parameter of the PGSZ output formatter command

• The p2 parameter of the OPTN output formatter command

If you set values for more than one of these commands, the TRAY value supersedes the PGSZ value. The OPTN value has the lowest priority.

p2 Value Tray Definition

1 Tray 2

2 Manual feed, paper

3 Manual feed, envelope

4 Tray 1

5 Tray 3

20 Tray 4

21 Tray 5 (8100 series only)



TXFL - Text String Definition CharactersThe TXFL command changes the characters that COMPUSET recognizes to introduce named string definitions.

Normally, named string definitions begin with either an asterisk (*) or a crosshatch (#). The asterisk indicates a named string whose font selections remain in effect only within the named string. The crosshatch indicates a named string whose font selections remain in effect beyond the named string. TXFL appears in the Configuration file. It is used only by COMPUSET, not by the output formatter.

Syntax TXFL p1,p2

Parameters

p1

Decimal code for the single character to replace the asterisk (*).

Default: 0 (* is unchanged).

p2

Decimal code for the single character to replace the crosshatch (#).

Default: 0 (# is unchanged).

Note: The following notes apply to the TXFL command:

• Whether the values for p1 and p2 are ASCII or EBCDIC depends on the host computer.

• The character codes selected must be for printable alphanumeric characters (type 12 characters), without syntactic significance (for instance, <, >, ^, and ~ are not allowed).



XLAT - Translation TableThe XLAT command specifies the output character translation table. XLAT appears in the Configuration file. It is used by COMPUSET, not by the output formatter.

Syntax XLAT p1,p2,p3,p4,p5

Parameters

p1

Decimal value of the character code that represents the input character, as typed from a terminal.

Default: 0

p2

Decimal value of the character output to the printer when the unshifted input character is encountered.

Default: 0

p3

Decimal value of the character output to the printer when the shift-1 character precedes the input character.

Default: 0

p4

Decimal value of the character output to the printer when the shift-2 character precedes the input character.

Default: 0



p5

Character logical type used by COMPUSET for parsing.

1 — Uppercase alphabetic characters.

2 — Lowercase alphabetic characters.

3 — Numeric characters.

4 — Blank space.

5 — Significant blank, an accent grave (`).

6 — Opening command delimiter (<).

7 — Closing command delimiter (>).

8 — Shift-1 character, a circumflex (^) or a logical not (¬).

9 — Command parameter separator, a comma (,).

10 — Command separator, a slash (/).

11 — Macro and text definitions (=).

12 — Other graphic characters.

13 — End-of-line character (if used, indicates a line ending if the host computer delimits records with other than

a line feed.)

14 — Other control characters to identify control characters that are in the input file.

15 — Used in page numbering (if used, indicates a character other than the period to be used with the circumflex

for page numbering. The new character then becomes unavailable for use in any other tags).

16 — Shift-2 character, a tilde (~).

Default: Character type unchanged.

Caution: Use caution if you are changing the character type, because it affects the way COMPUSET treats characters.



Note: Changing the character type for one character does not affect the character type for any other characters. For example, setting the percent sign (%) as a shift-2 character does not nullify the tilde (~) as a shift-2 character.



XPSM - Select Composition ModeThe XPSM command selects the COMPUSET composition mode, which is standard composition mode or XPS composition mode.

There are two ways to specify the XPSM command:

• Include it in the Configuration/Widths file by adding it to the Configuration file and running the FDB utility program to update the Configuration/Widths file.

• Add the XPSM command to the Configuration file read by COMPUSET during execution.

An instruction in the Configuration file overrides the setting, if any, in the Configuration/Widths file. If COMPUSET is running with a Configuration/Widths file and a null or small Configuration file, XPS/standard host mode can be set in the Configuration file on a run-by-run basis. XPSM appears in the Configuration file. It is used only by COMPUSET, not by the output formatter.

Syntax XPSM p1

Parametersp1

Composition mode switch.

0 — Operate in standard host composition mode.

1 — Operate in XPS composition mode.

2 — Operate in XPS composition mode and buffer input through a scratch stream to avoid repositioning the

input files.

Default: 0

Note: The following notes apply to the XPSM command:

• XPSM is available on these platforms: IBM z/OS, Microsoft Windows, and all supported UNIX platforms.



• When XPSM p1 = 2, CompuSet does not reposition the primary or secondary input text files, which are read sequentially.

• If your input files span disk volumes on an z/OS platform, specify XPSM p1=2, which enables CompuSet to open the input files in a mode that permits the files to span volumes.


492

Appendix FThe Compubld.ini File

This chapter details the contents of the Compubld.ini file. Compubld.ini is the initialization file that configures the xPression Design viewer (also known as the CCF viewer). It uses the standard Windows INI file structure. It must be located in the same directory as the Cmv32.dll. The following topics detail the sections and keys contained in this file.

• Sample Compubld.ini File

• [dirs] Section

• [MergeOptions] Section

• [layout] Section

• [PostScript] Section

• [Hardware] Section

• [Afp] Section

• [ilats] Section

• Optional Sections


Appendix F - The Compubld.ini File493

Sample Compubld.ini FileThis section shows a sample Compubld.ini file. The paths represented in this file may not match the paths on your system.

; compubld.ini;-------------

[dirs]CompuSet=C:\Program Files\xPression\SystemWordType=little32

[MergeOptions]SuppressImages=FALSESuppressDocs=FALSE

[layout]AdjustLetterSpacing=ON

[Postscript]FontPath=C:\Program Files\xPression\fonts\psMaxResolution=300

[Hardware]MaxPrinterResolution=300ShadingMethod=1

[Afp]ResourceDataPath=C:\Program Files\xPression\CompuSet\AFP Viewing\ResourceFontDataPath=C:\Program Files\xPression\CompuSet\AFP Viewing

[ilats]Ilat02=C:\Program Files\xPression\bin\ilat02.dat



Ilat13=C:\Program Files\xPression\bin\ilat13.datIlat14=C:\Program Files\xPression\bin\ilat14.datIlat15=C:\Program Files\xPression\bin\ilat15.dat

[dirs] Section This section contains information on the keys used to locate files.

compusetcompuset = System Directory Path

This key defines the path name to the location of the directory where CompuBuild searches for the basic CompuSet system files including the license key file, the Message databases, Merge libraries, Widths files, Configuration files, Font databases and the Hyphenation Dictionary. If this path is not specified, CompuBuild searches in the directory specified as the Config Directory in the File/Setup dialog box that creates the Compubld.sys file. By default, this path is:C:\Program Files\xPression\System

Note: This key is required for Cmv32.dll to locate the message database and the DLLs of the dependent API.

WordTypeWordType = subdirectory

This key specifies the name of a subdirectory of the CompuSet System Directory path defined by the CompuSet key used to search for word length dependent files such as Widths files, the CompuSet key file, the Message databases, and the Font databases. If this key is specified, its value is appended to the path defined by the CompuSet key when CompuBuild searches for these files.

By default, this parameter is: WordType=little32



Note: This key is required for Cmv32.dll to locate the message database and the DLLs of the dependent API.

Optional KeysThe following keys are not included in the default Compubld.ini file, but may be added if needed.

Editor

Editor = Editor Directory Path

This key defines the path name to the location of the directory for the editor used during interactive composition. If this key is not supplied, CompuBuild searches for the editor in the subdirectory named "Editor" of the directory where the .ini file is located.

UseCwrite

UseCwrite = ON | OFF | TRUE | FALSE

This key determines whether the CodeWright editor (cw32) or the built-in CompuSet Editor is used during interactive composition. If UseCwright is set to ON or TRUE, CompuBuild attempts to use CodeWright as the editor. Otherwise, it uses the CompuSet editor.

[MergeOptions] SectionNot used in xPression.

[layout] SectionNot used in xPression.



[PostScript] SectionThis section contains information on the keys used to control PostScript output formats.

MaxResolutionMaxResolution = n

When CompuBuild calls the Ghostscript DLL to rasterize PostScript images for printing, by default it selects a resolution of 300 dots per inch. Restricting the resolution reduces the memory usage and increases the performance of the rasterizer. This setting enables the user to override this default. If set to higher than 300, it allows higher resolution images to be created for high-resolution printers. If set to a non-zero value less than 300, it reduces the resolution and quality of the printed output but increases performance.

FontPathFontPath = path for locating font resources for Ghostscript

This key defines the search path to be used when locating font and other resources needed by the Ghostscript system, which is used by CompuSet to display PostScript and PDF documents and images. It uses the standard search path format of directory paths separated by semi-colons.

[Hardware] SectionThis section contains information on the keys used to designate screen and print output options.

ShadingMethodShadingMethod = 0 | 1 | 2 | 3



Default: 0

MaxPrinterResolutionMaxPrinterResolution = n

The value n is used to control the resolution (in dots per inch) selected on printers when creating the printer device context. Many printers allow programs to select the resolution of the printer from a menu of choices. If MaxPrinterResolution is set to a number other than 0, CompuBuild selects the available

ShadingMethod = 0 Shaded areas are produced by laying down one of three 48 x 24 bit patterns onto the area to be shaded using the BitBlt function. This enables shading to be done in the same pass as text, since it does not obliterate any text that is already in the shaded area. It does, however, produce large print output files for pages that contain a lot of shading and on some printers the shading does not abut very well. This method is the default.

ShadingMethod = 1 This method makes two passes through the CIF input file (and any merged documents) to enable shaded areas to be filled in before any text is output. This enables the use of a much simpler shading technique with the FillRect function. This produces more even shading and much more compact printer files, but because the FillRect function obliterates anything that is already in the shaded area, it forces the use of two passes. There is a slight impact on performance, which is more than compensated for by improved shading quality, and faster print performance.

ShadingMethod = 2 This is a slight variation on ShadingMethod 0. It creates a separate bitmap the size of the area to be shaded, filling this bitmap using the FillRect function and then overlaying it on the final shade area using the BitBlt function. This technique only involves one pass, and avoids an abutment problem. It also produces slightly more efficient printer files than Method 0 (but far less efficient than method 1).

ShadingMethod = 3 This setting is the same as ShadingMethod 1, except that in the first pass scan all rules are output, not just shaded rules. This method permits the use of solid color backgrounds to text.



printer resolution that is equal to or less than the value specified. If there is no available resolution less than or equal to the value specified, CompuBuild selects the closest available resolution. Restricting the resolution on printers can reduce the amount of memory needed to produce and print CompuBuild pages on very high-resolution printers. It can also bypass overflow problems that can be caused by the high scaling factors associated with very high-resolution printers. If the value is 0, CompuBuild outputs at the default resolution of the printer. If this value is not defined in the .ini file it is initialized as 300.

Optional SettingsThe following settings are not inlcuded in your default Compubld.ini file, but may be added if necessary.

MaxMergeDocPrinterResolution

MaxMergeDocPrinterResolution = n

When CompuSet merges PostScript and AFP documents to be viewed or printed, it first uses a subsystem to convert these documents to bitmaps. When displaying the document, the resolution of the bitmap is set to the resolution of the screen. When printing the document, the resolution is controlled by the value of n. The value of n is used to set an upper limit to the resolution (in dots per inch) of the bitmap produced. Setting n to a low value (for example, 150) improves performance but reduces image quality. Setting to a higher value improves quality at the expense of performance. If n is set as 0, the bitmaps are built as the default resolution of the printer. Merge document bitmaps are always built as a resolution no greater than the resolution selected by the MaxPrinterResolution key. If this value is not defined in the .ini file it is initialized as 300.

ScalePrintedPagetoVisibleArea

ScalePrintedPagetoVisibleArea = ON | OFF | TRUE | FALSE

If ScalePrintedPagetoVisibleArea is set to ON or TRUE, CompuBuild interrogates the printer about the area of a page that can actually be used for output. Many Windows printers cannot print out to the edges of the page. If this option is selected, CompuBuild automatically scales pages down by the ratio of the printable area to the actual size of the page.



PrintCharByChar

PrintCharByChar = ON | OFF | TRUE | FALSE

If PrintCharByChar is set to ON or TRUE, text strings are output to the printer with each character positioned individually. This switch is available because some printer drivers cannot handle the API call (ExtTextOut) used to output character strings. This switch should only be used if absolutely necessary because it can increase the size of the printer output stream significantly.

UseStretchDIBits

UseStretchDIBits = ON | OFF | TRUE | FALSE

If UseStretchDIBits is set to ON or TRUE, single bit per pixel bitmaps are output to printers using the StretchDIBits API call rather than the normal StretchBlt API call. Some printer drivers, most notably the Acrobat PDFWriter, can invert image bitmaps when they are output using StretchBlt.

ExpandPrinterFonts

ExpandPrinterFonts = n

ExpandPrinterFonts defines a percentage amount by which printer fonts are expanded in size when printed. Increasing the size does not increase the horizontal space occupied by the characters; it just causes the characters to be butted together more closely. A negative value causes the font size to be reduced by the corresponding percentage amount.

For example, an ExpandPrinterFonts value of 10 causes 10-point text to be output using 11-point characters (a 10% increase in size). This setting enables you to force characters to be more closely abutted. This can be useful when the character is constructed with an inverse video (white character/black background) and it is desired that no gaps appear in the background.



ExpandScreenFonts

ExpandScreenFonts = ON | OFF | TRUE | FALSE

ExpandScreenrFonts defines a percentage amount by which screen fonts are expanded in size when displayed. Increasing the size does not increase the horizontal space occupied by the characters; it just causes the characters to be butted together more closely. A negative value causes the font size to be reduced by the corresponding percentage amount.

DllPreload

DllPreload = ON | OFF | TRUE | FALSE

If DllPreload is set to ON or TRUE, CompuBuild preloads the CompuSet, DOCUTL, and WBMUTL DLLs as soon as execution begins. This option is mainly useful on Windows 3.x systems that have low memory availability as it enables the preallocation of the memory for the DLLs.

XVGA

XVGA = ON | OFF | TRUE | FALSE

If XVGA is set to ON or TRUE, text strings displayed have a blank appended to the end. This is necessary on some XVGA display controllers to make the last real character of the string appear on the screen.

XPrint

XPrint = ON | OFF | TRUE | FALSE

If XPrint is set to ON or TRUE, text strings output to the printer have a blank appended to the end. This is necessary on some printers to ensure that all real characters are printed.



[Afp] SectionThis section contains information on the keys used to set AFP viewer options.

ResourceDataPathResourceDataPath = path for resource data used by the AFP viewer

This key defines the search path to be used by the AFP viewer DLLs to locate resources (formdefs, pagedefs, images) used by the AFP viewer when displaying AFP documents from within CompuBuild. It uses the standard search path format of directory paths separated by semi-colons.

FontDataPathFontDataPath = path for finding font data used by the AFP viewer

This key defines the search path to be used by the AFP viewer DLLs to locate font resources (coded font files and code pages) used by the AFP viewer when displaying AFP documents from within CompuBuild. It uses the standard search path format of directory paths separated by semi-colons.

The resources, font files and code pages required by the IBM workbench-viewing engine are located in the %COMSET%\AFPVIEW directory.

[ilats] SectionNot used in xPression.

Optional SectionsThe following sections are not included with your default Compubld.ini file.

[ActivityLog] SectionThis section contains information on the keys used to set activity log options.



LogFileName

LogFileName = Path name of the file to use for logging activities

This key specifies the path name of a file to be used to log selective activity that occurs during a run. The name may contain spaces; you do not need to enclose the name in double quotes (they will be ignored if used).

If you do not specify this name, the following keys have no effect.

IntialOpen

InitialOpen = OVERWRITE | APPEND

This key specifies if you want the activity for this run appended to the end of the current activity log (if one exists), or if you want the log deleted and replaced by the activity details of the new run. The default is to overwrite the current file.

LogOpens

LogOpens = YES | NO | TRUE | FALSE

If you set this key to YES or TRUE, each time the viewer initially opens a file for viewing, it is logged.

LogPrints

LogPrints = YES | NO | TRUE | FALSE

If you set this key to YES or TRUE, each time a printing operation terminates normally or abnormally, it is logged.

LogFontErrors

LogFontErrors = YES | NO | TRUE | FALSE

If you set this key to YES or TRUE, then a message is logged if a file being viewed or printed references a font for which there is not matching screen font defined.



[Preferences] SectionThis section describes the keys used to direct print and PDF output.

PrintAllByDefault

PrintAllByDefault = ON | OFF | TRUE | FALSE

The PrintAllByDefault key selects the initial default settings of the All and Page options in the Print Range group of the standard Print dialog box. If PrintAllByDefault is ON or TRUE, the All option is selected when the first Print dialog box is opened. If OFF or FALSE, the Page option is selected with a page range limited to the current page. If the user changes this selection before printing, the new selection is used the next time the Print dialog box is opened.

AdjustPdfWriterFileName

AdjustPdfWriterFileName = ON | OFF | TRUE | FALSE

This key is provided to compensate for a bug in the Adobe Acrobat PDFWriter printer driver version 4.0. It affects only print output generated with the /P and /F options of the command line or the command string sent to the viewer DLL using the CMV_SendDDECommand API entry point. If the /F option is used to select a file name for the PDF output from the Acrobat PDFWriter, the PDFWriter currently appends an arbitrary .pdf to the end of the resulting output file name regardless of whether the file name already has an extension. If AdjustPdfWriterFileName is set to TRUE or ON, CompuBuild attempts to correct the resulting filename under the following conditions:

• The device name of the selected output printer contains the characters "PDF" or "pdf."

• Output is directed to a file specified by the /F command line option.

• After the print operation a file is created with a name consisting of the name specified on the /F option with .pdf appended to it.

• A non-zero length file with the name specified on the /F option does not exist.

The correction involves automatically renaming the incorrect file to the name specified on the /F option.


© 2011 - 2013 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change

without

notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO

REPRESENTATIONS OR

WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND

SPECIFICALLY

DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United State and other

countries.

All other trademarks used herein are the property of their respective owners.