Printing of asian characters after ECC 5.0 / unicode upgrade

Does anyone know what do we need to do in order to print documents in asian languages. We have upgraded to ECC5.0/unicode.

I solved my issue as follows.
Here are 4 options I analyzed, you may chose one that best fits your needs.
We chose option 1.1
1.1     PRINTER UPGRADE/REPLACEMENT
This is a h/w based solution. This option requires certain compliant models of the printers and installation of special font card to that printer. It provides faster response times since the fonts dont have to be sent across the network. Although there are less number of fonts available compared to other options, they are sufficient to cover major world languages.
1.2     SAPLPD/SAP SPRINT
This is a s/w service running on a NT Box, also known as Frontend printing. This decentralizes printing landscape from Unix (our SAP instances are on unix) to windows based printing and would require changes to printng support procedure in our landscape.
1.3     OMS
Using a Output Management System ( OMS) such as HP OMS or VPSX ( using a plugin such as Impulse for Double Byte printing).   This is full-fledge output management solution but requires additional resources and capital investment and is suited for organization with significant(sometimes complex) output needs that need to be carefully managed.
1.4     PDF
Convert SAP output to pdf and send the pdf file with fonts embedded inside it to printer. Requires ABAP resource and uncertainty over whether all the different types of output can be converted to pdf besides the pdf printing will add network overhead and cause slowness affecting other processes.May be something for future since SAP is collaborating with adobe on forms/output delivery.

Similar Messages

Printing in Russian Language - after ECC 6.0 unicode upgrade

Hello ,
Earlier users from russia are able to print in SAP 4.6C using SAPWIN Device type in russian language.
but after unicode conversion and ECC 6.0 EHP 4 upgrade, they are not able to print in russian using SAPWIN.
In print preview ,it is showing correclty, but not in output.
any help ?
regards,
Chaitanya.

Hi,
It should not be necessary to change to SAPWIN5. Device type SAPWIN5 only supports cyrillic fonts like COURCYR, HELVCYR or TIMECYR. Therefore, even if the erong font is used in the form, the device type converts it to a Russian font. If yuo use a correct font for Russian characters in the form, then SAPWIN should also work.
SWINCF should also work with the current form setting.
Regards,
Aidan

Report printing in Greek characters after changing Font

Hi All,
We had a bunch of reports created in 'Courier New' font whose output type is PDF. The users wanted the reports to print in 'Arial' font. When I changed the same from Courier New to Arial and ran the report , the report is printing in Greek characters instead of English. I initially thought that it prints in Greek may be because of insufficient space or something for the text fields but there seems to be sufficient spaces to print characters. I tried reducing the size and still the reports prints in Greek in lower size.
Can anyone let me know how to get rid of this?
Thanks,
Srini.

See if the solution in the following thread applies to you:
Problem converting font to .afm using ttf2pt1

Printing to Canon iP4000 after 10.3 - 10.4 upgrade works

I got a new Canon PIXMA iP4000 printer and connected it to my Airport Extreme Base Station.
I downloaded and installed the 2.6.2 drivers from Canon's site on my iMac (upgrades from 10.3 to 10.4). When I tried to add the printer, using the Printer Setup Utility, it would not automatically select my printer driver. Only a list of GIMP drivers would appear for Canon.
I download the latest Canon printer drivers and Bonjour for Windows onto my Windows XP ThinkPad. Installed them both and printing worked flawlessly. I was glad, but not to happy about my Mac.
Next I installed the Canon drivers on my new iBook which came preloaded with 10.4. The printer setup utility found the printer and it's driver just fine and printing worked fine.
I then compared my iBook's /Library/Printers/Canon directory to the same directory on the iMac. There were not a 100% match, and the timestamps on the files did not match up at all. I crossed my fingers and deleted the Canon folder, then reinstalled the Canon driver I downloaded, and rebooted.
This time the Printer Setup Utility found the driver for the Canon and printing works fine now!

Nevermind. I discovered the problem was not properly closing the inner cover of the printer when I changed one of the ink cartridges. It had nothing to do with the recent upgrade in the system software..

FTP transfer gives incorrect characters after unicode upgrade

Hello all,
We write a file on a FTP drive containing data from an internal table. We use FM FTP_R3_TO_CLIENT to write this file. The internal table contains characters like 'ü'. Before our unicode upgrade this process worked fine. After our unicode upgrade the FTP file contains instead of the 'ü' characters like 'Ã¼'.
The internal table passed to the FM is still ok in the unicode system, only the result seems not. We did set the unicode flag on the SAPFTP RFC destination but this made no difference.
Any idea?
Thanks and best regards,
Boris

