open print release notes 6 - files.oceusa.com

Paris Boston Bristol www.sefas.com

Open Print

Release Notes 6.3

This manual, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. The content of this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Sefas Innovation. Sefas Innovation assumes no responsibility or liability for any errors or inaccuracies that may appear in this documentation. Except as per-mitted by such license, no part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Sefas Innovation, Inc.

All cited product names and logos are the respective property of their owners.

Document version: 6.3a© Sefas Innovation, 2009. All rights reserved.

© Sefas Innovation, 2009 1

BackStage 6.3 . . . . . . . . . . . . . . . . . . . . 3Decimal font support . . . . . . . . . . . . . . . . . . . 3FTP Connector . . . . . . . . . . . . . . . . . . . . . . . 3PDF linearization . . . . . . . . . . . . . . . . . . . . . . 3PDF font subsets . . . . . . . . . . . . . . . . . . . . . . 4PDF/A support . . . . . . . . . . . . . . . . . . . . . . . 4Widow/Orphan Composer API . . . . . . . . . . . . . . 5VPF viewer . . . . . . . . . . . . . . . . . . . . . . . . . . 5Arabic support . . . . . . . . . . . . . . . . . . . . . . . 5License files . . . . . . . . . . . . . . . . . . . . . . . . . 5Full Java VpfApi . . . . . . . . . . . . . . . . . . . . . . 5Encoding records with JDE/JDL calls in the beginning of a file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6DataLoader copybook support . . . . . . . . . . . . . 6Migration requirements and known issues . . . . . . 6

Techprint libraries (Windows only) . . . . . . . . . . . . . 6Python 2.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Font library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Dynamic fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . 6AFP Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

MiddleOffice/FrontOffice 6.3 . . . . . . . . . . 7Image placement options . . . . . . . . . . . . . . . . 7Default local plug-in naming . . . . . . . . . . . . . . 9Spreading content . . . . . . . . . . . . . . . . . . . . 10

Spread textual content . . . . . . . . . . . . . . . . . . . . 10Spread full content with styles . . . . . . . . . . . . . . . 10

Making Smart Form Group regions collapsible . . 10Radio button alignment . . . . . . . . . . . . . . . . 13Description field settings in Smart Form Theme . 14Image insertion in wizard . . . . . . . . . . . . . . . 16Use of clickable images as action buttons . . . . . 18Variables in Smart Form labels . . . . . . . . . . . . 20

User variable label fields . . . . . . . . . . . . . . . . . . . 20Substitution table label fields . . . . . . . . . . . . . . . . 21Smart Form action label fields . . . . . . . . . . . . . . . 21

Paragraph widows and orphans . . . . . . . . . . . . 21Decimal font support . . . . . . . . . . . . . . . . . . 22

Fontlist.xml file . . . . . . . . . . . . . . . . . . . . . . . . . . 22Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22WebServices API . . . . . . . . . . . . . . . . . . . . . 23SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Remake 6.3. . . . . . . . . . . . . . . . . . . . . . 24AFP Line Mode Normalization . . . . . . . . . . . . . 24

Line mode keywords . . . . . . . . . . . . . . . . . . . . . . 25PostScript Normalization . . . . . . . . . . . . . . . . 28

The TechMulti normalization engine . . . . . . . . . . . 28Configuration files . . . . . . . . . . . . . . . . . . . . . . . . 28Verifying third-party applications . . . . . . . . . . . . . 28Gathering the required resources . . . . . . . . . . . . . 29

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

Managing fonts and images . . . . . . . . . . . . . . 30Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

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

Overview of techmulti.cfg . . . . . . . . . . . . . . . . . . 30Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Overview of techmulti_ibin.cfg . . . . . . . . . . . 31Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Creating the batch file . . . . . . . . . . . . . . . . . 33Setting environment variables . . . . . . . . . . . . . . . 33Command line parameters . . . . . . . . . . . . . . . . . . 33Example command line . . . . . . . . . . . . . . . . . . . . 34Normalizing the stream . . . . . . . . . . . . . . . . . . . . 34Handling errors. . . . . . . . . . . . . . . . . . . . . . . . . . 35Locating the VPF output . . . . . . . . . . . . . . . . . . . 35

PDF Normalization. . . . . . . . . . . . . . . . . . . . 35LCDS and Metacode Engines Merged . . . . . . . . 35

Tablei Editor . . . . . . . . . . . . . . . . . . . . . 36Edit Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Manage Table Rows. . . . . . . . . . . . . . . . . . . . . . . 37Filter Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

2 Open Print 6.3 Release Notes


B a c k S t a g e 6 . 3Dec ima l f o n t s uppo r t

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

BackStage 6.3

Decimal font support

BackStage 6.3 supports decimal fonts that allow you to specify font sizes in increments of 0.01. Decimal font support facilitates the precise conversion of legacy documents that must be converted for use with new hardware.

The "S" composer command now accepts decimal numbers that are specified within the body of the command. For example, the following command would be used to set the font to Bold with a size of 12.8:

S12.8G

FTP Connector

BackStage 6.3 supports the FTP Connector that is delivered with FrontOffice. The FTP Connector is integrated with SMD and provides FTP/FTPS capabilities to upload or download files from a client to a server.

