Well, I guess we kind of expect the page to be utf-8 encoded, as that is most common case. Is there any special reason why you can't send your page as utf-8? That way the javascript would be encoded correctly (it would match the page).
-Matej On 8/2/07, Stefan Simik <[EMAIL PROTECTED]> wrote: > > Hi, > I search old discussion, but I cannot find answer. > > We use a DatePicker component from wicket.extensions. > This component has many *.js files for localization (we use Slovak locale -> > calendar-sk-utf8.js ) > Problem is, that these files are written using UTF-8 encoding. > > Header contribution: > <script type="text/javascript" > src="/udzs/run/resources/wicket.extensions.markup.html.datepicker.DatePickerSettings/lang/calendar-sk-utf8.js"></script> > does not reflect this encoding, and diacritics in DatePicker is broken. > When I manually change character encoding to UTF-8 in browser, it's good. > > It's possible to solve this problem in Wicket or I have to write some > servlet filter, > which adds HTTP header: "Content-Type: text/javascript; charset=UTF-8" > for *.js requests ? or any alternative ideas ? > > Thanks > > > -- > View this message in context: > http://www.nabble.com/DatePicker-localization-%28*.js%29-files-are-in-UTF-8---problem-with-diacritics-tf4205759.html#a11963261 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
