Océ Document Designer - Océ | Printing for Professionals

Océ Release Notes
Océ Document Designer V6.2.45.0
General Availability/ Windows
June 2010
Table of Contents
Table of Contents
Chapter 1
What is Océ Document Designer .............................................................................. 4
Chapter 2
What's New in Version 6.2 ........................................................................................ 5
New Features in 6.2 Beta Release .............................................................. 5
General ................................................................................................. 5
Workflow ............................................................................................... 5
Data Input .............................................................................................. 6
Data Processing ..................................................................................... 7
Layout ................................................................................................... 8
Impositioning .......................................................................................... 9
Proof ..................................................................................................... 9
Production ........................................................................................... 10
Related Applications ............................................................................. 14
Scripting .............................................................................................. 15
Projects ............................................................................................... 15
New Features in 6.2 GA Release ............................................................... 15
General ............................................................................................... 15
Layout ................................................................................................. 16
Production ........................................................................................... 16
Chapter 3
Changes in Default Setting ..................................................................................... 17
Chapter 4
Application Requirements ......................................................................................
Supported Platforms .................................................................................
Hardware Requirements ...........................................................................
Compatibility ............................................................................................
VCS Client and Server Compatibility .......................................................
18
18
18
18
18
Chapter 5
Testing Results ......................................................................................................
Test Environment .....................................................................................
Test Statistics ..........................................................................................
List of Tested Printers ...............................................................................
Tested IPDS Connections .........................................................................
Tested VPS RIPs .....................................................................................
Viewers and Converters ...........................................................................
PPML Output – RIPs Image Compatibility ..................................................
20
20
20
21
21
21
21
23
Chapter 6
Known Issues ........................................................................................................
Issues Known at the Time of GA Release ...................................................
Level 1 Issues ......................................................................................
Level 2 Issues ......................................................................................
Third Party Issues .................................................................................
28
28
28
28
28
2
Table of Contents
Chapter 7
Known Limitations .................................................................................................
General ...................................................................................................
Known Limitations of the 64-bit Version of Océ Document Designer ..............
PDF/EPS Native Import Known Limitations .................................................
AFP Native Import Known Limitations ........................................................
PCL Native Import Known Limitations ........................................................
XSLFO Known Limitations ........................................................................
DOC and RTF Files Import Known Limitations ............................................
Font/Image Replacement ......................................................................
HTML Simple Output Known Limitations ....................................................
Text Style .............................................................................................
Paragraph Styles ..................................................................................
Tables ..................................................................................................
Border Style .........................................................................................
Line Style .............................................................................................
HTML Output Known Limitations ...............................................................
Known Limitations Resulting from General HTML Principles .....................
Website Generation Mode Known Limitations ..........................................
Email Generation Mode Known Limitations .............................................
Metacode Output Known Limitations and Recommendations .......................
30
30
30
31
31
32
33
33
36
36
36
37
37
37
37
37
37
38
38
39
Chapter 8
Localization ........................................................................................................... 40
Appendix A
Fixed Issues ........................................................................................................... 41
3
What is Océ Document Designer
1 What is Océ Document Designer
Océ Document Designer is an integrated, variable document design and composition
solution that enables users to create and produce high impact, personalized communications
tailored to the exact needs and interests of a client or groups of clients.
The software offers a single platform that can support an extensive range of transactional,
promotional, trans-promo, and on-demand publishing applications. Compatibility with
Macintosh, Windows, and Linux/UNIX platforms makes Océ Document Designer a smooth,
risk-free fit into mixed production environments and job flows. Broad input and output
support accommodates the diverse data streams and delivery options needed for a convergence of applications.
Data Input
Design Import Operating
Systems
Protocols
Printers
Output
DBF
Delimited
Flat
Line data
ODBC
PDF Bookmarks
SAP
XML
InDesign
AFP
EPS
MS Word
PCL
PDF
Océ Document
Designer TNO
QuarkXPress
RTF
XSLFO
AFP
Docx
HTML
HP PPML
IJPDS
IPDS
Metacode
MIBF
PCL
PDF
PostScript
Podi PPML
Screen TOP
Text
VDX
VIPP
VPS
SX/AP
Canon
HP
HP Indigo
InfoPrint Solutions
Kodak Digimaster
Kodak Nexpress
Kodak Versamark
Konica/Minolta
Miyakoshi
Nipson
Oce
Ricoh
Screen
Xeikon
Xerox
Archive
Data
Email
Print
Web
AIX
Linux
Mac OS X
Windows
Solaris
z/OS
Océ Document Designer features a classic desktop publishing look and feel, and provides
easy to use design and advanced data handling to create attractive, customized documents.
For designers, it supports traditional platforms and tools such as Mac OS X, Quark and
Adobe InDesign. For IT users, the software integrates with standard production platforms,
manages input from multiple sources, and handles output in any volume and in multiple
formats.
A highly intuitive GUI interface and WYSIWYG layout and proofing let users see exactly
what they are doing. Automated management of forms, images and fonts; dynamic table
generation; and workflow wizards simplify even the most complex projects.
4
What's New in Version 6.2
2 What's New in Version 6.2
2.1 New Features in 6.2 Beta Release
2.1.1 General
■ Projects in the recent files list – The Workflow window File menu displays among recently opened files also project files.
■ Log window-pane scrolling enhancement – It is possible to stop/hold scrolling of the
Proof and Production log-messages by clicking within the log window-pane in the required spot. Selecting the Scroll to End option from the log window-pane context menu
scrolls the log-messages down to display the newest one.
■ Customized character encoding for IPTC keywords – It is possible to customize character encoding for IPTC keywords via a command in the CONFIG file.
■ Overriding the user's name in the CFG file is possible – A CONFIG file command allows
to save the settings in the CFG file according to the current user's name.
■ PDF version 9.0 – The PDF library installation has been updated to version 9 in order
to support PDFs edited in the current Adobe Acrobat version.
2.1.2 Workflow
■ The List recursively option in the Cross Reference Browser Dialog – Listing files from
sub-folders as well as the defined folder is possible.
Native Import
■ Native import without elements – The option Create elements from overlays in the
Native Import Advanced Options Dialog can be unchecked so that imported objects
are placed on pages without being grouped by elements.
■ True Type font support in AFP native import – The True Type fonts are supported,
with the exceptions listed in the AFP Native Import Known Limitations.
■ Processing of AFP files has been optimized – For processing natively imported mixed
mode AFP files the Pagedef is accepted when needed, but is not required, if not necessary.
■ Support for multiple AFP resource directories – The AFP Import dialog enables you
to select multiple resource directories if needed.
■ BCOCA support enhancements – The Royal Mail, MaxiCode, PDF417 and the QR
barcodes support has been implemented.
■ DeviceGray colorspace conversion for PS and PDF – If a PS or PDF file contains
DeviceGray colorspace and it is to be imported into a workflow, the colors are assigned
to either RGB or CMYK via the PDF Import options on the Workflow Options dialog.
■ Maximum file size and number limit for cached data for files imported natively in
Layout and/or through the PnetT Native module – The limit values for cached data can
be edited through the CONFIG file.
5
What's New in Version 6.2
■ Possibility to force user selected text encoding for the imported PCL file – Enabling
the Force default for all check-box allows proper display of text when editing the
imported file in the Text in Rect module.
■ Highlight color mapping in the PCL Native Import Configuration – The Color dialog
allows to map specific colors to highlight colors used in the imported PCL file.
■ Transparency flattening – It is possible to merge transparent objects into a non-transparent bitmap in the imported PDF file.
■ INDD files import – With the Adobe InDesign installed locally, INDD files can be
processed in Océ Document Designer as PDFs or viewed when:
■ imported natively via the PNetT Native module or using the Import | Native option
in the Layout File Menu,
■ inserted into Layout as an INDD image,
■ dragged-and-dropped into Sheet Proof or Océ Document Designer Viewer.
■ Import of layered InDesign and QuarkXPress documents into Océ Document Designer–
Layers in InDesign documents are imported into Océ Document Designer as separate
Object Groups. This makes it easy to manipulate with the layers. If there is only one
layer, all objects are placed directly on the page. For the QuarkXPress documents, only
objects from the Default layer are always exported as independent objects directly onto
the page.
■ URL links in files exported from InDesign – URL links from InDesign are supported.
2.1.3 Data Input
■ DBF7 support – You can feed DBF files version 7 through the Data Input module.
■ Different TSD file structure allowed – A TSD file loaded via the Internal Input module
can have a data structure different from the workflow, e.g. unused variables can be deleted or new added. Océ Document Designer displays only a warning.
■ Skipping SAP input file header – In the PNetT.config file you can set that headers of
SAP input files will not be read and checked for correctness, which is useful in case
that the length of the header is not in accordance with the file format specification.
6
What's New in Version 6.2
2.1.4 Data Processing
■ Data Remapper module – Data can be assigned to a new (imported) data structure using
the Data Remapper module.
■ Enhanced data extracting for sending personalized emails via Email Gateway – The
Email Gateway Data module included into a workflow allows reorganizing the input
data into an input CSV file for Email Gateway. This way, within one workflow, you
can easily generate all files (e.g. CSV, PDF, HTML) needed for email sending via Email
Gateway.
■ Field sorting – The order of fields in the data structure can be changed via the Field
order area of the Data Transformer module.
■ Editable path to cache – The path to cache files in the Data Cacher module is editable.
Also a relative path can be entered.
■ Indication of disabled MinMax Generator – A better indication of the disabled status
has been implemented for the MinMax Generator module.
7
What's New in Version 6.2
2.1.5 Layout
General
■ Object modification effects – It is now possible to create effect areas in Layout where
objects can be modified using modulation effects: Perspective, Warp (in the image below), Emboss etc.
■ Font shadow effect – In text styles it is possible to define a font shadow with any fill
style and offset.
■ Widened functionality of URL links used in PDF output files – It is possible to insert
signature fields, tool-tips and links to specific pages within the PDF document.
■ Dithering of black-and-white images in Layout – For images with the Black and white
color space, the Edit Dithering dialog enables you to define the required dithering settings.
■ Warning of missing characters – Océ Document Designer can search for characters
used in Layout that are not present in the font applied. If such characters are found a
warning is generated. The functionality can be switched on by enabling the option
Undefined character check in the Layout Options dialog.
■ The number of merged table borders put in overlays can be controlled – With the
Overlay Properties settings it is possible to limit the merged table borders put in overlays,
and further decide how they are handled, in order to optimize memory usage during
processing.
To set the default number of overlays used for merged table borders generally (not only
for current Layout), you can use a command in the CONFIG file. It is especially useful
for workflows created in Océ Document Designer version 6.1 and earlier.
■ Chart formatting options – The size of charts can be adjusted to fit all point labels
within the chart border by using the Scale to fit option on the General Tab. Also, point
labels' position can be optimized.
■ Messages modified according to the customer ID – New condition type Listed customer
IDs has been added to the rules for modification of messages. This feature is intended
mainly for campaigns created in PrintNet Interactive.
■ Message category scripting methods can return integer values – From version 6.2,
message category scripting methods return string values. It is possible to have them
returning integer values by enabling the Interpret message category in script as 'Int'
option in the Layout Options dialog.
8
What's New in Version 6.2
Barcodes
■ Selectable font of the text characters in the UPC A and UPC E barcodes – The font
used by the text style selected in the Text and Align tab is employed.
Minor Layout Enhancements
■ Default image for variable images – It is possible to define an image that will be displayed if the controlling variable returns no image for the current record.
■ Preview of images in variable selection conditions – In the Layout Properties, hover
the mouse cursor over the image name to display its preview.
■ Editing of multiple messages – The properties of messages can be edited collectively.
■ Easier editing of font replacement settings – It is possible to copy and paste values in
the current column of the Font Replacement Layout Properties.
■ Text styles properties' categories – Some properties of text styles have been recategorized
to different smaller tabs/groups for easier user navigation.
2.1.6 Impositioning
■ Text in Rect module enhancements:
■ Scripted conditions – Scripts can be entered in context in the Text in Rect module
to allow any condition to be performed.
■ Support of Data Matrix – Data can be read from the Data Matrix type of barcode.
■ Rectangle groups – Rectangles can be grouped for easier viewing when many rectangles have been drawn.
■ Warning about sheet name duplication – A warning will show if any sheet name is
used for two or more different rectangles.
■ The Center target option in the Marks Inserter Module – The reference point of the
Center target mark is in its middle.
2.1.7 Proof
■ Primer coats – Viewing of the primer coats, that can be applied with the MIBF engine,
is possible in Proof with a raster proof profile.
■ New output color for raster proof/engine – CMYK split dithered colorants has been
added to the Output colors combo-box of both the Raster Proof Profile and Raster
Engine Config dialogs. It uses assigned colorants in combination with dithered CMYK
colors.
■ Merging static objects into an overlay and grayscale printing emulation – The Merge
static objects into overlay functionality and the AFP grayscale image support can now
be emulated in the raster proof environment.
■ Full PCL support in printing from Proof – The Print from Proof dialog options Size X,
Y and Autofit are available also for the PCL engine.
9
What's New in Version 6.2
■ TSD files support – TSD files can now be viewed in the Data Proof window and in Océ
Document Designer Viewer.
■ Colorants auto-add – The colorants defined in Layout are added automatically when
opening the Colorants edit-box of the Raster Proof Profile dialog.
■ Character count displayed – The Data Proof window shows the number of characters
that the value of the selected variable has for the current record.
■ New shortcuts – You can toggle between the Sheet and Proof windows using the keypad
shortcuts: <Alt>+<1>, and <Alt>+<2>.
2.1.8 Production
General
■ Bézier curve support for raster engines – The Graphic support option for AFP, IPDS,
PDF Fixed Resolution and Raster engine configurations has the more efficient selection
Full with outlines and Beziers which represents curves as points of a Bézier curve to
be rendered by the printer.
■ Three new finishing operations in the AFP and IPDS printer configurations – Now you
can also select the X'85' Triplet operations: Ring bind, Perfect bind and Trim after fold.
■ Split spool files can be opened directly from the log window-pane – Enabling the File
logging check-box in the Warnings Config Dialog allows to generate individual logmessages for all split spool files. Double-clicking on that log-message (ID 0995), or
selecting Open Spool File from its context menu, opens the spool file.
■ Options renamed – The Graphic support options names in the AFP and IPDS engine
configurations have been changed to match the names in the Raster Proof Profile dialog:
Colored areas to Full, and Full to Full with outlines.
Improvements by Engine
Adobe PostScript
■ Reuse background images – Background images can be created with unique references
using Reuse generated background images on the Images tab, enabling them to be
found and reused for multiple jobs. This feature is available for ScreenTOP and Xerox
modes.
■ Merging overlays – Overlays from a workflow can be merged using the options Merge
overlays and Merge also images on the Images tab of either PostScript Engine Config
dialogs. One intention of this is to be able to produce a single background image which
contains all static content. This feature is available for ScreenTOP and Xerox modes.
■ Enhanced support of fonts in native inputs – The Adobe PostScript2 and Adobe Postscript3 engines retain the Unicode information relevant to fonts from native inputs, so
that they can be fully utilized downstream the workflow.
10
What's New in Version 6.2
■ Custom groups in the PostScript engine configuration – They can be used with the
Xerox option selected for Enhancement; additionally the group name defined here is
specified in the PS file(s) metadata as the folder name parameter.
■ Xerox CF printer X490/980 – Back form creation for the X490/980 device is supported.
AFP
■ Consistent processing of invalid MICR color – The AFP engine handles incorrect use
of MICR colors and issues a production warning.
■ Skipping the processing of images included in AFP output files – Image formats that
do not require processing can be selected in the Images tab of the AFP Engine Configuration.
■ Multi-page PDF image handling for AFP output files – PDF image data can be put into
AFP output files in their original form, converted into EPS or split into single-page
PDF images.
■ Setup verification ID's availability for all color modes – Setup verification ID is now
available for all color modes. The controls have been moved from General to Advanced
tab of the AFP Engine Config dialog.
■ AFP Engine supports transparency in TIFF images – The TIFF Object-type OID
X'06072B12000401010E' has been substituted with TIFF Object-type OID
X'06072B120004010142', that supports the TIFF alpha channel. Also, for TIFF images
that are used without processing, you can enable the transparency support or use them
as fully opaque.
■ Printer resolution settings – A new predefined printer resolution – 1200 DPI – has been
added to the General tab of the engine configuration. Users can also enter any resolution
that is required.
■ Enhanced functionality of the Assign AFP Font Shortcuts Dialog in the AFP Engine
Configuration – It is possible to type in font names or load the complete list of fonts
used in Layout(s), for assigning shortcuts used for the AFP file production.
■ Tone transfer curves and half tones applied by the printer – Commands can be sent requesting that the printing device applies tone transfer curves (LUT) and half tones according to preset methods. The curves and half tones are referenced by name, hence
device independent.
Creo VPS
■ Possibility to name externally generated images – It is possible for the user to name
externally generated images. Using substitution characters for variable names is also
possible.
11
What's New in Version 6.2
HTML / HTML Simple
■ The XHTML/HTML outputs generated via Océ Document Designer comply with specifications:
■ The HTML engine spool files comply with the XHTML 1.0 Transitional specification
and
■ The Simple HTML engine spool files comply with the HTML 4.01 Transitional
specification.
■ HTML table-based positioning – You can select the required type of positioning using
two new radio-buttons in the HTML Engine configuration, Web (absolute positioning)
and Email (table-based positioning).
■ Element support in the HTML Simple engine – Elements placed in the main flow intended for production via the HTML Simple engine will be generated as rasterized images.
Using elements enhances the control over HTML Simple output files positioning.
■ URL links support in HTML Simple – URL links are supported within elements as well
as outside of them (in the Main Flow).
■ Using a hash function while generating HTML and HTML Simple output files significantly saves the processing time – Hashing allows to quickly retrieve once generated
images when they are used repeatedly in an output file. During production the images
are referred to by unique fixed-length hash keys generated for each image.
■ Redesigned and enhanced HTML Engine configuration:
■ The Thread count edit-box allows to enter the chosen number of threads to speed
up the processing when multi-core processors are used.
■ The Rasterize flows check-box allows native processing of objects (text) in flow
areas.
■ The Text at Start tab offers the possibility to enter a header with text to the generated
HTML file(s).
■ The Fonts tab allows to define fonts you wish to be supported/rasterized in the
HTML output file.
IPDS
■ Adjustment in the IPDS Engine Configuration for processing double-byte fonts – The
Sections 0x41 – 0x44 only check-box allows to use only the indicated sections of the
double-byte fonts while processing.
■ Tone transfer curves and half tones applied by the printer – Commands can be sent requesting that the printing device applies tone transfer curves (LUT) and half tones according to preset methods.
■ Ignore ICC Profiles for certain objects – No ICC conversion is applied to CMYK colors
of objects that are placed in defined handling groups.
■ The Full color + dithered colorants option has been added to the IPDS Output colors
combo-box.
12
What's New in Version 6.2
■ Support for further exceptions – The IPDS exception codes 0120..00 and 02B3..01 have
been implemented in the Océ Document Designer.
■ Customization in the IPDS Exceptions Level Configuration Dialog – You can add and
edit added IPDS exceptions.
IJPDS
■ New predefined page side resolution – The RIP type "Prosper S" with 600 x 600 DPI
has been added to the Page Side Configuration dialog.
Metacode
■ Possibility to set encoding – It is possible to define encoding for Metacode spool files
on the Print Setting tab.
■ Resource file for split spool files – The new option Split file by group on the General
tab enables to create one extra file with all resources. The split files can then just reuse
these resources.
MIBF
■ Primer coats – Primer coats can be applied according to the settings for the MIBF Page
Side Configuration and a Primer type can be selected on the Advanced tab of the MIBF
Engine Config dialog.
■ Adjustable DPI for EPS/PDF images in the MIBF Engine Configuration – On the Advanced tab you can select the resolution intended for EPS/PDF images.
■ Enhanced processing of native PDF images by the MIBF engine – Static native PDF
images can be generated as external EPS files.
■ MIBF output colors – CMYK split + dithered colorants, which prints colors by dithering
colorants and dithering CMYK based dots, is a new color type selectable from Output
colors on the General tab of the MIBF Engine Config dialog.
PDF and PDF Fixed Resolution
■ Faster online viewing of the PDF output – Enabling the Optimize for fast web view
check-box in the PDF Engine configuration linearizes the output PDF files. Linearized
PDF files can be incrementally viewed online without the necessity to download the
whole file beforehand.
■ New encryption methods added for the PDF Engine – To the long implemented RC4
40-bit key, two others have been added: the RC4 with 128-bit key and the AES with
128-bit key.
■ PDF/X-4 compliance – The PDF/X-4 check-box on the General Tab of the PDF Engine
Configuration allows to generate self-contained PDF files.
■ Possibility to set behavior in Acrobat – The Acrobat tab is now available also for the
PDF Fixed Resolution engine. Some of the related command line parameters (-pd→
13
What's New in Version 6.2
fautoprint, -pdfshowprintdlg and -pdfshrinktofit) are now supported for
this engine too.
■ Single-byte text encoding panel has been added to the PDF Fixed Resolution Engine
Configuration – The new Fonts Tab allows setting text encoding options. Thanks to
text encodings support, the PDF Fixed Resolution output files allow text searches.
PPML
■ PPML version 3.0 – The protocol for version 3.00 of PPML is supported for both the
Podi PPML and HP PPML engine configurations.
SWF
■ SWF (Adobe Flash) Engine has been added – The SWF Engine can be used to create
a SWF file for adding a flash version of documents to web pages.
VIPP
■ VIPP engine supports overlays – In the VIPP Settings tab of the VIPP Engine configuration it is possible to enable using overlays.
■ Project Name and Folder name in VPF file – The VPF files generated along with VIPP
jobs contain now the Project name and the name of the folder, that images are generated
to.
2.1.9 Related Applications
PNetTC
■ Possibility not to export resources – The new PNetTC commands -exportusedfiles
and -includeall enable you to decide if you want to export resources when converting
WFD to XML or vice versa.
PNetTNetServer
■ Processor affinity configuration – In the PNetT.config file you can define preferred
processors for processes and threads.
VCS
■ Scripts run on action – It is possible to set up scripts that will be run on various actions
performed by the users of the VCS.
■ Authentication of users against an LDAP syncpoint – Users that do not have a password
set in the VCS can be authenticated against an LDAP authentication point.
■ Customizable VCS cache size – It is possible to set the VCS cache size in the
PNetT.config file.
14
What's New in Version 6.2
■ Quick navigation to search results – The option Go to File has been added to the contextual menu of a file listed under the Search results node. It forwards you to the directory
where the file is located.
■ Extended search options – It is possible to search for files stored in the VCS according
to their metadata.
■ Drag and drop support – Files and folders can be added to the VCS by dragging and
dropping them to the VCS Client Explorer.
■ The Path column was deleted – Paths to files are now available in Found results.
2.1.10 Scripting
■ Sending emails from Océ Document Designer – With the new Util.MailServer
and Util.Mail methods, it is possible to establish a connection to a SMTP server and
create and send email messages directly from Océ Document Designer.
■ Parameterizable SQL statements – It is possible to use parametrized SQL statements
in ODBC input related scripts to boost the security of access to databases.
■ Support of surrogate characters – New string methods, that are able to deal with surrogate
pairs, have been added.
■ Script Library indication in warnings in scripts – The Warnings table in the Script Editor dialog has a new column (named Module) that, in the case of error, indicates the
Script Library in which the error occurred.
■ Find and replace in scripts – The option Find in Script has been added to the rightclick menu in the Script Data Input and Impositioning Script modules.
2.1.11 Projects
■ Drag and drop support – Files can be copied from folder to folder by dragging and
dropping them. Projects can be opened by dragging and dropping a pnettwsp (project)
folder to a Océ Document Designer window. Files can be dragged and dropped to the
Project Browser window.
2.2 New Features in 6.2 GA Release
2.2.1 General
■ Warning for changed/removed external objects – When opening a master workflow
containing an external object which has been changed/removed in a slave workflow in
the meantime, a warning message is newly displayed.
This warning is also displayed in the command line, however, it can be suppressed using
the command -autoskipmissing. Then, such an external object can be printed.
15
What's New in Version 6.2
2.2.2 Layout
■ Using an array of data in scripted conditions of messages – When referencing variables
in scripted conditions of messages it is possible to start with the array name. It is not
necessary to write "DATA.Array" anymore.
2.2.3 Production
Improvements by Engine
Docx
■ Headers and Footers – Flow areas from the Layout of a workflow can be converted into
headers or footers in the DOCX file. See the option Header/Footer support in the
Docx Engine Config dialog.
■ Templates – Headers, footers and margins can be pre-defined in MS Word and then
used when creating DOCX files from Océ Document Designer. See the option Merge
with predefined template in the Docx Engine Config dialog.
HTML
The Email generation mode of the HTML output has been enhanced with:
■ Support for bullets and numbering
■ Document alignment
■ Customizable background color
16
Changes in Default Setting
3 Changes in Default Setting
This section lists differences in the application’s default settings with the previous version
(applied to Beta and GA versions).
■ The option Merge static object into overlay in the IPDS Engine Config dialog is now
switched off by default.
■ PPML resource name is now a hash number which is the same for each resource ID in
every run.
■ The calculation of the week of year in the Parse Date Time field conversion has changed.
Week 1 is the week that includes the first Thursday of the year.
■ The rounding in tables when calculating the cell width changed and in a few specific
cases it may happen that one more line would fit into the flow area.
■ Due to a new PDF Library the value returned by the Max image color saturation field
converter is slightly different.
■ The Native Printer Engine has been renamed to the Desktop Printer (driver) engine to
avoid confusion with PNetT Native engine and other 'native' features of Océ Document
Designer.
■ Sheet Names in scripts are now referred to by an index starting from "1" (instead of
starting from "0" which meant that Sheet Name "0" referred to the actual "Sheet Name
1" in scripts). For (backward) compatibility with jobs created in versions 6.1 and
earlier, the Index Sheet Names from zero check-box is available in the Imposition
Script module.
■ The original JPEG image stream (JPEG compression for JPEG images specified in the
Group Handling options) is now used in the PDF output only when no changes are
applied to the original JPEG in Layout. Otherwise, it is recompressed.
■ Océ Document Designer gradient can specify extents with any colors. If the left extent
color is different from the first gradient color, or the right extent color is different from
the last gradient color, special handling of the situation has to be performed when generating a PDF file.
I.e. by inserting a new, very small, gradient interval at the beginning or end of the
gradient, respectively.
Formerly the right extent interval used to be considerably larger than the left one.
However, the right one now corresponds to the left one.
17
Application Requirements
4 Application Requirements
4.1 Supported Platforms
In its current version, Océ Document Designer is supported on the following Microsoft
Windows versions:
Océ Document Designer 32-bit:
Support Level
Windows XP
Fully supported
Windows Server 2003
Once a release*
Windows Vista
Fully supported
Windows Server 2008
Once a release*
Windows 7
Fully supported
Océ Document Designer 64-bit:
Support Level
Windows Vista Ultimate 64-bit
Fully supported
Windows 2008 64-bit
Once a release*
Windows 7 64-bit
Once a release*
* Selected versions are tested once in a testing cycle.
4.2 Hardware Requirements
Minimum Configuration
■ Pentium IV at 1500 MHz
■ 512 MB RAM memory
■ Monitor resolution 1024x768
4.3 Compatibility
4.3.1 VCS Client and Server Compatibility
The following table shows which VCS client versions and which VCS server versions are
compatible.
18
Application Requirements
Server
Client
6.0
6.1
6.2
6.0
Yes
Yes
Yes
6.1
Yes
Yes
Yes
6.2
Yes
Yes
Yes
19
Testing Results
5 Testing Results
The testing results are presented for the following version of Océ Document Designer:
■ Océ Document Designer 6.2.45.0
5.1 Test Environment
This version of Océ Document Designer has been tested in the following test environment
for which the performance and results are guaranteed.
Windows XP Professional, Windows Vista Business and Ultimate 32 and 64-bit versions,
Windows Server 2003, Windows 7 Ultimate and Professional 32 and 64-bit versions,
Windows Server 2008 Enterprise edition 32 and 64-bit versions
MySQL server: 5.0.15-win32, ODBC driver: mysql-odbc-3.51.19-win32, MS SQL server:
6.00.6001, MS SQL EXPRESS server: 2005
Océ Document Designer 6.2.45.0 was tested with Citrix MetaFrame. Remote access was
verified.
Clustering on Windows Server 2008 was verified.
5.2 Test Statistics
Design Part
Sum of test cases:
1424
Overall success:
100%
Outputs
Sum of test cases:
25828
Compared pages (BMP):
101786
Overall success:
100%
The testing sheet contains the item Overall success that is calculated from all of the performed testing scenarios and the number of Level 1 and Level 2 bugs that have been recorded. The testing scenario contains two parameters that are evaluated:
1. Assessment involves the evaluation of a selected testing scenario according to the
current error rate and according to the concept of any tested section from a personal
point of view.
2. Importance expresses the significance of the testing scenario for the whole product.
20
Testing Results
Both parameters can register any value between 1 and 5 (where 1 is the worst and 5 is the
best value) and they are also involved in the overall statistics. The Importance parameter
usually registers a value from 3 to 5.
Example: An assessment with the value 4 represents a decrease of overall success even
though there is no record in the Known Issues. The value 4 can be caused by the presence
of minor issues that have not been included in the overall statistics.
5.3 List of Tested Printers
For the list of tested printers and recommendations for printing see the separate document
Printer Guide.
5.4 Tested IPDS Connections
■ SCSI
■ TCP-IP
5.5 Tested VPS RIPs
VPS output was tested successfully on Creo CXP6000, Creo CXP 6060 and Creo CSX
2000.
5.6 Viewers and Converters
AFP
■ AFP Browser 1.4 (BTB)
■ IBM Workbench 2.01.00.08
■ AFP analyzer 0.4.5
■ IBM InfoPrint Manager UR53463S
PostScript, PDF
■ Adobe Acrobat Professional 6 and 8
■ Adobe Acrobat Reader 9.0
■ Adobe Acrobat Distiller 5.0, 6.0, 8.0
■ Ghost Script 8.64
■ GhostView 4.7
■ Xerox Phaser 8200
21
Testing Results
■ Creo Spire CXP8000 V.2.0
■ Xeikon X-800 v.1.80
VPS Creo
■ Creo Spire CXP8000 V.2.0
■ Adobe Acrobat Distiller + VPS Plugin
IPDS
■ ITF 2.30
■ Trueproof 04.06.10
IJPDS
■ IJPDS Viewer 0.0.0.4
■ IJPDS View 1.1
■ Scitex Proofer 5.2.12
PCL
■ PageView 3.4.10.0
■ PCL Codes 7
■ Escapee 8.19
VDX
The correctness of spool files has been confirmed by Kodak/Nexpress.
■ NexPress VDX viewer 3.2.0 BLD2145
■ NexStation imposition viewer 3.2.0 BLD2145
■ NexPress VDX Auditor v. 3.0
PPML
■ Creo Spire CXP8000 V.2.0
■ Xeikon X-800 v.1.80
■ HP SmartStream Production Pro Print manager V3.2.4, Build 2543
■ Xeikon PPML2PS v.2.05
MIBF
■ MIBF Viewer v.2009.09.09.01
Metacode
■ Only BARRSPOOL MODE has been tested. The remaining spool modes could not be
tested.
22
Testing Results
Xerox VIPP
■ Only VIPP plug-in for Acrobat Distiller
5.7 PPML Output – RIPs Image Compatibility
Creo RIP: Creo Spire CXP8000 Color Server
Xeikon RIP: X800 v 1.8
HP RIP: SmartStream Production Pro Print manager V3.2.4, Build 2543
Note:
■ TIF format – transparency is not allowed according to the PPML specification
■ JPG – transparency is not supported in the JPG format
Remarks:
BMP monochrome
HP
Xeikon
HP
Xeikon
Creo
Creo
Without conversion
JPG
HP
Xeikon
Creo
HP
Xeikon
Creo
Océ Document Designer Convert to image types
Image Type Source
EPS
TIFF
2
4bitpalette
8bitpalette
truecolor
24bitcolor
32bitcolor
16bi_R5G6B5
16bi_X1R5G5B5
16bi_X4R4G4B4
24bi_R8G8B8
24bitcolor_inverse_order
32bi_X8R8G8B8
JPG
optimized
progressive
4
standard
JIF
ICbCr1x1_1x1_1x1
23
Testing Results
Xeikon
HP
HP
Xeikon
Creo
JPG
HP
Xeikon
Creo
HP
Without conversion
Creo
PNG
Xeikon
Creo
Océ Document Designer Convert to image types
Image Type Source
EPS
TIFF
5
5
5
standard
interleave
transparent
PCX
version_0
1
2
3
version_2
version_5
TIF
nocompress
JPEGcompress
LZVcompress
palette
transparent_LZV
transparent_nocompress
transparent_ZIP
ZIPcompress
EPS
6
Huffman_RLE
3
3
CCITT_Fax3
3
3
CCITT_Fax4
3
3
withcolorprofile
transp
no boudingbox
AdobeAcrobat5_level1
AdobeAcrobat5_level2
AdobeAcrobat5_level3
GIF
87a_interlaced
87a_nointerlaced
89a_interlaced
89a_nointerlaced
87a_interlaced
transparent
24
6
6
6
6
6
2
Testing Results
HP
Xeikon
HP
Xeikon
Creo
Creo
Without conversion
JPG
HP
Xeikon
Creo
HP
Xeikon
Creo
Océ Document Designer Convert to image types
Image Type Source
EPS
TIFF
TGA 8bit_compressed
8bit_uncompressed
16bit_compressed
16bit_uncompressed
24bit_compressed
24bit_uncompressed
PDF
AdobeAcrobat5
PDF_12
PDF_12_GMC
PDF_13
PDF_13_GMC
PDF_13china
PDF_14
25
Testing Results
Legend
1. Incorrect rotation and scaling.
2. The image is displayed as a black rectangle.
26
Testing Results
3. Incorrect (inverse) color used in the image - it is to be corrected in the new version
of the Xeikon RIP.
4. Incorrect size and content.
5. JPG compressions in TIF images.
6. Error on RIP.
27
Known Issues
6 Known Issues
6.1 Issues Known at the Time of GA Release
6.1.1 Level 1 Issues
No Level 1 issues have been detected.
6.1.2 Level 2 Issues
#69323 – AT#22307 In imported AFP documents containing relative-metrics fonts with
a defined underscore, Océ Document Designer may display the underscore line incorrectly. The line can be shifted and its thickness may not correspond to the set values.
Fixed in versions: 7.0.7.0
#69326 When a job with the IPDS output is printed via the Océ Document Designer
console and the job is autorestarted, an exit code 03 (Error logged) is returned instead
of an exit code 0 (No error).
#69344 When the following conditions are met:
■ several external flows are used from one external workflow
■ the Evaluation Statistics feature is enabled
Then the statistics are reset (and do not display correct values) for all external flows
from the external workflow when using one of these external flows for the first time.
Fixed in version: 7.0.7.0
6.1.3 Third Party Issues
#21609 PDF library issue on two-processor machines – Océ Document Designer will
crash when spooling a large number (thousands) of PDF images.
#24984 If a PostScript2 file, used as an input file in the PNetT Native module, contains
a general mask object that is filled with an image and if the mask is defined inside an
overlay, then the Normalizer will convert the file incorrectly.
#28019 Wiziway barcode – Incorrect barcodes are created due to an error in the TagGener.dll file – a proprietary customer’s solution.
#34792 If an attempt is made to run Océ Document Designer using a Citrix client then
Océ Document Designer does not open because it cannot find system fonts. It searches
for them via the path c:\Documents and Settings\"user"\WINDOWS\.
Workaround: Set a system variable CX_FONT.
28
Known Issues
#65904 PDF import – If transparency flattener is applied, some glyphs might be replaced
by incorrect (different) ones.
Workaround: Use the option Convert all text to outlines in the PDF&PS Import
section of the Workflow Options dialog.
#65905 PDF – If transparency flattener is applied, new images are created for all original
images which had the DeviceCMYK color space set (i.e. they had no ICC profile).
These new images are assigned the US Web Coated ICC profile. This results in color
differences between images with and without this profile.
Workaround: Select the US Web Coated ICC profile in the CMYK profile combobox on the Graphics tab of the PDF Engine Config dialog. This ICC profile will then
be applied to all images.
29
Known Limitations
7 Known Limitations
7.1 General
a. PS like – Using large raster images as a text fill style can slow down printing speed
because the whole image is used for each character.
b. The Japanese KAJO font is not displayed correctly as the FreeType interpreter
has different behavior than Windows.
c. It cannot be guaranteed that text using the Big5 encoding will be displayed properly
in Océ Document Designer. Océ Document Designer uses the Unicode standard
to which the Big5 encoding cannot be unambiguously transformed.
d. If the user with administrator rights has the UAC function enabled, starting
PNetTNetServer as a service is not possible on the MS Vista operating system.
e. In a native AFP font, some glyphs can have several bitmaps, each with a different
code point. When a job using such a font is spooled to AFP (with native usage of
fonts), the last bitmap is used. This can cause misprint in paper output and impossibility to recognize text in electronic documents.
f. It is not possible to execute flattening of one document using parallel processing.
Even with the Parallel processing check-box in Production enabled, the internal
settings allow the document to be still processed (single-threaded) but the processing time increases in comparison to processing with the Parallel processing
check-box disabled.
7.2 Known Limitations of the 64-bit Version of Océ
Document Designer
a. Software licensing and License Manager are available for the 64-bit version. For
this version the Aladdin HASP licensing solution is unavailable, therefore neither
local or network dongles can be used.
b. The following features cannot be used with the 64-bit version of Océ Document
Designer because only 32-bit dll files are available:
a. Import of DOC files (DocCallerDll.dll library)
b. Wiziway barcode (TagGener.dll library)
c. DirecType plug-in
d. Line Data Input module
e. Condproc and PNet3
f. Mediabin
30
Known Limitations
7.3 PDF/EPS Native Import Known Limitations
Due to the high complexity of the PDF document format, the implementation of the Native
Import of PDF/EPS Files is still being enhanced.
Therefore, before running the production of a workflow file using the native import functionality, it is highly recommended to proof the workflow thoroughly.
This chapter lists the features of both PDF and EPS files that are not usable in the current
Océ Document Designer version after import of these document types using the Load
natively feature.
a. PDF transparent model (from 1.4 version of PDF). Transparency is not fully supported. It can be rasterized by using the Flatten transparency option.
However, using this option may cause some areas on the PDF page which were
previously transparent to now be opaque (solid white) due to rasterization. Layout
objects placed under the PDF image that took advantage of being visible due to
the previously transparent area might not be visible anymore. This issue can be
fixed by changing the Z-order in Layout.
Note:
The Flatten transparency feature has high memory requirements and it
is a third party software component.
b. If a font is not embedded and belongs to the 14 standard fonts defined in the PDF
specification (refer to the section 5.5.1 in the PDF Reference [http://
partners.adobe.com/public/developer/pdf/index_reference.html]), it is replaced
automatically because those fonts are contained in the PDF library directory. For
other un-embedded fonts, a message created during Production is displayed in the
log file. The font replacement rules can be set using the "Insert Font Replacement"
functionality in the Others node of the Layout Tree.
c. For Type 3 fonts, the glyphs description can contain only monochrome images
and shapes, it cannot contain a color specification. See also the Type3 Fonts chapter
in the PDF Reference [http://partners.adobe.com/public/developer/pdf/
index_reference.html].
d. All patterns are rasterized (the vector information is lost), i.e. they are transformed
to an image fill style in Océ Document Designer.
7.4 AFP Native Import Known Limitations
The following features of the AFP format are not supported by the current Océ Document
Designer version:
a. Line data:
a. XMD based pagedefs
b. RCD – Graphics Descriptor (X'7E') Triplet
b. Non-presentation object containers (True Type fonts, PDF resources, etc.)
c. ACMA – AFP Color Management Architecture
31
Known Limitations
d. IPG – Include Page
e. Character precision of GOCA text
f. Barcodes:
a. MSI (modified Plessey code)
b. UPCTwo-digit Supplemental (Periodicals)
c. UPCFive-digit Supplemental (Paperbacks)
d. USPS Four-State
g. Resources inside page
h. Medium maps before page
Note:
If you get the following warning message: "The OID format of Fully Qualified
Name triplet is not supported." it means that a part of a Structured Field cannot
be parsed and read, but as it is not used during the import, it does not have any
influence on it and the AFP will be imported correctly.
7.5 PCL Native Import Known Limitations
For PCL documents' objects, i.e.:
■ areas
■ images and
■ fonts,
it is possible to apply patterns and Logical Operations Command parameters.
Native import of PCL documents into Océ Document Designer supports them with certain
limitations (see the table below).
Type
Feature
Images
Areas
Fonts
Patterns
solid white
Full support for
monochromatic
images only
Full support
Opacity in Sou
Transparent M
supported.
solid black
Full support
shading
Full support for
monochromatic
images only
cross-hatch
user defined
ROP
252 T OR S (default)
240 S (source only)
204 T (texture only)
32
Full support for
monochromatic
images only
Some patterns
fill styles migh
different appe
Full support
Known Limitations
HP-GL/2 Known Limitations
a. Text is not supported.
b. Only non-vector patterns defined inside HP-GL/2 are supported. Patterns referenced
from PCL are not supported.
c. HP-GL/2 content is not scaled in case that scaling is prescribed from outside from
PCL parts (Plot Size command).
d. HP-GL/2 content is not be clipped (InputWindow command).
e. Wedges and pen colors other than black and white are not supported.
7.6 XSLFO Known Limitations
Océ Document Designer does not support the following specifications of the FO format:
a. "Float" with anchors – Float is an object that can overflow between pages. If a
float overflows, there can be an absolute position specified to which the end of
the page should be set.
b. "Footnotes" – are appended at the end of a flow (not at the end of a page).
Example: There is a two-page document with a flow overflowing from the first
page to the second page. There is a note on the first page. The footnote related to
the note is not placed at the bottom of the first page but on the second page at the
end of the flow.
c. "last-line-…" (e.g. last-line-end-indent) – unsupported property in ParaStyle. The
properties of the last line cannot be defined because Océ Document Designer
cannot locate the last line.
d. All possibilities of formatting list blocks (e.g. bullets are justified left and text is
justified right). List blocks mean numbering and bulleting.
e. Setting of a different border style for the table header, body, footer (Océ Document
Designer only supports setting different border styles for the whole table and for
separate cells) <fo:table-body border-bottom-style="solid">
f. Setting of a fixed height for the whole table.
7.7 DOC and RTF Files Import Known Limitations
DOC import is only supported for MS Word version 2000 and higher.
DOC import can be carried out only if MS Word is installed locally. Otherwise a warning
is displayed when trying to import DOC files.
The following list of limitations contains MS Word 2007 features currently not supported
when imported into Océ Document Designer and also describes the results of import of
features which are not fully supported.
33
Known Limitations
Note:
It may happen that you find another unsupported feature than those listed below.
The reason why there cannot be a complete list is that the RTF specification is
open and new features are developed and added into the specification. However,
the import into Océ Document Designer does not react parallel to this process
and not every new feature in RTF/DOC is enabled in the import automatically.
In case that you find a feature that is not implemented nor listed among these
known limitations, please report the issue you have found, so that it can be either
fixed (implemented) or included in this known list.
Text – font format style:
■ Double strikethrough – is imported as Strikethrough.
■ Shadow – is imported as plain style (without shadow).
■ Emboss, Engrave – is not imported, i.e. the text to which these styles have been applied
is missing.
Text – underline style:
■ Words only – is imported as plain underline style (continuous, including spaces).
■ Wavy – is imported as plain double underline.
Text – other features:
■ Column format – is imported as plain text without columns.
■ Initials – the initial letter (in the size as defined in the document) is imported one line
above the text.
■ Decimal tabulator – works with all kinds of decimal delimiters except for the space.
Tables:
■ Nested tables – are not imported. Only the basic table (level 1) is imported. The text
from the nested table, if there has been any, is kept in the basic table.
■ Rotated text in tables – is imported as non-rotated.
■ Borders – only solid borders applied to cells or the whole table are imported.
■ Shading – only solid colors are imported.
■ Wrap anywhere – is unsupported for long texts in cells (and in text boxes).
Lines and shapes:
■ Lines and shapes – are unsupported. The import results in showing only the bounding
box (rectangle of the line or shape size) and the line-style used, i.e. only rectangles with
solid borders can be imported correctly.
■ AutoShape – is unsupported. The import results in showing only the bounding box
(rectangle of the shape size).
■ WordArt – is unsupported. Word Art objects can be imported as PNG images if storing
as PNG was allowed in the DOC file.
34
Known Limitations
Images:
■ Image types – Import of images is restricted to image types supported by Océ Document
Designer. Import of any other image type (e.g. EMF) results in showing the sample
image in Layout and the note that this image is "invalid" on the Image tab of the sample
image.
■ Image position – Images (and other kinds of objects) may change their position after
import into Océ Document Designer.
■ Crop from – is unsupported. The import results in showing the whole image.
■ Image control (post-processing of images) – is unsupported. This feature can be used
e.g. for setting an image to greyscale or black&white. The import results in showing
the original image. Océ Document Designer features in Layout (Advanced tab for the
image) and in output engine must be used.
■ Wrapping style (Runaround) – "In front of text" style is imported as "Behind text",
which is the default Océ Document Designer style.
Page size:
■ Page size – If there is a document with more pages of different size, the import results
in importing the pages all in one size only. The size of the first page of the document
is used.
Equations:
■ Equations – are unsupported. Equation objects can be imported as PNG images if
storing as PNG was allowed in the DOC file.
Text boxes and frames:
■ Text boxes – are imported as anchors. Supported features: border lines, dashing, line
style, filling with color.
■ Wrap anywhere – is unsupported for long texts in text boxes (and table cells).
■ Frames – are unsupported. The import results in expanding the text with a border to
the usable page width.
Forms:
■ Text Form Field, Check Box Form Field, Drop-Down List – can be imported. Other
form controls are unsupported.
■ Option button (ActiveX control) – will be imported as PNG image if storing as PNG
is allowed in the DOC file.
Foot note:
■ Foot note – is not imported at all.
Page numbers:
■ Page numbers – are inserted as static numbers based on the number calculated in MS
Word. It may happen that this number does not correspond with the page number in
Layout (after import).
35
Known Limitations
Fields (variables):
■ Fields – are not recognized as variables during the import to Océ Document Designer
and that is why they cannot be connected to variables. The import results in showing
the 'X' characters (which in MS Word represent the field).
OLE functionality:
■ OLE functionality (e.g. images rendered by external COM objects) including ActiveX
– is unsupported. The linked object is missing after the import.
Layout Options:
■ All of the options in Word Options (available after clicking on the MS Word icon) |
Advanced | Layout Options (at the very bottom of the Word Options dialog) – are
unsupported.
For example, the feature "Split apart page break and paragraph mark" by which you
can choose, if the paragraph mark will be displayed on the same line as the page break
or below it, is also unsupported.
7.7.1 Font/Image Replacement
If you import RTF or DOC files (or others like XML, PLS, PTF) containing fonts or images
not installed (located) on the current machine, there is a Font (resp. Image) Replacement
dialog displayed, allowing you to replace such a font/image with another one.
7.8 HTML Simple Output Known Limitations
Not supported features are listed below.
7.8.1 Text Style
a. Font subfamily
b. Superscript
c. Subscript
d. Horizontal scale
e. Language
f. Kerning
g. Image fill style
h. Gradient fill style
i. Border style
j. Line fill style
36
Known Limitations
7.8.2 Paragraph Styles
a. Line spacing
7.8.3 Tables
a. Alignment
b. Line gap
7.8.4 Border Style
a. Cap
b. Corner
c. Join
d. Shadow
e. Margin
f. Offset
g. Gradient fill style
h. Image line fill style
i. Gradient line fill style
7.8.5 Line Style
a. Dash style with more than two line gap values
b. Stripe style
c. Line ending
Note:
Employing Elements in Layout allows to use the features otherwise unsupported
in HTML Simple. The content of Elements is generated as rasterized images.
7.9 HTML Output Known Limitations
7.9.1 Known Limitations Resulting from General HTML
Principles
a. Barcodes are always generated as images.
b. Used fonts are not embedded and due to this fact, supported text could be displayed
differently from the layout.
37
Known Limitations
c. Flow areas with unsupported objects (e.g. scaled or rotated text, sections, etc.) are
rasterized and saved to the specified folder as PNG images.
d. Anchors are not supported.
e. Text with scale, rotation, skew or flip is rasterized and the quality of the final image
depends on the image resolution.
7.9.2 Website Generation Mode Known Limitations
a. HTML files generated in the Website mode, are not suitable for emails as some
email clients might not display the content properly (e.g. MS Outlook 2007 does
not support absolute positioning). It is recommended to select the Email generation
mode or use the HTML Simple engine for generating files that are intended to be
sent by email.
7.9.3 Email Generation Mode Known Limitations
a. Text in sections is not supported and is rasterized.
b. Elements (with objects having URL paths assigned) that are not at the beginning
of a line or a table cell in a flow area can be displayed incorrectly in Outlook 2007
(in other email clients the issue does not occur).
Clickable areas of such elements are placed in the space off the assigned objects
in a blank space or over other objects. The issue may additionally interfere with
the HTML document's background (if set).
38
Known Limitations
Example
Both images are placed in elements, that are placed in one flow area.
Legend
i. Clickable area assigned to the first image works correctly.
ii. Clickable area is shifted below the image that the URL path is assigned
to.
Workaround
■ Placing elements, with the URL path assigned, into separate table cells or separate flow areas assures that all of those objects are displayed correctly and
keep their functionality in Outlook 2007.
■ Making the image area, with the URL path assigned, exactly the same size as
the element box.
7.10 Metacode Output Known Limitations and
Recommendations
The output protocol in Metacode has the following limitations:
a. The maximum number of images/overlays per page depends on the printer.
b. The maximum size of a font depends on the printer.
If the maximal values are reached, the user should attempt the following:
■ Re-use the same elements as much as possible (cells in tables, images, etc.).
■ Use the grouping functionality of Océ Document Designer to create small overlays.
■ Split static and variable parts of the page, such as an empty table with border styles/fill
style and a table with variable text without border styles/fill.
39
Localization
8 Localization
The 6.2.45.0 version includes GUI strings that have been translated to other languages.
The languages available and the versions on which the translations are based are listed in
the below table.
40
Language
Océ Document Designer Version
French
6.2.36
German
6.2.36
Czech
6.2.36
Spanish
6.2.36
Italian
6.2.36
Portuguese
6.2.36
A Fixed Issues
A Fixed Issues
This chapter lists public issues fixed since the last published version, i.e. for the versions
6.2.37.0 up to 6.2.45.0.
Fixed in Version 6.2.45.0
#69090 AT#22054 Barcode drawn by PTOCA is distorted after passing through PNT
#69102 AT#22072 Clipboard doesn't show message when it fail
#69179 AT#22190_Paragraph style used in chart is not marked as used
#69205 AT#21055 Netserver fails open worklows during/after VCS backup
#69257 AT#22251 Crash relates Data output in Layout
Fixed in Version 6.2.44.0
#68406 AT#21770 - "PPML Page Media" feature behavior
#68934 AT#21990 WFD checked in VCS is not saved
#68995 AT#22075 - Designer crashes with GlobalPageCount in Script
#69029 AT#22077_[PCL import] PCL not according the specification
#69090 AT#22054 Barcode drawn by PTOCA is distorted after passing through PNT
#69116 AT#22163 - TEXT in RECT odd Behavior
#69165 AT#22178 - Error code 0941 is not ignorable, so should be italic in GUI
#69179 AT#22190_Paragraph style used in chart is not marked as used
#69183 AT#22169 - PNetC crashes after finishing a JOB with exit code -529697949
Fixed in Version 6.2.43.0
#68676 AT#21809 - Shifted or missing images in PPML
#68795 AT#21815 - Settings for SheetStatistic module from JOB file are ignored in
PNetTC
#68851 AT#21994 LDIM terminates unexpectedly due to missing external codec
#68937 AT#22004 default line GOCA behaviour
41
A Fixed Issues
Fixed in Version 6.2.42.0
#68445 AT#21806 AFP Graphic support set to Full with outlines and Beziers
#68471 AT#21816 PCL Native Missing image
#68534 AT#21857 Data Output Flat or Pure Flat without Field Separator
#68549 AT#21811 - Issues with "Justify with margin"
#68672 AT#21549 - Static StringMap not initialized in external workflow
Fixed in Version 6.2.41.0
#68431 AT#21800 AFP Native Unable to draw image
Fixed in Version 6.2.40.0
#67557 NFR11781 AT#21320 Warning when name of external object is changed
#68358 AT#21731 PNetTNative - Set filename to sheetname doesn' work when Merge
all native files selected
#68397 AT#21762 Workflow.OutputName doesn't work for external output module
#68409 AT#21657 Saddle stitch removes group begin
Fixed in Version 6.2.39.0
#68189 AT#21583 PDF Some bars of CodaBar are displayed/generated together
#68231 AT#19971_[AFP line data] Investigation of Formdef and resource placement
#68326 AT#21709 Graphics is missing in AFP - missprint
#68358 AT#21731 PNetTNative - Set filename to sheetname doesn' work when Merge
all native files selected
Fixed in Version 6.2.38.0
#67748 AT#21399 - Incorrectly imported ligature from GlyphArea
#67779 AT#21387 PDF Missing background if NS Splitter or N-Upper is used
#67842 AT#21295 XSD Content of typeId is missing
#67999 AT#21506 Workflow parameters don't allow negative values in Int parameters
#68003 AT#21512 Double display of dir directory function in VCS help
#68027 AT#21374 - Folder with Chinese characters in root
42
A Fixed Issues
#68029 AT#21516 - PDF cannot be opened in Acrobat Reader
#68039 AT#21054 Creates a new field crashes PNT
#68060 AT#21546 - QR barcode error
#68077 AT#21562 - VCSExplorer folder copy&paste returns error/errors
Fixed in Version 6.2.37.0
#66225 AT#20766 - Missing PDF in HP-PPML
#66663 AT#20836 - Error importing XSD
#66798 AT#21046 PDF Adobe Pro 9 Preflight
#66842 AT#21075 TNO with dynamic variables crashes PNT
#66932 AT#21133 Text In Rect PCL native
#66956 AT#21143 - Incorrect shape in PCL after rotation
#66980 AT#20661 - PnetTc hangs during autorestart
#66987 AT#21157 PNT freezes when searching for nonexisting when flow in flow area
is conditional
#67015 AT#21175 DataPrecise 5.3 to 6.0 - Converter lost
#67019 AT#21188 - Slow import of RTF file
#67087 AT#21195 Spooling Speed Gradually Slows Down when Importing a Larger
Number of RTF Files
#67233 AT#21179 Numerical formatting (Test Tab)
#67243 AT#21166 - PDF Glyph Text Colour issue in PDF output
#67310 AT#21188 - rtf import - all pages except first page of document has wrong position
#67392 AT#21270 - PNT crashes when processing PDF with more than 10281 pages
#67421 AT#21236_"direx vcs://" command crash the netserver
#67580 AT#21341 - PNT creates Object Group outside of Page object and crashes in
Proof
#67742 AT#21395_[HTML engine]: wrong interpretation of variable page size in "Email"
generation mode
43