We've noticed the same behavior and have a patch for that. Thanks for
the confirmation.

-Elias

Alex D wrote:
> Ok I made some tests...
> I changed each occurence of " = " with "=" in
> ApplicationResources_es.properties. Then I restarted tomcat.
> $text.get("macro.weblog.postedby")  was still in english.
> 
> Then I copied ApplicationResources.properties to
> ApplicationResources_en.properties and copied
> ApplicationResources_es.properties to ApplicationResources.properties. Then
> I restarted Apache
> $text.get("macro.weblog.postedby")  was still in english !!!!!!!!
> 
> Finally I  dropped ApplicationResources_en.properties and copied
> ApplicationResources_es.properties to ApplicationResources.properties. Then
> I restarted Apache
> $text.get("macro.weblog.postedby")  was finally in spanish !!!!!!!! That
> makes me think the ApplicationResources_es.properties is not corrupted
> (just
> some texts are missing, for instance macro.weblog.readMore or
> macro.weblog.readMoreLink; in that case it just displays the "macro" name
> instead of the text).
> 
> So, my opinion is that, in any case, Roller3 doesn't take the locale id
> sent
> to the URL into consideration for $text.get use, it takes the values set in
> ApplicationResources.properties, and only if there is no
> ApplicationResources_en.properties is defined.
> 
> 
> Alex
> 
> On 2/22/07, Oscar Puga <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>> > Does it mean that the bundle ApplicationResources_es.properties, coming
>> > with
>> > the default install of Roller 3.0, is corrupted?
>>
>> Just checking the ApplicationResources_es.properties files of Roller 3.0,
>> I
>> founded that '=' symbol between the key and value parts is surronded by a
>> whitespace in both sides. Perhaps this causes Roller to never match a
>> key.
>>
>> This also happens with the "nl" and "ru" locales.
>>
>> -- 
>> View this message in context:
>> http://www.nabble.com/Multi-language-weblogs-with-Roller-tf3238306s12275.html#a9096565
>>
>> Sent from the Roller - Dev mailing list archive at Nabble.com.
>>
>>
> 

Reply via email to