japanese character

[Former Member]

Hi All,

Is there is any way to display the japanese character in the application.We have made a smart sync application which is working fine for English language but when we use the application for Japanese user for japanese data..the data is coming in garbage form like "•É“ìŽs–¯•a‰@ " what settings needs to be done either in mobileengine config file or on to the server side to enable the support for unicode characters on to the client.

The MI server configuration

a) Operation system version – AIX

b) OS 32 bit or 64 bit? – 64 bit

c) Unicode or Non-Unicode – Unicode

R/3 one SAP system configuration

a) Operation system version – AIX

b) OS 32 bit or 64 bit? – 64 bit

c) Unicode or Non-Unicode – Non Unicode

Thanks in advance.

Regards

Devendra kumar

[Former Member · Accepted solution]

hi deven,

here's what you can try. in your client application, try creating a japanese record

and try to display it. if this is fine, then you will have to deal with the encoding of

your server data.

is your problem only related with the server data?

regards

jo

[Former Member · Accepted solution]

Hi Jo/Siva.

Jo in the output of R/3 function module i m gettting the data as garbage value like " #ú#{#Ô####Ð#a#Ì#R#ã#Ã#Z###^#["as it is a non unicode system.Is it because of this i am not getting the correct data in the output(client) because i have already tried the option what siva has mentioned to make changes in SM59 for common user.

If is it because of non unicode R/3 system what can be done to solve the issue.

Also please guide me how to display a japanese character on to the client.

Siva i m using only syncbo of type S01 do i need to make some other configuration other than in SM59.

Thanks in advance.

Regards

Devendra

[Former Member · Accepted solution]

Hi Jo/Shiva,

After making changes to user id in backend in user profile for japanese language.I am able to see the data for user in japanese language on the R/3 as well in middleware.But on to the client side it giving me the output as "????????????:??"..i m getting all the japanese data in this form.Please suggest if i have to make some settings on to the midleware or on to the client side to see the data in japanese language.

Thanks in advance

Regards

Devendra

[Former Member · Accepted solution]

Hi Devendra,

The current setup will not work. You will have to have Unicode Middleware if the backend is Unicode and also if the Japaneese characters needs to be supported.

Also replication will not happen for T01/T51 Syncbos due to this as it will result in duplicate R3keys error. Even if replication will take place, japaneese charachters will be shown as junk.

There can be no settings be made on the client or on the middleware to achieve the above functionality.

Thanks..

Preetham S

[Former Member · Accepted solution]

Hi Preetham,

I have the unicode middleware but the backend is not unicode.In the backend and middleware i can see the records with japanese text but on the client its coming as some garbage value.

Thanks

Regards

Devendra

[Former Member · Accepted solution]

hi deven,

can you see what is the raw data format sent by the middleware to the client?

you can lookat the mobile worklist and look on the record sent; also in the client

thru the trace inbound data dump.

regards

jo

[Former Member · Accepted solution]

Hi Jo,

i m getting the japanese data in the middleware as well as on to the client trace file but on the application jsp page the data is coming as "??????? ".Please suggest...

Thanks in advance.

regards

Devendra Phate

[Former Member · Accepted solution]

hi deven,

you can check on the jsp's page coding. something like.

<%@page pageEncoding="UTF-8" contentType="text/html; charset=UTF-8"%>

as well as the meta html tag.

<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>

you have to set the charset value to its proper value UTF-8, Shift-JIS, EUC etc...

depending on what your encoding is.

regards

jo

[Former Member · Accepted solution]

Hi Jo,

I tried all the possbile charset values but the problem is still the same.I tried to print the æ± character in japanese in JSPits getting converted in to japanese character but the data to my application is still coming as "?????"..please suggest.

Thanks in advance.

Thanks

Regards

Devendra Phate

[Former Member · Accepted solution]

Hi Jo,

When i m trying using

<%@page pageEncoding="shift_jis" contentType="text/html; charset=shift_jis"%>,

<META http-equiv="Content-Type" content="text/html; charset=shift_jis">

like for all encodng type i m getting the error as

"Page directive: Invalid attribute, pageEncoding " in the JSP page.

Please suggest.

Thanks

Regrards

Devendra

[Former Member · Accepted solution]

hi deven,

the pageEncoding="shift_jis" attribute for is for jsp 1.2.

<%@page contentType="text/html; charset=shift_jis"%> would be enough.

is it possible to look on your MI installation and application with data?

just send me the zip installation to jogel.sdn[at]gmail.com. i might have time this

weekend and look into it. if the files are big, just send me the link where i can

donwload it.

regards

jo

[Former Member · Accepted solution]

Hi Jo,

Thanks ...Thanks a lot for your help..The Japanese character is working now .I tried the way u have mentioned i tired that on Desktop MI client but on Mobile 5 (English os)device its still an issue for me..Its could be because as japanese fonts are not there by default....I tried copying the msgothic font on to my Mobile Device but the characters are still not getting refllected..Please let me know if something else need to be done to enable japanese fonts on PDA.

Thanks again..:)

Regards

Devendra

[Former Member]

Hi,

If you are using MI2.5 SP18...then ensure that the client is using Patch 01. Also in the worklist monitor check if the data is sent in Japaneese.

Thanks...

Preetham

[Former Member]

Hi Preetham,

Can u please give me the link from service.sap.com or search string for patch01 because i tried finding it but coludn,t get it.Is something recommended by SAP for SP18 patch 01 in terms of japanese characters..

Thanks

Regards

Devendra Phate

[Former Member]

Hi Devendra,

The latest patch on SP18 is patch07, since it is a cumulative patch patch07 will contain the fixes in patch01, Patch01 contained some Multilanguange fixes. You will find the latest patch in the service marketplace.

Best Regards,

Karthik

[Former Member]

Hi Karthik,

I tried searching for the patch07 in service market place but was unable to find the same.Could you please help me out to find the same.

Thanks

Regards

Devendra

[Former Member]

Hi Devendra,

Please use the following link.

http://service.sap.com/swdc

SAP Support Packages -> Entry by Application Group -> Sap Netweaver -> Sap Netweaver -> SAP Netweaver 04 -> Entry by component -> MI Client -> MI Client 2.5 -> OS independant

Here you will find the patch for SP18 named MI25SP18P_7-10002889.ZIP will give you your delta patch and NWMCLIENT18P_7-10002889.SCA will give you a complete install.

I also want you to check Jo's post above about encoding, that could help solve your problem

Best Regards,

Karthik

[Former Member]

Hi Devendra

Have you used the Multi Language Feature made available with MI 2.5 SP18 or MI7.0 SPS09? Please refer to the note 1029594 for more information on this. If no, then request to you implemente this feature. If yes, I feel the problem you are facing is directly related to you backend being a Non Unicode system and MI Server being a Unicode system. If you read the word document attached to the note mentioned, there is an indication referring to such a combination <i><b>In a Multi language scenario, if the backend is Unicode based then the middleware must also be Unicode based. The Unicode languages get converted to junk characters when they are transferred from the backend to the middleware. In such scenarios replication may fail or data may not get downloaded to the client</b></i>. Just FYI, Please refer to the replies in thread which might be useful to you.

Best Regards

Sivakumar