Re: T4.1.3: "Upgrade" from 4.1.2 problem with messages

On 10/3/07, andyhot <[EMAIL PROTECTED]> wrote: > > Patrick, you've already commented on > https://issues.apache.org/jira/browse/TAPESTRY-234 > and Jesse has reopened it > > Malin, i'm wondering, what's the VM's default locale? Uhmm... how do I know? /Malin Patrick Klein wrote: > > Hello! > > >

Re: T4.1.3: "Upgrade" from 4.1.2 problem with messages

Hello! Thnx for the heads up, I just saw it. For the fallback issue in the translation I just added the bug https://issues.apache.org/jira/browse/TAPESTRY-1803 Regards, Patrick Patrick, you've already commented on https://issues.apache.org/jira/browse/TAPESTRY-234 and Jesse has reopened

Re: T4.1.3: "Upgrade" from 4.1.2 problem with messages

Patrick, you've already commented on https://issues.apache.org/jira/browse/TAPESTRY-234 and Jesse has reopened it Malin, i'm wondering, what's the VM's default locale? Patrick Klein wrote: Hello! Thanks Patrick - feels good I might have some sanity left then :) So - is this a bug?

Re: T4.1.3: "Upgrade" from 4.1.2 problem with messages

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

Re: T4.1.3: "Upgrade" from 4.1.2 problem with messages

Thanks Patrick - feels good I might have some sanity left then :) So - is this a bug? I'm not sure what you mean with the table columns handling and the '_'/'.' - what's that? \\Malin On 10/3/07, Patrick Klein <[EMAIL PROTECTED]> wrote: > > Hello! > > I can confirm this behavior. > It looks lik

Re: T4.1.3: "Upgrade" from 4.1.2 problem with messages

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 con

T4.1.3: "Upgrade" from 4.1.2 problem with messages

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. B