> > In my opinion, there should be settings.setInputMarkupEncoding(String). The > initial value will be null and Wicket will work as it works today. In the > case you want to feed in markup that doesn't contain XML declaration, this > will be used as override of JVM default encoding.
sounds reasonable to me. > BTW, if you want to produce HTML output (not XHTML), how do you set the > input markup encoding? You cannot use the XML declaration. > I'm not sure this is true. Do you have any reference which says that HTML must not contain <?xml?>? > Actually things are little bit more complicated, because the input markup > encoding also affects response header content type. This is in my opinion > another weak area in Wicket, because the header content type and meta > Content-Type should be in concert. Wicket wiki says, that the meta > Content-Type is not controlled by Wicket... > sorry, but I disagree. There are plenty of discussions on the internet on which one to prefer and why and I think there is a link in the wiki to what the standards says about it. 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 Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
