Ricoh InfoPrint Pro C900AFP InfoPrint Manager - Page 279

Note: If you are not able to stop the server because you are not authorized for that action, check the InfoPrint Manager Access Control List (ACL) for the Shutdown operation. Log off and log back on as a user who is on the access control list. 3. Select Edit → Service Configuration. 4. Update both the Default Font Search Path field and the Default Resources Search Path fields with the directory where the OpenType fonts reside. Using OpenType fonts with line data When printing line data with OpenType fonts through InfoPrint Manager, you need to specify the appropriate parameters on the line2afp command. To define the location of the OpenType fonts to the line2afp command, you can either use the InfoPrint Manager global search path (using "Updating the global search path on an InfoPrint Manager Windows server" on page 260) or use the appropriate values on the line2afp command. For more information about these values, see either Using OpenType Fonts in an AFP System or ACIF: User's Guide. For more information about either creating or modifying page definitions for line data jobs to print with OpenType fonts, see Page Printer Formatting Aid: User's Guide. Limitations when printing line data with OpenType fonts Before you can print this data, you must transform it to Unicode Transformational Format (UTF-16), with big-endian byte order. Big-endian byte order means that in a two-byte UTF-16 code point the high-order byte is specified first, followed by the low-order bytes. You can transform it through the uconv utility, or any other application that transforms ASCII to Unicode. For more information about the uconv utility see the AIX operating system documentation. Line data using OpenType fonts supports using the Byte Order Mark (BOM) and little endian data InfoPrint Manager can process the Unicode Byte Order Mark (BOM) when printing line data with OpenType fonts. (For UTF8 or UTF16-BE data, the BOM is skipped and not printed. For UTF16-LE, the data is reversed to BE before it is printed, and the BOM is not printed.) In addition, InfoPrint Manager can now recognize multi-byte carriage return and line feed characters when parsing Unicode line data. This support lets you process UTF8 and UTF16 line data in either little-endian or big-endian order using a traditional line data or record-format page definition. As many Windows and AIX editors default to UTF8 or UTF16LE encodings and automatically insert a BOM at the beginning of the file, you can now print documents created with these editors using Unicode-enabled Open Type Fonts. Mixed mode data is line data mixed with MODCA structured fields. You can use mixed mode data with UTF8, UTF16LE, and UTF16BE with a BOM as long as the BOM is the first bytes (following any cc or trc bytes) of the first line of data. To mix UTF8 or UTF16BE data with other data encodings, you can do that if there is no BOM. In this case, the font selected for the data tells InfoPrint Manager the data encoding. You can't do this with UTF16LE data because it always requires a BOM. This support includes a -o newlineencoding flag for the -o flag, a stream,(newline=characters,encoding) value for the fileformat parameter on the Chapter 26. Working with fonts 261