On 31 jul, 12:18, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > There may well be a problem, but from the current information there is a > 0% chance of anybody being able to guess the solution. There are just > too many things it could be from bad strings in your code to bad > handling on some uncommon code path in Django to some inadvertent > encoding mismatch somewhere else. So if you can come up with a small > reproducible test case, that will help greatly. >
I understand it and please forgive my pour words :-) I'll do what you said and I'll try to fix it by my self today. If not, I'll write to this list for any comments. Regards. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
