I think Martin's idea is that in the absence of a localized properties file localization via a call to google translate would be attempted.
I think there are likely to be more problems the benefits with this design. To wit, http://tinyurl.com/y8nvx2x. Perhaps a shell script to localize your base properties files followed by manual intervention, correction. Ed. On Thu, Jan 28, 2010 at 11:28 AM, Victor Dolirio Ferreira Barbosa <victor...@gmail.com> wrote: > There the default properties file for this purpose. Just make a properties > file without locale info in this name, like this example: > > + > |- Application_en_US.properties > |- Application_pt_BR.properties > |- Application.properties > > The last file is used if no other is found for the current locale. > > On Thu, Jan 28, 2010 at 2:15 PM, Martin Makundi < > martin.maku...@koodaripalvelut.com> wrote: > >> Hi! >> >> I wonder, has anybody implemented a wicket stringresource localizer >> that if localized property is not found for the selected language, it >> would attempt to translate it using the default language? >> >> ** >> Martin >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > -- > []s, > Victor Dolirio > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
