Unicode Printing

Hi,
We are moving to unicode and looking into the possibility of printing Chinese simplified, japanese and english all together in a single page. We are advised to get the printer DIMM that support the 2 asian languages.
My doubts are
1. Must we get the printer DIMM just to print the 2 asian languages in unicode system?
2. Isn't Unicode suppose to be code page independent and thus we do not need to specify a different device type eg. CNSAPWIN for printing a different languages?
3. SAP mentions in its Unicode conversion that a unicode printer is required. HP only has UTF8 compliant printer. However, our setup is UTF16 and SAP only supports this HP UTF8 printer. This would mean that we can't use Unicode printer?
Any advice is greatly appreciated. Thanks.
regards
WS

Ok. I have the answers to my questions. For those who wish to know, this is what I can share:
1. Must we get the printer DIMM just to print the 2 asian languages in unicode system? Ans: No. We can use cascading font for Unicode.
2. Isn't Unicode suppose to be code page independent and thus we do not need to specify a different device type eg. CNSAPWIN for printing a different languages?
Ans: For Unicode, I don't think we need xxSAPWIN. We can use ZSWINCF.
3. SAP mentions in its Unicode conversion that a unicode printer is required. HP only has UTF8 compliant printer. However, our setup is UTF16 and SAP only supports this HP UTF8 printer. This would mean that we can't use Unicode printer?
Ans: I guess we cannot use the HPUTF8 solution. Cascading font can also do it.

Similar Messages

Unicode Printing in ABAP program

Hi all,
I have a problem in Unicode printing. When I write a report, I use Unicode font. Everything is Ok when I print preview this report. But when i send it to the printer, the unicode font doesn't present.
Do you know how to solve this problem ?
Thank you very much.
Sylvecast.

Hi Atish,
Yes, of course. I can print any word document with unicode font. I don't know if there must have any settings in ABAP program ? But when i print preview it, evrey thing is OK.
Kindly regards,
Sylvecast.

Which device type support Unicode printing ?

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 ?
Thanks,
Best regards,

Hi
see this OSS notes may be useful
OSSNote:960341
Symptom
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).
Example:
%Charwidth values from HP4300 HELVE 060 normal
/Widths
[ 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.
Solution
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
Symptom
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
Solution
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) *******
DE,EN,FR,ES,NL,SV       COURIER, HELVE, TIMES
                        (LETGOTH, LNPRINT)
Latin-2 (Central Europe) ****************
PL, CZ                  COURIER, HELVE, TIMES
ISO 8859-4 (Baltic) *********************
ET, LT, LV              COURIER, HELVE, TIMES
ISO 8859-5 (Cyrillic) *******************
BG, RU, SR, UK          COURCYR, HELVCYR, TIMECYR
ISO 8859-7 (Greek) **********************
EL                      COUR_I7, HELV_I7, TIME_I7
ISO 8859-8 (Hebrew) *********************
HE                      COURIER, HELVE, TIMES
ISO 8859-9 (Turkish) ********************
TR                      COURIER, HELVE, TIMES
Simplified Chinese **********************
ZH                      CNHEI, CNKAI, CNSONG
Japanese ********************************
JA                      JPMINCHO, DBMINCHO, DBGOTHIC
Korean **********************************
KP                      KPBATANG, KPDODUM, KPGULIM
                        KPGUNGSE, KPSAMMUL
Traditional Chinese *********************
ZF                      TWDPHEI, TWMING, TWSONG
Thai ************************************
TH                      THANGSAN, THDRAFT, THVIJIT
Arabic (Unicode systems only) ***********
AR                      ANDALE_J
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
IN04EALEXTEST_ZEBRA
IN05%PAGE1
OPDINA4 P 144 240 1683811906000010000100001
IN06%WINDOW2
MT0024401289
CP11000000E
FCHELVE 120 00109XSF100SF101110000067E X
UL +0000000000000
SW00067
CT00000000
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:
IN04EALEXTEST_ZEBRA
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.
CP11000000E
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>
Regards
Anji

Non-unicode printing unreadable character for Thai

Hello All,
Our current system 4.7 running on Oracle datavase on Window NT server, codepage set to 8600 with supported TH and EN.
Previously, user logon as 'blank' and set character (at user setting) to 'TH', the printing of SAP documents to printer is able to print TH language.
However, there is recent 'EN' activated via I18N without the any changes to the instance profile and printer id, the printing to printer is unreadable character although we are able to read TH for table, and online document in SAP system.
Our database code page is 1100 and 8600. and the installed language are 2DE. In RSCPINTST, there are GE, EN and TH.
Is it because we have 3 languages in the RSCPINTST, and need to remove 'GE'?
May i know what would be the problem, as i have searched through the forum.
Can please advice? Thank you

