Showing results for 
Search instead for 
Did you mean: 

Which device type support Unicode printing ?

Former Member
0 Kudos

Hi all,

Do you know which cascading font device types support Customer-defined true type fonts ?

I use HP LaserJet printer. I've imported ZSWINCF device type in to SAP system and installed some true type fonts required for my report. It's able to print <b>Unicode </b>text in ABAP List but unable in SAPScript/Smartform printing.

I also try to use ZHPUTF8 or HPUTF8, and install these fonts. But i've problem in printing out.

Do you know how to resolve this problem ?


Best regards,

Accepted Solutions (0)

Answers (2)

Answers (2)

Active Contributor
0 Kudos

Only way to solve your problem is your printer should be unicode enabled.



Former Member
0 Kudos

Hi SaiRam,

Yes, my printer support Unicode.



Former Member
0 Kudos


see this OSS notes may be useful




In some device types (e.g HPLJ4, HPLJ5) you experience non-uniform character spacing in the PDF document after the PDF conversion of SAPscript or Smart Forms documents, using HELVE or TIMES fonts. You want to know the reason.

Other terms

CONVERT_OTF, SAPscript, Smart Forms

Reason and Prerequisites

The problem is not due to an error in the PDF converter but due to the fact, that the printer font, underlying the device type (e.g. Univers or CG Times in PCL-5 device types), is not available for the PDF converter and is either not available in Adobe Reader. The PDF converter has to try to simulate the layout of the printer font by means of a font which is predefined in Adobe Reader. This is done by assigning the letter widths of the printer font to the font used in Adobe Reader.

The PDF file contains a table with letter widths, used by Adobe Reader in the output of text, for each used printer font (except PostScript fonts).


%Charwidth values from HP4300 HELVE 060 normal


[ 278 333 500 633 633 1000 758 333 333 333 633...

Adobe reader converts this width table, by modifying the space between each character, so that the specified letter width (= space between the current and the next letter) is kept.

This 'Simulation' of printer fonts results in the sometimes visible irregular spaces in PDF.

The PDF converter always uses the Helvetica Adobe PostScript font for the display of HELVE and the Times Roman Adobe PostScript font for the display of TIMES. However, for these Adobe PostScript fonts, Adobe Reader often uses a Windows TrueType font, which differs slightly from the original PostScript font.


Workaround: Use the POST2 PostScript device type or the PDF1 PDF device type for the PDF conversion of documents in the Latin-1 character set. They both use the Adobe PostScript fonts Helvetica or Times Roman for the HELVE/TIMES printer fonts.

Header Data

Release Status: Released for Customer

Released on: 30.06.2006 12:44:06

Priority: Recommendations/additional info

Category: Consulting

Primary Component: BC-CCM-PRN Print and Output Management

Secondary Components: BC-SRV-SCR SAPscript

OSS Note: 776507



Documents printed via SAPscript or SmartForms do not print with correct special characters, e.g. ### prints instead of Japanese or Russian characters. What to do?

Other terms

SAPscript, SmartForms, printing, device types, OTF

Reason and Prerequisites

Help required to choose proper fonts in a SAPscript or SmartForm


When using SAPscript or SmartForms to print (or email or fax) a form from a business application, many factors influence the outcome of the actual text within the form. All these factors must be checked in order to ensure a correct printout:

1) The language version of the form used to produce the printout.

Example: If you want to print a French invoice, you need to have a FR version of your SAPscript or SmartForms invoice form RVINVOICE01. And the application program must specify the corresponding language key (FR) when calling the SAPscript or SmartForms API.

2) The font selections specified in the form (possibly also in a SAPscript style or SmartStyle used in a form).

Example: In a SAPscript form or a SmartStyle you need to specify HELVE if you want to print German text in Helvetica (or similar) font. If you want to print Japanese text, HELVE is not a valid choice but you need to specify a Japanese font like JPMINCHO in your Japanese form.

3) The output character set of the device type

Every printer in transaction SPAD has a "device type" assigned. Device types used by the spooler for printing support only one single specific output character set. All text from the form has to be converted (using SAP's built-in character conversion mechanism) to this output character set.

A character set can typically support either a single language (e.g. Shift-JIS which supports only Japanese) or a set of languages (e.g. ISO 8859-1, which supports Western-European languages). It is possible that a given language (such as German) can be supported by several output character sets, e.g. you may use either ISO 8895-1 (Latin-1) or ISO 8859-2 (Latin-2) to represent German text. This is so because both character sets contain the special characters used in German.

Example: HPLJ4000 is a HP LaserJet device type supporting the ISO 8859-1 (Latin-1) character set. ISO 8859-1 can be used to represent e.g. Dutch, English, French, German, Spanish, Swedish but NOT Russian or Japanese.

As a consequence, it is ok to use HPLJ4000 to print English, German French etc. but not for Japanese or Russian.

4) The set of available printer fonts for a given device type

When formatting a document, SAPscript and SmartForms perform an automatic mapping of the font definitions in the form (e.g. "HELVE 14 point bold") and the available printer fonts of the device type. A replacement printer font is chosen, should the specified font selection not be available in the device type. Now this replacement can be problematic if a language-specific font, such as Chinese CNSONG, is specified in a form and it gets replaced by a font which does not support this language, e.g. COURIER.

