What is the encoding of your outputted pages (in firefox right click, view page info)? This will depend on what platform you are running on (os and webserver). if it is not utf-8 then you will need to change your setup so that it is. then it *should* work. its also possible that the page encoding is being forced to something else by the browser.
you could also try adding this line to your html head <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> btw, I dont think this isnt really a wicket problem, more a server setup problem. Toscano wrote: > > Hello, > > We are developing a multilanguage application, so our standard is utf-8. > We are making intensive use of Wicket's localization features, but > recently we found a problem and we can't find a good solution for it. > > Basically is this: for not getting corrupted Japanese, we have to include > the following line in the html file: > <?xml version="1.0" encoding="UTF-8"?> > > But if we include that file, then all the layout in > http://lists.xml.org/archives/xml-dev/200109/msg00182.html IE6 is a mess . > We tried to change the <?XML declaration with metatags inside the head of > the file, but it doesn't work, the Japanese only shows correctly if the > tag is there. > > So if we leave the tag, we get Japanese but the layout is a mess in IE6. > If we removed it, we get good layout but corrupted Japanese. > > Is there any tag or something to configure in Wicket for making the > Japanese show correctly without the <?XML tag? > > As always, thank you for your time, > Oskar > > -- View this message in context: http://www.nabble.com/%3C-xml-tag%2C-japanese-and-ie6-tp18400121p18400483.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
