Originally posted by: SystemAdmin

An Input XML file to the WTX contains following special ñ character
<SiteName>Hospital Muñiz</SiteName>
This xml is valid & able to open in a XML editor like Oxygen.

The above xml is tranformed in WTX(i.e XML to XML - utf-8 encoding). The ouput XML from WTX also contains same data with special character. But this xml file is not valid & cannot be opened in Oxygen.Also transformation is failing in datapower since this is not a valid xml. So output xml produced by WTX is invalid due to this special character.

When this special character is removed from that output xml, opens fine in Oxygen editor & also works in DataPower.

When i opened this output xml in Notepad++, data looks as follows (ñ is replaced with F2)
<FacilityName>Hospital Mu/FacilityName>. This is the reason for xml not being able to open in Oxygen editor & hence invalid.

WTX is replacing ñ with F2.
Is there any setting in WTX to overcome this issue?

Many thanks in advance.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: Kepa_Screen

Hi

I think that you need to change the header to something similar to this :

<?xml version=
"1.0" encoding=
"ISO-8859-15" standalone=
"yes"?>

ISO-8859-15 supports "ñ" character. It's "International Spanish"
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Correctly transforming extended characters isn't always trivial. It is helpful to know what the target display application is. You will need to verify the extended characters are displaying correctly in the application that is ultimate target. How they display in Notepad++ isn't relevant. If you are working with codepages, I recommend a hex editor such as UltraEdit. Displayed characters are dependent on the codepage your editor is using. With UltraEdit you can select the codepage to use but this isn't really necessary. Find a hex table for the target codepage you need to use and just make sure your output has the correct hex codes in it.

You can specify the correct code page in the target type tree Properties under Item Subclass-->National Language-->Data language.

ISO-8859-1 can handle all Spanish characters. It is also known as Latin-1.

Jim Divoky
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Hello Jim,

We are importing the type trees from XSDs supplied by one of our customers. Customer insists that we should not change any type tree after importing it. So we are looking at ways to handle Spanish(double byte) characters in SOlaris environment.

Let me know if you have found any other way of doing it.

Thanks,
Ismail
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Hello Jim,

We are importing the type trees from XSDs supplied by one of our customers. Customer insists that we should not change any type tree after importing it. So we are looking at ways to handle Spanish(double byte) characters in SOlaris environment.

Let me know if you have found any other way of doing it.

Thanks,
Ismail
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: gunturi

Did this ever got resolved . need similar help for spanish characters. currently map trace shows every thing is good but still throws an error at the end of input trace

#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: gunturi

especially this is happening in Solaris environment where the Spanish text contain

#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: repanzer

Something to note, and this drove me crazy;
Watch out when opening a document with multi-byte characters in Notepad, and then saving it, because Notepad puts in 3 non-printable characters as the first three bytes. Took me a few days and a lot of sanity to figure that one out. I can view multi-byte in Notepad because I have a language patch install in Windows, but without it, it's way more trouble then it's worth. I use ultra edit also. Works great.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

We have a similar issue - is there an 'easy' way to only allow UTF-8 encoded characters - we were looking at character substitution using an exclude rule but I can't see a way of specifying non standard characters doing this, ie hex values?
Any advice would be greatly appreciated.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender