> > The Streams.readString uses java.io.InputStreamReader with default or > supplied encoding. It is also clear that settings.setDefaultLocale() will > not be in action. > > I think that there should be more control over the input markup encoding. I > cannot change the JVM default encoding (or can I?)
yes you can, though it is operating system specific. Unfortunately I can only tell you how to do it the unix / linux way. > and if I want to produce > XHTML that will switch IE into standards compliant mode (see > http://www.wellstyled.com/html-doctype-and-browser-mode.html), I have to > ommit XML declaration. > > Fortunately I found a solution (at least for Wicket 1.0). I will override > the configureResponse() method. The body will be the same as the > Page.configureResponse(), I will just comment out the > response.write(markupStream.getXmlDeclaration()); > works for current head as well. > Side note: Wicket is bright new and nice package, I am surpriced that it > doesn't support HTML 4.0 / XHTML Strict mode standards and that nobody > complains about it. The samples for Wicket are not valid. I'm not exactly sure what you mean. Why is it not HTML 4.0 or XHTML compliant? in case you're talking about the tags and attributes in wicket namespace, you can remove them for production (settings.setStripWicketTags). Please correct if I'm wrong, but you require to remove <?xml?> because of IE, not because it is not (X)HTML compliant? Juergen ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
