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 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 line2afp transform, and a new-line-option-data-encoding document/default document attribute. For more information about this support, see RICOH InfoPrint Manager: Reference.