Yes, we are seeing different values. Then again we have i18n support turned of, so I guess the Locale is not set properly. We set the Local ourselves when initializing a page. I was just a bit puzzled because we set it in AggregationState... but that did not work everywhere. That's why I started digging.
-will On 08.01.2010, at 18:43, Grégory Joseph wrote: > > > On Jan 8, 2010, at 2:36 PM, Will Scheidegger wrote: > >> >> Dear Magnolians >> >> There seems to be a bit of a mess when it comes to the Locale used for i18n >> stuff. For instance the paragraph renderer looks for the local in >> MgnlContext.getAggregationState().getLocale(). However the MessageManager >> looks in MgnlContext.getInstance().getLocale(). Should one of the two be >> deprecated? > > Yes - this is in part related to MAGNOLIA-2530 [1] and linked issues. > However, as far as I know, both calls should return the same value. Are you > experiencing the opposite ? Did you stumble upon an issue with this ? > > -g > > [1] http://jira.magnolia-cms.com/browse/MAGNOLIA-2530 > > > ---------------------------------------------------------------- > 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]> ----------------------------------------------------------------
