Adobe Output Designer

Version 5.7

Readme File

March 2009

Edition 3.0

Copyright 2009 Adobe Systems Incorporated. All rights reserved.

This file contains important information that was not available when the product documentation was written. Review this information before running this version of Adobe Output Designer.


Contents

What's New

Supported Platforms and System Requirements

Known/Resolved Issues

·  List of Supported Barcodes Not Updated

·  Character Spacing

·  Achieving Better Fidelity Between PCL and PDF Output

·  Greek Characters Delta and Omega Do Not Display Correctly in Adobe Reader

·  Spell Checking Text on Grouped Objects

·  Improved Dialog Box Font for Simplified and Traditional Chinese Systems

·  Importing IFD Template Designs

·  Cursor Behavior

·  Extended Characters in Template File Names

·  Boilerplate Containing Text Substitution Fields Do Not Print Using Test Presentment

·  Documentation - Output Designer version numbers

The Documentation Set

Licenses and Copyrights


What's New

The What's New document (WhatsNew.pdf) contains details on the new features added to Adobe Output Designer for this release.

Back to Contents


Supported Platforms and System Requirements

The following are the supported Microsoft Windows platforms for Output Designer 5.7:

Supported Platform

Supported Version

Microsoft Windows 2003  (x86)

Server - Service Pack 2

Microsoft Windows 2008  (x86)

Server - (32/64 bit)

Microsoft Windows XP (x86)

Service Pack 3

Microsoft Windows Vista (x86)

Service Pack 1

To run Output Designer on the platforms above, you require:

Back to Contents


Known Issues

List of Supported Barcodes Not Updated

The list of support barcode types has not been updated in the Output Designer Help.  For a list of barcode types that have been added to this release refer to the What's New document.

Back to Contents

Character Spacing

Changes were made in version 5.6 of Output Designer that improves the fidelity of the character spacing between PDF and PostScript output.

However, you can have Output Designer revert to the previous method of calculating character spacing, by changing the ICS file for the PDF presentment target and then updating the presentment target setup to reflect the change. To do so:

  1. Locate the file pdf.ics in the Output Designer \Config folder.
  2. Change the PrinterFlag value from 132 to 4228.
  3. Save and close pdf.ics.
  4. Click File > Presentment Targets.
  5. Ensure Portable Document Format (PDF) - [pdf] is the default target.
  6. Click Font Setup to display the Property sheets for the target.
  7. On the Font Cartridges tab, click OK.

Output Designer re-reads the ICS file and the new font information becomes available to the presentment target.

Back to Contents

Achieving Better Fidelity Between PCL and PDF Output

To achieve better fidelity between PCL and PDF output, you can change the resolution of the PDF driver to match that of the PCL driver. By default, the pdf.ics file sets the value of the Printer X and Printer Y resolution to 1000; however, you can change this to match the resolution of the PCL driver when using a multi-target .MDF that includes PDF and PCL presentment targets.

To set a new value for the Printer X and Printer Y resolution of the PDF driver in the pdf.ics file:

1.       Locate the file pdf.ics in the Output Designer \Config folder.

2.       Navigate to the lines:

·         PrinterXDPI 1000 ; Printer resolution – horizontal

·        PrinterYDPI 1000 ; Printer resolution - vertical

3.       Change the default resolution value of 1000 to your required resolution value. For example, to change the value of the resolution used by the PDF driver to 300, the file would read:

·         PrinterXDPI 300 ; Printer resolution - horizontal

·         PrinterYDPI 300 ; Printer resolution - vertical

4.       Save and close pdf.ics.

5.       Click File > Presentment Targets.

6.       Ensure Portable Document Format (PDF) - [pdf] is the default target.

7.       Click Font Setup to display the Property sheets for the target.

8.       On the Font Cartridges tab, click OK.

NOTE: You must recompile all forms compiled for the PDF driver to have these forms take advantage of the chang­es made to the pdf.ics file.

Back to Contents

Greek Characters Delta and Omega Do Not Display Correctly in Adobe Reader

The Greek letters delta (Unicode U+0394) and omega (Unicode U+2126) do not display correctly in Adobe Reader if the font is embedded in the PDF file. To work around the issue, open jetkeys.ini from c:\install path\Adobe\Output Designer\Config and make the following additions under the section labeled: MS Code Page 1253 (Greek) to Unicode UCS-2 and vice versa.

  • Under the subsection labeled [Translate 63 to 102], add the following:

0xC4=0x2206

