Game data are created by various legacy programs. Most of them are
saved in OS's default encoding method. No one is going to take the
effort to convert them to utf8.
On Sep 12, 8:59 pm, Equand [EMAIL PROTECTED] wrote:
why not utf-8?
On Sep 12, 4:46 am, Guoliang Cao [EMAIL PROTECTED] wrote
using that
charset? How?
Thank you.
Guoliang
On Jul 5, 11:36 pm, Rhapidophyllum [EMAIL PROTECTED] wrote:
I think you don't have to change the entire server setting, but header
information in your individual server responses should be set to gb.
On Jul 4, 2007, at 11:29 AM, Guoliang Cao wrote
Hi,
I'm using jQuery 1.1.3 in my AJAX-based game viewer. I download game
data through ajax calls. Game data are mostly encoded in gb2312. I
currently have a problem: if I don't change the server side setting to
send data in gb2312 format, I got unreadable characters on client
side. Is it
Hi,
I'm using jQuery 1.1.3 in my AJAX-based game viewer. I download game
data through ajax calls. Game data are mostly encoded in gb2312. I
currently have a problem: if I don't change the server side setting to
send data in gb2312 format, I got unreadable characters on client
side. Is it
Hi,
I'm using jQuery 1.1.3 in my AJAX-based game viewer. I download game
data through ajax calls. Game data are mostly encoded in gb2312. I
currently have a problem: if I don't change the server side setting to
send data in gb2312 format, I got unreadable characters on client
side. Is it
Hi,
I'm using jQuery 1.1.3 in my AJAX-based game viewer. I download game
data through ajax calls. Game data are mostly encoded in gb2312. I
currently have a problem: if I don't change the server side setting to
send data in gb2312 format, I got unreadable characters on client
side. Is it
6 matches
Mail list logo
