|reported faults||version 220.127.116.11||version 18.104.22.168|
Changes in this release:
|Enhancement||Font Sample||If a multi-byte Text Parsing Method is selected (applicable when a 16-bit symbol set is selected), more than one range offset value may be selected (each such range defines up to 256 characters); previous versions only allowed one such range to be selected for each job.|
|Enhancement||Font Sample||If a User-defined symbol set file is specified, the target Unicode code-points (as defined by the mapping in the specified symbol set file) may (optionally) be shown (in hexadecimal) at the top of each cell in the printed grid.|
|Enhancement||Font Sample||For a PCL XL font, a User-defined PCL symbol set file
may now be used to determine the mapping of character-codes to target code-points.
The generated print job will select the Unicode symbol set (identifier = 18N, equivalent to Kind1 value 590), and the contents of the specified file will be used to define which Unicode code-points will be used for each cell in the grid.
For a PCL font, a similar action may now (optionally) be selected, instead of the usual action of downloading the contents of the specified file at the start of the generated print job, and selecting the symbol set defined within that file (i.e. the printer will interpret the downloaded symbol set definition to determine the required mapping).
|Error clearance||Font Sample||For a PCL font, if the Unicode character set was chosen, and the (default) associated Text Parsing Mode 83 ("UTF-8") was selected, invalid UTF-8 data values were generated for the 'upper-half' of the grid, if the range offset was specified as zero (valid data was generated if the range offset was non-zero).|
|Error clearance||Font Sample||If the Symbol set option was set to the
<specify identifier> value when the tool was started (i.e. this
and the associated custom identifier were the values restored when the application was
started), this symbol set identifier was not used when the print job was generated (so the
printer would probably use its default symbol set).
The problem did not occur if the custom option was selected after a different earlier preceding value had been set.
|Error clearance||Misc Samples||With the Unicode Characters option, the variant part of the name of
the selected font name was shown on the printed page as a numeric value, rather
than as the variant name.
For example, Arial Regular was shown as Arial 0.
Soft Font Generate
Symbol Set Generate
|Mappings have been defined for more of the standard symbol sets.
Slight changes have also been made to how this information is displayed, and to the effect on the Mapping panel in various tools.
|Error clearance||PRN File Analyse||The hexadecimal value following the decimal value of the Mapping: Kind1 property, as shown in the analysis of PCL XL font headers, was not the correct equivalent value.|
|Enhancement||Soft Font Generate||The format of some of the diagnostic data (output when the Log diagnostics option is selected) has been changed, and additional interpretation is provided for some entries in certain tables (e.g. ttcf, name, OS/2, and cmap) of the donor TrueType font.|
|Error clearance||Symbol Set Generate||In a number of cases, the symbol set type of a generated symbol was set to Bound PC8, rather than the correct Bound 8-bit designation; in a few cases, the opposite occurred.|
|Enhancement||Tray Map||The original version of this tool generated test print jobs which printed up to 300
simplex sheets (each selecting a different tray source identifier
(in the range 0 - 299), but the same paper size,
paper type and orientation attributes).
This version only allows for a maximum of six sheets in each generated print job, but each sheet may:
|Enhancement||-||To avoid apparent 'hang-ups' if the target network printer is unavailable, or there are unspecified network issues, socket timeout periods can now be set.|