I've had problems with system/JVM default locale before.
When no encoding/charset is specified in new String(bytes[] data)
or String getBytes(), it uses the default locale. When the default
locale is not UTF-8, there will be a problem. I'm not sure where
the problem is, though.

You can capture the HTTP traffic and see what encoding it
uses to determine in what link in the request-response-storage
chain the encoding got wrong.

BTW, Just saw David's reply. Looks like he's found the problem.

On Sat, Oct 24, 2009 at 10:59 AM, Neil.Lv <anim...@gmail.com> wrote:
> In my page the Charset is UTF-8, and thisi is my platform information.
> Apache Maven 2.2.1 (r801777; 2009-08-07 03:16:01+0800)
> Java version: 1.6.0_05
> Java home: C:\Java\jdk1.6.0_05\jre
> Default locale: zh_CN, platform encoding: GBK
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> The lift doesn't store the character using the encoding UTF-8
> automaticly ?
> Cheers,
>  Neil
> On Oct 25, 1:51 am, jlist9 <jli...@gmail.com> wrote:
>> I'm not familiar with how Lift handles strings but if the encoding conversion
>> is what's missing, check out the Java String class, look for work encoding
>> or charset in java doc. Basically you can create a String with a specified
>> encoding and use getBytes() to convert it to a different encoding.
>> You can also try setting charset in your page to UTF-8. Maybe this is
>> the default in Lift.
>> On Sat, Oct 24, 2009 at 10:45 AM, Neil.Lv <anim...@gmail.com> wrote:
>> >  I just use the User's edit method that the ProtoUser ?
>> >  What's method that i can do for conventing GBK to UTF-8 before
>> > saving ?
>> > Cheers,
>> >  Neil
>> > On Oct 25, 1:34 am, jlist9 <jli...@gmail.com> wrote:
>> >> It sounds like you aren't converting GBK encoding to UTF-8
>> >> before you store the text?
> >

You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to