Hello Anil,
Below items we checked between MDMP 46B and Unicode ECC6 with production client table SKAT. some Spanish display not correct.
Unicode ECC6.0     46B
Short Text     Short Text
Ant a prov - Gto imp     Ant a prov - Gto imp
Regal¨ªas     Regalías
Prov Herramentales     Prov Herramentales
Provisi¨®n de SLA     Provisión de SLA
Prov Fin Vida (EOL)     Prov Fin Vida (EOL)
Gtos de imp     Gtos de imp
Mat dañado o perdido     Mat dańado o perdido
Papeleria e insumos     Papeleria e insumos
Gastos Vtas-Diseño     Gastos Vtas-Diseńo
Ganancia p fluc camb     Ganancia p fluc camb
Aj anual p inf     Aj anual p inf
Depreciaci¨®n fiscal     Depreciación fiscal
Best Regards
Key

Asian characters appear after last update

I just installed the latest Adobe Reader update and after completing steps 1-3, I get a message in center of screen in Asian characters and none of my PDF files will open now.

Thank you! Yes, that was my problem. I got it resolved and went to my
Preferences and unchecked the box for "Allow plug-ins." All is well now.
Thank you so much for the quick response.
--P
On Fri, Jul 11, 2014 at 4:23 PM, MobileDevCK <[email protected]>

Preview and Printing of Chinese Characters in Smartform

Hi everyone!
I have a development that needs to output in Smartform a combination of Chinese and English characters, on an English Logon,
When I debug the form, the Chinese characters are shown in the debug screen, but when it is previewed or printed, it shows garbage. Can anyone help me with this?
Thanks a lot! Points for any helpful answer!

Hi
check this OSS Note
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
Regards
Anji

Handling of asian characters in CRM ICWC / WebUI?

hi
we would like to allow people entering asian text (e.g. chinese) in Interaction Center WebClient / WebUI. they'll be using English as logon language.
will now everyone (also european users etc.) looking at this text see the correct characters? or will only asian users be able to see it properly?
thanks for helping out on this.
regards
nicola

The related systems need to be upgraded to unicode (CRM, ECC) and the chinese language loaded.
The ICWC should then support the asain characters.
We'll find out for ourselves in the next 3 - 6 months as we are just about to do the unicode upgrade.

Completed Form requires Asian Language Pack w/ no visible Asian characters

Why do Reader users receive a notification requiring them to install the "Asian Language Pack" after I fill out a form and send it? The form has no visible Asian characters.

Fonts listed under Document Properties of the completed form are: TimesNewRomanPSMT (TrueType) & TimeNewRomanPS-BoldMT(Embedded) TrueType.
I neglected to mention that the original form (incomplete) does not require the Language Pack. What settings/preferences can be changed in Acrobat to prevent Unicode (or other unwanted Fonts) from being used when completing the form?

We would like to use cyrilic language characters in ECC system with custome

We would like to use cyrilic language characters in ECC system with "customer reserve" language (Z1).
We have positive experience on one system for certain business partner in Macedonia (there is no Macedonian language to install as SAP standard) by using "customer reserve" language (Z1).
Now we are about to introduce other system with same approach. The trouble is that after entering Macedonian language on an cost center with language Z1 on first language and transfering it via idoc we get hashes("#") instead of characters on second language
What could be the reason? I suplemented with english (as on the first system where everything is ok) the "Customer reserve"(Z1) language normaly(with default settings).
On first system this was not done by me.
Should supplementation be done specificly?.(how to find settings for supplemention on first system?)
Please give me a hint

Hi,
To check supplement language go to T-code, SMLT ->Language ->Special actions->Supplementaion
you can get more information from below SDN thread.
Cyrilic char not coming properly
Below SAP help document gives you how to find supplement language & installation of languaes.
http://help.sap.com/saphelp_nw70/helpdata/en/a3/30ad5296b511d384bb0060975b04f3/content.htm
Regards
Nagaraju

Using FileReader/Writer with Asian Characters - can you spot my problem?

