Encoding problem (via ORB)

Question

Hello,
I posted this problem few months ago, but still havent been able to solve this.
I have a Client Server program which communicates via ORB, i.e. using CORBA, with server running on Solaris OS and Client running on windows.
The server returns string containing chinese characters to the client.
However, my chinese characters dont appear properly on the client side.
If i run the client on the Solaris OS there is no problem with it.
I tried converting the encode of the string by getting its byte and creating
a new string with encoding parameter. None of this seems to work.
I can see the chinese character when the server is writing to OutputStream of CORBA, but on the InputStream of CORBA it does not
show properly.
Any ideas on how i can overcome this encoding problem where the C/S is
communicating via CORBA (ORB)?
Thanks in advance.

Answer 1

Thanks for your reply
Yes, i know the BIG5 is for Traditional Chinese and japansese is using like Shift-JIS or EUC.
So when i try to post japanese in a BIg5 web page, i think it's normal that i can't see it in BIG5 encoding.
But then i change the Safari default decoding to BIG5 HKSCS, the japanese appers! At the same time i can see the traditional chinese too!
And if i use Firefox, i can both see the japanese and chinese at the default BIG5 encoding.
So i simple think maybe safari translate my japanese into BIG5 HKSCS,not Shift-JIS. But if i use Firefox, i can get the same result with only BIG5 encoding, not BIG5 HKSCS. So i am just wondering why it's different between Safari and Firefox with the same BIG5 encoding.
Following is a example URL
It's a MAC discussing froum with BIG5 encoding in Taiwan.
http://ubb.frostyplace.com.tw/viewtopic.php?t=19162
It's a froum topic posted by me. I input some japanese into this topic
If you browse this page with Safari BIG5 encoding, you can see a lot of question mark instead of the original japanese word that i and other people posted.
But if you change the encoding to BIG5 HKSCS, the japanese appears. And if you using Firefox with BIG5 encoding, the japanese appears too.
So is it someing wrong with Safari's BIG5 encoding or some other reason makes this happen?