How InfoPrint processes code pages from ABAP and OTF jobs

Code page support for OTF jobs is more flexible than for ABAP jobs.

Because OTF jobs request a specific font, the SAP transform compares the specified font name and point size values with the entries in the fonts.tab configuration file. If the transform finds a match, it uses both the AFP character set and AFP code page for the print job.

ABAP jobs can use different character sets, but are confined to using the same code page. When processing ABAP files, the SAP transform uses:

  • The defcp.tab file to map single-byte ASCII code points to EBCDIC code points before calling the uconv utility.
  • The pagedef.tab file to match the Paper parameter value with the PJPAPER or PJFORM (depending on the SAP/R3 version used) parameter value in the ABAP print job.

    Once they are matched, the SAP transform uses the FontNorm and FontBold parameters on the selected line in the pagedef.tab file to determine which character sets to use in both normal and bold mode.

Note: For ABAP jobs that are processed using Unicode, the FontNorm and FontBold fields are ignored, because the Unicode fonts are mapped in the page definition.

As a result, all ABAP jobs sent to a particular InfoPrint server use the same code page, but potentially different character sets, depending upon the PJPAPER value specified in the job.

Parent topic: Customizing print characteristics