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 > different. I assume that the translations of "Average" and "Poor" are > ascii. Try changing the translation of "Good" to something without > special characters, and see if that helps. If it does, you at least > know > that this is a charset/encoding issue - although this doesn't solve > it. Good has special characters, Average and Poor do not. Changing Good to average displays it. But then I also have 'Male' in the same report which has a special character(a different one) and displays it. (all these problems are only in reportlab pdfs) > > Next, I would look at finding the difference between this report > and the > ones that work. Could it be that this report uses a different font, > 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 another part of the *same* report that doesnt display Good. Ok, so it is just that one line of code that is at fault - I will keep staring at it until I find whats bad about 'Good' - thanks for helping narrow it down. -- regards kg http://lawgon.livejournal.com http://nrcfosshelpline.in/web/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
