The sap2afp configuration files
- barcode.tab
- defcp.tab
- defcp.tab.unicode
- defcp.tab.japan
- defcp.tab.korea
- defcp.tab.spchinese
- defcp.tab.tdchinese
- defcp.tab.cyr
- fonts.tab
- fonts.tab.unicode
- fonts.tab.unicode.truetype
- image.tab
- pagedef.tab
- pagedef.tab.unicode
- pagedef.tab.unicode.truetype
- pagedef.tab.japan
- pagedef.tab.korea
- pagedef.tab.spchinese
- pagedef.tab.tdchinese
- pagedef.tab.cyr
- userenv
- xxxxyyyy.tab
- Note:
- All tables can contain comments (starting with // in column 1) and empty lines. These lines are ignored by the sap2afp transform.
- All table entries are case-sensitive.
barcode.tab configuration file
This table describes the bar code mappings. SAP calls bar codes by names that must be mapped into the matching bar codes available with Bar Code Object Content Architecture (BCOCA).
Bar code Type field values
Bar code Type field values | Description |
---|---|
X'01' | Code 3 of 9 |
X'02' | MSI |
X'08' | EAN-8 |
X'09' | EAN-13 |
X'0C' | Interleaved 2 of 5 |
X'11' | Code 128 |
X'21' | Code 93 |
X'18' | POSTNET |
X'1E' | PDF 417 |
X'1C' | Data Matrix |
X'20' | QR Code |
barcode.tab
uses these keyword-value pairs:
- BarCode
- Specifies the OTF bar code names (SAPBARCODE parameter of the BCOTF command). The maximum length of this field is 8 bytes. It can contain any value.
- Type
- Specifies the AFP bar code type as defined in InfoPrint Data Stream and Object Architectures: Bar Code Object Content Architecture Reference for the Barcode Type parameter of the Barcode Data DescriptorStructured Field. The content can be any decimal value between 0 and 999. The sap2afp transform does not verify that this value maps to a valid hexadecimal barcode type.
- Mode
- Specifies the modifier byte in the Barcode Modifier parameter of the Barcode Data DescriptorStructured Field. Any numeric value between 0 and 999 is accepted and not verified.
- Flag
- Controls the printing of the Human Readable Interface (HRI) character. Specify one of these values:
- 0
- Causes the HRI character to be printed
- 128
- Causes the HRI character not to be printed
- ModWidth=n
- This optional keyword specifies the width of the smallest defined bar code element,
using mils (thousandths of an inch). For bar code types that explicitly specify the
module width, such as POSTNET or RM4SCC, this field is ignored. The range of values
allowed is 1–254. If ModWidth is not specified, the printer default ModWidth is used.
n specifies the width of each module, using thousandths of an inch (1/1000) as the unit of measurement.
- Ratio=n
- This optional keyword specifies the ratio between the width of the wide and the narrow
bar code elements. The range of values allowed is 100–500, but you must specify a
value appropriate for your printer and bar code type. If the values you specify are
not appropriate for your printer, error messages are issued at printing time. If Ratio is not specified, the printer default Ratio is used.
n specifies the Ratio as a percent value. The ratio value should be between 200 and 300 in the formnnn. For example, 200 represents a ratio of 2 to 1; 250 represents a ratio of 2.5 to 1. For bar code types that explicitly specify the module width (for example, POSTNET and RM4SCC, this field is ignored. If RATIO is not specified, the default ratio for the bar code symbol is used.
- Note:
- Many barcode types do not support Ratio values or if they do, the Ratio values are in certain ranges that are type-specific.
This example uses both the Ratio and ModWidth optional keywords:
BarCode=BC_CD39 Type=001 Mode=001 Flag=128 Ratio=200 ModWidth=10
- Note:
- The system administrator is responsible for the values entered in the table. Incorrect values are not verified and might result in errors.
- The second group of bar codes in the
barcode.tab
file (following the blank line) is supported from R/3 Release 3.0A only. - Although 2D barcode support has been added to InfoPrint Manager, the system administrator needs to update the
barcode.tab
with the information for 2D barcode for users who need to use them.
The next figure shows a sample barcode.tab
configuration file.
Sample barcode.tab configuration file
// Barcode table // Format : Barcode=ARTNR Type=017 Mode=002 //BarCode = 30F9 Type = 001 Mode = 001 Flag = 000 //BarCode = 30F91 Type = 001 Mode = 002 Flag = 000 //BarCode = MSI Type = 002 Mode = 002 Flag = 000 //BarCode = UPCA Type = 003 Mode = 000 Flag = 000 //BarCode = UPCE Type = 005 Mode = 000 Flag = 000 //BarCode = UPC2 Type = 006 Mode = 000 Flag = 000 //BarCode = UPC5 Type = 007 Mode = 000 Flag = 000 //BarCode = EAN8 Type = 008 Mode = 000 Flag = 000 //BarCode = EAN13 Type = 009 Mode = 000 Flag = 000 //BarCode = IND25 Type = 010 Mode = 002 Flag = 000 //BarCode = MAT25 Type = 011 Mode = 002 Flag = 000 //BarCode = INTER Type = 012 Mode = 002 Flag = 000 //BarCode = CODA Type = 013 Mode = 002 Flag = 000 //BarCode = C128 Type = 017 Mode = 002 Flag = 000 //BarCode = EAN2 Type = 022 Mode = 000 Flag = 000 //BarCode = EAN5 Type = 023 Mode = 000 Flag = 000 //BarCode = POST Type = 024 Mode = 002 Flag = 000 //BarCode = AUFNR Type = 001 Mode = 001 Flag = 128 BarCode = ARTNR Type = 017 Mode = 002 Flag = 000 BarCode = AUFNR Type = 017 Mode = 002 Flag = 000 BarCode = BARCLVS Type = 001 Mode = 001 Flag = 000 BarCode = BC_C128B Type = 017 Mode = 002 Flag = 128 BarCode = BC_CD39 Type = 001 Mode = 001 Flag = 128 BarCode = BC_CD39C Type = 001 Mode = 002 Flag = 128 BarCode = BC_EAN13 Type = 009 Mode = 000 Flag = 128 BarCode = BC_EAN8 Type = 008 Mode = 000 Flag = 128 BarCode = BC_I25 Type = 012 Mode = 001 Flag = 128 BarCode = BC_I25C Type = 012 Mode = 002 Flag = 128 BarCode = BC_MSI Type = 002 Mode = 001 Flag = 128 BarCode = BC_MSIC Type = 002 Mode = 002 Flag = 128 BarCode = BC_MSIC1 Type = 002 Mode = 003 Flag = 128 BarCode = BC_MSIC2 Type = 002 Mode = 005 Flag = 128 BarCode = KUNAUNR Type = 017 Mode = 002 Flag = 000 BarCode = KUNAUPS Type = 017 Mode = 002 Flag = 000 BarCode = MBBARC Type = 017 Mode = 002 Flag = 000 BarCode = MBBARC1 Type = 008 Mode = 000 Flag = 000 BarCode = RSNUM Type = 017 Mode = 002 Flag = 000 BarCode = RSPOS Type = 017 Mode = 002 Flag = 000 BarCode = RUECKNR Type = 017 Mode = 002 Flag = 000
defcp.tab configuration file
The next figure shows the default conversion table for the conversion of ASCII characters into EBCDIC. The sap2afp transform uses this table for ABAP data conversion.
The left column consists of the ASCII code, while the right column contains the corresponding EBCDIC value. The values are checked for a decimal numeric value between 0 and 255.
Sample defcp.tab configuration file
// Linedata CodePage //---------------------------------------------------- // This file is used internally by sap2afp, as well as // to convert ABAP data to linedata. // Format : Ascii=Ebcdic // T1000819 + box characters -> T1DABASE 000 = 064 001 = 064 002 = 064 ⋮ 253 = 064 254 = 062 255 = 223
defcp.tab.unicode configuration file
This file is used for processing ABAP files in a Unicode environment. Its structure
is the same as the defcp.tab
file with the addition of the Unicode conversion directives.
defcp.tab.japan configuration file
This file is used for processing ASCII-encoded ABAP files containing Japanese characters
in a non-Unicode environment. The structure of the file is the same as the defcp.tab
file with the addition of some conversion directives.
defcp.tab.korea configuration file
This file is used for processing ASCII-encoded ABAP files containing Korean characters
in a non-Unicode environment. The structure of the file is the same as the defcp.tab
file with the addition of some conversion directives.
defcp.tab.spchinese configuration file
This file is used for processing ASCII-encoded ABAP files containing Simplified Chinese
characters in a non-Unicode environment. The structure of the file is the same as
the defcp.tab
file with the addition of some conversion directives.
defcp.tab.tdchinese configuration file
This file is used for processing ASCII-encoded ABAP files containing Traditional Chinese
characters in a non-Unicode environment. The structure of the file is the same as
the defcp.tab
file with the addition of some conversion directives.
defcp.tab.cyr configuration file
This file is used for processing ASCII-encoded ABAP files containing Cyrillic characters
in a non-Unicode environment. The structure of the file is the same as the defcp.tab
file with the addition of some conversion directives.
fonts.tab configuration file
This table maps the fonts used in the OTF data stream to AFP fonts in a non-Unicode environment.
There are predefined mappings for these font families:
FONTFAMILY | Font |
---|---|
COURIER | Courier |
HELVE | Helvetica |
TIMES | Times New Roman |
LETGOTH | Letter Gothic |
LNPRINT | Line Print |
OCRA | Optical Character Recognition A |
OCRB | Optical Character Recognition B |
JPMINCHO | Japanese Heisei Mincho |
DBMINCHO | Japanese Heisei Mincho |
DBGOTHIC | Japanese Heisei Gothic |
KPSAMMUL | Korean |
CNSONG | Simplified Chinese Song |
CNHEI | Simplified Chinese Hei |
CNKAI | Simplified Chinese Kai |
TWSONG | Traditional Chinese Sung |
COURCYR | Courier Cyrillic |
HELVCYR | Helvetica Cyrillic |
TIMECYR | Times New Roman Cyrillic |
- Note:
- JPMINCHO and DBMINCHO are different names for the same font.
A font named BARCODE must be defined for the HRI character of a bar code. The predefined mappings for the font families specified do not refer to all possible font sizes.
These parameters in the fonts.tab
configuration file set the format of the fonts you use to print:
- DefCodePage
- Specifies the default SBCS code page used if no FCOTF command is given or if the requested font is not found in the
fonts.tab
table. - DefCharSet
- Specifies the default SBCS character set used if no FCOTF command is given or if the requested font is not found in the
fonts.tab
table. - DBDefCodePage
- Specifies the default DBCS code page used if no FCOTF command is given or if the requested font is not found in the
fonts.tab
table. - DBDefCharSet
- Specifies the default DBCS character set used if no FCOTF command is given or if the requested font is not found in the
fonts.tab
table. - SBDefCodePage
- Specifies the default SBCS code page used for half-width characters in DBCS fonts
if no FCOTF command is given or if the requested font is not found in the
fonts.tab
table. - SBDefCharSet
- Specifies the default SBCS character set used for half-width characters in DBCS fonts
if no FCOTF command is given or if the requested font is not found in the
fonts.tab
table. - Font
- Describes the font family (FONTFAMILY parameter of the FCOTF command). The maximum size is 8 bytes and content is not verified.
- Size
- Specifies the font size in 1/10 of a point (FONT SIZE parameter of the FCOTF command). The value must be numeric and is not verified.
- Type
- Defines the font type (BOLD and ITALIC parameter of the FCOTF command). Type=0 is normal, Type=1 is italic, Type=2 is bold, and Type=3 is italic bold. Any other value is not valid.
- CodePage
- Specifies the code page and requires a valid AFP code page name (8 bytes). The value is not verified. An incorrect name can result in an error message.
- CharSet
- Specifies the AFP font character set. The content is not verified.
- CodedFont
- Specifies the AFP coded font. The content is not verified.
- DB
- Specifies whether the font is an SBCS font (DB=0) or a DBCS font (DB=1).
- SBCodePage
- Specifies the single-byte code page used for half-width characters in DBCS fonts. The value is not verified. An incorrect name can result in an error message.
- SBCharSet
- Specifies the AFP single-byte font character set used for half-width characters in DBCS fonts. The content is not verified.
- SBCodedFont
- Specifies the AFP single-byte coded font used for half-width characters in DBCS fonts. The content is not verified.
If an SBCS font that matches the Font, Size and Type values is not found, the code page and font character set from the DefCodePage and DefCharSet keywords are used and a warning message is displayed. If a DBCS font that matches the Font, Size and Type values is not found, the code pages and font character sets from the DBDefCodePage, SBDefCodePage, DBDefCharSet, and SBDefCharSet keywords are used and a warning message is displayed.
ISO 8859-1 (Latin-1) is the default code page that maps to the 1148 code page in the fonts.tab configuration table. This ISO code page maps to the German T1V10273 code page and must be modified for non-Latin-1 installations. You can make this change
on the xxxxyyyy.tab
configuration file that is used to convert data from ASCII data to EBCDIC data so
that these characters are mapped correctly.
Use the font Letter
Gothic Latin1 of the coordinated font family for ABAP listings. If you do not want
to install the coordinated font family and plan to use the traditional Gothic text
fonts found in the IBM Compatibility Fonts, you can adjust the font names in the pagedef.tab
configuration file.
If you wish to use fonts that are not supported, take these steps:
- Obtain the font as Adobe Type 1.
- Convert the font into a raster using the Type Transformer that can be downloaded from the IBM website for no-charge, unsupported use at http://www-01.ibm.com/support/docview.wss?uid=psd1P4000840.
- Contact your Ricoh representative for further details.
The next two figures show examples of sections of the fonts.tab
configuration file.
Header and Courier portions of a sample fonts.tab configuration file
// Fonts table // Format : // Font=COURIER Size=070 Type=0 CodePage=T1V10273 CharSet=C0420070 DB=0 // or // Font=COURIER Size=090 Type=0 CodedFont=X0GT2A DB=0 // or // Font=JPMINCHO Size=060 Type=0 CodePage=T10300 CharSet=CZJHMN DB=1 \ // SBCodePage=T1H01027 SBCharSet=CZJHMN // or // Font=JPMINCHO Size=060 Type=0 CodedFont=XZJHMN DB=1 \ // SBCodedFont=XZN16J
DefCodePage = T1V10273 DefCharSet = C0420000 DBDefCodePage = T10300 DBDefCharSet = CZJHMN SBDefCodePage = T1H01027 SBDefCharSet = CZJHMN // Courier Font=COURIER Size=070 Type=0 CodePage=T1V10273 CharSet=C0420070 DB=0 Font=COURIER Size=070 Type=1 CodePage=T1V10273 CharSet=C0430070 DB=0 Font=COURIER Size=070 Type=2 CodePage=T1V10273 CharSet=C0440070 DB=0 Font=COURIER Size=070 Type=3 CodePage=T1V10273 CharSet=C0450070 DB=0 Font=COURIER Size=080 Type=0 CodePage=T1V10273 CharSet=C0420080 DB=0 Font=COURIER Size=080 Type=1 CodePage=T1V10273 CharSet=C0430080 DB=0 Font=COURIER Size=080 Type=2 CodePage=T1V10273 CharSet=C0440080 DB=0 Font=COURIER Size=080 Type=3 CodePage=T1V10273 CharSet=C0450080 DB=0 Font=COURIER Size=100 Type=0 CodePage=T1V10273 CharSet=C0420000 DB=0 Font=COURIER Size=100 Type=1 CodePage=T1V10273 CharSet=C0430000 DB=0 Font=COURIER Size=100 Type=2 CodePage=T1V10273 CharSet=C0440000 DB=0 Font=COURIER Size=100 Type=3 CodePage=T1V10273 CharSet=C0450000 DB=0 Font=COURIER Size=120 Type=0 CodePage=T1V10273 CharSet=C04200B0 DB=0 Font=COURIER Size=120 Type=1 CodePage=T1V10273 CharSet=C04300B0 DB=0 Font=COURIER Size=120 Type=2 CodePage=T1V10273 CharSet=C04400B0 DB=0 Font=COURIER Size=120 Type=3 CodePage=T1V10273 CharSet=C04500B0 DB=0 Font=COURIER Size=140 Type=0 CodePage=T1V10273 CharSet=C04200D0 DB=0 Font=COURIER Size=140 Type=1 CodePage=T1V10273 CharSet=C04300D0 DB=0 Font=COURIER Size=140 Type=2 CodePage=T1V10273 CharSet=C04400D0 DB=0 Font=COURIER Size=140 Type=3 CodePage=T1V10273 CharSet=C04500D0 DB=0 Font=COURIER Size=200 Type=0 CodePage=T1V10273 CharSet=C04200J0 DB=0 Font=COURIER Size=200 Type=1 CodePage=T1V10273 CharSet=C04300J0 DB=0 Font=COURIER Size=200 Type=2 CodePage=T1V10273 CharSet=C04400J0 DB=0 Font=COURIER Size=200 Type=3 CodePage=T1V10273 CharSet=C04500J0 DB=0
Heisei Gothic portion of a sample fonts.tab configuration file
// Japanese Gothic
Font=DBGOTHIC Size=060 Type=0 CodePage=T10300 CharSet=CZJHKG DB=1 SBCodePage=T1H01027 SBCharSet=CZJHKG Font=DBGOTHIC Size=080 Type=0 CodePage=T10300 CharSet=CZJHKG DB=1 SBCodePage=T1H01027 SBCharSet=CZJHKG Font=DBGOTHIC Size=100 Type=0 CodePage=T10300 CharSet=CZJHKG DB=1 SBCodePage=T1H01027 SBCharSet=CZJHKG Font=DBGOTHIC Size=100 Type=1 CodePage=T10300 CharSet=CZJHKG DB=1 SBCodePage=T1H01027 SBCharSet=CZJHKG Font=DBGOTHIC Size=120 Type=0 CodePage=T10300 CharSet=CZJHKG DB=1 SBCodePage=T1H01027 SBCharSet=CZJHKG Font=DBGOTHIC Size=140 Type=0 CodePage=T10300 CharSet=CZJHKG DB=1 SBCodePage=T1H01027 SBCharSet=CZJHKG Font=DBGOTHIC Size=160 Type=0 CodePage=T10300 CharSet=CZJHKG DB=1 SBCodePage=T1H01027 SBCharSet=CZJHKG Font=DBGOTHIC Size=180 Type=0 CodePage=T10300 CharSet=CZJHKG DB=1 SBCodePage=T1H01027 SBCharSet=CZJHKG
fonts.tab.unicode configuration file
The fonts.tab.unicode
file is used for processing OTF files in a Unicode environment. The structure of the file is the same as the fonts.tab
file.
image.tab configuration file
This table defines values used to print image data. It contains these parameters:
- DEFRES
- Specifies the default resolution used for printing image data if you do not specify a value for the -r flag of the sap2afp command. Valid values are 240, 300, 360, 480, 600, and 720.
- Width
- Specifies the width of the dither matrix.
- Height
- Specifies the height of the dither matrix.
- Cell
- Specifies the values for the dither matrix.
- Transform
- Specifies 256 grayscale correction values.
The next figure shows an example of the image.tab
configuration file.
Sample image.tab configuration file
// image.tab // from image.tab.85lr // // This file is used to determine the dither matrix and the // grayscale correction values. // Define the default output resolution DEFRES = 600 // Define the dither matrix Width = 78 Height = 78 Cell = 15 63 184 219 249 240 158 109 98 54 82 118 133 113 75 64 87 104 166 215 234 229 179 62 38 4 15 59 186 220 246 240 166 123 87 61 65 108 133 118 78 64 100 105 167 219 234 230 ⋮ 28 73 193 223 253 247 199 76 31 8 20 93 148 156 203 178 136 126 144 186 201 155 151 90 43 24 28 75 199 222 254 251 196 79 31 7 // // Grayscale correction values // Transform = 0 1 2 ⋮ 248 252 255
fonts.tab.unicode.truetype configuration file
The fonts.tab.unicode.truetype
file is used for specifying TrueType fonts to be used for OTF files in a Unicode environment. The structure of the file is similar as the fonts.tab
file except for more additional parameters.
These additional parameters in the fonts.tab.unicode.truetype
configuration file set the names and paths of the fonts you use to print:
- DefFullFilePath
- Specifies the default path for the font location. Specify only full paths.
- FullFilePath
- Specifies the path where the font is located. Specify only full paths.
- LinkFontPaths
- Specifies the linked fonts for the corresponding base font that was specified using FullFilePath. If the default font does not contain a certain character, that character is then searched in the fonts specified as linked fonts. You are allowed to enter multiple paths separated by semicolon (Windows) or colon (AIX). The linking order is the order you entered the linked fonts paths. This parameter is optional and may be entered only after the FullFilePath column. Specify only full paths.
- DefFullFontName
- Specifies the default full font name.
- FullFontName
- Specifies the font full name.
When the Full Font Name is specified, it is assumed that a Resource Access Table (RAT) is present for printing the resulted AFP file. Therefore, the TrueType/OpenType fonts are not embedded into the AFP file.
When the full path to the TrueType/OpenType font file is specified, it is assumed that there is no Resource Access Table (RAT) present at printing time. As result, the TrueType fonts are embedded into the AFP file.
Samples of the fonts.tab.unicode.truetype
files.
Sample of the fonts.tab.unicode.truetype file without RAT present
DefFullFilePath = "/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" // Courier Font=COURIER Size=070 Type=0 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" \ LinkFontPaths="/usr/lpp/fonts/linkfntn.ttf:/usr/lpp/fonts/linkfntn2.ttf" Font=COURIER Size=070 Type=1 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=070 Type=2 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=070 Type=3 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=080 Type=0 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=080 Type=1 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=080 Type=2 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=080 Type=3 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=100 Type=0 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=100 Type=1 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=100 Type=2 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=100 Type=3 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=120 Type=0 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=120 Type=1 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=120 Type=2 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=120 Type=3 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=140 Type=0 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=140 Type=1 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=140 Type=2 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=140 Type=3 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=200 Type=0 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=200 Type=1 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=200 Type=2 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf" Font=COURIER Size=200 Type=3 FullFilePath="/usr/lpp/fonts/worldtype/v7.1/printer/wt_dw___.ttf"
Sample of the fonts.tab.unicode.truetype file with RAT present
DefFullFontName = "WT Serif Duo" // Courier Font=COURIER Size=070 Type=0 FullFontName="WT Serif Duo" Font=COURIER Size=070 Type=1 FullFontName="WT Serif Duo" Font=COURIER Size=070 Type=2 FullFontName="WT Serif Duo" Font=COURIER Size=070 Type=3 FullFontName="WT Serif Duo" Font=COURIER Size=080 Type=0 FullFontName="WT Serif Duo" Font=COURIER Size=080 Type=1 FullFontName="WT Serif Duo" Font=COURIER Size=080 Type=2 FullFontName="WT Serif Duo" Font=COURIER Size=080 Type=3 FullFontName="WT Serif Duo" Font=COURIER Size=100 Type=0 FullFontName="WT Serif Duo" Font=COURIER Size=100 Type=1 FullFontName="WT Serif Duo" Font=COURIER Size=100 Type=2 FullFontName="WT Serif Duo" Font=COURIER Size=100 Type=3 FullFontName="WT Serif Duo" Font=COURIER Size=120 Type=0 FullFontName="WT Serif Duo" Font=COURIER Size=120 Type=1 FullFontName="WT Serif Duo" Font=COURIER Size=120 Type=2 FullFontName="WT Serif Duo" Font=COURIER Size=120 Type=3 FullFontName="WT Serif Duo" Font=COURIER Size=140 Type=0 FullFontName="WT Serif Duo" Font=COURIER Size=140 Type=1 FullFontName="WT Serif Duo" Font=COURIER Size=140 Type=2 FullFontName="WT Serif Duo" Font=COURIER Size=140 Type=3 FullFontName="WT Serif Duo" Font=COURIER Size=200 Type=0 FullFontName="WT Serif Duo" Font=COURIER Size=200 Type=1 FullFontName="WT Serif Duo" Font=COURIER Size=200 Type=2 FullFontName="WT Serif Duo" Font=COURIER Size=200 Type=3 FullFontName="WT Serif Duo"
pagedef.tab configuration file
The pagedef table provides the PAGEDEF and FORMDEF values used from the value of the *PJPAPER or *PJFORM (depending on the version of SAP/R3 used) parameter that is passed to the sap2afp transform with any access method that can submit SAPGOF to sap2afp, including the E or L access method. It also provides the fonts used for ABAP data.
The name of a PAGEDEF for line data is restricted to five digits instead of the usual six characters. The reason for this restriction is that the PJPAPER field is twelve bytes long and must begin with a Z. This restriction applies to ABAP reports (line data) with user-specific formatting only.
- Paper
- Specifies the value of the OTF print option parameter PJPAPER. The value is not verified.
- FormDef
- Specifies the name of the form definition to be used for printing both OTF and ABAP reports. This value is not verified. An error results if the form definition is not found on the print server system.
- PageDef
- Specifies the name of the page definition to be used for printing ABAP reports. This value is not verified. An error results if the page definition is not found on the print server system.
- FontNorm
- Specifies the normal coded font used for line data printing. The value is not verified.
- FontBold
- Specifies the bold coded font used for line data printing. The value is not verified.
The next figure shows a sample pagedef.tab
configuration file:
Sample pagedef.tab configuration file
// PageDef table // Format : Paper=X_65_132 FormDef=F1A10111 PageDef=P1H01SP1 // FontNorm = 50D0 FontBold = 50F0 // Notes: // ====== // 1) The pagedefs apply to letter size paper. // A4 paper size might require modifying the PageDef field. // 2) Z_INCH12 is a sample for a user specification
Paper=X_65_132 FormDef=F1A10111 PageDef=P1V06683 FontNorm = GB2A \ FontBold = GB2A Paper=X_44_120 FormDef=F1A10111 PageDef=P1V06683 FontNorm = GB2A \ FontBold = GB2A Paper=X_58_170 FormDef=F1A10111 PageDef=P1V06683 FontNorm = GT8A \ FontBold = GT8A Paper=X_65_255 FormDef=F1A10111 PageDef=P1V06683 FontNorm = GT24 \ FontBold = GT24 Paper=X_65_80 FormDef=F1A10111 PageDef=P1C09182 FontNorm = GT2A \ FontBold = GB2A Paper=X_90_120 FormDef=F1A10111 PageDef=P1C09182 FontNorm = GT5A \ FontBold = GT5A Paper=X_PAPER FormDef=F1A10111 PageDef=P1C09182 FontNorm = GT2A \ FontBold = GB2A // Sample of an added user-defined pagedef entry: // Paper=Z_INCH12 FormDef=F1SAPFD PageDef=P1SAPPD FontNorm = GT2A \ // FontBold = GB2A
pagedef.tab.unicode configuration file
The pagedef.tab.unicode
file is used for processing the ABAP and OTF files in Unicode environment. The structure is the same as the pagedef.tab
file.
The two new page definitions mapping the Courier Unicode font are used by default.
If you need to process ABAP files containing CJK characters, specify the names of the corresponding Unicode page
definitions for Japanese, Simplified Chinese, Traditional Chinese, or Korean in the
pagedef.tab.unicode
configuration file.
If you have your own custom page definitions that you want to use for Unicode processing,
modify your sources to include mappings and associations for the needed Unicode fonts
and recompile them. Specify the name of the custom page definition either in the pagedef.tab.unicode
configuration file or with the -pagedef
parameter to sap2afp.
pagedef.tab.unicode.truetype configuration file
The pagedef.tab.unicode.truetype
file is used for specifying the form definitions to be used with TrueType for ABAP and OTF input files, and page definitions to be used with TrueType for ABAP files, in Unicode environment. The structure is similar with the pagedef.tab
file except for more additional parameters.
- TTF_PATH
- Specifies the path where the TrueType fonts are located. You are allowed to enter multiple paths separated by semicolon (Windows) or colon (AIX).
- TTFembedNorm
- Specifies the file name of the embedded TrueType normal font used for line data printing.
This column must be used when no Resource Access Table (RAT) is present. You may enter
both full and relative paths. The relative paths are based on the path specified on
TTF_PATH and if not found, the search continues in the default
/reslib
and/fontlib
folders.
- TTFembedBold
- Specifies the file name of the embedded TrueType bold font used for line data printing.
This column must be used when no Resource Access Table (RAT) is present. You may enter
both full and relative paths. The relative paths are based on the path specified on
TTF_PATH and if not found, the search continues in the default
/reslib
and/fontlib
folders.
- TTFlinksNorm
- Specifies the linked fonts for the corresponding embedded TrueType normal font. You are allowed to enter multiple paths separated by semicolon (Windows) or colon
(AIX). The linking order is the order you entered the linked fonts paths. This parameter
is optional and may be used only when TTFembedNorm is present. You may enter both full and relative paths. The relative paths are based
on the path specified on TTF_PATH and if not found, the search continues in the default
/reslib
and/fontlib
folders.
- TTFlinksBold
- Specifies the linked fonts for the corresponding embedded TrueType bold font. You are allowed to enter multiple paths separated by semicolon (Windows) or colon
(AIX). The linking order is the order you entered the linked fonts paths. This parameter
is optional may be used only when TTFembedBold is present. You may enter both full and relative paths. The relative paths are based
on the path specified on TTF_PATH and if not found, the search continues in the default
/reslib
and/fontlib
folders.
Sample of the pagedef.tab.unicode.truetype file without RAT present
// WARNING: Please specify here the path to the TrueType or OpenType fonts! TTF_PATH="/usr/lpp/fonts/worldtype/v7.1/printer/" // ABAP Formats; FontNorm and FontBold are ignored in this table, // because they are set in the corresponding unicode pagedef. Paper=X_65_132 FormDef=F1SAP PageDef=P1UTT683 FontNorm=xxxx FontBold=yyyy TTFembedNorm="wt_dw___.ttf" TTFembedBold="wtsdw___.ttf" Paper=X_44_120 FormDef=F1SAP PageDef=P1UTT683 FontNorm=xxxx FontBold=yyyy TTFembedNorm="wt_dw___.ttf" TTFembedBold="wtsdw___.ttf" Paper=X_58_170 FormDef=F1SAP PageDef=P1UTT683 FontNorm=xxxx FontBold=yyyy TTFembedNorm="wt_dw___.ttf" TTFembedBold="wtsdw___.ttf" Paper=X_65_255 FormDef=F1SAP PageDef=P1UTT683 FontNorm=xxxx FontBold=yyyy TTFembedNorm="wt_dw___.ttf" TTFembedBold="wtsdw___.ttf" Paper=X_65_80 FormDef=F1SAP PageDef=P1UTT182 FontNorm=xxxx FontBold=yyyy TTFembedNorm="wt_dw___.ttf" TTFembedBold="wtsdw___.ttf" Paper=X_90_120 FormDef=F1SAP PageDef=P1UTT182 FontNorm=xxxx FontBold=yyyy TTFembedNorm="wt_dw___.ttf" TTFembedBold="wtsdw___.ttf" Paper=X_PAPER FormDef=F1SAP PageDef=P1UTT182 FontNorm=xxxx FontBold=yyyy TTFembedNorm="wt_dw___.ttf" TTFembedBold="wtsdw___.ttf"
Sample of the pagedef.tab.unicode.truetype file with RAT present
TTF_PATH="" // ABAP Formats; FontNorm and FontBold are ignored in this table, // because they are set in the corresponding unicode pagedef. Paper=X_65_132 FormDef=F1SAP PageDef=P1UTT683 FontNorm=xxxx FontBold=yyyy Paper=X_44_120 FormDef=F1SAP PageDef=P1UTT683 FontNorm=xxxx FontBold=yyyy Paper=X_58_170 FormDef=F1SAP PageDef=P1UTT683 FontNorm=xxxx FontBold=yyyy Paper=X_65_255 FormDef=F1SAP PageDef=P1UTT683 FontNorm=xxxx FontBold=yyyy Paper=X_65_80 FormDef=F1SAP PageDef=P1UTT182 FontNorm=xxxx FontBold=yyyy Paper=X_90_120 FormDef=F1SAP PageDef=P1UTT182 FontNorm=xxxx FontBold=yyyy Paper=X_PAPER FormDef=F1SAP PageDef=P1UTT182 FontNorm=xxxx FontBold=yyyy
pagedef.tab.japan configuration file
This file is used for processing ASCII-encoded ABAP files containing Japanese characters
in a non-Unicode environment. The file structure is the same as the pagedef.tab
file.
pagedef.tab.korea configuration file
This file is used for processing ASCII-encoded ABAP files containing Korean characters
in a non-Unicode environment. The file structure is the same as the pagedef.tab
file.
pagedef.tab.spchinese configuration file
This file is used for processing ASCII-encoded ABAP files containing Simplified Chinese
characters in a non-Unicode environment. The file structure is the same as the pagedef.tab
file.
pagedef.tab.tdchinese configuration file
This file is used for processing ASCII-encoded ABAP files containing Traditional Chinese
characters in a non-Unicode environment. The file structure is the same as the pagedef.tab
file.
pagedef.tab.cyr configuration file
This file is used for processing ASCII-encoded ABAP files containing Cyrillic characters
in a non-Unicode environment. The file structure is the same as the pagedef.tab
file.
userenv configuration file
The userenv
configuration file is used to specify the environment for the ASCII-encoded ABAP files. The configuration file may contain one of these values:
NORMAL - specifies European non-Unicode environment. The defcp.tab
and pagedef.tab
files are used.
JAPANESE - specifies Japanese non-Unicode environment. The defcp.tab.japan
and pagedef.tab.japan
files are used.
KOREAN - specifies Korean non-Unicode environment. The defcp.tab.korea
and pagedef.tab.korea
files are used.
SPCHINESE - specifies Simplified Chinese non-Unicode environment. The defcp.tab.spchinese
and pagedef.tab.spchinese
files are used.
TDCHINESE - specifies Traditional Chinese non-Unicode environment. The defcp.tab.tdchinese
and pagedef.tab.tdchinese
files
are used.
CYRILLIC - specifies Cyrillic non-Unicode environment. The defcp.tab.cyr
and pagedef.tab.cyr
files are used.
UNICODE - specifies Unicode environment. The defcp.tab.unicode
and pagedef.tab.unicode
files are used. If the -truetype flag is specified, then the pagedef.tab.unicode.truetype
is selected as the pagedef table file.
xxxxyyyy.tab configuration file
These tables are used for the mapping of characters of an individual SAP ASCII code page into an EBCDIC codepage. SAP uses two kinds of code pages: input code pages and output code pages.
SAP provides the the code page configuration files listed in the next figure.
SAP code page configuration files
File Name | Input Code Page | Description | Output Code Page | Description |
---|---|---|---|---|
00000000.tab | T1000819 | Latin-1 ISO ANSI 8-bit | T1V10273 | Germany F.R./Austria-CECP |
11000000.tab | T1000819 | Latin-1 ISO ANSI 8-bit | T1V10273 | Germany F.R./Austria-CECP |
15000000.tab | T1000915 | Cyrillic ISO 8859/5 | T1001172 | Cyrillic Multilingual with Box Draw |
40010000.tab | T1000876 1 | OCR-A ASCII | T1000892 | OCR-A |
40040000.tab | T1000877 1 | OCR-B ASCII | T1000893 | OCR-B |
80000000.tab | IBM-943C | Japanese ISO Shift-JIS | IBM-1399-SAP2AFP | Japanese |
83000000.tab | IBM-950 | Traditional Chinese ISO Big5 | IBM-937-SAP2AFP | Traditional Chinese |
84000000.tab | IBM-1386 | Simplified Chinese ISO GB2312 | IBM-1388-SAP2AFP | Simplified Chinese |
85000000.tab | IBM-970 | Korean ISO KSC 5601 | IBM-933-SAP2AFP | Korean |
|
The file names correspond to the 4-digit value of the INPUTCODEPAGE plus the 4-digit value OUTPUTCODEPAGE parameter of the CPOTF command.
Sample xxxxyyyy.tab configuration file (single-byte code pages)
// Codepage table // Inp CodePage 0000 // Out CodePage 0000 // Format : Ascii=Ebcdic 000 = 000 001 = 001 002 = 002 003 = 003 ⋮ 253 = 064 254 = 062 255 = 223
Sample xxxxyyyy.tab configuration file (Double-Byte Code Pages)
// Japanese // SAP2AFP is configured to use IBM-943C-SAP2AFP as the uconv // "From" value. // This table sets the "To" value to IBM-1399-SAP2AFP. // CONVERT FOR=8000 CONVERT TO=IBM-1399-SAP2AFP