Re: baffling i18n problem after unicode update

2007-09-20 Thread Kenneth Gonsalves
On 21-Sep-07, at 7:55 AM, Kenneth Gonsalves wrote: >> which has problems with the special characters? > > all reports use the same font. And all the other reports display that > particular problem character ok. And, just noticed that the same > problem character that refuses Good uses appears in

Re: baffling i18n problem after unicode update

2007-09-20 Thread Kenneth Gonsalves
On 20-Sep-07, at 7:09 PM, Nis Jørgensen wrote: >> it does - but so do other words that are getting translated >> successfully, and 'Good' itself is getting rendered properly in other >> parts of the site and in other reports >> > Still, those other parts/reports may be doing something slightly >

Re: baffling i18n problem after unicode update

2007-09-20 Thread Nis Jørgensen
Kenneth Gonsalves skrev: > On 20-Sep-07, at 4:42 PM, Werner F. Bruhin wrote: > > >>> other pdf reports. Not this particular one. I *know* there has to be >>> some very simple explanation for this - but cant for the life of me >>> find what it is. >>> >>> >> Does "Good" in Finish use some

Re: baffling i18n problem after unicode update

2007-09-20 Thread Kenneth Gonsalves
On 20-Sep-07, at 4:42 PM, Werner F. Bruhin wrote: >> other pdf reports. Not this particular one. I *know* there has to be >> some very simple explanation for this - but cant for the life of me >> find what it is. >> > Does "Good" in Finish use some special characters? it does - but so do other

Re: baffling i18n problem after unicode update

2007-09-20 Thread Werner F. Bruhin
Kenneth Gonsalves wrote: > there is only one .po file - Good, Poor and Average are all there. > Further, all three were working for the past year, only on update to > the unicode branch that this happened. I thought maybe Good was > marked as Fuzzy, but it is not - and anyway it translates f

Re: baffling i18n problem after unicode update

2007-09-20 Thread Kenneth Gonsalves
there is only one .po file - Good, Poor and Average are all there. Further, all three were working for the past year, only on update to the unicode branch that this happened. I thought maybe Good was marked as Fuzzy, but it is not - and anyway it translates fine in other pdf reports. Not t

Re: baffling i18n problem after unicode update

2007-09-20 Thread Bert Heymans
Kenneth You most probably checked this but in the spirit of Ockham's Razor ... maybe you just don't have the translation for 'Good' filled in in the Finnish po file for that .py file but do have it translated for another context? That could explain why it shows up in some other places but not in

baffling i18n problem after unicode update

2007-09-19 Thread Kenneth Gonsalves
hi, I have choices like this: HEALTH_CHOICES = ( ('G',_("Good")), ('A',_("Average")), ('P',_("Poor")), ) my site is english and finnish. These choices are used in several models. When finnish is on, they get translated in the web interface. I also generate reports in repo