Malcolm Tredinnick wrote: > I completely agree this is painful and normally I would punt. But my > crystal ball tells me that you will then get bug reports from Mr > Sagalaev, who is generally both very diligent in his debugging and likes > to use some language with a funny alphabet. If whatever you come up with > works naturally in places like Ivan's setup and maybe somebody who lives > in Hong Kong or Japan or some other East Asian locale, you could > consider this "solved" to some extent.
I'm afraid I'm not very good tester with this exact problem. Python on my Ubuntu happily says 'UTF-8' when asked 'locale.getpreferredencoding()'. But indeed I can always try these things with my compatriots using Windows or configuring their linuxes with old single-byte 'KOI8-R'. In fact I was under impression that a string returned from this function can be safely used for decoding. For example on Russian Windows it returns 'cp1251' which works perfectly well while not being a standard ISO name which is 'windows-1251' and works well also. So may be we can just rely on Python's smart little brain and do something like this: - try decoding from locale.getpreferredencoding() - failing that try something safe like iso-8859-1 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers -~----------~----~----~----~------~----~------~--~---