PDF linearization

BackStage 6.3 supports FastWEB PDF, also known as PDF linearization, to optimize PDF viewing behavior. When a PDF is loaded, this feature immediately displays a requested page while loading the remainder of the file, so that by the time the first page has been read, the next page is also immediately available. This feature is especially useful for larger PDF files that can take some time to download.

To activate linearization for PDF files, you must add the following keyword to the PDF section of the drivers.cnf file:

Keyword Description

linearization Sets the PDF linearization flag for a PDF file in Adobe Reader so that the first page of a PDF file is displayed to the user while the remainder of the document is downloaded.

Value:

• 1 (Default value)

Activates PDF linearization for PDF files.

For example:

linearization=1


B a c k S t a g e 6 . 3PDF f o n t s ub se t s

PDF font subsets

BackStage 6.3 supports PDF font subsets to minimize the size of output PDFs. To activate font subsets for PDF files, you must add the following keyword to the PDF section of the drivers.cnf file:

PDF/A support

BackStage 6.3 supports PDF/A-1a and PDF/A-1b. PDF/A is a file format that is used for the long-term archiving of electronic documents.

PDF/A is based on PDF Reference Version 1.4 from Adobe Systems Inc. (implemented in Adobe Acrobat 5 and latest versions), and is defined by ISO 19005-1:2005, an ISO Standard that was published on October 1, 2005.

The standard specifies two levels of compliance for PDF files:

• PDF/A-1a - Level A compliance in Part 1 • PDF/A-1b - Level B compliance in Part 1

PDF/A-1b has the objective of ensuring reliable reproduction of the visual appearance of the document. PDF/A-1a includes all the requirements of PDF/A-1b and additionally requires that document structure be included (also known as being "tagged"), with the objective of ensuring that document content can be searched and repurposed.

Keyword Description

font_subset Reduces the size of an output PDF by embedding only those character definitions that are used in a document instead of embedding complete fonts. For a font to use the font subset feature, it must satisfy the following conditions:

• The font must be external and not the result of a previous normalization step.

• The font must be of either a TrueType or bitmap format (type1 fonts cannot be used).

• The font must be defined as embedded by either:

• Setting the embed_fonts flag in the drivers.cnf file (for example, embed_fonts=1).

• Setting the load flag (for example, load=yes) in the .fnt file for the driver that is being used.

Value:


Activates font subsets for PDF files.

For example:

font_subset=1


B a c k S t a g e 6 . 3Widow/O rph an Compose r AP I

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

Widow/Orphan Composer API

MiddleOffice 6.3 includes support for widow/orphan lines that originate from the beginning or end of a paragraph. When displayed, these lines are separated from the rest of the paragraph and appear at the top or bottom of a page or column. Rules that determine widow/orphan behavior for a paragraph can now be set within MiddleOffice as additional rendering attributes for a paragraph. When using the Widows/Orphans feature, please be aware of the following:

• The widows/orphans rule is defined within the MiddleOffice interface along with the other properties of the paragraph.

• The Composer API cuts the paragraph into lines according to the widows/orphans rule.• The widows/orphans rule is ignored if a carriage return is found in the paragraph.• The Composer API only works in conjunction with MiddleOffice, and cannot be called directly

via a Composer command.

For more information on using widow/orphan rules in MiddleOffice, see Paragraph widows and

orphans on page 21.

VPF viewer

BackStage 6.3 includes a new version of the VPF Viewer.

Arabic support

BackStage 6.3 includes support for Arabic fonts and Arabic text.

License files

BackStage 6.3 allows license files to be used in your Open Print environment:

• Static licenses: Licenses that are restricted to specific IP addresses. These licenses let users run Open Print on machines without network access.

• Floating licenses: Licenses that are not restricted to specific IP addresses. This allows more flexibility for customers who might, for example, have numerous staff who can use Open Print, but require only five to use it at any given time.

For more information, see the Open Print Installation Guide Version 6.3.

Full Java VpfApi

For Backstage 6.3, the JniVpfApi has been deprecated and VPF and image manipulations within Open Print are now controlled by a full Java vpfapi component. The Java vpfapi has some currently known limitations:

• Advanced functions such as shading, dithering, clipping, stretching, skewing, etc. are not supported by the viewer.

• Opacity and transparency are not managed by the viewer.• Some special encodings are not supported, so displayed text cannot be read.


B a c k S t a g e 6 . 3Encod i n g r e co r d s w i t h JDE / JDL c a l l s i n t h e beg i nn i ng o f a f i l e

Encoding records with JDE/JDL calls in the beginning of a file

BackStage 6.3 allows you to encode a record containing a JDE/JDL call at the beginning of the file by using the dynamic_jsl_call keyword. For more information, see the Open Print Operating

Manual.

DataLoader copybook support

BackStage 6.3 includes support for COBOL COPYBOOK input streams.

Migration requirements and known issues

Techprint libraries (Windows only)

The Techprint libraries used by Open Print Studio, Remake, and MiddleOffice now use MultiThread mode on Windows systems. While MultiThread mode is compatible with all V6 and later C++ compilers, any external C++ libraries will need to be recompiled in MultiThread mode in order to be used by an application.

