Author |
Message
|
triniti |
Posted: Fri Jun 16, 2006 2:16 pm Post subject: xml files encoding |
|
|
Newbie
Joined: 15 Jun 2006 Posts: 8
|
I did it, and the xml file that I've recieved have two enconding fields.
encoding=ISO88..
encoding=UTF-8
I only want UTF-8. I've seen that in the remote queue the option "conversion" is cheked "no".
Why appears encoding=ISO88..? how could I change it?
Thanks.
trnt. |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Jun 16, 2006 4:56 pm Post subject: Re: xml files encoding |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Did what?
I don't understand your question at all. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
triniti |
Posted: Fri Jun 16, 2006 11:59 pm Post subject: |
|
|
Newbie
Joined: 15 Jun 2006 Posts: 8
|
I did it..
is a replay for a posible solve that someone talked me two days before in another post with the same tittle. |
|
Back to top |
|
 |
jfluitsm |
Posted: Mon Jun 19, 2006 4:59 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002 Posts: 160 Location: The Netherlands
|
Did both encodings show between '<?xml' and '?>' ?
If one of them didn't, you forgot the (XML.Decl) bit.
Otherwise, try the MRM settings, there is one about suppressing XML declaration.
For UTF-8 a XML declaration is not needed.
Als, don't forget to set OutputRoot.Properties.CodedCharSetID = 1208, otherwise the receiver might have problems with characters > 127. _________________ Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
Back to top |
|
 |
triniti |
Posted: Mon Jun 19, 2006 6:34 am Post subject: |
|
|
Newbie
Joined: 15 Jun 2006 Posts: 8
|
I've seen that in the target queue the message have "encoding=utf-8", maybe the problem is in the "get", probably it makes an encoding converse. do you Know if it's possible? |
|
Back to top |
|
 |
jfluitsm |
Posted: Mon Jun 19, 2006 6:41 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002 Posts: 160 Location: The Netherlands
|
If you use convert on the get and the MQMD.Format = MQFMT_STRING only the characters are converted. Nothing is done with the content of the message. This might be different when an user format with an user conversion routine is used, but I have never seen that before.
Also keep in mind that the XML recommendation states that an external encoding (MQMD.CodedCharSetID) has priority over the encoding in the xml declaration. So if your XML message has encoding=UTF-8 and the CCSID in MQMD states 819, you should use ISO-8859-1 instead. _________________ Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
Back to top |
|
 |
triniti |
Posted: Thu Jun 22, 2006 2:09 am Post subject: |
|
|
Newbie
Joined: 15 Jun 2006 Posts: 8
|
We´ve resolve the problem.
we saw that in the target queue, the message had utf-8 encoding, the problem was that the program that get the message introduced a header with ISO encoding. We've modified this program and the xml file now have the right header, UTF-8.
But we've now another problem, if the message contains characters like "ñ" it doesn´t apears rigth. We've seen that in the target queue the caracters are right, and the program which get the message doesn´t make an encoding conversion. Do you Know why we can not see this characters rigth???
I´m sorry about my english..
Thank's a lot!!!!!!!!!!!!! |
|
Back to top |
|
 |
jfluitsm |
Posted: Thu Jun 22, 2006 2:53 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002 Posts: 160 Location: The Netherlands
|
Please check the CCSID of the message. This should state 1208 (utf- .
The broker uses the CCSID of the message and not at the XML-encoding. This behaviour is conform the XML recommendations. _________________ Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
Back to top |
|
 |
triniti |
Posted: Thu Jun 22, 2006 4:27 am Post subject: |
|
|
Newbie
Joined: 15 Jun 2006 Posts: 8
|
Hi!
the CCSID of the message is 1252, if I try to change the CCSID of the Qmgr it fails. How could I change the CCSID of the message?? I've tried it writting in esql "SET OutputRoot.Properties.CodedCharSetID = 1208;" but the CCSID of the message didn´t change.
Thanks!
trnt.  |
|
Back to top |
|
 |
jfluitsm |
Posted: Thu Jun 22, 2006 4:45 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002 Posts: 160 Location: The Netherlands
|
You misspelled CodedCharSetId (d instead of D). However, best-practise is to set the CCSID in de properties.
Code: |
SET OutputRoot.Properties.CodedCharSetId = 1208; |
_________________ Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
Back to top |
|
 |
triniti |
Posted: Thu Jun 22, 2006 8:02 am Post subject: |
|
|
Newbie
Joined: 15 Jun 2006 Posts: 8
|
That's running perfect!!!!
Thank's Jan!!! |
|
Back to top |
|
 |
|