Re: Witango-Talk: WiTango - Korean

Mon, 13 Jan 2003 18:05:24 -0800

We used to run Korean language content using Tango2000 on an English-language version of Win2k.
 
The encoding we used was EUC-KR.
 
Tango2000 doesn't know what double-byte characters are, but it doesn't break them either.
So you can shove text in and out quite happily, but you probably can't trust metatags like <@LENGTH> and <@REGEX> when working with Korean.
 
There's plenty more about multi-byte encodings in the archives (especially on UTF-8, where the same issues pop up), but I'll paste an old post from Anthony Humphreys below, which should give you most of The Answers.
 
Ed Edgar
The Princeton Review
Asian Hosting, Tokyo
[EMAIL PROTECTED]
 
-------------------------------
From Anthony M. Humphreys
RE: Witango-Talk:  Good be be back, and a big Japanese question
2002-04-24

1) Turn OFF Tango's encodeResults , that is
<@ASSIGN SCOPE=system NAME=encodeResults VALUE="false">
as this will prevent Tango from mangling High ASCII values
into like turning e into #233;

2) Re-write the HTTP header to include the actual character set you are
using.
By default Tango is set to write the header with iso-8859-1

3) Use caution when using the built-in e-mail action.
It's design is ONLY for iso based 8-bit character sets.
Double byte character sets may or may not work
as expected. You may find a way to get the action to work,
but use it at your own risk

4) The Tango editor still has some unexpected strangenesses
when working with nvarchar (unicode) datatypes. You
will need to modify any builder apps that used
non-8-bit character datatypes.

-------------------------------
----- Original Message -----
Sent: 2003年1月14日 6:22
Subject: Witango-Talk: WiTango - Korean

Has anyone ran websites in WiTango that were translated into Korean.  I think it requires a double-byte character set and was wondering if anyone had experience in that?

Dave Machin
 

Reply via email to