Japanese Characters

[Former Member]

Hi.

We have a http solution where the source system makes a http call towards our messageinterface.

The solution works fine until we use Japanese characters in the message.

One line in the message should have japanese characters but we get this in XI.

<SHORT_TEXT>伿çu201D»å®¤;伿çu201D»å®¤;99991231;19990401;O;</SHORT_TEXT>

This is what we see when we receive the message in XI but the sender has japanese characters in the outgoing message.

The imported XSD has codepage <?xml version="1.0" encoding="UTF-8"?>

When we import that structure in XI the imported document gets the following encoding.

<?xml version="1.0" encoding="ISO-8859-1"?>

Why is this? I sthis the cause of the problem?

If not why do we get the strange characters in XI?

The owner of the sourec system tells me that they send the message in UTF-8.

I hope somebody could help me here so I can solve this problem.

BR

Kalle

[stefan_grube]

Hi Kalle,

The encoding in the XSD has no impact of the content of the XML message.

The incoming XML message has its own encoding declaration.

Check which encoding declaration you find in the XML header.

If you see UTF-8 and the characters are not readable in SXMB_MONI, the characters might not be in the correct encoding.

Regards

Stefan

[Former Member]

Toke the payload and tested to send it with my test htmlpage.

Worked fine and all the characters looked ok.

My conclusion is that the sending part does not send it in the correct encoding.

We will see what they discover.

BR

Kalle

[former_member206760]

also try GB 2312

[former_member206760]

Dear Kalle,

tryr using UTF-16 and Binary transfer ..if u are using file adapter.

Edited by: Tarang Shah on Mar 18, 2009 10:13 AM

[JoelTrinidade]

Hi Kalle,

In case you missed out here is something i would like you to read carefully.

" UTF-8 and all ISO-8859 codepages are based on ASCII. Therefore they are compatible

when only printable characters from ASCII are used. Other characters like European ä,

ê, ñ, u0161 and letters from other alphabets are represented differently or are only available in

specific codepages. These characters cause errors in interpreting XML messages if the

wrong codepage is used.

Some adapters get the information about the codepage from the sender or receiver

system and do the transformation automatically _*whilst other adapters need this

information in the configuration*._

The transformation between codepages is carried out by operating system routines. If

you want to work with different codepages then you have to _*make sure that the

codepages are implemented in the operating system where XI or the adapter framework

is installed.* "_

Also try your hand at the codepage identifier, for example ISO-8859-1 which is for West European Latin, and

GB18030 is a standard for Japanese/ Chinese characters. Try GB18030 instead of UTF-8 or ISO-8859

Edited by: joel trinidade on Mar 18, 2009 1:49 PM

[Former Member]

According to collegues at work we have that codepage (GB18030) installed on our OS.

Do the sending system need to send it in GB18030?

BR

Kalle

[Shabarish_Nair]

1. provide GB18030 as the encoding in your XSD.

2. are they flexible to send it in the code page as specified?

[former_member750652]

Hi Kalle,

I think there are some settings to be done to handle special characters like this.Can you please refer the following link that discuss similar issues and settings.

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79...

Thanks,

Ram.

[Former Member]

Hi.

That documents covers if you use SOAP adapter to make the call into XI.

That was not the case fo our solution. We are using plain HTTP calling directly towards our message inteface.

//Kalle