Matteo,
The AggregationState holds the current Locale, which is set by your
implementation of I18nContentSupport, which in turn is used by the
I18nContentSupportFilter.
This def. works for Freemarker templates (${i18n['mykey']}, see STK
for examples), and I18nContentSupportFilter also sets the Locale for
JSTL's Config object.
HTH,
-g
On Aug 17, 2009, at 5:37 PM, Matteo Pelucco wrote:
Hi all,
we are now ready to implement some I18n with Magnolia 3.6.3.
I have a little question.
I succesfully managed to display multilanguage content, but I would
like also to display multilanguage labels around the content, I mean
for instance navigation labels (NEXT, PREVIOUS...).
I know that I can use JSTL support for I18N, but I need to know the
current locale for each request.
No problem if a user click on "change to English / change to
Italian" action, because I can wrap this action on a Template
Renderer and in that tplR set the current selected locale or/and
redirect to right URI.
But what if a user cames from the outside pointing for instance to a
page like:
- http://<my:host>/<magnoliaCtx>/en/home
NB: please note the "en" prefix...
the content would be rendered in English, but what about the labels?
I need to take care also of this case from my Template Renderer or
Magnolia is capable to change automatically the current locale?
Thanks for any answers..
Matteo
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