Hi Claudia,
You need to verify if German language was always active on the system or if it was only recently activated in error. If it was, it needs to be removed to return you to your former configuration (provided no German data was saved to the database while active, as this data will be lost once German is removed). I would therefore presume the issue would then no longer occur.
I would assume that the issue is occuring as English was configured to use code page 8600 - i.e. when you used to logon to the system teh code page was loaded and English and Thai characters could be input. Now the German language is active, hence the system probably has 2 code pages active (8600 and 1100) and by default English is now using 1100. Hence when using English now, code page 1100 is loaded which cannot interpret Thai characters -- hence the incorrect printing.
So, it is vital to check why German is now active on the system and why it was introduced.
I hope this helps,
Regards,
Safina Hillis

Unicode fonts and printing

Hi,
To enable pure Unicode printing with UFT8 device types it is needed to use Unicode fonts. Is somebody aware if there are more than one R/3 Unicode font available? In WAS 6.20 there is only font called Andale which is Unicode font.
Brgds,
Jarmo

Hi Jarmo,
interesting question...
In SAP standard WAS 6.20 I'd agree with you regarding Andale. For sure you (or third parties) are able to create your own fonds in R/3.
Let's see what the experts of SDN are saying. I'll also watch your post.
Regards
Juergem

Korean Language Printing

Hi SDN,
Im trying to print few details in the Korean Language from an SAP Script. I have made the changes to the existing script and the Print Preview comes perfectly fine.
When I take the Print Out from the Spool Request, blank boxes get printed instead of Korean Language Text. Im using the Unicode Printer
Can anyone help me out with this.
Thanks and Regards,
Manu Kapur

Hi Manu,
You need to check whether the korean font is support by that printer & whether you have the Koren font uploaded in SAP in transaction SE73.
Check whether the font is converted to some other font at runtime.
Goto SP01, enter the spool no.
Click Execute
Click GOTO=> Display request => Settings
Select hexadecimal format..
Check the font.
If its converted, then you need to upload the font in SE73
Best regards,
Prashant

Problem with custom paper size on dot matrix printer

Hi All,
I'm using CR2008 with updated to SP2. I have a problem with custom paper size (W=21; H=14), the CR Viewer show report with custom paper size correctly but when I print it to a dot matrix printer (Epson LQ 300+) the content was rotated to landscape. If print to a laser printer the content was printed correctly. My report was printed correctly by CR10 or previous versions I got this issue when upgraded to CR2008. I aslo tested my computer and printer with orther application like MS Word the printing have no problem with custom paper size.
Thanks for any advice for me.
Han

Looking at the Epson LQ 300+ driver, I see that the latest update is from 2002. In my experience, most matrix printer drivers are not unicode. Crystal Reports is designed to only work with unicode printer drivers. See the [How Printer Driver Options Affect a Report|https://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/a09051e9-721e-2b10-11b6-f9c65c64ef29&overridelayout=true] article, page 6 for details. Also, see [this|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_dev/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes.do] note.
Finally, see if you can print from the CR designer to this printer and if you get the correct results here.
Ludek

Problem in Russian Forms while printing

Hi All,
when i'm printing Russian forms with TimesNewRoman Font,printer is printing some junk texts..but if i am using cyrlicCourier Font,it prints well.
I need to print the form in TimesNewRoman Font.where i have to change the settings???
Thanks
Merlin

Note, to print double digit characters( on uni-code enabled printer) we have to use cyrillic fonts.. Ordinary fonts may give junk values most of the time... Use TIMECYR (it is times font for unicode printer)
close thread once your question is answered.
Regards,
SaiRam

Another Hex to Unicode Question

public static void main(String[] args) {
      char ch = (char)Integer.parseInt("672c",16);
      System.out.println(ch);
      System.out.println("木"); //Character meant to show up in Hex - > Unicode print
}According to the other questions and answers that I've read on the forum about changing a string hex into its equivalent Unicode character, what I have there should work. But it doesn't.
I'm not sure if it'll be visible to everyone, but the second println() statement is the character that should be represented from the hex, but when I run the program in console the 1st print statement (Hex-> Unicode) outputs a "?" but the second works fine outputing exactly what I put it as.
Is this a charset problem?
Thanks

By default most consoles print a very timited subset of the available unicode character set. You will have to make sure that they (the consoles) use a font capable of displaying the unicode characters that you wish to display. Since I have never had to do this I can't help you here but the following Swing example shows how it might be done in a Swing or AWT application.
import java.awt.*;
import javax.swing.*;
public class Fred503 extends JPanel
    public Fred503()
        super(new GridLayout(0,2));
        char ch = (char)Integer.parseInt("672c",16);
        String[] fontNames =
            "Kochi Gothic",
            "Kochi Mincho",
            "Baekmuk Dotum",
            "Baekmuk Batang",
            "Baekmuk Gulim",
            "AR PL SungtiL GB",
            "AR PL KaitiM Big5",
            "AR PL KaitiM GB",
        for (int fontIndex = 0; fontIndex < fontNames.length; fontIndex++)
            JLabel label = new JLabel(fontNames[fontIndex] + " : ", JLabel.RIGHT);
            add(label);
            label = new JLabel(Character.toString(ch));
            label.setFont(new Font(fontNames[fontIndex], Font.PLAIN, 20));
            add(label);
    public static void main(String[] args)
        JFrame frame = new JFrame("Fred503");
        frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
        frame.setContentPane(new Fred503());
        frame.pack();
        frame.setVisible(true);
}

