I've made some changes to the only ODBC option I can find ('perform translation for
character data') and it doesn't make a difference. Plus, I don't get accurate Unicode
when using the File action to load Unicode text (which I assume takes ODBC out of the
loop).
However, I did find a charset converter program and converted the Unicode to EUC-KR
Korean, imported that into the database, and it's selected and displayed by WiTango
just fine (now using EUC-KR Charset). One difference seems to be that the Unicode
import into SQL had to be done as nvarchar type but the EUC-KR import seems to work as
varchar data. Would there be a difference from WiTango's point of view because of the
data type difference?
----- Original Message -----
From: "Ed Edgar (mailing lists)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 24, 2003 6:13 PM
Subject: Re: Witango-Talk: Unicode and WiTango Problem
> Dave,
>
> A couple of thoughts:
>
> 1. It would be good to confirm whether
> a) Bad data is being sent to the browser
> or
> b) The wrong headers are being sent to the browser, so the browser is
> just displaying it wrong.
> (By default WiTango tells the browser that the content is
> ISO-8859-1. However, it you have a meta tag the browser should normally use
> that instead.)
> If you look under View->Encoding in IE, is UTF-8 checked, or something else?
> Also, If you look at the source code raw, does it contain the same
> garbage as is displayed in the browser window?
>
> 2. If it's (a), which it probably is, it could well be going wrong before
> it even gets to WiTango.
> I assume you're using ODBC, right?
> Have a play around with the options in your ODBC data source setup. I
> seem to recall there's one for character encoding translation, which has be
> checked or unchecked or something..
>
> Good luck,
>
> Ed Edgar
>
> At 16:47 03/09/24 -0700, you wrote:
>
> >I've got a MS-SQL 2000 table with a column that contains unicode data
> >(Korean). The data displays correctly on my screen in Enterprise manager.
> >I do a simple select in WiTango to retrieve the first 20 rows from that
> >column and display them on the screen and all I get are question marks
> >(except for where some English words appear amongst the Korean):
> >
> >????? email? ??? ?? ??? ?? ? ???? ?? ?? ???? ????
> >
> >I have <META http-equiv=Content-Type content="text/html; charset=utf-8">
> >in the head of the WiTango file and ENCODERESULTS=FALSE in my config.
> >
> >I also do a test by creating a unicode text file that just says 'test'
> >and loading it with the file action and then displaying it on the screen,
> >but what I get is:
> >
> >?est
> >
> >I'm running WiTango 5, and W2K
> >
> >Any ideas what I should do to make the text appear correctly?
> >
> >Dave Machin
> >
> >
> >E-Mail. [EMAIL PROTECTED]
> >Tel. 805.614.0123 x 30
> >Address: 3130 Skyway Drive #702
> >Santa Maria, CA
> >93455ラララララララララララララララララララララララララララララララララララララララララララララララララララララララララララララララララララララララユネS
> >
> >盤P頒ヤ単鮮維ネ桐ンンンヒ旡ン俚叺ヒ俚ロヒロリレロン享俛
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: Go to
> http://www.witango.com/maillist.taf________________________________________________________________________TO
> UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
