Re: [Codestriker-user] Issues in the 1.9.2 unicode version

[<wa...@ne...>]

Hi David,

In China, we use GB2312 to encode text(simplified Chinese), for =
Traditional
Chinese, I think it's BIG5, I'll check it again and tell you later.

Hertz

-----Original Message-----
From: cod...@li...
[mailto:cod...@li...] On Behalf Of =
David
Sitsky
Sent: 2006=C4=EA5=D4=C230=C8=D5 7:23
To: Hertz Wang =CD=F5=BB=B3=D6=BE
Cc: cod...@li...
Subject: Re: [Codestriker-user] Issues in the 1.9.2 unicode version

Hi Hertz,

Thanks for your email.  Yes, one of the last issues to handle is the =
actual
topic text itself, when it is not ISO-8859-1.  I am working on these =
issues
now, this also explains why adding the comment is not working, as the =
email
contains non ISO-8859-1 text when displaying the source code lines.

I'm working on these issues next.

Just out of interest, what character encoding are your source code files =
in?

Cheers,
David

Hertz Wang =CD=F5=BB=B3=D6=BE wrote:
> Hi David,
>=20
> =20
>=20
> I tried Unicode version and found it's great ^_^, I can now input=20
> Chinese characters in the topics and comments, it's very convenient=20
> for us. And I also found the following issues in the Unicode version,
>=20
> =20
>=20
> 1. the comments in the code doesn't support Chinese, they are replaced =

> by question marks. =A1=B0?=A1=B1
>=20
> =20
>=20
> 2. email notification doesn't work when adding a comment, but it works =

> fine when creating a topic.
>=20
> =20
>=20
> It always stops here. When I run it in the server, it prompt the=20
> object is null, the code is in the line 412 in=20
> codestrikerhtml\codestriker.cs file, the response is null.
>=20
> =20
>=20
> Thank you and best regards,
>=20
> =20
>=20
> Hertz
>=20
> =20
>=20
> =20
>=20