Search device Type for Printer Ricoh Aficio BP20n

Hi does anyone knows a Device type for the printer
Ricoh Aficio BP20n
I looked the sNOTE 8928 which routes me to sNOTE 485240.
but "485240" does not exist.
Notes with device types for Gestetner and Savin are not listening the BP20n printer.
"Savin" is a US subsidiary company from Ricoh.
greets chris

Hi Christian,
That's strange, I could see note 485240: Device types supplied by SAVIN
<a href="https://websmp204.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=485240&_NLANG=E">https://websmp204.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=485240&_NLANG=E</a>
Symptom
The printer manufacturer SAVIN supplies SAP with the following device types. These device types are produced, maintained and supported by Ricoh.
Should you encounter problems while you are using these device types in SAP, do not direct them to the SAP Support hotline. Instead, use the support addresses of the SAVIN Corporation listed below.
Other terms
Device type, SAVIN
Reason and Prerequisites
Detailed information on the SAP device types supplied by the printer manufacturer SAVIN.
Solution
The following products are supported by the SAVIN device types:
Multi-functional Devices
- 4015/4018/4018d
- 8016/8020/8020d
- 9922DP/9927DP *1
- 2522/2527
- 4022/4027
- 8025/8030
- 8025e/8030e *2
- 9935D/9935DP/2035DP/9945DP/2045DP *1
- 2535/2235/2545/2245
- 4035/4135g/4045/4145g
- 4035e/4135eG/4045e/4145eG
- 8035/8045
- 8035e/8035eg/8045e/8045eg *2
- 2055DP/2070DP Type700
- 2555
- 2560/2575
- 4051/4060/4075
- 8055/8065/8075 *2
- 2085DP/2105DP Type850
- 2585/25105 Type850
- 4090/40105 Type2105
- 8090/8110/8135 *2
- C2408/C2524/C3210/C2532
- C2525/C3030 *2
- C2820/C3224/C3828
- C2410/C3210e
- C2824/C3528/C4535
- C3535/C4540 *2
- C6045/SDC555
Printers
- SLP26/SLP26n
- MLP26/MLP26n
- MLP25/MLP25n
- MLP28/MLP28n
- SLP32
- MLP32/MLP35n
- MLP45
- MLP145 *2
- CLP1620
- CLP22
- CLP1036
- SLP38c
- CLP28
- CLP35
- CLP17
- CLP18
- CLP831
- CLP26DN
- CLP27DN/CLP31DN *2
- MLP75n
- MLP175n *2
- CLP128/CLP135
SAP device types ZA001vvv (Latin-1)/ZA002vvv (Latin-2)
These device types support the above-mentioned printers and multi-functional devices. You can download them from the Internet sites listed under "Support".
Latin-1 (Western Europe) supports the following languages:
English, German, French, Italian, Spanish, Portuguese, Dutch, Swedish, Norwegian, Danish, Finnish
Latin-2 (Eastern Europe) supports the following languages:
Hungarian, Polish, Czech, Croatian, Romanian, Slovak, Slovenian
The ZA001vvv/ZA002vvv device types support the following functions:
Input bin / Output bin
Stapling & Hole punching
Paper type
Duplex printing
Job offset
Resolution
Number of Copies & Collation
EconoMode / Toner saving
Auto tray change/switching
Edge enhancement/Smoothing
Paper size
Orientation
Character set / Symbol set
Color printing
Slip sheet
Edge-to-edge mode
*1: Does not support bar code printing and OCR typefaces.
*2: Supports Unicode printing.
For more information, download the customer documentation from the Internet sites listed under "Support".
Support:
Telephone: 1-800-RICOH(74264)-38
Internet: http://www.savin.com/
Download: http://www.savin.com/savin/savin_com.nsf/SupportDrivers/

