Hm, what you describe would be a bug. the basic syntax should
definitely support i18n content.
Note: STK 1.1 adds its own i18n support implementation, do you use
that or plain magnolia?
Thanks for clarifying. In any case you can create a bug report.
Philipp
On 27.06.2009, at 17:19, Igor Klimer wrote:
>
>
> Hi all,
> I've run in into the following problem:
> First off - I'm using Freemarker for my templates (very cool stuff,
> great
> job on introducing this :))
> Now, using the guide on the wiki
> (
http://wiki.magnolia-cms.com/display/WIKI/Introduction+to+I18nContentSupport
> )
> I managed to i18n-ify my pages, however it only works when I output
> the
> values in the template using the cms:out tag - it doesn't work with
> the very
> nice Freemarker syntax ${content.something}.
> Is this just the current limitation of the Freemarker support for
> Magnolia
> or am I missing something? :)
>
> PS: I don't mind using the cms:out tag, it's just that with
> Freemarker I can
> some cool stuff like ${content.date?string("MMM")} - I can simulate
> it with
> [#if] etc, but it's less readable - maybe there's a way to use
> cms:out and
> do some Freemarker stuff?
> --
> View this message in context:
http://www.nabble.com/i18n-and-cms%3Aout---%24%7B...%7D-tp24225887p24225887.html> Sent from the Magnolia - User mailing list archive at Nabble.com.
>
>
> ----------------------------------------------------------------
> For list details see
>
http://www.magnolia-cms.com/home/community/mailing-lists.html> To unsubscribe, E-mail to: <
user-list-unsubscribe@...>
> ----------------------------------------------------------------
Best regards,
Philipp Bärfuss
Magnolia International Ltd.
---------------------------------------
Meet us at the Magnolia Conference
http://www.magnolia-cms.com/conference---------------------------------------
Magnolia® - Simple Open Source Content Management
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.htmlTo unsubscribe, E-mail to: <
user-list-unsubscribe@...>
----------------------------------------------------------------