> discussions about it. We want to make Wicket 1.1 rock! For me, even Wicket 1.0 rocks :-)
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. BTW, if you want to produce HTML output (not XHTML), how do you set the input markup encoding? You cannot use the XML declaration. Jan 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... "Eelco Hillenius" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Could you tell us what misses? Any idea's on how we could improve things? > > Ofcourse, everybody that reads this, if you have any idea's about > improving Wicket, pls feel free to file requests for enhancement > (https://sourceforge.net/tracker/?group_id=119783&atid=684978) and start > discussions about it. We want to make Wicket 1.1 rock! ------------------------------------------------------- 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_id=7477&alloc_id=16492&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
