Hi Wangwei,
the encoding that you setup there is the encoding of the template
source files on your filesystem, not of the response. Use this
element method to set the encoding with the content type:
http://rifers.org/docs/api/com/uwyn/rife/engine/
ElementSupport.html#setContentType(java.lang.String)
You can also set that up in the element declaration with the
'contenttype' attribute.
Note that RIFE is setup to use UTF-8 correctly by default, all over
the place. You can change the response n-encoding, but you'll be
responsible for making sure that the request data is sent in an
encoding that can be read. This can get very tricky and you're never
sure that the visitor used a particular encoding. UTF-8 proved to
work the best in general. So, if you set the response encoding, also
set this in the head of your html file:
<meta content="text/html; charset="gb2312" http-equiv="content-type" />
Good luck, tailoring with encodings can be very frustrating.
Best regards,
Geert
On May 4, 2006, at 8:51 AM, wei wang wrote:
Hi,
To make my web more friendly to people in China, I would like to
set the default encoding of the template to "gb2312". So I set
<param name="TEMPLATE_DEFAULT_ENCODING">gb2312</param> in
config.xml. But when I view the page, it is still encoded in
UTF-8. Anything I missed ?
Thanks in advance :)
Best Regards
wangwei
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
--
Geert Bevin Uwyn bvba GTalk: [EMAIL PROTECTED]
"Use what you need" Avenue de Scailmont 34 Skype: gbevin
http://www.uwyn.com 7170 Manage, Belgium AIM: geertbevin
gbevin at uwyn dot com Tel: +32 64 84 80 03 Mobile: +32 477 302 599
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