Python 2.6

Python 2.6 is required by BackStage 6.3. If you have created any scripts that use accents, you must add the following to the head of the script:

#!/usr/bin/python

# -*- coding: latin-1 -*-

Font library

The font library in Backstage 6.3 has changed to support FreeType 2.3.9. This support was included so that inter-character widths and heights can differ by a maximum of 2 picas from those specified in BackStage 6.2.

Dynamic fonts

The Composition and Rendering engines now support and use dynamic fonts. Dynamic fonts are converted automatically without requiring the specification of metrics, which can change the size of characters by a maximum of one pica.

If you do not wish to use dynamic fonts, continue to use your original font environment that was installed at the following location, by default:

$opInstallDir/common/chasse/

AFP Driver

For Backstage 6.3, the APF driver rounds all non-orthogonal rotations to the nearest square angle (for example, either 0, 90, 270, or 360 degrees).

Note On some older machines, it is possible to receive either of the following errors:

• LDR: LdrpWalkImportDescriptor() failed to probe python26.dll for its manifest, ntstatus 0xc0150002

• "loadlibrary failed"

To resolve this issue, please install vcredist_x86.exe.

Note If tabulations are used in a document, a difference of one point can cause text to jump to the next tabulation.


M i d d l e O f f i c e / F r o n t O f f i c e 6 . 3Image p l a c emen t op t i o n s

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

MiddleOffice/FrontOffice 6.3

Image placement options

There are two options for placing images in templates:

• As a LOGO: If you select this, the following apply :• By default the image is aligned to the left. You cannot change this alignment.• The image placement does not modify the current location of subsequent resources in

the template tree. For example, if text comes after the image, inserting an image does not move the text.

• The image is factorized in the output stream. Therefore, if the image is present on every page in an output stream, the image only needs to be present once in the data stream.

• Gauged: If you select this, the following apply:• The subsequent resources in the template tree are moved down so that they are

located under the image.• You can set the alignment of the image: left, center, or right.• The image cannot be factorized in the output stream.

If you select As a LOGO, the Factorization and Alignment fields are dimmed out.

If you select Gauged, select one of the following from the Alignment drop-down list:

• Left: Aligns the image on the left.• Center: Aligns the image in the center.• Right: Aligns the image on the right.


M i dd l e O f f i c e / F r o n t O f f i c e 6 .3Image p l a c emen t op t i o n s

To apply Factorization, select the Factorization check box.


M i d d l e O f f i c e / F r o n t O f f i c e 6 . 3De fau l t l o c a l p l ug - i n n am i ng

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

Default local plug-in naming

When you create a new plug-in in MiddleOffice 6.3, the default name reflects the plug-in type. For example, if the new plug-in is a macro, the default name is New Macro.

To create a new plug-in, do the following:

1. Select File>New>Plug-in....

2. Select a plug-in type in the dialog box, then click OK.

3. The new plug-in opens in a tab with the default name reflecting the type of plug-in. To change the plug-in name, type the name in the Name field.


M i dd l e O f f i c e / F r o n t O f f i c e 6 .3Sp re ad i ng c on t en t

Spreading content

You can copy content from one conditional resource tab to selected conditional resource tabs for resources in a template. You can also spreading content to all other conditional paragraph tabs. For conditional paragraphs, you can also copy text to the other tabs.

Right-click in a tab to display the following options:

• Spread textual content (without styles)• Spread full content with styles

Spread textual content

If you select Spread textual content without styles, text only from that tab is copied to other tabs. No paragraph formatting is copied.

To spread textual content without styles, right-click this item in the menu. Several check boxes appear in a sub-menu: one labeled Spread to all tabs and the rest labeled with the other condition names. Do one of the following:

• To spread content to all of the other tabs in that conditional paragraph, select Spread to all tabs.

• To spread the content to selected tabs, select the appropriate check box(es) next to the names of those to which you want to spread content.

Spread full content with styles

If you select Spread full content with styles, the text and all formatting associated, such as borders and style attributes, is copied into the other tabs.

To do this, right-click, then select Spread full content with styles. Several check boxes appear in a sub-menu: one labeled Spread to all tabs and the rest labeled with the other condition names. Do one of the following:

• To spread content to all of the other tabs in that condition, select Spread to all tabs.• To spread the content to selected tabs only, select the appropriate check box(es) next to the

names of those to which you want to spread content.

Making Smart Form Group regions collapsible

You can make the North region of a Smart Form Group collapsible, as follows:

1. Click on the Smart Form Group, then expand the Smart Form Group attribute panel on the right.

2. Under Specifics, select Collapsible panel in the Layout drop-down list.


M i d d l e O f f i c e / F r o n t O f f i c e 6 . 3Mak i ng Sma r t Fo rm G rou p r e g i on s c o l l a p s i b l e

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

3. If desired, select an image to represent the Expand and Collapse icons by clicking on the

search button to the right of those fields in the attribute panel. The select an image from the appropriate domain in the dialog box.

The image below shows a Smart Form Group when not collapsed.


M i dd l e O f f i c e / F r o n t O f f i c e 6 .3Mak i ng Sma r t Fo rm G r oup r eg i o n s c o l l a p s i b l e

