|changes||version 188.8.131.52||version 184.108.40.206|
Faults reported in this release:
|220.127.116.11||Symbol Set Generate||In a number of cases, the symbol set type of a generated symbol is set to Bound PC8, rather than the correct Bound 8-bit designation; in a few cases, the opposite could occur.|
|18.104.22.168||Font Sample||For a PCL font, if the Unicode character set is chosen, and the (default)
associated Text Parsing Mode 83 ("UTF-8") is selected, invalid UTF-8 data values
are generated for the 'upper-half' of the grid, if the range offset is specified as zero;
valid data is generated if the range offset is non-zero.
In order to obtain the expected printed grid, select the (single-byte) ISO-8859-1 character set instead; this is an exact subset of Unicode (it matches row 0 of plane 0 (the Basic Multilingual Plane)).
|22.214.171.124||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, is not the correct equivalent value.|
|126.96.36.199||Font Sample||If the Symbol set option is set to the <specify identifier> value
when the tool is started (i.e. this and the associated custom identifier are the values restored when the
application is started), this symbol set identifier is not used when the print job is generated (so the printer
will probably use its default symbol set).
The problem does not occur if the custom option is selected after a different earlier preceding value has been set.
|188.8.131.52||Misc Samples||With the Unicode Characters option, the variant part of the name of the selected
font name is shown on the printed page as a numeric value, rather than as the variant name.
For example, Arial Regular is shown as Arial 0.