Hi,

Is Red Hat and the webserver is configured to serve in UTF-8. The point is
that IE6 has problems to proccess HTML with the <?XML, so I need Wicket to
not output that tag without affecting to the encoding of the content which
has to be utf-8. Trust me, the layout results really hurt in IE6 with that
tag.

I have more experience working with Japanese websites, and I already checked
all the encodings: file, webserver... 



richardwilko wrote:
> 
> Ok, but what os are you using?
> 
> on windows the default character encoding is not utf-8 and java uses the
> system default character encoding.  Also check that the html files are
> saved in utf-8
> 
> tbh i think that meta tag only works for really old browsers, but doesn't
> hurt anything if it is there.
> 
> 
> 
> Toscano wrote:
>> 
>> Hello,
>> 
>> Thank you for your answer.
>> 
>> In every case, the encoding in the browser is utf-8. It doesn't work with
>> the metatag you send to me, it is already added in all the pages. It only
>> works if I add the <?xml tag.
>> 
>> Even more, I have one page with three different panels. Two of them have
>> the <?xml line in the markup and the Japanese shows correctly, the third
>> one has not and the japanese is corrupted. So in the same page we have
>> correct and incorrect japanese, because the <?xml is not there.
>> 
>> Has to be something related with Wicket... 
>> 
>> Thank you again,
>> Oskar
>> 
>> 
>> 
>> 
>> richardwilko wrote:
>>> 
>>> 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-tp18400121p18401237.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]

Reply via email to