> on unix you can. But I prefer your suggesting of providing > setMarkupFileDefaultEncoding (or however we name it).
On Windows you cannot do that. Maybe -Dfile.encoding=UTF-8 helps? > > If you look at samples, the helloworld is not valid HTML. (Maybe it > > validates with Transient versions of the standard, I didn't tried). > > The <span> cannot be child of <head>, <h3> cannot be inside <a> and > > <font> doesn't exist at all (use CSS). > > > > ok, that is the example where the example markup is not HTML > compliant. But it does not mean that Wicket is not able to > create/handle (X)HTML compliant markup. You are right that > wicket does not test for HTML or XHTML compliance. Does any > of the other frameworks do it? A 1.1 DTD or schema will > eventually solve that problem. Until than, most html editors > (e.g. dreamweaver) do allow to ignore "unknown" namespaces > like "wicket". Wicket can produce (X)HTML compliant output, this is one of the reasons why we are interested. There are some troubles with IE, but, fortunately now we know the solution. I don't expect that Wicket will validate the pages before output :-). I would just expect, that the samples will be compliant not to further spread the bad HTML habits, but it's just my nitpicking. Thanks for your kind replies, Jan ------------------------------------------------------- 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 Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
