anyway, I just create a quickstart with encoding "cp866", a Russian encoding. I can't read Runssian, either. but it should be enough to demo the problem. please see attachement.
In quickstart I do :
(1) set QuickStartApplication:
getMarkupSettings().setDefaultMarkupEncoding("cp866");
getRequestCycleSettings().setResponseRequestEncoding("cp866");
(2) template use cp866 ecoding both in <?xml> and <meta> tag.
On 9/26/06, Johan Compagner <
[EMAIL PROTECTED]> wrote:
If you set the request encoding to Big5.
What does the browser say when you ask for where it is in?
johanOn 9/26/06, Ingram Chen < [EMAIL PROTECTED]> wrote:Thanks the advice!
Some chars just can't translated into Big5. Big5 is popular Chinese encoding before unicode in Taiwan... etc and it lack some rare chars defined in unicode.
make conversion at DAO layer would be good or even migrate db to unicode is better.... but it require a lot effort. My problem is just Wicket Ajax not work correctly in different encoding. If it couldn't be solved, we are forced to give up wicket ajax and fallback to plain request...sigh....
Is there anything I could check or trace... ?
--
Ingram Chen
Java [EMAIL PROTECTED]
Institue of BioMedical Sciences Academia Sinica Taiwan
blog: http://www.javaworld.com.tw/roller/page/ingramchen
encodingProblem.IAmZip
Description: Binary data
------------------------------------------------------------------------- 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
