In data Fri, 21 Apr 2006 12:47:51 +0200, Eric Fesler ha scritto: > What happens if you force the browser to consider the page having UTF-8 or > ISO-8859-1 content.
let me explain the action i made with some detail to avoid confusion. the page contains a string of "èèèè" hard coded just for debug. the page contains a form that is filled with data coming from the db (postgres db created as an utf-8 db) 1. the page is loaded and detected as UTF-8, the debug string is ok, the form data is messed (because was inserted wrong in the db from previous tests, not for db reasons, i can exclude the db part and use debug data if necessary) 2. i change the encoding to 8859-1 of the browser, the page is reloaded and the debug string is messed up, the form data is messed up twice (the messed up data is messed up again) 4. i fill the form with all accented values i like "èèèìììùùù" 3. i submit the form, the data is processed and the form page is reloaded (the form actions returns to the same form after submit) and the data and the debug string are all OK (the page is recognized as UTF-8) so it seems again that tapestry outputs UTF-8 but inputs ISO8859... as stated in my previous email, i changed some configiration parameters without success. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