Hi,
I can read in and write out one byte at a time with Asian characters, but if I try to do it one line at a time the Asian output is garbage. I will list both little programs here, and hopefully someone can educate me on my problem.
+++1st, *this {color:#339966}works fine{color} with Asian characters:*+
+{color:#000000}import java.io.*;*{color}+
{color:#000000}class copybyte
public static void main (String args[]) throws IOException
if (args.length != 2)
System.out.println("Usage: java copybyte srcfile dstfile");
return;
final boolean DEBUG=true; // switch for ascii display
int ch; // the buffer{color}
{color:#000000}// Create streams
FileInputStream fis = new FileInputStream (args[0]);
FileOutputStream fos = new FileOutputStream (args[1]);{color}
{color:#000000}while ((ch = fis.read()) != -1)
fos.write(ch);
if (DEBUG)
System.out.print(ch);
System.out.println(" "+Character.toString((char)ch));
fis.close(); fos.close();
}{color}
But the following code outputs Asian characters in garbage to my text file:
{color:#000000}import java.io.;
// Does not seem to handle Japanese....
class CopyLineIO
public static void main (String args[]) throws IOException
if (args.length != 2)
System.out.println("Usage: java copyline srcfile dstfile");
return;
final boolean STRIP=true; //strip blank lines from file ??
String buf,temp;
// Create streams
FileReader fr = new FileReader (args[0]);
FileWriter fw = new FileWriter (args[1]);
BufferedReader br=new BufferedReader(fr); //wrap basic object
BufferedWriter bw=new BufferedWriter(fw); //wrap basic object
while ((buf = br.readLine()) != null)
temp=buf.trim();
if ((temp.length()>0)||(!STRIP)) {bw.write(buf"\n");}
br.close(); bw.close();
fr.close(); fw.close();
Can anyone advise on what to change in CopyLineIO so that Asian characters work?{color} Thanks!
PS Sorry about the code formatting - not sure how to get it looking decent here when pasted in....
Edited by: JavaNeo on Jan 14, 2010 7:10 AM

[From the documentation|http://java.sun.com/javase/6/docs/api/java/io/FileReader.html]:
Convenience class for reading character files. The constructors of this class assume that the default character encoding and the default byte-buffer size are appropriate. To specify these values yourself, construct an InputStreamReader on a FileInputStream. To post code use { code } // your code here { code } without the spaces or simple select the code and press the CODE button.
// your code here

Printing of Chinese characters issue

Hi all,
I have a SAPScript Layout with Chinese characters to be displayed.But in the hard-copy printout I do not get the chinese characters printed, instaed it prints some funny characters like '####'.
How can i get the chinese characters printed ?
Your ideas are appreciated.
Thanks,
Stock

The logic to build SAP Script and Smart form of all languages will be same. But while working on Asian language please take care of the following points.
1 Make sure you logon to SAP in Chiness language only.
2 At the Operating system level install the Chinees language.[Control panel - >Regional and language Option - >language Tab - > Click on Install Files for East Asian languages] If these language already installed then click on Detail and add the Chinese languages[Chinese (PRS) and Chinese(Taiwan).
3 At SAP level click on Customizing of Local layout[Alt+F12] and click on options.Go to tab I18N and click on Activate the multi-byte functionalities to support check box.
4.Take care of the Font while assigning to Character formar or paragraph format. Dont use normal font name. Example of chinese phone "CNSONG

Cannot print a PDF file after upgrading to Windows 8.1

Cannot print a PDF file after upgrading to Windows 8.1
I can print anything else from either the Desktop or Start but not a PDF. No error message but just does not print.
Update: down loaded Adobe Reader which runs on the desktop so when I read a PDF file it now runs on the desktop and I can print it.

Cannot print a PDF file after upgrading to Windows 8.1
I can print anything else from either the Desktop or Start but not a PDF. No error message but just does not print.
Update: down loaded Adobe Reader which runs on the desktop so when I read a PDF file it now runs on the desktop and I can print it.

Printer will not work after update to Mavericks

I have a macbook pro and an HP7280 printer connected wirelessly. After upgrading to Mavericks the printer will not work. The first time I used it the system upgraded automatically (I forget what it said but it just went ahead and did some upgrading) When I clicked on something to print it did recognized the printer but just scrolled and scrolled and never printed. So I deleted the printer and reset the system and then added the printer back on - same thing. Any ideas??

It means there is no issue with the driver you are using and with it working correctly on Mavericks. So you have a network issue with the printer queue you are using. Normally a reset of the printing system and re-adding the printer would be enough to get things working again. But since you have done this and your issue is not resolved, there must be some other gremlins in the system.
With the HP connected to the network, if you know its IP address you can enter this as a URL into a web browser. This should result in you connecting to the internal web page of the HP. Does this work?

PKUNRE field not getting populated in 2LIS_13_VDITM after ECC upgrade

Hi,
We are seeing blank values for PKUNRE / 0BILLTOPARTY during extraction from 2LIS_13_VDITM.
We are experiencing this issue after ECC upgrade which went live recently.
We have applied note 580694 to correct missing fields in the billing extractor.
This field is sourced from VBPA/VBRP.
Our functional teams confirmed that VBPA/VBRP are updated properly and there seems to be no timing issue.
However, the record is landing in PSA with blank BILLTOPARTY.
Where could the problem be?
Is there any thing we missed?
Can any one throw some light if you have experienced this kind of an issue after upgrade.
Thanks a ton in advance,
Sandy.

Hi Sandy:
In my system I didn't find the Field PKUNRE on the VBPA / VBRP Tables, so my guess is that you're dealing with a Custom Enhancement, if this is the case the SAP Note 576886 - "Change to user-defined fields not extracted" might help you in solving this issue.
Regards,
Francisco Milán.
***Follow up note:
I double checked and found the Field PKUNRE on the Extract Structure for 2LIS_13_VDITM (using Transaction Code LBWE) so now I know that you're working with a Standard field and not with a custom ehnancement, the SAP Notes below address a similar issue to yours but they are related to Applications 11 and 12, not for App 13. I apologize for the confusion.
Note 621684 - "Fields PKUNRE and PKUNRG are not filled from delivery"
Note 379237 - "BW Content LE-SHP: missing partners in 2LIS_12_VCITM"
Edited by: Francisco Milan on Jan 28, 2011 12:54 PM

Printing of asian characters after ECC 5.0 / unicode upgrade

Similar Messages

Maybe you are looking for