Right now, if I have a localized property file (e.g. Welcome_de.properties), it seems I must have all resource keys defined in it.
I would prefer to have the localizer be smart enough to fallback to the default properties file (e.g. Welcome.properties) if a property is not present in the localized property file. This would make it possible to add properties to the system and not have to translate them all immediately - let it fall back to the default language until someone gets around to translating it. Does Wicket have this easily configurable, or do I need to roll my own resource resolvers or other classes for this purpose? -- View this message in context: http://www.nabble.com/localized-resource-property-file---fallback-to-default--tf3493032.html#a9755878 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
