Hello!
> Thanks Patrick - feels good I might have some sanity left then :)
>
> So - is this a bug?
>
Good question, looks like one to me, but I'm not 100% sure...
At least it is a change in the localization handling which I could not
locate in the changelog
> I'm not sure what you mean with the table columns handling and the '_'/'.' -
> what's that?
>
The column heads of tables seem to be transformed from "SOME_VALUE" to
"SOME.VALUE" before piping them through the localization.
Regards,
Patrick
> \\Malin
>
> On 10/3/07, Patrick Klein <[EMAIL PROTECTED]> wrote:
>
>> Hello!
>>
>> I can confirm this behavior.
>> It looks like the fallback to the default property file is not done in
>> case there is no match for the given key in the current locale's
>> property file...
>> Additionally there is a change in the table colums handling which breaks
>> your localization if the keyword contains one or more "_" (which seems
>> to be replaced with a ".") :|
>>
>> Regards,
>> Patrick
>>
>>> I have a localized app with all literals in properties file.
>>> I recently downloaded the latest 4.1.3, earlier I used 4.1.2.
>>>
>>> Some messages which are not locale dependent (like the app version and
>>> webmaster email for example) I have stored in the
>>> MyApp.properties file and it worked fine with 4.1.2.
>>> But with 4.1.3 it seems I need to put these messages in each locale
>>>
>> file,
>>
>>> like
>>> MyApp_en.properties, MyApp_sv.properties etcetera.
>>>
>>> Is this by design? Or have I missed something?
>>> Anyone else experienced this?
>>>
>>> Cheers, Malin
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
