Subcommands

HEIGHT Subcommand
HEIGHT 10 POINTS | HEIGHT n [POINTS | IN | CM | MM | PELS]
Specifies the height of a Data Object font.
n
A number specifying the height of the Data Object font. This number can be up to 3 decimal places.
Note: If HEIGHT is not specified the default is 10 points.
units
One of the following standard units:
POINTS
Each point is equivalent to 1/72 of an inch (default)
IN
Inches
CM
Centimeters
MM
Millimeters
PELS
Pels in the current Logical Units per inch; for example, in 240ths of an inch
RATIO Subcommand
RATIO percent
Specifies the ratio of scaling the width relative to the height in a font.
percent
Represents the percent of the normal width of the character that is printed. For example, RATIO 50 yields a font with characters half as wide as normal.
ROTATION Subcommand
{ROTATION [0 | 90 | 180 | 270]
Specifies the rotation of characters in degrees. The specified value is relative to the inline direction of the line to be printed. Valid rotations are 0, 90, 180, and 270. Zero is the default.
PRELOAD Subcommand
PRELOAD
To preload the font before starting the print job, specify this subcommand. Preloaded fonts enhance print performance. The printer must support this function.
UDType Subcommand
[UDType of the PAGEDEF |  
UDType {EBCDIC [CP {'T1V10500' | code-page-name}] |
EBCDIC2 CP code-page-name |
ASCII [CP {'T1000819' | code-page-name}] 
UTF8 | UTF16}]
The UDType subcommand specifies the user's data type and, optionally, the code page name for mapping the font.

If UDType is not coded on the DOFONT command it defaults to the coded or default UDType of the page definition.

    Note:
  1. Using a code page with a UDType specifies the code page used by the application to create the data.
  2. To use multiple font mappings for a line in ASCII, UTF8, or UTF16 you must use the FIELD command, since automatic font switching for single and double byte text is only done for EBCDIC data.

EBCDIC
Single byte EBCDIC.
CP
Code Page name. This parameter is optional here and, if not coded, the default is single byte EBCDIC code page T1V10500.
code-page-name
Enter a quoted or unquoted string for the code page name. If the string is unquoted it can be up to 6 characters. The string will be folded to upper case and the two-character prefix T1 is added. If the string is quoted, it can be up to 8 characters, will retain the case, and no prefix is added.
EBCDIC2
Double byte EBCDIC.
CP
Code Page name. This parameter is mandatory.
code-page-name
Enter a quoted or unquoted string for the code page name. If the string is unquoted it can be up to 6 characters. The string is folded to upper case and the two character prefix T1 is added. If the string is quoted it can be up to 8 characters, will retain the case, and no prefix is added.
ASCII
Single byte ASCII.
CP
Code Page name. This parameter is optional here and, if not coded, the default is single byte ASCII code page T1000819.
code-page-name
Enter a quoted or unquoted string for the code page name. If the string is unquoted, it can be up to 6 characters. The string is folded to upper case and the two character prefix T1 is added. If the string is quoted, it can be up to 8 characters, will retain the case, and no prefix is added.
UTF8
Unicode encoding form UTF-8.
UTF16
Unicode encoding form UTF-16.
MICR Subcommand
MICR
Specifies that this font is to be used for MICR print. MICR print defines that the font is to be used for Magnetic Ink Character Recognition (MICR) printing. When MICR printing is requested, the font needs to be designed for use in MICR applications. MICR text is normally printed using a toner that is mixed with a magnetic material.
INLINE Subcommand
INLINE
Specifies that this font resource is to be found in an inline resource group when processing the line data and no additional resource libraries are to be searched. Its use is intended to correspond to a data object font resource used with complex text contained in a PTOCA text object. This PTOCA text object is included using the OBJECT command in PPFA.

Complex text languages provide different layouts for the presentation of text and its storage. Bi-directional (BIDI) languages present text normally from right to left; however, some text such as numbers and embedded Latin, Cyrillic and Greek scripts, are written from left to right. These BIDI languages include Arabic, Urdu, Farsi and Hebrew.

It is strongly recommended that all TrueType/OpenType fonts that are used for complex text rendering be placed in the print file resource group (inline). To ensure that only a font from the print file resource group is used by the presentation system, it is strongly recommended that the INLINE parameter be used for such fonts. The user is responsible for including the font in an inline printfile resource group.

Parent topic: DOFONT Command