The following image shows a Smart Form Group when collapsed.


M i d d l e O f f i c e / F r o n t O f f i c e 6 . 3Rad i o bu t t on a l i g nmen t

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

Radio button alignment

In addition to the default vertical alignment, you can align radio buttons and check boxes horizontally in wizard forms.

To do this, open the user variable Scenario editor, then select the Horizontal radio button in the Alignment field. In the example below, the user has selected radio buttons as the type of wizard control.

After selecting horizontal alignment, the radio buttons appear horizontally in the wizard.

Note You can set the alignment for radio buttons and check boxes, but not combo boxes or list boxes, even though the Scenario form shows the choice. All combo boxes and list boxes are shown as vertical lists in the wizard.


M i dd l e O f f i c e / F r o n t O f f i c e 6 .3Des c r i p t i o n f i e l d s e t t i n g s i n Sma r t Fo rm Th eme

Description field settings in Smart Form Theme

In Smart Forms you can control the appearance of the Description area by setting its parameters independently of the other Smart Form Theme parameters.

The Description area of a Smart Form refers to the area containing the titles/labels for the radio buttons and other controls under it. In the example below, this is the darker-shaded area on the left where the Select Plan, Select Status, and Edit Last? headings appear.

The following parameters can be controlled:

• Description label font• Description area background color• Description area width

These options are set inside the wizard theme editor, under the Description section.


M i d d l e O f f i c e / F r o n t O f f i c e 6 . 3Des c r i p t i o n f i e l d s e t t i n g s i n S ma r t Fo rm Theme

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

To set the parameters for a Smart Form theme, open the theme editor, then set the following under the Description setting:

• Font

Select a font and size from the drop-down lists, then select the Manual radio button. If you want the font to be bold or italic, click the appropriate buttons.

• Width

Type the desired width in the Width field, then select the Manual radio button. You might want to increase the width if, for example, a label in the Description area is too long to fit in the defined space.

Note To match existing behavior and grant compatibility, you can set these parameters manually or automatically (inherited from the global theme parameters), with the Automatic option set by default.

Each parameter is set individually; there is an Automatic radio button for each parameter.


M i dd l e O f f i c e / F r o n t O f f i c e 6 .3Image i n s e r t i o n i n w i z a r d

• Background color

Select a color from the drop-down list, then select the Manual radio button. In the image on the previous page, the background color of the Description area is darker than the background color of the rest of the Smart Form. You might want to use this option in order to set the Description area apart. The image below shows the user selecting the color to match the rest of the Smart Form.

Image insertion in wizard

In addition to inserting images in a document template, you can insert images in a wizard. These images are not clickable and have no action associated with them, but are used to enhance the appearance of the wizard form.

To insert an image into a wizard, do the following:

1. In the Smart Form template tree, right-click the resource under which you want to insert the resource, then select Insert>Wizard Image.


M i d d l e O f f i c e / F r o n t O f f i c e 6 . 3Image i n s e r t i o n i n w i z a r d

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

2. Click one of the following buttons in the wizard image editor:

• Import: Lets you import an image saved on your workstation.• Clipboard: Lets you paste the contents of the clipboard into the new image.

3. Set the attributes in the Attribute panel.


M i dd l e O f f i c e / F r o n t O f f i c e 6 .3Use o f c l i c k ab l e image s a s a c t i on bu t t o n s

4. Save the image.

5. The new image appears in the designated region in the wizard.

Use of clickable images as action buttons

In addition to standard action buttons, MiddleOffice 6.3 lets you depict action buttons as the following:

• Clickable images• Standard action buttons containing an image

To do this, follow the normal steps for creating an action button. In the button Type drop-down list, select one of the following:

• Standard button to use the standard action button.• An image in the button to paste a graphic within the standard action button. If you select this

option, select an option from the imagePosition drop-down list, then drag and drop an image file from the resource list into the associatedImage field.


M i d d l e O f f i c e / F r o n t O f f i c e 6 . 3Use o f c l i c k ab l e image s a s a c t i o n bu t t on s

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

• The button is an image to replace the standard button with an image; for example, a clickable arrow graphic replaces the Next or Previous action button. If you select this option, drag and drop an image file from the resource list into the following fields:

• raisedImage: This is the image that appears when the action button appears raised; that is, when it is in its default, non-activated state. If no Button raised image is set, the standard button displays.

• downImage: This is the image that appears when the user clicks the action button. If no Button down image is set, the image set for Button raised also appears when the button is clicked.

6. Save the template by clicking File>Save Template. The button appears on the new template.


M i dd l e O f f i c e / F r o n t O f f i c e 6 .3Va r i a b l e s i n Sma r t Fo rm l a b e l s

Variables in Smart Form labels

You can now insert variables into the following:

• User variable label fields• Substitution table label fields• Smart Form action label fields

User variable label fields

To insert a variable into a user variable label field, drag and drop a variable from the dataloader panel into the Label field.


M i d d l e O f f i c e / F r o n t O f f i c e 6 . 3Pa rag raph w i dows and o rphan s

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

Substitution table label fields

Smart Form action label fields

