Hello, the *pub* example (http://wicketstuff.org/wicket13/pub/) shows how a localized string can be retrieved from a properties file and then dinamically inserted in a page. Still, with the exception of that string, the remaining markup is kept static, which results in separated, localized HTML files for each locale.
So is this the current best practice regarding localization in Wicket? Or would it be better to replace all static UI labels with dynamic Wicket labels such that their localized values are defined in the corresponding properties files? I'm asking because the 2nd option, even though it allows the production of a single HTML file for all locales, obviously has a higher development cost... Would the benefit be high enough to justify that choice? Thanks so much, Cristina -- View this message in context: http://www.nabble.com/Best-approach-to-localization-tf4572706.html#a13052285 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