Boxes getting Printed for Language Printout

Hi SDN,
Im trying to print few details in the Korean Language from an SAP Script. I have made the changes to the existing script and the Print Preview comes perfectly fine.
When I take the Print Out from the Spool Request, blank boxes get printed instead of Korean Language Text. Im using the Unicode Printer
Can anyone help me out with this.
Thanks and Regards,
Manu Kapur

Hi
First of all Welcome to SCN Forum
Please check wheather any subroutine has been assigned to the output type access sequence.If the problem is with printout only then check the Logical destination that has been maintained in VV32 for those 3 customers.In VV32 for those 3 customers check wheather Release Immediately has been checked or not. Before reprocessing it go to VF02 and check on determine analysis
Regards
Srinath

Language Printing

Hi SDN,
Im trying to print few details in the Korean Language from an SAP Script. I have made the changes to the existing script and the Print Preview comes perfectly fine.
When I take the Print Out from the Spool Request, blank boxes get printed instead of Korean Language Text. Im using the Unicode Printer
Can anyone help me out with this.
Thanks and Regards,
Manu Kapur

Even if it is a unicode printer, check if there is any requirement for Korean font. You might have to see that with your network team and see if you need to install any font.
That can be the cause of the problem.
ashish

Printing unicode from an xml file

I have a unicode character in an xml file
say
< item name="Notification" value="hi amigo\u0041" />
When I parse this file and try to print out the String value I get the follwoing output
hi amigo\u0041
Thoug what I expected was
hi amigoA
any idea what am I doing wrong or what am I missing?
any help would be greatly appreciated.

Yep I tried that too.
if I try it with ) I get
java.lang.reflect.InvocationTargetException:
org.xml.sax.SAXException: **Parsing Fatal Error**
Line: 38
URI: file:C:/opt/config/mmcpSpecific.conf
Message: Illegal decimal character reference.
at
configuration.ConfigParser$ConfigErrorHandler.fatalErr
r(ConfigParser.java:1005)
at
org.apache.crimson.parser.Parser2.fatal(Parser2.java:3
38)
at
org.apache.crimson.parser.Parser2.fatal(Parser2.java:3
23)
at
org.apache.crimson.parser.Parser2.parseCharNumber(Pars
r2.java:2327)
at
org.apache.crimson.parser.Parser2.parseLiteral(Parser2
java:730)
at
org.apache.crimson.parser.Parser2.maybeElement(Parser2
java:1375)Nope as the doctor mentioned you are not doing it the right way
< item name="Notification" value="hi amigo\u0041" />
instead of this you should use
< item name="Notification" value="hi amigo)" />
you would not get the exception if you dont miss the semi colon. I guess you must have been missing that
< item name="Notification" value="hi amigo)" />

Sap script - Problem while printing Hungarian characters during Unicode

Hello Friends,
We had done unicode changes ie Version upgrade from 4.6 C to ECC and because of that sap script Hungarian characters are printing as Junk characters ex - #####.
Can any one please help me on this issue. In SO10 Print preview also we are facing same issue.
Thank you,
Regards,
Phaneendra

Hi Phaneedhra,
the below thread explains the font issue for Hungary..
SAPScript with Hungarian characters on it. Weh we review the output online it looks good, but when we print it we get a u2018#u2019 in place of Hungarian characters. I found the following link in SDN and am wondering if you can help.
Hungarian Character Printing problem
Problem in displaying special chars
Prabhudas

Character encoding of Unicode (UTF-8) is what seems to be the default for printing. The page looks funny and the print is spread out.

the layout of the page is different that it appears on the screen. I printed the confirmation of my VISA payment on line and it is not concise. The information is correct, but the layout isn't.
Should I use another encoding? One of the Western ones? Maybe unicode (UTF-16)?

There is a known bug involving printing in beta 12 that has been fixed in the Firefox 4 release candidate which is due out soon.

Unicode Printing

Similar Messages

Maybe you are looking for