| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Reading japanese character through MQ |
« View previous topic :: View next topic » |
| Author |
Message
|
| bruce2359 |
 Posted: Tue Aug 23, 2011 10:52 am Post subject: |
 |
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
This may be painfully obvious, but...
The native language of computers and data is NOT English, not Spanish, not Japanese... none of the languages represented by code-pages (CCSIDs).
The common language of (most) computers and data is the byte - of 7 or 8 bits. With a single 8-bit bytes, it is possible to represent 256 different characters - with bits set from all 0's to all 1's.
Some characters may require two bytes - so-called double-byte characters. Kanji characters, for example, are logographic - pictures, and not letters and numbers. Examples: hiragana (ひらがな, 平仮名), katakana (カタカナ, 片仮名).
So, when the OP says that the other end is sending Japanese language, this is not precise.
It is the responsibility of the sender and receiver to AGREE on what is being sent and received. This is true whether the it is the contents of a letter, or digital data. Both ends must tell the other exactly what the contents is. This is accomplished in WMQ by the CCSID.
The receiver could be IE, but if IE doesn't have knowledge of what the sender sent, AND the appropriate code-page conversion table(s), then IE will attempt best-rendering - often little boxes as depicted in prior posts.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
 |
| gbaddeley |
| Posted: Wed Aug 24, 2011 5:02 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| bruce2359 wrote: |
...So, when the OP says that the other end is sending Japanese language, this is not precise.
It is the responsibility of the sender and receiver to AGREE on what is being sent and received. This is true whether the it is the contents of a letter, or digital data. Both ends must tell the other exactly what the contents is. This is accomplished in WMQ by the CCSID. |
Yes, the MQMD CodedCharSetId identifies the character set of the senders message data, and MQMD Format should be MQFMT_STRING.
If the receiving app specifies GMO_CONVERT, or the channel has CONVERT(YES), MQ uses this CCSID to automatically convert the message into the receivers app CCSID or qmgr CCSID.
Commonly the sender app does not explicity set the CCSID when it puts the message, so it inherits the Queue Managers's default CCSID. This is OK except when the app thinks its using one CCSID and the Queue Manager default is another CCSID ! Issues with EBCIDC code pages have been discussed on this forum. eg. 500 has some chars codes which are different to 37.
Make sure the app sets the CCSID to the correct value when it puts msgs, or uses the char set of the QM's default CCSID.
_________________
Glenn |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Fri Aug 26, 2011 12:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| bruce2359 wrote: |
| The receiver could be IE, but if IE doesn't have knowledge of what the sender sent, AND the appropriate code-page conversion table(s), then IE will attempt best-rendering - often little boxes as depicted in prior posts. |
Rendering is actually a separate step between applications and devices, outside the scope of mapping bytes to/from characters. Even if IE reads a properly declared and encoded xml document, it still needs the proper font support to display it. That's why hexdump utilities are useful, for ruling out problems with the message itself, when the display can't be trusted. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Aug 26, 2011 6:14 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
IE is not a diagnostic tool. You can't depend on IE to successfully render hex data (to anything other than the installed fonts).
There are quite a few free hex tools available. Search Google.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Fri Aug 26, 2011 1:54 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| bruce2359 wrote: |
IE is not a diagnostic tool. You can't depend on IE to successfully render hex data (to anything other than the installed fonts).
There are quite a few free hex tools available. Search Google. |
MQ Explorer (SupportPac MS0T), SupportPac MO71 (MQMON), SupportPac IH03 (RFHUTIL) and SupportPac MA96 (gmqbrw) can browse messages as hex bytes.
_________________
Glenn |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
