Yes, each country's site has its own set of encodings for the headers and meta tags. The appropriate ones are pulled out of the database for each site.
We don't do any Korean data input here at all, so we don't need Korean input support here in Tokyo; All the content gets entered by the Korean office using our browser-based content management system. http://kr.review.co.jp/tafs/welcome.taf?lg=2b Let me know if it breaks... Ed ----- Original Message ----- From: "Garth Penglase" <[EMAIL PROTECTED]> To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> Sent: 2002?9?3? 4:21 Subject: Re: Witango-Talk: Tango and UTF-8 encoding. | Which Korean site was that? I am currently using NJStar Communicator to | view and test sites - interested in seeing how the development was done for | your Korean site - I assume you used a custom Korean HTTP header in your | tafs, and then entered your content using a korean font set. | Garth | | At 03:49 3/09/02 +0900, you wrote: | >Hi Garth. | > | >I guess Korean UTF8 would just be a subset of everyone else's UTF8, so the | >same would apply. | > | >Namely: | > | >Tango2000 won't break the text, but it won't know how to handle multi-byte | >characters intelligently either. | > | >Be careful with tags like <@LENGTH> and <@SUBSTRING>, which may work | >wrongly or break things unexpectedly. | > | >We've been running a Tango website for our Korean office in EUC-KR for a | >few years now, and haven't had any problems as far as I know. (Although | >the office in question ended up making themselves a _much_ cooler site | >using PHP...) I've never used KSC (CP949), but I guess it's just another | >multi-byte encoding and can't be any worse than shift-jis... | > | >Presumably you'll need to do some kind of conversion (UTF8 to UTF7?) if | >you want to gather information on the web (UTF8 or whatever) and send it | >as e-mail (7-bit-only, strictly speaking, so UTF7?). My MB_String thing | >should be able to use any encoding Java supports (which is pretty much any | >of them) so it should work for those conversions. If it works at all... | > | >Ed Edgar | >The Princeton Review | >International Hosting, Tokyo | >[EMAIL PROTECTED] | > | >http://www.review.co.jp | >http://www.princetonreviewhk.com | >http://www.tprthai.com | >http://www.princetonreview.com.tw | > | > | >----- Original Message ----- | >From: "Garth Penglase" <[EMAIL PROTECTED]> | >To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> | >Sent: 2002?9?3? 1:26 | >Subject: Re: Witango-Talk: Tango and UTF-8 encoding. | > | > | >| Interested in this from a Korean perspective. Any experience with that? | >| Want to create web pages and email in Korean UTF8 UTF7, or KSC (CP949). | >| Haven't worked with any different languages before. | >| Garth | >| | >| | >| At 09:42 2/09/02 +0900, you wrote: | >| >Tango 2000 doesn't know anything about encodings. | >| > | >| >As far as I can tell it just assumes everything's ISO-8859. (There's | >nothing | >| >in the manual, so I'm guessing...) | >| > | >| >On the other hand, it doesn't break non-Ascii text; It just handles it as a | >| >bunch of bytes. If you do everything in UTF8, and you never need to convert | >| >it into anything another encoding, you should be OK. | >| > | >| >Previously people on this list have reported doing lots of work with | >Tango in | >| >UTF8, and not having any problems. | >| > | >| >If I've got this right, the basic 7-bit Ascii characters are the same in | >| >UTF-8 as in ISO-8859, so you can handle those without worrying about | >| >encodings at all. | >| > | >| >But when it comes to multi-byte characters, there's plenty of room for | >things | >| >to go wrong. At a minimum, string functions like <@LENGTH> will treat the | >| >text as bytes, not characters. | >| >Actually we've managed to live with this kind of thing while working | >with all | >| >kinds of Asian multi-byte encodings, including the evil Shift_JIS, but it's | >| >not ideal. | >| > | >| > | >| >A while back I kludged together a Tango Class File and a Java bean | >| >to do things like encoding conversions and multi-byte-sensitive string | >| >operations. If this is the kind of thing you need to do, take a look at: | >| > | >| >http://www.edochan.com/tango/MB_String.htm | >| > | >| >There are some custom tag definitions there as well, so if it works you | >| >should be able to do things like: | >| > | >| ><@ASSIGN local$myUTFString '<@MB_CONVERT STR="my text" | >| >FROM_CHARSET="ASCII" TO_CHARSET="UTF8">'> | >| > | >| >I've never used this stuff in a production environment (or anywhere except | >| >the Japanese laptop I wrote it on), so you should consider it best, | >erm, beta | >| >quality code. But if you think it might be useful, help yourself, and | >let me | >| >know if you have any problems. (You probably will...) | >| > | >| >Good luck, | >| > | >| > | >| >Ed Edgar | >| > | >| >On Monday 02 September 2002 08:30 pm, you wrote: | >| > > I want to use UTF-8 encoded strings when I'm posting forms. | >| > > | >| > > Is it possible to parse strings to UTF-8 in Tango? | >| > > | >| > > Can't find anything i the manuals, please help. | >| > > | >| > > Thanks, | >| > > | >| > > Hans-Goran Persson | >| > > ________________________________________________________________________ | >| > > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] | >| > > with unsubscribe witango-talk in the message body | >| >________________________________________________________________________ | >| >TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] | >| > with unsubscribe witango-talk in the message body | >| | >| ________________________________________________________________________ | >| TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] | >| with unsubscribe witango-talk in the message body | > | >________________________________________________________________________ | >TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] | > with unsubscribe witango-talk in the message body | | ________________________________________________________________________ | TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] | with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
