There are just too many place where things can go wrong. The first place to
start is SQL server which is not a multi-lingual data base unless you use
Unicode. The other concern that I have is how it the charset being
detected? If shift_jis is not being detected the DBCS_Lead byte is
different than Big5.
You have to find out exactly when the error is occurring.
From: Marco.Cimarosti@icl.com [mailto:Marco.Cimarosti@icl.com]
Sent: Thursday, October 12, 2000 5:01 AM
To: Unicode List
Subject: RE: [OT] problem with shift_jis
Raghu Kolluru wrote:
> My email delivery programs works with most of the charsets
> but not with
> Here are the steps that I do,
> 1) I get a text file from Japan which as the content in the
> encoded charset.
> 2) I paste this content in web based UI and store it in SQL server
> 3) Then I send it out with appropriate content header.
Could you attach one of the shift-JIS files that you received (step 1), and
the same text as you send it out (step 3).
> This works fine with big5,euc-jp, etc but not with shift_jis.
Are you sure that it really works fine?
Notice that random sequences of bytes (over 0x7F) often *look* like genuine
Asian text to someone who cannot read it. Can you (or someone else in your
team) read Chinese/Japanese to see that the text actually makes sense? If
not, you may wish to also send some sample of these.
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:14 EDT