<?xml tag, japanese and ie6

[Toscano]

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 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

[richardwilko]

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 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

[Toscano]

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




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 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

[richardwilko]

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.



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 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

[Serkan Camurcuoglu]

Do you include static japanese text within the markup? I believe the
only time when the <?xml declaration is important is when the template
is initially parsed from file by wicket using an xml parser. I don't
think dynamically included japanese text (such as text that's defined by
the model of a label object) has anything to do with the <?xml
declaration (so in my opinion converting static japanese text directly
included in the markup to <wicket:message tags should solve the problem
but it's only my guess)..



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
>>>
>>>
>>>      
>>    
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Toscano]

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...



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.



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 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

[richardwilko]

Ok, but first rule of debugging is check the simple stuff first so I did :)

In my application I have added the <?xml to my page and panel markup and have added some non-ascii chars to my markup (not sure if they are Japanese but look like it) as a test.  

There is no <xml declaration in the source of the page in the browser (wicket removes it) and the non-ascii chars show up correctly in both ie6 and firefox.

I'm not sure what you are doing differently.  Which version of wicket are you using?  We are using wicket 1.3.4, linux, sun java 5 and tomcat 6.

[Timo Rantalaiho]

On Fri, 11 Jul 2008, Toscano wrote:
> Is Red Hat and the webserver is configured to serve in UTF-8. The point is

What is the locale of the session running the JVM?
With what file.encoding is the application built, and with
what file.encoding (Java system property) is it running?

Best wishes,
Timo

--
Timo Rantalaiho          
Reaktor Innovations Oy    <URL: http://www.ri.fi/ >

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Toscano]

Hello,

Thank you all for your quick responses. It is always nice to find people like you who are willing to help.

The server is Red Hat, but I'm developing in local Windows machine... that is the mistake, the JVM is not using UTF-8 like in the Linux one. We tried to upload the files to the server without the <?xml tag, and everything worked smoothly.

Again, thank you so much for your time,
Oskar



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.



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 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

[Timo Rantalaiho]

On Tue, 15 Jul 2008, Toscano wrote:
> is the mistake, the JVM is not using UTF-8 like in the Linux one. We tried

You can set that with command line options:

  -encoding encoding
         Set the source file encoding name, such as EUC-JP and UTF-8. If
         -encoding is not specified, the platform default converter is
         used.

  http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javac.html

Best wishes,
Timo

--
Timo Rantalaiho          
Reaktor Innovations Oy    <URL: http://www.ri.fi/ >

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...