0xD9=0x2126

  • Under the subsection labeled [Translate 102 to 63], add the following:

0x2206=0xC4

0x2126=0xD9

Back to Contents

Spell Checking Text on Grouped Objects

In Output Designer, the spell checking program does not spell check text that is included in grouped objects. To spell check text contained in grouped objects, you must first ungroup the objects.

Back to Contents

Improved Dialog Box Font for Simplified and Traditional Chinese Systems

Output Designer 5.5 and later contain an improved dialog box font for use with Simplified and Traditional Chinese systems. After installing Output Designer, double-click the appropriate .reg file from the ...\Chinese_Reg_Files directory on the Output Designer media: SimplifiedChinese.reg for Simplified Chinese systems, and TraditionalChinese.reg for Traditional Chinese systems.

Back to Contents

Importing IFD Template Designs

As noted in the Output Designer help, you cannot import .ifd template designs of more than one page. If you try to import a multi-page template design, the first page does not get imported and you receive the error message:

Adobe Message #5 - Error reading file.

As a workaround, if you place a guideline on each page of the multi-page template design that you want to import, the first page will import successfully.

Of course, you can always import a multi-page template design by first exporting it to a FIF file, and then import the FIF file. In this case, all pages will import successfully.

Back to Contents

Cursor Behavior

Two issues have been noted with regard to how the cursor behaves in certain situations. Although these behaviors will not impact your ability to work with Output Designer, their presence should be noted.

  • When dragging an object onto your template from the Template Object Library, if the object contains fonts that are not supported by your default presentment target, you are presented with dialog boxes to convert the fonts. Once you have accepted the font conversions, the cursor does not return to the Pick cursor, but remains as an hour glass. You can return the cursor to the Pick cursor by moving it over the status bar or the toolbar.
  • When you select an object group and attempt to move it by holding down the SHIFT and CTRL keys, the cursor does not change to the Move cursor, but remains as a Pick cursor. However, you can still move the group.

Back to Contents

Extended Characters in Template File Names

Do not use decimals or extended characters such as ½ in template file names.

Back to Contents

Boilerplate Containing Text Substitution Fields Do Not Print Using Test Presentment

When Test Presentment is run with the Create sample data file containing subform and field names option selected, boilerplate containing text substitution fields will not print.  To resolve this issue you can do the following:

1.       Open up the .IFD in Output Designer.

2.       Click Format > Template Preamble.

3.       In the Customer Properties dialog, go to JFPREAMBLE_1.

4.       Select all the text substitution field commands as well as the first ^comment that follows and copy them to the clipboard.  These appear at the end of JFPREAMBLE_1 in the format: “^define global:$TextF_presentment_target_1".

5.       Close the Customer Properties dialog.

6.       Click File > Test Presentment.

7.       Click the Create Sample Data File button.

8.       Select the checkbox Create a sample data file containing subform & field names.

9.       Specify a file name and click Save.

10.   In the Test Presentment dialog, click the Edit button and make the following changes:

·         On the first line change -rno to -ryes.

·         Insert a new second line containing ^symbolset 5.

11.   Paste the text that was copied from the clipboard in step 4 above.

12.   Save the modified data file.

13.   Click OK on the Test Presentment dialog.

Back to Contents

Documentation - Output Designer version numbers

Any references to version 5.6 in the documentation should be considered applicable for this version of Output Designer (5.7).

Back to Contents


The Documentation Set

Output Designer includes a complete set of documentation to help you understand how to use the product and its components. The Output Designer Documentation Map (DocMap.pdf) provides access to this documentation set. To view the documentation, you must have Adobe Reader installed on your computer. You can download Adobe Reader from the Adobe website at www.adobe.com.

Back to Contents


Licenses and Copyrights

By installing this product, in addition to the Adobe license terms, you also agree to be bound by the third-party terms specified in the additional-legal-notices.html document, installed in the same location as the Output Designer executable. Adobe recommends that you review these third-party terms.

Adobe Output Designer includes technology from Symbol Technologies, Inc. Portions © 1994 Symbol Technologies, Inc.

The Freetype Project is © 1996-2000 by David Turner, Robert Wilhelm, and Werner Lemberg.

Portions based in part on the work of the FreeType team

Portions © 1995-1996 Access Softek, Inc. All rights reserved. 

© 1995-2002 Jean-Loup Gailly and Mark Adler

Back to Contents


Readme File -- Adobe Output Designer, Version 5.7 --1/19/2009 1:40:56 PM