TRC

Specifies whether the input file contains table reference characters (TRCs). In line data, you can use different fonts on different lines of a file by specifying a TRC at the beginning of each line after the carriage control character, if one is present.

Note: TRC characters can be used to map fonts in documents that reference either TrueType and OpenType fonts or FOCA fonts, but not a combination of the two.

For more information about TRCs, see Advanced Function Presentation: Programming Guide and Line Data Reference, S544-3884.

TRC={NO | YES | YES, FIX | YES, STRICT | YES, DISCARD | YES, IGNORE}
The values are:
NO
The input file does not contain table reference characters.
YES
The input file contains table reference characters. The first byte, or second byte when carriage control is enabled, is interpreted as a table reference character, therefore it is not printed. Line data records shorter than the number of bytes required to hold a table reference character and carriage control are not correct, when enabled.
FIX
ACIF allows zero-length line data records, including single spacing.
When specified, FIX is also used for the CC parameter. See CC, for more information.
DISCARD
ACIF discards zero-length line data records.
When specified, DISCARD is also used for the CC parameter.
IGNORE
ACIF allows zero-length line data records, including the selection of font 0. However, ACIF does not correct and does not report missing TRC bytes.
When specified, IGNORE is also used for the CC parameter.
    Note:
  1. The order in which the fonts are specified in the CHARS parameter establishes which number is assigned to each associated TRC. For example, the first font specified is assigned 0, the second font 1, and so on.
  2. If you specify TRC=YES but TRCs are not contained in the file, ACIF interprets the first character of each line (or second, if carriage control characters are used) as the font identifier. Consequently, the font that is used to process each line of the file might not be the one you expect and 1 byte of data is lost from each record.
  3. If you specify TRC=NO or you do not specify TRC at all, but your line data contains a TRC as the first character of each line (or second if carriage control characters are used), ACIF processes the TRC as a text character in the output, rather than using it as a font identifier.
  4. Table reference characters may cause line data records to contain an odd number of bytes with UTF-16 encoding.
Parent topic: Parameter values for ACIF