Hi David,
Thank you for you help!
I had changed the codestrikerdb database/table/field charset to utf8, =
ascii
and gb2312, the results were same. The Chinese characters are supported =
when
uploading topic file, but not supported when comparing 2 different
revisions. I checked database content, there is no different when I =
switch
different charset.
I guess there might be something wrong while inserting the comparison =
result
to topic or delta table, it's not database charset problem.
I attached 2 cvs diff result, hope it helpful for you.
Have a nice trip! Hope you can come to China, I will host you with open
arms.=20
Hertz
-----Original Message-----
From: David Sitsky [mailto:sits@...
Sent: 2006=C4=EA5=D4=C231=C8=D5 7:22
To: Hertz Wang =CD=F5=BB=B3=D6=BE
Cc: codestriker-user@...
Subject: Re: [Codestriker-user] Issues in the 1.9.2 unicode version
> Thank you for your so quick improvement! I downloaded and tried it=20
> again, it works fine when I upload topic text, all the Chinese=20
> characters are rendered correctly, but it doesn't work when I compare=20
> 2 different cvs version, all the Chinese characters are still not =
right.
This is an interesting question actually - when you do a CVS diff, what
encoding is the text output as? Is it gb2312 or is it utf8? Perhaps if =
you
can email me an example diff, that would be helpful.
Cheers,
David
|