Paragraph widows and orphans

You can set widow and orphan controls in a paragraph when that paragraph is breakable, as follows:

1. Select Everywhere in the Divisibility>Breakable drop-down list. This allows more flexibility in where the paragraph can break, rather than only allowing it to break at a carriage return.

2. Use the arrows to select the values in the following fields:

• Orphans: Determines the minimum number of allowable lines from the beginning of a paragraph at the bottom of a page. You can define up to four lines.

• Widows: Determines the minimum number of allowable lines from the end of a paragraph at the top of a page.


M i dd l e O f f i c e / F r o n t O f f i c e 6 .3Dec ima l f on t s u ppo r t

Decimal font support

MiddleOffice 6.3 supports decimal fonts that allow you to specify font sizes in increments of 0.01. To use decimal fonts, you must edit the fontslist.xml file.

Fontlist.xml file

The fontlist.xml file defines the fonts available on your production system, and you must edit this file to use decimal font sizes. To declare a decimal font, do the following:

1. Open the fontlist.xml file using the editor of your choice ($InstallDir/home, by default).

2. Locate the font definition you wish to change, then edit the <SIZELIST> tag as follows:

<SIZELIST type="decimal">

The type="decimal" attribute specifies that decimal font sizes are allowed for this font.

3. Optionally, you can also edit the list of standard sizes to include decimal values. For example:

<SIZE attrs="BI"> 5 6 6.5 7 7.5 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 30 40 50 60</SIZE>

This font definition permits any size between the minimum and maximum values, including integer values. Decimal fonts are identified in the user interface by non-integer display values, such as 11.00 rather than 11.

4. When you are satisfied with you edits, save the file.

Zones

MiddleOffice 6.3 includes enhanced support for Zones that allow all possible combinations of absolute and relative position, and all widths and heights.


M i d d l e O f f i c e / F r o n t O f f i c e 6 . 3WebSe r v i c e s AP I

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

WebServices API

FrontOffice 6.3 provides a standard WebServices interface API that can be accessed by an application server context or WSDL definition. The WebServices API is used to activate Open Print assembly, composition, and rendering engines.

For more information, see Open Print FrontOffice 6.3 Guide to FrontOffice.

SSL

MiddleOffice, FrontOffice, and Projector 6.3 include support for https protocols. The implementation of SSL in these products is based on standard libraries and supports the standard set of certificates.


R e m a k e 6 .3AFP L i n e Mode No rma l i z a t i o n

Remake 6.3

AFP Line Mode Normalization

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

[COMMON]

verbose=-1

stderr=stderr.txt

stdout=stdout.txt

show_file_offset=yes

statistic_file=stat.txt

include_overlay_mode=vpf

include_pageseg_mode=vpf

dump_resource=0

input_format=fixed_flat

record_length=16

input_type=mixed_mode

carriage_control=ansi

page_def_name=P1SEFAS3

form_def_name=F1SEFAS4

font_embedding=1

use_index_file=0

barcode_mode=keep

resource_map=ttf_map.txt


R e m a k e 6 . 3AFP L i n e Mode No rma l i z a t i o n

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

Line mode keywords

The following is a list of keywords that are specific to AFP line mode and mixed mode streams.

Keyword Description

carriage_control Specifies the type of carriage controls that drive the PAGEDEF.

Possible values:

• none (default value)

No carriage controls are used.

• ansi

ANSI carriage controls are used.

• machine

Machine carriage controls are used.

For example:

carriage_control=ansi

chars Declares up to four coded fonts during the analysis of a stream.

Possible values:

• none (default value)

No declared coded fonts.

• XFONT1,XFONT2,XFONT3,XFONT4

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

For example:

chars=X0TR12NP

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

default_charset Specifies the default charset. This charset is used:

• If no font is declared in an AFP page• If a font is declared in a MCF with an unknown GRID codeFor example:

default_charset=C0S0CR12

The keywords default_charset and default_codepage must be used together.


R e m a k e 6 .3AFP L i n e Mode No rma l i z a t i o n

input_format Specifies the format of the input file.

Possible values:

• variable_flat (default value)

The input file is a flat file with records of variable length. This is the standard MO:DCA format.

• fixed_flat

The input file contains 0x0D 0x25 terminated records.

• variable_native

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

• fixed_native

The input file is an FB dataset file.

• xmit_flat

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

• cr_lf


• bl_rl

The input file contains block length + record length prefixed records.

• block

The input file is a FTP block mode file.

• rl

The input file contains record length prefixed records.

For example:

input_format=xmit_flat

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

input_type Specifies the nature of blocks of the AFP stream. Possible values:

• modca (default value)

Blocks are records in MO:DCA format.

• line_mode

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

For example:

input_type=line_mode

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

For example:

page_def_name=P1SEFAS4

pagedef_dir Specifies the output path for the PAGEDEF. This overrides the path specified in res_dump_folder.

Use dump_resource to specify whether resources remain in this directory after normalization, or are only placed here temporarily and then deleted.

Keyword Description


R e m a k e 6 . 3AFP L i n e Mode No rma l i z a t i o n

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

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

Possible values:

• 0 (default value)

The length of records is not specified.

• [length]

