Re: [Wicket-user] The problem about encoding and event in ajax

[Ingram Chen]

Well, the database is only allowed to store chars encoded as Big5. If user input charactors, which defined in Unicode but outside of Big5 cover, the database only store garbage code like ???.  By setting page encoding to Big5, the browser will escape non-Big5 chars to "#&XXXX;" automatically. Althought database still store these escape chars, these chars can be re-rendered correctly on the web page.

On 9/25/06, Matej Knopp <[EMAIL PROTECTED]> wrote:

That's strange. I've tried wicket examples and the only one that didn't
work was the editable label one, which used get to send the data to
server. All other examples worked for me.

I don't understand why you can't use utf-8 encoding. What has this to do
with your database encoding? In java all strings are internally unicode.
  How does encoding of your html pages and urls affects your database?

-Matej

--
Ingram Chen
Java [EMAIL PROTECTED]
Institue of BioMedical Sciences Academia Sinica Taiwan
blog: http://www.javaworld.com.tw/roller/page/ingramchen

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user