7.6

Codepage 1252 (ANSI - Latin 1) is used for many Latin language documents, since it can be used for Afrikaans, Basque, Cat-
alan, Danish, Dutch, English, Faroese, Finnish, French, Galician, German, Icelandic, Indonesian, Italian, Malay, Norwegian,
Portuguese, Spanish, Swahili and Swedish. Codepage 932 is often used for Japanese.
Input
Any text-based data file.
Processing
The characters in the data file are converted from the old encoding to the new one.
Output
The data file in its new encoding format. Metadata, job info and variables are unchanged.
Translator action task properties are as follows:
General tab
l Source encoding: Select the current data encoding. Note that the source encoding is not selected automatically and
you must therefore select the proper encoding from this list in order for the conversion process to be performed suc-
cessfully.
l Target encoding: Select the encoding to which you want the data to be converted.
l Include target encoding signature: This option is only available when converting to UTF-8 (Windows code page
65001) or UCS-4 (code page 12000 or 12001). Select to include the character encoding signature—also known as the
byte order mark—at the beginning of the target string.
l Default character on translation: You may enter a character to be used to replace all those characters that can-
not be found in the source encoding. If you leave this box empty, they will be simply stripped from the data, so you may
consider using a space as a place holder for unidentified characters.
On Error Tab
The On Error Tab is common to all tasks. Details can be found on Task Properties Dialog.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are
being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window
will be available for the rest of your process, or whenever they are overwritten.
Windows Print Converter
Windows Print Converter action tasks are designed to convert Windows print files into Line Printer files, that can then be used
in a variety of other PlanetPress Suite Workflow Tools tasks. Typically, Windows Print Converter action tasks are located
below WinQueue input tasks (note that the latter include options specific to Windows Print Converter action tasks).
The full conversion process is performed in two phases:
l The Windows print file is first converted into an XML file in which each printable character appears with its horizontal
and vertical coordinates.
l The XML file is then converted into a standard Line Printer file.
Note that although it is more common to perform both phases in a single pass, each phase can be performed selectively, as
required.
Input
A print job in EMFformat, generally captured from a WinQueue input task.