The length of records is a fixed size (in octets).

For example:

record_length=8205

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

The format of the actual stream must be specified with the input_format parameter.

Possible values:

• variable_flat (default value)

The input file is a flat file with records of variable length. This is the standard MO:DCA format.

• fixed_flat


• variable_native

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

• fixed_native

The input file is an FB dataset file.

• xmit_flat

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

• cr_lf


• bl_rl

The input file contains block length + record length prefixed records.

• block

The input file is a FTP block mode file.

• rl

The input file contains record length prefixed records.

For example:

res_input_format=variable_flat

use_trc Specifies whether the stream contains table reference characters.

Possible values:

• no (default value)

The stream contains no table reference characters.

• yes

The stream contains table reference characters.

For example:

use_trc=no

Keyword Description


R e m a k e 6 .3Pos t S c r i p t No rma l i z a t i o n

PostScript Normalization

Open Print Remake supports normalization of PostScript files.

PostScript normalization converts a PostScript data stream into a Virtual Page Format (VPF) file.

PostScript resources may be inline or external to the stream. Inline resources are processed automatically during normalization.

PostScript normalization is not available in the Remake user interface. You need to use the following to perform a PostScript normalization:

• The input .ps file• The TechMulti normalization engine, as identified in the next section• A batch file to set the environment variables and run the command line parameters

necessary to perform normalization. Sefas supplies a batch file sample; you can modify this to meet your organization’s needs.

Two additional files, techmulti.cfg and techmulti_ibin.cfg, may also be used to set configuration options for the normalization engine.

The PostScript normalization process includes:

• Analyzing the .ps file to determine its contents• Setting optional configuration keywords and values, if needed• Executing the command line using a batch file

If you are running Windows, PostScript normalization also requires a hardware USB dongle and associated third-party software to validate licensing information. For more information about these requirements, see the Open Print Prerequisites Guide or contact Sefas Customer Support.

The TechMulti normalization engine

The TechMulti normalization engine converts a PostScript data stream into a VPF file.

A batch file executes the normalization engine using a set of runtime parameters.

For example, the -i parameter sets the access path to the PostScript input stream. For more information on available parameters, see Command line parameters on page 33.

Configuration files

Additional processing options for the engine are set using two optional configuration files

• techmulti.cfg - The file contains keywords that can be used to set special options for processing the PostScript data stream.

• techmulti_ibin.cfg - This file is used to set options for printer trays.

The configuration files are edited using a standard text editor. For the syntax and keywords, see Configuring the normalization engine on page 30.

Verifying third-party applications

For all supported platforms, PostScript normalization requires Adept Suite software. Adept Suite provides files required by the TechMulti engine.

Under Windows, PostScript normalization also requires:

• Sentinel Protection software and USB dongle - These are required by Adept for authentication purposes.

Note All the Adept and, if necessary, Sentinel components are provided by Sefas at install time.


R e m a k e 6 . 3C rea t i n g t h e app l i c a t i on d i r e c t o r y s t r u c t u r e

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

Sefas also recommends that you have a:

• PostScript viewer installed on the computer where you perform the normalization. Ghostview is recommended on UNIX and GSView is recommended for Windows. Both of these programs require GhostScript.

• PostScript printer connected to the computer for testing purposes.

Gathering the required resources

Before launching a PostScript normalization, you should:

• Gather and have available a selection of the original printed and electronic PostScript documents as a reference.

• Review and assess the nature of the resources to be normalized.

Creating the application directory structure

While virtually any directory structure can be used to perform the normalization, it is helpful to use a standard directory structure and standard naming conventions.

Creating project directories

Sefas recommends you use a directory structure based on the following environment variables:

opWd - The working directory that acts as the group entry point

opFam - The group directory

opAppli - The application directory that contains all the subdirectories and files needed to run normalization

A sample directory structure follows:

In the sample above:

normalization is the opWd directory.

samples is the opFam directory.

ps_sample is the opAppli directory.

In addition, the opInstallDir variable is used to define the installation directory path (often C:\oprint). All of the above variables are used in the command line to execute the engine.

Note For detailed system and software requirements, see the Open Print Prerequisites Guide or contact Sefas Customer Support.

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

Operating Manual.


R e m a k e 6 .3Manag i ng f o n t s and image s

Managing fonts and images

Fonts

PostScript normalization automatically includes fonts that are embedded in the PostScript file in the VPF.

PostScript supports Type1 and Type3 fonts as input. PostScript does not support TrueType fonts.

In the VPF file, fonts are rendered as 300 dots per inch (DPI) bitmap fonts.

Images

Images are converted as follows:

• Black and white images (colorized or not) to TIFF• Color images to JPEG

Preparing the input file

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

Copy the file you want to normalize to:

C:\normalization\samples\ps_sample\spool

For example:

C:\normalization\samples\ps_sample\spool\ps_sample.ps

Configuring the normalization engine

Overview of techmulti.cfg

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

The configuration file is made up of one or more sections, such as [psnormalize], followed by keywords. Each keyword contains a value that corresponds to a process to be carried out on the stream.

The following is an example of the techmulti.cfg configuration file.

[psnormalize]

verbose=1

