PrintNet T Designer 7.

0
Release Notes
7.0 Service Pack 1
Windows
GMC Software AG
2011 GMC Software AG. All rights reserved.
PrintNet T Designer 7.0
Release Notes
7.0 Service Pack 1
Windows
Release date: April 2011
This document was reviewed and approved by:
GMC CEO: Rene Mueller
GMC CTO: Zbynek Hodic
Quality Control: Pavel Verner
GMC Software AG
www.gmc.net
Should you have any queries, suggestions or comments concerning these materials, please do
not hesitate to contact us at documentation@gmc.net.
This document contains information classified as Public.
The GMC Software Group of companies are ISO 9001:2008 certified.
Copyright
Information contained within this document may contain technical inaccuracies or typograph-
ical errors. Changes will be added periodically and modifications will be made thereto without
prior notification. GMC Software AG does not enter into any obligations or responsibilities re-
garding the content of this document and does not assume any legal liability neither expressed
or implied for its accuracy, completeness and/or usefulness.
Copying of the software or manual on to any data storage medium or in any other way, except
for explicit company internal use, is strictly forbidden without the prior written authorization
of GMC Software AG. Failure to comply with these restrictions is liable to prosecution.
Trademarks
GMC Software Technology and its logo are trademarks and service
marks of GMC Software AG registered in Switzerland, the US and
numerous other countries.
Adobe and Adobe PDF Library are trademarks or registered trademarks of Adobe Systems
Inc. in the US and other countries. The names of other companies, products and services are
the property of their respective owners.
Table of Contents
1 What is PrintNet T Designer 5
1.1 Contribute to PrintNet T Usability . . . . . . . . . . . . . . . . . . . . . . . . 5
2 What's New in Version 7.0 6
2.1 New 7.0 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.2 Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.3 Data Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1.4 Data Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1.5 Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1.6 Output Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1.7 Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1.8 Related Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.1.9 Scripting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3 Changes in Default Settings 14
4 Application Requirements 15
4.1 Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.2 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.3 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.3.1 VCS Client and Server Compatibility . . . . . . . . . . . . . . . . . . 16
4.3.2 DirectSmile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.3.3 Line Data Input Module . . . . . . . . . . . . . . . . . . . . . . . . 17
5 Testing Results 17
5.1 Test Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.2 Test Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.3 List of Tested Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.4 Tested IPDS Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.5 Tested VPS RIPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.6 Viewers and Converters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.7 PPML Output RIPs Image Compatibility . . . . . . . . . . . . . . . . . . . . 20
6 Known Issues 24
6.1 Issues Known at the Time of the Service Pack 1 Release . . . . . . . . . . . . 24
6.1.1 Level 1 Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1.2 Level 2 Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.3 Third Party Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
7 Known Limitations 26
7.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.2 Known Limitations of the 64-bit Version of PrintNet T . . . . . . . . . . . . . 27
3
Table of Contents
7.3 PDF/EPS Native Import Known Limitations . . . . . . . . . . . . . . . . . . . 27
7.4 AFP Native Import Known Limitations . . . . . . . . . . . . . . . . . . . . . 28
7.5 PCL Native Import Known Limitations . . . . . . . . . . . . . . . . . . . . . 28
7.6 XSLFO Known Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.7 DOC and RTF Files Import Known Limitations . . . . . . . . . . . . . . . . . 30
7.7.1 Font/Image Replacement . . . . . . . . . . . . . . . . . . . . . . . . 33
7.8 HTML Simple Output Known Limitations . . . . . . . . . . . . . . . . . . . . 33
7.8.1 Text Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.8.2 Paragraph Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.8.3 Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.8.4 Border Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.8.5 Line Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.9 HTML Output Known Limitations . . . . . . . . . . . . . . . . . . . . . . . 34
7.9.1 Known Limitations Resulting from General HTML Principles . . . . . . 34
7.9.2 Email Generation Mode Known Limitations . . . . . . . . . . . . . . 35
7.9.3 Known Third Party Issues . . . . . . . . . . . . . . . . . . . . . . . . 35
7.10 Metacode Output Known Limitations and Recommendations . . . . . . . . 36
8 Localization 37
9 Printing with Xerox 980 38
A Fixed Issues 38
4
Table of Contents
1 What is PrintNet T Designer
PrintNet T 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 PrintNet T 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.
Output Printers Protocols Operating
Systems
Design Import Data Input
Archive Canon AFP AIX InDesign DBF
Data HP Docx Linux AFP Delimited
Email HP Indigo HTML Mac OS X EPS Flat
Print InfoPrint Solu-
tions
HP PPML Windows MS Word Line data
Web IJPDS Solaris PCL ODBC
Kodak Digi-
master
IPDS z/OS PDF PDF Book-
marks Metacode PrintNet T TNO
SAP Kodak Nex-
press
MIBF QuarkXPress
XML PCL RTF
Kodak Ver-
samark
PDF XSLFO
PostScript
Konica/Mi-
nolta
Podi PPML
Screen TOP
Miyakoshi Text
Nipson VDX
Oce VIPP
Ricoh VPS
Screen SX/AP
Xeikon
Xerox
PrintNet T 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 frommultiple
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.
1.1 Contribute to PrintNet T Usability
For GMC, the continuous improvement of the usability of our products is a major point of focus.
To achieve this goal, we measure user satisfaction with product usability.
5
1 What is PrintNet T Designer
If you would like to contribute to this effort, you can provide feedback on the usability of our
products (for versions you use) by filling in this form: http://rad.gmc.net/surveys/usability.
2 What's New in Version 7.0
2.1 New 7.0 Features
2.1.1 General
Repositories for data Repositories are storages in a database that are specifically for
data analysis and manipulation performed by GMC Software Technology products such
as PrintNet T, Click-Through Server and Campaign Manager. In PrintNet T, workflows
can read data from the repository, manipulate it and write it back to the repository.
One intention is to be able to quickly analyze data from this storage in order to match
customer profiles, so that communication is better personalized.
Throughout PrintNet T there are new features that manage and use these repositories:
Repositories in VCS (where they are created and managed); the Repository Config, Re-
pository Input, Repository Merger and Repository Output modules (which allow work-
flows to work with the data from the repositories and write new data into them); and
also the Output type of Data repository in the Data Output module.
Customization of labels and module icons Labels and module icons in the Workflow
windowcan be customized using user-defined images. This helps to customize workflows
and distinguish between them better.
Labels and module icons take over the proportions of the image.
Skin choice extended The Windows 7 skin is now available for the Windows platform
to enable new look of PrintNet T. This skin is used, by default, for Windows Vista and
Windows 7 operating systems.
HTTP format in Open dialogs Files in the HTTP format can now be loaded via Open
dialogs.
Alternative method of thin-line rendering For PostScript and PDF files that are not
loaded natively, thin lines (around 1 px) are rendered in a different way (as a consequence
of updating the PDF Library). However, you can still render them as done in previous
versions of PrintNet T by checking the option Use legacy method for thin line ren-
dering in Workflow Options.
2.1.2 Workflow
Data record count displayed In the Workflowwindow, the number of records (available
in the root array) is displayed above each connection line passing data records. This is
applied after the workflow is once proofed.
Preserve black color Black color can often appear black but not be pure black, i.e.
CMYK C: 0, M:0, Y:0, K:100. Selecting option Preserve black in ICC transformations
in the Current Workflow Options of the Workflow Options dialog, ensures that when
black is near or very close to 100% then it is redefined as pure black.
6
2 What's New in Version 7.0
This allows for true black color reproduction in cases where pure black was intended
and helps avoid problems with ink selection at the printer.
Proofing and production despite of errors Errors in the Workflow window newly do
not stop proofing or production.
2.1.3 Data Input
Module re-designed The Line Data Input module has been re-designed and offers
better functionality.
This module is intended to read data from text files that were originally formatted as
multiple pages for simple line-feed printers, but in fact it can be used to read other data
files. It creates regular expressions that match the format of the file and reads data
(from specific positions in that format) to data fields. The new design is more user
friendly and consistent with the GUI of the workflow environment in PrintNet T.
SAP merge data structures In the SAP Data Input module, new data structures can
be merged with ones that have been created previously using the Read & Merge
Definition icon on the Input File tab.
2.1.4 Data Processing
Data Case module The Data Caser module offers the optimal way to filter data. Ad-
vanced filtering can be applied with just this one module without the need to employ
scripting or multiple Data Filter modules. Data Caser creates one output link for every
filtering condition you define, plus one output link for the remaining data.
Confidential data Sensitive data can be printed without breach of confidentiality. Such
data can be replaced by defined characters in Proof and Production. Technically, this
feature is ensured by a new field converter.
Repeated run of selected modules The new Data Repeater module enables users to
run all modules connected before this module repeatedly, as many times as needed. It
can be used, for example, to read several data input files with one data input module
in a single PrintNet T run.
DirectSmile integration PrintNet T enables users to add variable images provided by
DirectSmile into Layout. Using this feature, personalised images with special effects can
be displayed. Technically, this feature is ensured by a new field converter.
Data Filter module with optional second output The Else output option enables data
filtered off by the defined condition to pass through.
Easy to use Email Gateway Data module Using the Email Gateway Data Module is
nowmore user friendly as it automatically adds the Data Output module to the workflow
too.
7
2 What's New in Version 7.0
2.1.5 Layout
2.1.5.1 General
DOC, DOCX and RTF as native DOC, DOCX and RTF file formats are supported as
native to PrintNet T.
Therefore, these file types can now be: Imported into a workflow (via the PNetT Native
module or Layout) allowing them to be easily manipulated with impositioning modules
or have extra text, images or variable data added to the current format; or loaded directly
to Proof or Production, which offers all the advantages of processing or converting the
format of files with the speed of PrintNet T.
Color libraries extended More color libraries are now available in PrintNet T to satisfy
customer preferences. To be specific, Pantone + Solid Coated LAB, Pantone + Solid
Uncoated LAB, Pantone Color Bridge Coated CMYK and Pantone Color Bridge Unicoated
CMYK have been added to the Color dialog.
Talo hyphenation support An extended hyphenation (provided by Talo) support is
available in PrintNet T now. Due to this extention, also deviant hyphenations and special
cases can be used.
The Talo hyphenation is not a part of PrintNet T installer, it is provided on request.
TrustCopy interface support TrustCopy provides an interface where it is possible to
incorporate watermarks into your documents. In this way, critical information of the
document (e.g., personal details, serial numbers) can be embedded into a watermark.
After the document is printed, the information can only be read using optical decoder
keys.
The TrustCopy plugin is not a part of PrintNet T installer, it is provided on request.
OverflowMessage variable The newvariable connected to a flowarea displays inform-
ation on objects in this flow area in case its content overflows. This helps to manage
document logic which can be adjusted based on the information returned from the
variable.
Unsupported characters substituted by Arial For variable text in natively imported im-
ages, when the Use dynamic variables option is applied with no Font replacement
defined, any unsupported characters are substituted with the default font (Arial).
2.1.5.2 Barcodes
Direct metrics for GS1 Barcode Enhanced control over the GS1 barcode measurements
allows to customize the bars and spaces relations, for instance to adjust the ink spread
on press.
Data characters in barcodes original form The barcode data text can be displayed in
the original or processed (coded) form. The coded form differs from the original when
sequences of characters allowed in a given barcode, code other characters. The original
form is typically displayed. The choice has been made possible for backward compatib-
ility.
8
2 What's New in Version 7.0
2.1.5.3 Charts
Funnel charts A new type of chart, the funnel chart, is available in 2D and 3D repres-
entations. It can be selected for Chart Type in the Chart Properties dialog.
This type of chart is ideal for marketing where they can be used to measure the success
of advertising campaigns.
2.1.5.4 Messages
Easier usage of message sources Messages sources for message groups can now be
scripted directly in PrintNet T so that the XML file does not have to be prepared in ad-
vance.
This feature is intended for PrintNet Interactive integration.
Clipping paths in message areas Using clipping paths in message areas is nowsuppor-
ted. You will see the clipped objects in Proof correctly.
2.1.5.5 DOC, RTF Native Import
Space before/after The paragraph style option Take maximum from space be-
fore/after is set to Yes automatically during RTF/DOC import to achieve the same
design as in the imported file. The maximum from the values Spacing After set for a
paragraph and Spacing Before set for a subsequent paragraph in MS Word is taken.
2.1.5.6 Minor Layout Enhancements
Variables in imported DOC/DOCX files In addition to the support of variables from
RTF format, PrintNet T can now match the variables from data also to the variables
predefined in DOC or DOCX files.
External flow definition The variable that defines the content of the external flow can
now contain the XML definition itself, not only the path to the XML (or RTF) file.
2.1.6 Output Modules
Flattened XML output Another format of XML data has been added to the Data
Output module which does not include array or optional elements. Select the Output
type: Flat XML.
This XML format is easier to read into another workflowvia the XML Data Input module.
2.1.7 Production
2.1.7.1 General
Creo software agent definition The PostScript RIP Speed Estimation can employ user
defined Creo software agent.
9
2 What's New in Version 7.0
2.1.7.2 Improvements by Engine
Adobe PostScript
Adobe PostScript ScreenTOP and Xerox background The Adobe PostScript engines
can generate externally background images keeping their original size and name. If the
images are processed, they are renamed after the workflow, with the"_b" suffix.
Keeping the original images names allows to refer to images by their original name (the
way they were registered in RIP) for PS files with external images.
AFP
AFP Engine optimizations Basic rotation (that is by 90, 180, and 270) of images (those
that are not processed, e.g. JPG, TIFF, PNG) is supported. Those images are not rasterized.
Also, resizing of images will not effect in rasterization as long as the aspect ratio is kept.
PNG images PNG images can be printed without being processed using the option
PNG on the Images tab of the AFP Engine Config dialog.
Only repeated images as resources New functionality enables to select that images
become a part of the overlay only if they appear more than once, otherwise they will
be placed directly on the page.
DOCX
DOCX engine enhancements This engine has been enhanced with the following
functionality:
Flow break after functionality for Column and Page,
Page numbering inserted in header can be set to start from a number you select,
Page orientation is defined according to X/Y axis values set in Layout,
Text rotation by 90 and 270 in text boxes is supported.
HTML / HTML Simple
HTML Simple output enhancements This engine has been enhanced with the following
functionality:
Bulleted and numbered lists are supported.
Table cells' margins (padding) can be defined in Border Properties in Layout. This
way you can further influence the text position in cells.
The Adjustable tables' widths option allows to influence the table form.
Metadata support HTML documents can newly contain additional information about
themselves which can be further used by other applications (e.g. Email Gateway, web
browsers).
10
2 What's New in Version 7.0
Clickable warnings in HTML Production Double-clicking on a warning in Production
when generating any HTML / HTML Simple job takes you to the spot, where the respect-
ive issue needs sorting.
Enhanced control over glyph positioning correction in HTML files You can choose to
do the necessary positioning corrections in text flows between words. This way individual
words are not split so that they are searchable in viewers.
IPDS
Map black color to OCA black Colors defined as black RGB, CMYK or CIELab in a
workflow can be ensured to print as pure OCA "black" using the Map black color to
OCA black option on the Color Management tab of the IPDS Engine Config dialog.
NewTIFF type supporting transparency For TIFF (0x42), transparency is nowsupported
when using the RGB TIFF compression or native TIFF files. This is applied only when the
printer supports transparency. If the printer does not support it, a warning is displayed
and transparency is omitted.
PDF and PDF Fixed Resolution
PDF Engine fonts enhancements The Adobe Japan1-6 glyphs are supported and do
not have to be embedded. This allows to reduce the size of the output files.
Also it is possible to select the fonts, that would only be referenced and not embedded
in the PDF output file.
PDF output compliant with more subsets This engine has been enhanced with the
following functionality:
PDF/A-1a gives a highly adaptable format for various viewing or importing/editing
methods. This subset employs PDF tags, that enable to mark (and potentially access)
the original document structure and allow to add alternative content to some ob-
jects. The tags can also be used independently of the PDF/A-1a subset.
PDF/VT subset is meant for variable-document printing (VDP). It can employ Docu-
ment Part Metadata, that allow to refer to the PDF document pages in a way sim-
ilar to a structured database select query. Referencing external XObjects reusable
for multiple files can be used with the PDF/VT-2 subset or independently.
Different processing way JPEG images with ICC profiles coming from native PDF files
are newly processed in a different way in case you have the Compression for JPEG
images set to JPEG. This results in faster processing of such images.
PDF pop-up notes You can add notes (annotations) to your PDF files using the URL
link functionality for PDF. The notes are, in the default state of the document, only in-
dicated by a note symbol. They can be unfolded and viewed by an interested reader.
Customlanguage values in Tagged PDF When creating tagged PDF files you can define
a custom value for the Document language field. The values need to be compliant
with the RFC 3066 standards, that are based on the ISO 639-1 codes.
11
2 What's New in Version 7.0
PNet T Native
Reporting of objects printed out of page This PNetT Native engine feature enables
users to switch on logging of warnings if some objects of the design are printed out of
page.
2.1.8 Related Applications
2.1.8.1 PNetTNetServer
Parallel processing of workflows One workflow can be processed in more threads at
a time when using the runw command. The runwcachelimit parameter specifies
the number of workflows that can be in cache at a time.
Run with licence for web products Usage of PrintNetTNetServer can now be distin-
guished; it can be used for production or for web products. If PNetTNetServer is intended
to be used for web products (not for production) it can be run using a new command
-runforweb which calls a licence limited for web products. Alternatively, this can also
be specified in the CONFIG file for PNetTNetServer.
Additional message It is possible to use the -reportjobfinishedmessage com-
mand for PNetTNetServer, which will then display the Job finished. message after a job
is finished.
VCS login setup To increase security you can specify the user name and password to
VCS in a CONFIGfile (instead of using the -vcsuser and -vcspassword commands)
so that this information is not kept in operating system processes.
2.1.8.2 PNetTC
WorkflowProcessing Parameter -createjobconfigonly The method allows smart
edition and generation of JOB files. This way you can extract parameters, edit them and
generate a new JOB file in the specified location, without having to open a workflow.
2.1.8.3 VCS
Forced branches in VCS Usage of branches can now be more specific; you can define
what should be done when a non-existing branch is in the file path. This is ensured by
using new parameters (FB and FBNI) in the path to a file in VCS.
This can be useful in case you do not want to execute Production when a non-existing
branch is defined in the file path.
Case insensitive log-in Login to VCS is not sensitive to casing any longer. Except when
two or more people have the same name and the only difference between them is the
casing used, which will still count as separate user names.
This is to improve compatibility with Windows user names which are also case insensitive.
12
2 What's New in Version 7.0
2.1.9 Scripting
Managing email settings from PrintNet T With the numerous new Util.Mail
methods, it is possible to work with email format and content as well as manage the
recipients data.
Scripting enhancements
Utilities Util.encodeURL(), Util.decodeURL(), Util.escapeURL()
and Util.unescapeURL() can be used for ASCII encoding URL addresses. This
helps embedding URLs in HTML outputs such as e-mails and web pages.
The string method toReplaced() replaces all instances of a given character in
a string with another character. This is a quicker method than replace() if all
occurrences of a specific character must be replaced.
UTL Utility methods Utilities Util.encodeURL(), Util.decodeURL(),
Util.escapeURL() and Util.unescapeURL() can be used for ASCII encoding
URL addresses. This helps embedding URLs in HTML outputs such as e-mails and web
pages.
toReplaced method The string method toReplaced() replaces all instances of a
given character in a string with another character. This is a quicker method than re
place() if all occurrences of a specific character must be replaced.
IntTable Utility IntTable can be used in all scripts for storing, manipulating and retrieving
two-dimensional data of the integer type Int.
readStringS The method readStringS can read a surrogate pair (consisting of two
characters) as one character, if it occurs in the data. It has been added among the script
data input methods as well as text stream methods.
Customizable timeout for receiving data from a server The setTimeout method allows
to set the waiting time limit according to the assumed time required. The default value
is 30 seconds.
Advanced VCS location specification in JOB file A JOB file with VCS location of a
workflow can be used in GUI Production, Simple Production, PNetTC and Proof.
Checking workflowdependencies Checking dependencies (used files) of any workflow
is now also possible via a script using the method detectDependencies.
This is an alternative method to using the Cross Reference Browser.
13
2 What's New in Version 7.0
3 Changes in Default Settings
This section lists differences in the applications default settings with the previous version (applied
to Beta and GA versions).
By default, characters higher than 65,536 (Unicode) that are written vertically are not
rotated in the vertical direction so that they are easily readable.
The way of generating external JPEG images has been changed so that generating is
now faster. Due to this, PDF files created in this version of PrintNet T are not able to
use external JPEG images saved by PrintNet T versions older than this one.
The Split file by group option in the File Driver Config is newly checked, by default,
for the HTML and HTML Simple engines.
JPEG images with ICC profiles coming from native PDF files are newly processed in a
different way in case you have the Compression for JPEG images set to JPEG. This
results in faster processing of such images.
The Do not correct character positions inside words option for the AFP, HTML,
IJPDS, Metacode and PCL engines is renamed to Keep glyphs positions within words
and this option is by default checked for the HTML engine.
TrueType fonts can nowbe referenced by name also for CID encodings (Japan1, Japan2,
CNS1, GB1, Korea1).
In previous versions unembedded fonts for the PDF outputs were searched in the system
directory and then in the PDF library. Newly, the search process for the Standard 14
fonts is adjusted to individual fonts (e.g. Arial is always searched in the systemdirectory,
Symbols in the PDF library).
In previous versions, PDF Flattener converted colorspaces to CMYK, newly PDF Flattener
(with the update of the PDF library to 9.1) keeps the original colorspaces.
PDF library has a limitation in passing real numbers to PrintNet T, used particularly for
text glyph positioning and shape object coordinates. Numbers lower than -32768 and
higher than 32767 are represented as the exact number -32768 or 32767. Newly, a
warning message is displayed when this occurs.
Proof run from Production behaved as Production but newly it behaves as Proof. I.e.
settings related to Proof are also applied in Proof run from Production. The Workflow
method IsProof returns true if Proof is run from Production.
The behavior of warnings and errors with different Abort and Error Recovery settings
was unified. The combinations of settings and the corresponding result, i.e. if the
warning/error with the specific settings ends as a warning, as a recovered error, or if it
aborts the job, can be found in the Warnings/Errors Behavior section.
The logic of handling license zones has changed. Customers affected by this change
will be contacted by GMC to ensure that license zones function in the same way as
before.
Newly, the Flatten transparency option is by default unchecked for WFD files that
were saved in the PrintNet T version 6.1 and older (that does not support this option).
14
3 Changes in Default Settings
PPML When the crop box and media box is different and the Use media box option
is not checked in Layout, the image in the PPML output was displayed as rescaled.
Newly, when the crop box and media box values differ, the following behavior occurs:
For PDF images used as fill styles for shapes and for object groups with clipping
paths (both with Use media box unchecked), the images are rasterized into EPS
including clipping paths.
For details on the Use media box option combinations and the consequences for the
PPML output see PrintNet T User Manual (Podi PPML Engine Configuration chapter).
PS2, PS3 Transparent monochromatic images are newly processed in a different way
in case you have the Put transparent monochromatic images into fonts option
unchecked. This results in faster processing of such images.
ICC profiles for PDF/A To conformto the PDF/A specification, the default Built in sRGB
Profile now uses the ICC profiles of the version 2 instead of the version 4.
In addition, it is internally ensured that the PDF/A subset will use only ICC profiles of
the version 2.
PostScript2, PostScript3 When using the Reuse generated background images
option for Xerox and ScreenTOP, the hash EPS file is generated. Now, the hash EPS file
also contains indexed fonts (Arial0, Arial1, Verdana0, ...); originally the fonts were not
indexed at all.
Thus, do not forget to regenerate the hash EPS file with this new content if you use
the file repeatedly without generating it with every spool.
New mode for bookmarks Generating bookmarks is now more intuitive. You can use
the new option Skip bookmark which excludes those bookmarks whose sheet names
are empty.
PDF The LAB color space has been newly defined in the correct way. Thus, LAB colors
might be different compared to previous versions.
4 Application Requirements
4.1 Supported Platforms
In its current version, PrintNet T is supported on the following Microsoft Windows versions:
PrintNet T 32-bit:
Support Level
Once a release* Windows Server 2003
Fully supported Windows Server 2008
Fully supported Windows Vista Ultimate
Fully supported Windows 7
15
4 Application Requirements
PrintNet T 64-bit:
Support Level
Fully supported Windows Vista Ultimate 64-bit
Once a release* Windows 2008 64-bit
Once a release* Windows 7 64-bit
* Selected versions are tested once in a testing cycle.
Note Windows XP (32-bit and 64-bit) can be supported on demand for enterprise clients.
4.2 Hardware Requirements
Minimum Configuration
Pentium IV at 1500 MHz
512 MB RAM memory
Monitor with resolution 1024x768 for the Classic and XP skin or 1280x800 for the
Win 7 skin
Note Even though the technical data and information as mentioned before have been prepared
with the utmost care and GMC believes to the best of its knowledge that the information
supplied is correct, GMC does neither expressly nor implicitly assume any legal liability or re-
sponsibility for its accuracy, completeness and/or usefulness.
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 com-
patible.
Client Server
7.0 6.2 6.1
Yes Yes Yes 6.1
Yes Yes Yes 6.2
Yes Yes Yes 7.0
4.3.2 DirectSmile
The following table shows which DirectSmile versions are compatible with the current version
of PrintNet T.
16
4 Application Requirements
Version DirectSmile
4.0 DirectSmile Image Server
4.0 DirectSmile Integration Server
4.3.3 Line Data Input Module
LDIM Line Data Input Module version 5.1.2.0 plug-in for PrintNet T can be added to the
PrintNet T installation using a special installer distributed separately.
The Line Data Input GUI enables users to transform data structured into pages and lines into
a record based data stream usable in PrintNet T.
For more information regarding the LDIM please see the document PNT-LDIM_Release_Notes-
V5.1.2.0-GA.pdf.
5 Testing Results
The testing results are presented for the following version of PrintNet T:
PrintNet T 7.0.63.0
5.1 Test Environment
This version of PrintNet T has been tested in the following test environment for which the
performance and results are guaranteed.
Windows XP 32-bit and 64-bit, Windows Vista Business 64-bit, Windows Vista Ultimate 32-
bit, Windows 2003 server R2 EE 64-bit, Windows 7 Ultimate 64-bit, Windows 7 Professional
32-bit and 64-bit, Windows Server 2008 EE 64-bit.
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
PrintNet T 7.0.63.0 was tested with Citrix XenCenter. Remote access was verified.
Clustering on Windows Server 2008 was verified.
5.2 Test Statistics
Design Part
2687 Sum of test cases:
100% Overall success:
17
5 Testing Results
Outputs
28570 Sum of test cases:
112395 Compared pages (BMP):
100% Overall success:
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.
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 section in PNT
User Manual (Tested Configurations for Printers).
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
18
5 Testing Results
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
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
19
5 Testing Results
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.
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:
20
5 Testing Results
Without
conversion
Convert to image types PrintNet T Image Type
Source
JPG TIFF EPS
H
P
X
e
i
k
o
n
C
r
e
o
H
P
X
e
i
k
o
n
C
r
e
o
H
P
X
e
i
k
o
n
C
r
e
o
H
P
X
e
i
k
o
n
C
r
e
o
2 monochrome BMP
4bitpalette
8bitpalette
truecolor
24bitcolor
32bitcolor
16bi_R5G6B5
16bi_X1R5G5B5
16bi_X4R4G4B4
24bi_R8G8B8
24bitcolor_in-
verse_order
32bi_X8R8G8B8
optimized JPG
4 progressive
standard
ICbCr1x1_1x1_1x1 JIF
standard PNG
interleave
transparent
3 2 1 version_0 PCX
version_2
version_5
nocompress TIF
5 5 5 JPEGcompress
LZVcompress
palette
transparent_LZV
transparent_nocom-
press
transparent_ZIP
21
5 Testing Results
Without
conversion
Convert to image types PrintNet T Image Type
Source
JPG TIFF EPS
H
P
X
e
i
k
o
n
C
r
e
o
H
P
X
e
i
k
o
n
C
r
e
o
H
P
X
e
i
k
o
n
C
r
e
o
H
P
X
e
i
k
o
n
C
r
e
o
2 6 ZIPcompress
3 3 Huffman_RLE
3 3 CCITT_Fax3
3 3 CCITT_Fax4
withcolorprofile EPS
transp
6 6 6 6 6 no boudingbox
AdobeAc-
robat5_level1
AdobeAc-
robat5_level2
AdobeAc-
robat5_level3
87a_interlaced GIF
87a_nointerlaced
89a_interlaced
89a_nointerlaced
87a_interlaced
transparent
8bit_compressed TGA
8bit_uncompressed
16bit_compressed
16bit_uncom-
pressed
24bit_compressed
24bit_uncom-
pressed
AdobeAcrobat5 PDF
PDF_12
PDF_12_GMC
PDF_13
PDF_13_GMC
22
5 Testing Results
Without
conversion
Convert to image types PrintNet T Image Type
Source
JPG TIFF EPS
H
P
X
e
i
k
o
n
C
r
e
o
H
P
X
e
i
k
o
n
C
r
e
o
H
P
X
e
i
k
o
n
C
r
e
o
H
P
X
e
i
k
o
n
C
r
e
o
PDF_13china
PDF_14
Legend
1. Incorrect rotation and scaling.
2. The image is displayed as a black rectangle.
23
5 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.
6 Known Issues
6.1 Issues Known at the Time of the Service
Pack 1 Release
6.1.1 Level 1 Issues
No Level 1 issues have been detected.
24
6 Known Issues
6.1.2 Level 2 Issues
#80720 When a MICR (Magnetic Ink Character Recognition) toner is assigned to a spot color
and vector graphics are employed in the same job, 64-bit version of PrintNet T may crash
in rare cases. Even though during the testing of the 32-bit version PrintNet T did not crash
in the same circumstances, this version may also be affected by this issue.
Fixed in version 7.0.64.0.
#80877 Post Script output using the ScreenTop feature with CCITT image compression may
result in the generation of invalid EPS files. This happens when the compressed images
turn out to be larger than the original ones. In such cases PrintNet T uses the smaller (ori-
ginal) images, but they are marked as CCITT compressed in the EPS file.
Fixed in version 8.0.4.0.
#80861 If natively imported PCL files contain soft fonts with fixed spacing, the size of such
fonts is calculated in a different way than for proportional character spacing. However,
PrintNet T uses the calculation method for proportional spacing which may result in a
different font size than expected.
#80847 AT#31412 If natively imported PCL files apply "Delta row" compression to images
and "raster-y offset" for rows is used in such files, the rows should be automatically deleted
when importing. However, PrintNet T keeps these rows which may result in incorrect
output.
6.1.3 Third Party Issues
#21609 PDF library issue on two-processor machines PrintNet T 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 customers solution.
#34792 If an attempt is made to run PrintNet T using a Citrix client then PrintNet T 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.
#65905 PDF If transparency flattener is applied, newimages are created for all original images
which had the DeviceCMYK color space set (i.e. they had no ICC profile). These newimages
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 combo-box on
the Graphics tab of the PDF Engine Config dialog. This ICC profile will then be applied to
all images.
#70299 PDF There is contradiction between the PDF specification and Adobe Acrobat be-
havior for rotated text. PrintNet T satisfies the PDF specification and displays this text as
not rotated (due to the PDF library), however, Adobe Acrobat displays this text as rotated.
25
6 Known Issues
Workaround: In the PDF file source, the 'cm' operator has to be used outside the text
object (BT, ET).
#77050 When converting a DOC file into any other format using the DCOM interface and
any problemoccurs during this conversion, the conversion freezes and cannot be finished.
This is because Microsoft does not support using server-side automation to provide MS
Office functionality.
7 Known Limitations
7.1 General
a. PS like Using large raster images as a text fill style can slow down printing because
the whole image is used for each character.
b. Concatenation of a large number (several thousand) of PDF files into one file might
cause PrintNet T to crash as the system runs out of memory.
Workaround: Use file splitting to generate files with a smaller number of pages.
c. The Japanese KAJO font is not displayed correctly as the FreeType interpreter has dif-
ferent behavior than Windows.
d. It cannot be guaranteed that text using the Big5 encoding will be displayed properly
in PrintNet T. PrintNet T uses the Unicode standard to which the Big5 encoding cannot
be unambiguously transformed.
e. If a user with administrator rights has the UAC function enabled, they can start Print-
NetTNetServer as a service on the MS Vista and Windows 7 operating systems only via
an elevated command line.
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 in-
creases in comparison to processing with the Parallel processing check-box disabled.
g. Parallel processing cannot be used for the following engines: DOCX, Text, HTML Simple
and HTML (if the option Raster flows is unchecked for the Email generation mode).
h. The library for color transformations has been updated. Thus, color profiles not loaded
correctly before are now loaded correctly. But, transformed colors might be insignific-
antly different compared to previous versions or text in the combo-box for selecting
ICC profiles might slightly differ.
i. PDF When generating a PDF file in PrintNet T with the option Tagged PDF checked
and the PDF file contains text with natural reading order fromright to left, the reflowing
functionality in Adobe Acrobat does not work correctly for such text.
j. When importing an RTF file to PrintNet T and if this file contains the "sl0" command
used for line spacing, the lines (for which the command is used) overlap in PrintNet T.
26
7 Known Limitations
7.2 Known Limitations of the 64-bit Version
of PrintNet T
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 PrintNet T 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. Condproc and PNet3
e. Mediabin
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 function-
ality, 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
PrintNet T 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 previ-
ously 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), 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 replace-
ment rules can be set using the "Insert Font Replacement" functionality in the Others
node of the Layout Tree.
27
7 Known Limitations
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.
d. All patterns are rasterized (the vector information is lost), i.e. they are transformed to
an image fill style in PrintNet T.
7.4 AFP Native Import Known Limitations
The following features of the AFP format are not supported by the current PrintNet T version:
a. Line data:
a. XMD based pagedefs
b. RCD Graphics Descriptor (X'7E') Triplet
b. Non-presentation object containers (linked/collection True Type fonts, PDF resources,
etc.)
c. ACMA AFP Color Management Architecture
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,
28
7 Known Limitations
it is possible to apply patterns and Logical Operations Command parameters.
Native import of PCL documents into PrintNet T supports them with certain limitations (see the
table below).
Fonts Areas Images Feature Type
Opacity in Source
Transparent Mode
not supported.
Full support Full support for
monochromatic
images only
solid white Patterns
Some patterns used
as fill styles might
Full support solid black
Full support for
monochromatic
images only
shading
have a different ap-
pearance.
cross-hatch
user defined
Full support Full support for
monochromatic
images only
252 T OR S (default) ROP
240 S (source only)
204 T (texture only)
A further limitation of PCL native import concerns underlining:
The underline feature is not supported for commands that execute absolute or relative
positive horizontal movements (screenshot 1). However, the typical usage a line
starting with an underlined text is supported (screenshot 2).
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.
29
7 Known Limitations
7.6 XSLFO Known Limitations
PrintNet T 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 PrintNet T 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 (PrintNet T 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 later.
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 PrintNet T and also describes the results of import of features which are not fully
supported.
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 newfeatures
are developed and added into the specification. However, the import into PrintNet T 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 (imple-
mented) or included in this known list.
30
7 Known Limitations
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.
Images:
Image types Import of images is restricted to image types supported by PrintNet T.
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 PrintNet T.
31
7 Known Limitations
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. PrintNet T 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 PrintNet T style.
Z-order:
Z-order The order of two overlapping objects (e.g. text and image) is not kept during
import. The method that PrintNet T and MS Word use to render the objects is different.
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 PNGimages 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).
32
7 Known Limitations
Fields (variables):
Fields are not recognized as variables during the import to PrintNet T 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. Subscript (if used, appears as smaller font)
c. Superscript (if used, appears as smaller font)
d. Horizontal scale
e. Language
f. Kerning
g. Image fill style
h. Gradient fill style
i. Border style
j. Line fill style
33
7 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. Margins (with the exception of table cells)
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.
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.
34
7 Known Limitations
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 Email Generation Mode Known Limitations
a. Text in sections is not supported and is rasterized.
b. Flow areas with borders are not supported and are rasterized. In Production a warning
is generated.
7.9.3 Known Third Party Issues
7.9.3.1 Email Clients
HTML clickable maps (areas with a link to another URL address assigned) can be displayed
incorrectly in Outlook 2007 (in other email clients the issue does not occur).
If in Layout, in one flow area, there are two (or more) elements with URL paths through
image areas assigned, only the one processed first is displayed and works 100%correctly
in Outlook 2007. The clickable areas of the remaining elements are placed outside of
the assigned objects in a blank space or over other objects. The issue may additionally
interfere with the HTML document's background (if set).
Example
Both images are placed in elements, that are placed in one flow area.
35
7 Known Limitations
Legend
1. The clickable area assigned to the first image works correctly.
2. The clickable area is shifted below the image that the URL path is assigned
to.
Workaround
Place elements, with the URL path assigned, into separate table cells or separate
flow areas. Then all of those objects display correctly and keep their functionality
in Outlook 2007, or
Make the image area, with the URL path assigned, exactly the same size as the
element box.
Some email clients (e.g. Outlook 2007) do not support background images in HTML
email content. To keep the intended design, any flow area overlapping with an object
drawable in the HTML output (in the Email mode) is automatically rasterized.
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.2 Web Browsers
MS Internet Explorer does not support CMYK images.
Workaround
In the Website generation mode disable the Support JPGcheck-box on the Images
tab, or
Generate the HTML file in the Email mode.
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.
36
7 Known Limitations
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 PrintNet T 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.
8 Localization
The 7.0.63.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.
PrintNet T Version Language
7.0.29.0 French
7.0.29.0 German
7.0.29.0 Czech
7.0.29.0 Spanish
7.0.29.0 Italian
7.0.29.0 Portuguese
37
8 Localization
9 Printing with Xerox 980
The following features and settings improve printing performance on the Xerox 980 printer:
ICC profiles can be applied at the time of spooling for all relevant engines in the Engine
Configuration dialog.
For Adobe PS2 and PS3 engines a hybrid PostScript output can be created for use on
the Xerox 980 printer. In the Custom Images Generating section on the Images tab
enable the option Use and select Xerox enhancements.
AFP settings:
Layout:
For images it is necessary to make sure their embedded profiles are used. In
the Layout Properties of images go to the Advanced tab and set the option
Embedded profile usage to Always use profile.
In the Layout Options dialog Current Layout Module Options select the color
space of the embedded profiles of images.
Engine Config:
On the General tab set Output Colors to Full color.
On the Color Management tab select the desired ICC profile.
See the PrintNet T User Manual for more information about the employed features.
A Fixed Issues
This chapter lists public issues fixed since the last published version, i.e. for the versions 7.0.43.0
up to 7.0.63.0.
Fixed in Version 7.0.63.0
#80653 AT#31470_customer DBF files cannot be previewed and cause crash in higher versions
#80694 AT#31227 - Japanese text doubled
#80722 AT#27942 JDF Xerox
Fixed in Version 7.0.62.0
#80639 AT#31494 PS file crashes PNetTView
#80642 AT#31350 ICP with incorrect lenght cannot be imported/ignored
#80654 AT#31417 IPDS Positioning space outside printable area returns position check
38
9 Printing with Xerox 980
Fixed in Version 7.0.61.0
#80251 AT#31149_[DocX]: check compatibility of DocX files from customer
#80533 AT#31287 Line Data Input - display data at wrong position
#80556 AT#31333 Data Caser module is missing if another language is chosen
#80618 AT#31433_Crash on Acknowledge button used with parallel processing
Fixed in Version 7.0.60.0
#80071 AT#30927 - Print from proof prints just 1 page
#80251 AT#31149_[DocX]: check compatibility of DocX files from customer
#80395 AT#31187 WorkFlow.detectDependencies() lists removed files from vcs
Fixed in Version 7.0.59.0
#79680 AT#30648 VCS access rights can be cheated
#80046 AT#30941_[RTF import] problem with tables import in 7.0 compared to 5.3
#80089 AT#30304 Variable in System variables is not visible in script.
#80193 AT#30930[Variable formatted flow]: Formatting lost when referenced Conditional
Text style
Fixed in Version 7.0.58.0
#79402 AT#30146 PNT random error
#79803 AT#30369 - VCS - Server Maintenance Clean Up feature
#79817 AT#30759 Change font in TextStyle
#79895 AT#29522 AFP - NOP not readed
Fixed in Version 7.0.57.0
#79681 AT#29761 - VCS crash
#79765 AT#30772 AFP IOCA images disappeared
Fixed in Version 7.0.56.0
#79569 AT#30562_[Net license]Delete dongle content when there is not used volume license
#79625 AT#30615 Wrong state of project after commiting remove operation and closing
project
#79664 AT#30661 PDF Native Large monochromatic image cannot be imported
#79709 AT#30150 Annual license error on Windows XP
#79710 AT#30649 VCS force login start wrong environment
39
A Fixed Issues
Fixed in Version 7.0.55.0
#79382 AT#30460 AFP Native BPG/BAG/MCF/RG(0)/t0x50: Value of ESidCP (0x0250) is out
of range.
#79414 AT#30499 ErrorRecovery doesn't work on stackFCV
Fixed in Version 7.0.54.0
#78754 AT#29820 2D Barcode - display encoded data
#79255 AT#30074 DataMatrixBarcodeReader - incorrect detection
#79429 AT#30519_Project wfd cannot be saved
Fixed in Version 7.0.53.0
#79127 AT#29804_[wfd2xml] PNetTC and PNetTGUI does not return same XML VCSLocation
tag value
#79215 AT#30255 CMYK to CMYK ICC transformation is not applied on vector objects
#79255 AT#30074 DataMatrixBarcodeReader - incorrect detection
#79263 AT#30362 Wrong color of commented script
#79275 AT#30337 Wrong raster output from barcode in PDF
#79329 AT#30247 - PDF Library limitation, object coordinates +-32768
Fixed in Version 7.0.51.0
#78068 AT#29033 - Font names displayed incorrectly
#78586 AT#29307 - PNT crash in Script Data Input module
#78958 AT#30086_ Crash when Proof workflow from Project
#79000 AT#29973 IPDS JPEG compression activated in Full Color modes
Fixed in Version 7.0.50.0
#75992 AT#26626 Metacode DJDE structure
#78572 AT#29460 - Cursor position jumps in Japanese
#78586 AT#29307 - PNT crash in Script Data Input module
#78628 AT#29787 - Renaming FlowAreas in PNT 7.0
#78647 AT#29822 - Error message when opening WFD from InDesign
#78701 AT#29591 - Chart axis issue
#78758 AT#28887 Simple Production Unloads workflow
#78960 AT#30086_Cannot compile scripts in external wfd in Project
40
A Fixed Issues
Fixed in Version 7.0.49.0
#78347 AT#28982 LAB values of gray color
Fixed in Version 7.0.48.0
#77921 AT#29137 AFP The glyph A? disappears when using outline fonts
#78122 AT#29225 Dates on Axis X
#78355 AT#29537 Setting group size to 0 produces invalid PDFs
#78397 AT#29627 Mistake in CID fonts with singlebytes encoding
#78456 AT#29636 - Crash after XML import
#78488 AT#29444_SAP data randomly not read
Fixed in Version 7.0.47.0
#77974 AT#29153 AFP Cielab values in Indexed colors are not accurate
#78068 AT#29033 - Font names displayed incorrectly
#78070 AT#29132 Run time error in Production
#78099 AT#29380_[PDF/PS] Barcode with certain height is not displayed due to the PS limit-
ation
#78158 AT#29441 TextInRect always shows pages from 1st ouput of preceding module
#78238 AT#29478_ Cannot open customer project in Project browser
Fixed in Version 7.0.46.0
#77974 AT#29153 AFP Cielab values in Indexed colors are not accurate
#78010 AT#29223 - Renaming variable
#78048 AT#29291_new method GetProcessID causes malfunction on Windows 2000
#78058 AT#27966 Allow clipping of Message Areas
Fixed in Version 7.0.45.0
#77226 AT#28390 PS Native Incorrect font
#77502 AT#28819 DOCX Font of added text in empty line in Word changed to default
#77799 AT#29023 - Cannot open WFD in 6.2 and 7.0
#77904 AT#29151 XSD Empty alias for XMLSchema xmlns namespace
#77909 AT#29121 - Crash in Project Browser
41
A Fixed Issues
Fixed in Version 7.0.44.0
#77148 AT#28248 - PCL Tray disabled in Output Module
#77229 AT#28348 missing text when import and load natively
#77237 AT#28373 Recursive XSD schema
#77260 AT#28340 - Variable FillStyle in graph
#77363 AT#28479 Error during PDF native import
#77463 AT#27942 Xerox JDF file
#77476 AT#28694 Util.Mail.setHTMLBodyFromFile() vs .setHTMLBody
#77484 AT#28812 AFP Object type different on BRS, BOC and MDR
#77487 AT#28495 AFP Native Unable to draw image on page 9
#77501 AT#28554 Problem with validation PDF/1A-b using validatepdfa.com
#77532 AT#28805 PNTC Error 0017 Processing TNO to PDF output
#77539 AT#28843 - Crash with drag and drop of table
#77567 AT#25487 - AFP file viewed in PNeTViewer
#77579 AT#28866 Imposition script does not work correctly on 64 bits
#77591 AT#28533 Error on netserver - unknown alias
#77595 AT#28263_[IJPDS]: investigate memory increase during spooling
#77630 AT#28945_ Data group by without sort divides same key
Fixed in Version 7.0.43.0
#76782 AT#26991_AFP image cannot be loaded during the spooling
#76972 AT#27942 Xerox JDF
#76977 AT#28076 - TIFF image distorted
#76983 AT#27954 VCS storage erased when .remove("") is used
#77020 AT#28147 Surrogate method midS(x) returns wrong result
#77040 AT#28152 MIBF font compression cut font
#77043 AT#28146 Compare workflows crash
#77086 AT#28219_Volume license count increased from 1Mi to more than 4Mi sheets
#77097 AT#28257 Font replacement warning message
#77188 AT#28310 XSD redundant virtual nodes
#77229 AT#28348 missing text when import & load natively
42
A Fixed Issues