Thank you in advance Matej, you're right - we had incorrect Page encoding.
After a few hours of debugging and testing I found, that the one page (which used DatePicker) had incorrect encoding - ISO-8859-2 and not UTF-8. All other pages were good. I didn't found the reason yet ( why the only one page used another encoding), but my temporary solution was to override method configureResponse(Response res) and set HTTP header with proper UTF-8 encoding. We are using Slovak locale -> so CharSetMap class in Wicket returns default "ISO-8859-2" encoding. It's OK. But our page has XML declaration with encoding="utf-8", what should be prior to settings in CharSetMap, but it does not function in our case. -- View this message in context: http://www.nabble.com/DatePicker-localization-%28*.js%29-files-are-in-UTF-8---problem-with-diacritics-tf4205759.html#a11979973 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
