looks like somewhere along the way we lost that ability, eg Locale#public String getString(final String key, final Component component, final IModel<?> model, final Locale locale, final String style, final String defaultValue)
is deprecated and localizer now only pulls the locale from the specified component. please add an rfe to readd this functionality. -igor On Tue, Jun 8, 2010 at 3:30 AM, Marieke Vandamme <[email protected]> wrote: > > Hello, > > Is it possible to use the getString or some other kind of function to get > translation not in the language of the session, but one that is different? > We need this to send email, but this email is to our internal employees, so > needs to be in language other than the one that is requesting something. > > Now I save the locale from the session into a temp-locale variable, and > change the locale from the session to the email-language. Than I can use the > getString function. Afterwards I put the temp-locale variable back into the > session. I don't find this a perfect solution, so I have you guys have some > better alternative. > > Thanks for any help ! Marieke > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/get-resource-translation-with-specific-locale-tp2247162p2247162.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