page_information=1

comment filter=%%MSD;%%KLF

Note A sample PostScript file, named ps_sample.ps, is provided with the sample application in the ..\ps_sample\spool directory. You can substitute the sample file with any PostScript file you would like to normalize.


R e m a k e 6 . 3Ove r v i ew o f t e c hmu l t i _ i b i n . c f g

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

Keywords

The following is a list of keywords that can be used in the techmulti.cfg configuration file.

Overview of techmulti_ibin.cfg

This optional configuration file can be used to preserve the tray selection settings from the PostScript file and translate them in the VPF file.

This file is enabled by the keyword page_information=1 in the techmulti.cfg configuration file.

Example 1

<<

/MediaType (BIN2)

/Duplex false

/PageSize [612 792]

>> setpagedevice

This calls the input tray named IBIN 2 ($IBIN 2 composer equivalent), providing that Techmulti_ibin.cfg contains the following:

Keyword Description

comment_filter Specifies whether to extract comments from the PostScript file and embed them in the VPF.

For example:

comment_filter=%% MSD; %% KLF

The above example extracts all comments starting with %% MSD or %%KLF

In the VPF output this will appear as:

DRV NOTE + BPAGE "%% MSD....."

DRV NOTE + BPAGE "%% KLF....."

page_information Enables the processing of printer tray information in accordance with the configuration file, techmulti_ibin.cfg.

Possible values:


No printer tray information is specified.

• 1

Printer tray information is set in accordance with techmulti_ibin.cfg.

For example:

page_information=1

For more information, see Overview of techmulti_ibin.cfg below.

verbose Specifies whether to display debugging information in the trace logs.

Possible values:

• 0

No debugging information is displayed.

• 1

Displays the debugging information on the command line.

Note This option activates the PostScript /Duplex and /Tumble commands.


R e m a k e 6 .3Ove r v i ew o f t e chmu l t i _ i b i n . c f g

<<

/IBIN1

<<

/MediaType (BIN1)

/PageSize [612 792]

>>

/IBIN2

<<

/MediaType (BIN2)

/PageSize [612 792]

>>

/IBIN3

<<

/MediaType (BIN3)

/PageSize [612 792]

>>

/IBIN4

<<

/MediaType (BIN4)

/PageSize [612 792]

>>

>>

Example 2

<<

/MediaPosition 2

/Duplex false

>> setpagedevice

The following can be used to select IBIN 2:

<<

/IBIN1

<<

/MediaPosition 1

>>

/IBIN2

<<

/MediaPosition 2

>>

/IBIN3

<<

/MediaPosition 3

>>

/IBIN4

<<

/MediaPosition 4

>>


R e m a k e 6 . 3C rea t i n g t h e b a t c h f i l e

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

Creating the batch file

Setting environment variables

Use the batch file to set environment variables and enter command line parameters necessary to run the normalization. Environment variables consist of the directory structure and information about the file to be normalized. For example:

set opInstallDir=C:\oprintset opWD=C:\normalizationset opFam=samplesset opAppli=ps_sample

The command line consists of the name of the executable that runs normalization (techmulti.exe), along with parameters and environment variables used to determine how the engine processes the file. For example:

%opInstallDir%\bin\techmulti.exe -E opInstallDir=%opInstallDir% -E opWD=%opWD% -E opFam=%opFam% -E opAppli=%opAppli% -i ps_sample.ps -o %opWD%\%opFam%\%opAppli%\printer\ps_sample.vpf -C %opInstallDir%\common\config\ps\techmulti.cfg -S psnormalize

pause

See Entering Command Line Parameters below for more information.

Command line parameters

Use the following case-sensitive parameters in the command line for running the TechMulti normalization engine:

Parameter Description

-C file_name Indicates the name of the optional configuration file (*.cfg) used for Post-Script normalization, for example techmulti.cfg.

-E Sets the environment variables for the application. This parameter is required.

-E opInstallDir= Sets the environment variable to indicate the access path for where the product is installed, including the bin and common subdirectories.

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

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

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

-f Generates an intermediate PDF copy during normalization.

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

-i file_name Indicates the location and name of the input PostScript file. This parameter is required.

-o file_name Indicates the location and name of the output VPF file. This parameter is required.

-ps n Starts the normalization at page n.

-pe n Stops the normalization at page n.

-S section_name Indicates the section of the configuration file to be used.

-v Corresponds to the verbose keyword. -v 1 displays debugging information dur-ing the normalization.


R e m a k e 6 .3C rea t i ng t h e b a t c h f i l e

Example command line

%opInstallDir%\bin\techmulti.exe -E opInstallDir=%opInstallDir% -E opWD=%opWD% -E opFam=%opFam% -E opAppli=%opAppli% -i ps_sample.ps -o %opWD%\%opFam%\%opAppli%\printer\ps_sample.vpf -C %opInstallDir%\common\config\ps\techmulti.cfg -S psnormalize

pause

The example command line above does the following:

%opInstallDir%\bin\techmulti.exe - The directory path to the executable (normalization engine) that runs normalization.

-E opInstallDir=%opInstallDir% - The directory path to the installation directory environment variable.

