Thanks for the information. However, it appears that saving the files in
the correct encoding, is not enough. One must also start Java with the
correct encoding. I am using Wicket with JBoss (ie Tomcat) under Win
XP/Java 5 for development and Linux/Java 5 for testing (and, who knows,
maybe
We should look at that loading problem then. Because we should read it right.About that CSS in IE6 this is quirks mode or not. Please do a search for thatif you don't put that declaration in IE6 , IE doesn't really comply to the CSS rules
(just look at the same css page in FF and IE without the
Hi Johan,
Very good advice indeed ! It appears (from
http://hsivonen.iki.fi/doctype/) that :
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
switches IE6 in almost standard mode but
?xml version=1.0 encoding=UTF-8?
Usually the root cause is that ?xml encoding=..? does not match
the encoding which was used to store the markup file.
application.getMarkupSettings().setStripXmlDeclarationFromOutput(false)
removes the XML decl from the output to the browser.
Juergen
On 8/1/06, Pierre-Yves Saumont [EMAIL
Usually the root cause is that ?xml encoding=..? does not match
the encoding which was used to store the markup file.
That was not the case here. Charset was OK with xml declaration but
layout was not. Layout was OK without declaration, but charset was not.
Hi,
I am new in using Wicket, but I had this problem with all the Frameworks
I used before.
In Wicket, it was absolutely no problem since I just added :
meta http-equiv=Content-Type content=text/html; charset=iso-8859-1
in the HTML template to make it work. It seems Wicket managed this
I would use UTF8 throughout everytingthe html templates, the database and the output to the browser.johanOn 7/29/06, Pierre-Yves Saumont
[EMAIL PROTECTED] wrote:Hi,I am new in using Wicket, but I had this problem with all the Frameworks
I used before.In Wicket, it was absolutely no problem since
