Originally posted by Lasse Koskela:
As a sort of continuation of this earlier question, I'd be curious to hear what kind of an approach should one take with Wicket to support layout-level localization, e.g. when bits of the page need to be positioned to a different place for certain locales or when text content needs to flow right-to-left for Arabic users?
So the easiest and often preferable way to go for localization is to use constructs like <wicket:message>. However, is that is not sufficient, you can take advantage of the way Wicket loads resources. For instance if you'd have MyPage.html and MyPage_nl.html and the user's locale is nl_NL, the MyPage_nl.html would be loaded.
See for instance the org.apache.wicket.examples.pub and org.apache.wicket.examples.pub2 examples for an illustration on this, and see org.apache.wicket.examples.forminput where this is used for just images (the flag icon).