-E opWD=%opWD% - The environment variable pointing to the Open Print working directory (group entry point).

-E opFam=%opFam% - The environment variable pointing to the name of the group application.

-E opAppli=%opAppli% - The environment variable pointing to the application name.

-i ps_sample.ps - The name of the PostScript input file to be normalized. Unless path information is specified, the engine assumes the file is located in spool directory of the application.

-o %opWD%\%opFam%\%opAppli%\printer\ps_sample.vpf - The directory path and name of the output file. In this example, ps_sample.vpf is output to the printer directory of the application.

-C %opInstallDir%\common\config\ps\techPostScript.cfg - The directory path and filename of the optional configuration file.

-S - The section of the configuration file used in normalization - [psnormalize].

Normalize PostScript files outside of the Remake user interface using the following files:

• techmulti.exe - The executable for the normalization engine entered on the command line.• PostScript input file - The .ps file to be normalized, such as ps_sample.ps.• techmulti.cfg - The optional configuration used to set keywords that determine how

normalization is accomplished.• techmulti_ibin.cfg - The optional configuration file used to preserve printer tray settings

from the PostScript file. • normalize.bat - Command line batch file that contains environment variables and

executable (techmulti.exe) necessary for normalization. When you execute this file, normalization runs.

Normalizing the stream

Run a PostScript normalization as follows:

1. Insert the dongle into an available USB port on your computer.

2. Make sure the .ps file you want to normalize is in the spool directory. For example:

C:\normalization\samples\ps_sample\spool\filename.ps

3. If applicable, edit techmulti.cfg in a text editor and add/edit keywords and values. For more information, see Overview of techmulti.cfg on page 30.

4. If applicable, edit techmulti_ibin.cfg in a text editor to configure printer tray information. For more information, see Overview of techmulti_ibin.cfg on page 31.

5. Create and edit the batch file normalize.bat to set the environment variables and any command line parameters you want to run during normalization. For more information and examples, see Creating the batch file on page 33.

6. Execute the batch file to run normalization.


R e m a k e 6 . 3PDF No rma l i z a t i o n

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

Handling errors

If you receive an error message during the normalization, try opening the PostScript file with a recent version of GhostView. If an error occurs in Ghostview, the PostScript file may be corrupt. Contact Sefas Customer Support for assistance.

Following are some limitations of the TechMulti engine:

• External resources cannot be found by TechPCL.• There is a limit of 65535 objects per page in the VPF. • Clipping is not supported.

Locating the VPF output

The VPF file is output to the directory that is specified using the -O parameter. Following the sample above, this is the printer directory. For example:

C:\normalization\samples\ps_sample\printer\ps_sample.vpf

The VPF file contains all of the original fonts and resources.

PDF Normalization

Image clipping is available in PDF Normalization. The clipping limits the drawing of a set of objects to a pre-defined area (clipping zone), or to hide objects.

Clipping occurs automatically and no configuration file is used. Limitations of this implementation are:

• You can clip texts on a character basis, the area to be clipped is inside red box:

You cannot clip a character, so the results of this clipping are:

• You can clip images using a box shaped clipping path only:

The result of this clipping is:

LCDS and Metacode Engines Merged

The techlcds engine can normalise the merged LCDS/Metacode streams. This new engine can also work in the old mode (techxrx) in order to maintain backward compatibility.


T a b l e i E d i t o rLC DS and Me t a code Eng i n e s Me rged

Tablei Editor

The tables editor is a generic tool to edit Open Print configuration tables (tablei files with extension *.tab in folder tablei). For ADF-specific cases, this editor can help the user configure daily production. In Front Office applications, this editor could be an option to display business configuration tables to the end user before triggering the T.P. process of on-line document creation.

When editing a table, access the table content in one of the following ways:

3 ways of accessing a table content:

• Select tables from the combo list and then select Table Set Selection > Table Selection.• Double-click in the dependant tables combo-list.• Link to the dependant table using the columns header of the table or in the form next to the

combo list.

Edit Tables

Edit table content as follows:

1. Select the row that contains the information you want to modify.

2. Click the Edit button in the toolbar. The form displays the content of the selected row.

3. In the input form panel click the next/previous icons to navigate through the rows highlighted in the table.

4. Complete the form's fields, for example text/figures/date or information selection in a combo list linked to a dependent table.

5. Double-click in a cell to change the values using the dropdown list attached to the cell.

Select information from the dropdown list or type in text, date (input control) in a single value not linked to an external table.


T a b l e i E d i t o rLCDS and Me t a c ode En g i n e s Me r ged

Op

en

Prin

t 6

.3 R

ele

ase

Note

s

Manage Table Rows

Add or delete rows from a table in one of the following ways:

• Right-click in the table and select one of the following from the popup menu:• insert row after• insert row before• remove row• move row up• move row down• duplicate row after• duplicate row before

• Select one of the following toolbar buttons:• Duplicate• Add

Filter Tables

You can use the filter panel to:

• Select which columns you want to display in the table.• Filter which rows to display based on their content.

Access the filter panel by selecting the Filter... button:


T a b l e i E d i t o rLC DS and Me t a code Eng i n e s Me rged

open print release notes 6 - files.oceusa.com

Documents