|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Write IOS-8859-10 / Latin-6 / Windows-1270 chars |
« View previous topic :: View next topic » |
Author |
Message
|
shrusonu |
Posted: Fri Apr 03, 2020 5:40 am Post subject: Write IOS-8859-10 / Latin-6 / Windows-1270 chars |
|
|
 Novice
Joined: 20 Dec 2013 Posts: 16
|
Hi All,
I am on IIB v10.0.0.9 - Windows
Problem :
I have a webservice, which writes fixed length record data to text file with encoding as ANSI. (A file opened in notepad and save as shows me ANSI encoding)
Consuming systems make a service call with UTF-8.
Nordic characters [Latin-6] in requests cause failures to write to file.
I have tried using Windows-1270 / ISO-8859-10
Could you help to achieve writing these characters to file but still to maintain same encoding ANSI
It works perfect with UTF-8
Many Thanks, |
|
Back to top |
|
 |
Vitor |
Posted: Fri Apr 03, 2020 6:34 am Post subject: Re: Write IOS-8859-10 / Latin-6 / Windows-1270 chars |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
shrusonu wrote: |
Could you help to achieve writing these characters to file but still to maintain same encoding ANSI |
How have you confirmed that these Nordic characters are available and printable in the character encoding you're trying to use? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
timber |
Posted: Fri Apr 03, 2020 12:29 pm Post subject: |
|
|
 Grand Master
Joined: 25 Aug 2015 Posts: 1292
|
The web service can only output characters supported by 'ANSI'. I don't know what you mean by 'ANSI' but it's definitely a character set with a restricted number of code points, else you would not be getting that error.
In general, your mission is hopeless. Read this article to see why: https://www.joelonsoftware.com/2003/10/08/the-absolute-minimum-every-software-developer-absolutely-positively-must-know-about-unicode-and-character-sets-no-excuses/
The best you can do is to scan for characters that are not supported by the target encoding and replace them with something that is supported. A better solution would be to modify the web service to use a UTF-8 instead of 'ANSI'.
Again, read that article. It really is very good, and will probably open your eyes to a few important facts about Unicode, character sets and encodings. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|