Thanks, Igor, it worked.
Regards,
Andrew Schetinin
On Fri, Oct 28, 2011 at 10:45 PM, Igor Vaynberg wrote:
> you are right. i was looking in 1.5 where we have exposed the locale.
>
> for the time being you can simply do this:
> Locale old=session.getlocale();
> session.setlocale(foo);
> localize
you are right. i was looking in 1.5 where we have exposed the locale.
for the time being you can simply do this:
Locale old=session.getlocale();
session.setlocale(foo);
localizer.get(..);
session.setlocale(old);
-igor
On Fri, Oct 28, 2011 at 1:22 PM, Andrew Schetinin wrote:
> Hi Igor,
>
> But
Hi Igor,
But as I said, this method is deprecated and ignores Locale parameter:
@Deprecated
public String getString(final String key, final Component component,
final IModel model,
final Locale locale, final String style, final String defaultValue)
throws MissingResourceEx
Localizer#getString(final String key, final Component component, final
IModel model, final Locale locale, final String style, final String
defaultValue)
-igor
On Fri, Oct 28, 2011 at 10:54 AM, Andrew Schetinin wrote:
> Hi,
>
> I have a question about Wicket localization I could not find an answe
Hi,
I have a question about Wicket localization I could not find an answer for.
I have a component where I'd like to get a translated message for a given
key.
The actual string is sitting somewhere in a grand-parent panel, and I have
no any access to it.
I'd like to get translations for that key
