Re: [T5] Application Message Catalog not read

Just a follow up for those who don't read the jira thread. The problem is in BOM (Byte Order Mark). If a property file is made with BOM included, then the localization fails. A cite from wikipedia (http://en.wikipedia.org/wiki/Byte-order_mark): "While UTF-8 do

Re: [T5] Application Message Catalog not read

I just found out why the translation does not work. If all property files are in ANSI (ISO-8859-1) encoding then everything works as advertised. If default file, for example app.properties is in ANSI and the app_sl_SI.properties is in utf8, then the localization breaks. If all property files are in

Re: [T5] Application Message Catalog not read

Hi, I have a sample application supporting multiple languages which doesn't exhibit this behavior: http://code.google.com/p/tapestry5-appfuse/ You may have something else going on. /Serge bbcooper wrote: > > I found a bug. First entry in properties file is never used. I tried > reordering en

Re: [T5] Application Message Catalog not read

I found a bug. First entry in properties file is never used. I tried reordering entries and the first entry never gets "translated". I used T 5.0.15, 5.0.16 and 5.0.17. This applies not only for application wide catalog but also for page catalogs. I am filing a bug report at https://issues.apache.

Re: [T5] Application Message Catalog not read

Nothing there has changed; it's still based on the filter name. On Thu, Dec 4, 2008 at 6:02 AM, Stephane Decleire <[EMAIL PROTECTED]> wrote: > Since 5.0.17, my localized messages are not read anymore from the > application message catalog. > My application message catalog is named backoffice.prope