BTW, if you are using RequestBuilder to send data, you need to make to set the Content Type of header: charset=utf-8.
-Ben On Sep 28, 10:47 am, David Given <[email protected]> wrote: > Jong Lee wrote: > > I input Korean into GWT EXT TextArea but it just stored ??? into > > MySQL. It seems to be stored broken. > > That's unlikely to be a problem with GWT --- what's almost certainly > happening is that MySQL is using the wrong encoding for its text. That > is, GWT is providing UTF-8 to MySQL, which is then parsing it as ASCII > and replacing all the Korean characters with strings of ? symbols. > > In general, when dealing with any language other than English, you want > to set the encoding in as many places as possible to UTF-8. So: > > - configure the server to send the appropriate Content-Type header > - *and* add the META tag to your pages to set the Content-Type too > - *and* ensure that in your server code you always use the UTF-8 > encoding when parsing strings > - *and* do whatever exotic configuration MySQL needs to parse strings as > UTF-8. > > I don't know how much of this you've already done, but what you've > described is a classic symptom of missing something. > > -- > ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─────http://www.cowlark.com───── > │ > │ "They laughed at Newton. They laughed at Einstein. Of course, they > │ also laughed at Bozo the Clown." --- Carl Sagan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
