i18n and cms:out / ${...}

View: New views
4 Messages — Rating Filter:   Alert me  

i18n and cms:out / ${...}

by Igor Klimer :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


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?

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------


Parent Message unknown Re: i18n and cms:out / ${...}

by Philipp Bärfuss :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


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.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------


Re: i18n and cms:out / ${...}

by Igor Klimer :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Thanks for replying.
I'm using STK 1.1 with Magnolia 4.1.
Under config.server.i18n.content.class I have
info.magnolia.cms.i18n.DefaultI18nContentSupport (the default value).
Of course enabled is set to true :) i18n-wise I haven't changed
anything other than that.

Could you tell me more about the i18n support implementation in STK
1.1? (or point to documentation about it or even the source code :))
I created a bug report for this:
http://jira.magnolia-cms.com/browse/MGNLSTK-404 (nice issue number ;))

Best regards,
Igor Klimer

On Mon, Jun 29, 2009 at 10:54 AM, Philipp
Bärfuss<philipp.baerfuss@...> wrote:

>
> 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.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------
>
>



--
Pozdrawiam,
Igor Klimer

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------


Re: i18n and cms:out / ${...}

by Philipp Bärfuss :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


>
> I'm using STK 1.1 with Magnolia 4.1.
> Under config.server.i18n.content.class I have
> info.magnolia.cms.i18n.DefaultI18nContentSupport (the default value).
> Of course enabled is set to true :) i18n-wise I haven't changed
> anything other than that.
I was not aware of that but it seams to be part of ETK which makes  
sense as it works now it is only relevant in a multi site environment.

> Could you tell me more about the i18n support implementation in STK
> 1.1? (or point to documentation about it or even the source code :))
For time being you can simply define the language of your site (in  
case of having more than one of them)
> I created a bug report for this:
> http://jira.magnolia-cms.com/browse/MGNLSTK-404 (nice issue number ;))
;-)

Thanks, hope we can make that part of Magnolia 4.1.1

>
>
> Best regards,
> Igor Klimer
>
> On Mon, Jun 29, 2009 at 10:54 AM, Philipp
> Bärfuss<philipp.baerfuss@...> wrote:
>>
>> 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.html
>> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
>> ----------------------------------------------------------------
>>
>>
>
>
>
> --
> Pozdrawiam,
> Igor Klimer
>
> ----------------------------------------------------------------
> 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.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------