To solve this problem, font families in SE73 have language attribute assigned, e.g. some fonts are characterized as being suitable only for certain languages. And when a replacement has to be chosen because the original font from the form is not available in the device type, a replacement font is chosen which has the same language attributes.

If no fonts for the language in question exist in the device type, the resulting font will not be able to print the special characters and you will see "wrong" output characters in the printout.

Note on SAPscript/SmartForms Print Preview:

The OTF Print Preview available in Windows GUI (e.g. from transaction SP01) will sometimes not show the "wrong" characters which appear on the final printout. Here is the reason: since the Print Preview runs in Windows environment, it will use Windows fonts to represent the actual printer fonts. A Windows font typically has more available characters (i.e. covers more character sets) than are actually available in a printer's resident font.

A typical example where the Print Preview will differ from the printout is here: if you have a Chinese PCL5 printer such as CNHPLJ4 and use the Western Latin font COURIER in your document, the print preview will show you Chinese characters if you (by accident) tried to format Chinese characters in COURIER font. This is because Windows will automatically choose a font that can output Chinese characters (which is actually not Courier). But when you print the job on an actual PCL5 printer with resident Western and Chinese fonts, the Courier font will not print any Chinese characters but Western special characters instead, because the printer's resident Courier font does not include Chinese characters.

Rule of thumb: all Asian device types (e.g. CNHPLJ4, JPHPLJ4, JPPOST, KPHPLJ4) support not only Asian fonts but also COURIER, HELVE and TIMES fonts. But these Latin fonts can only be used to print English text, not Chinese/Japanese/Korean characters.

Which fonts are suitable for a given language?

Language(s): Font family to use in a form:

                          • Latin-1 (Western Europe/Americas) *******



                          • Latin-2 (Central Europe) ****************


                          • ISO 8859-4 (Baltic) *********************


                          • ISO 8859-5 (Cyrillic) *******************


                          • ISO 8859-7 (Greek) **********************


                          • ISO 8859-8 (Hebrew) *********************


                          • ISO 8859-9 (Turkish) ********************


                          • Simplified Chinese **********************


                          • Japanese ********************************


                          • Korean **********************************



                          • Traditional Chinese *********************


                          • Thai ************************************


                          • Arabic (Unicode systems only) ***********


Verify your output by examining the OTF data

When analysing printing problems of this type, be sure to check the OTF data which gets produced by SAPscript or SmartForms. OTF or "Output Text Format" is the intermediate page-description format generated from SAPscript or SmartForms. OTF will contain the final printer font names and character set/language identifiers which help to solve the problem. OTF will even name the form and the language of the form used to create the output.

The easiest way to do this is to create a spool request from your application, run transaction SP01, use menu

Goto->Display Requests->Settings

and choose

Display Mode: Raw

Now display your spool request. If this is a SAPscript or SmartForms spool request, you will see OTF data. Each line represents one OTF command, every command starts with a 2-character cmd identifier and possibly some cmd parameters follow.

Here is an excerpt from a sample OTF file where we highlight the most interesting commands:

//XHPLJ8000 0700 00000000001



OPDINA4 P 144 240 1683811906000010000100001




FCHELVE 120 00109XSF100SF101110000067E X

UL +0000000000000



ST0453037Dieses SF hat Stil ALEXTEST_ZEBRA mit


The 1st line with the // (Control) command reveals the device type usedto print: HPLJ8000

//XHPLJ8000 0700 00000000001

The 2nd line (IN = Info command) shows the name and (internal 1-char)language key of the form:


In this case it is the English (E = EN) SmartForm ALEXTEST_ZEBRA

The OP-line (OP = Open Page) gives the page format used in the form, it is DINA4 Portrait orientation:

OPDINA4 P 144 240 1683811906000010000100001

The CP (CodePage) cmd shows the SAP system codepage used to code the text and the active language. In our case it is codepage 1100 and language E = EN = English.


Finally, the FC-cmd (Font Call) lists a printer font selected within SmartForms. Please note that every SmartForm has a designated default SmartStyle under "Form Attributes->Output Options". In addition, every text node can have a SmartStyle attached (which will override the definitions from the default style for the text). In our case the resulting printer font that was selected is HELVE 12.0 pt bold-off, italic-off.

FCHELVE 120 00109XSF100SF101110000067E X

Header Data

Release Status: Released for Customer

Released on: 22.08.2005 09:57:20

Priority: Recommendations/additional info

Category: Customizing

Primary Component: BC-CCM-PRN Print and Output Management

Secondary Components: BC-SRV-SCR SAPscript

BC-SRV-SSF Smart Forms

<b>Reward points for useful Answers</b>



Former Member
0 Kudos

Hi Anji,

Do you know which device type support cascading font (except SWINCF) ? I try to use cascading font for HPUTF8 or SWIN ? But the unicode text is not printed out corectly.

I used to try SWINCF for cascading font, it's good for ABAP list printing, but it doesn't support SApscript or smartform.

Have you any suggestion ?

It's very urgent for me.

Thank you very much.

Best regards,