Please open a ticket and put this info in so it won't be lost and can be handled by the developers when they have free time/ressources. Rgds Günter
-----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von hnak Gesendet: Mittwoch, 04. Februar 2009 06:41 An: Satchmo users Betreff: call locale.setlocale() using tuple instead of locale.normalize() I recently downloaded Satchmo 0.9 and tested on ubuntu 8.10 (Japanese). I wanted to translate messages into Japanese, but documentation is not sync with current code. I am waiting for the up=todate documentation. During the process, I found a problem in l10n/utils.py/get_locale_conv (). The code calls locale.setlocale() with a string parameter returned by locale.normalize(loc), which returns inconsistent value. For example, locale.normalize('ja') returns 'ja-JP.EUC-JP' even on UTF-8 system (ubuntu 8.10). As a result, the system crashes. As of Python 2.0, setlocale() allows passing a tuple instead of a string. So I modified the code to pass a tuple (loc,'utf-8'), and it started working as expected. Will you developers consider using the tuple format in future ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
