Code-It » UnicodeDecodeError http://lois.di-qual.net/blog Tue, 30 Oct 2012 19:19:29 +0000 fr-FR hourly 1 http://wordpress.org/?v=3.5.1 Django – UnicodeDecodeError using i18n http://lois.di-qual.net/blog/django-unicodedecodeerror-using-i18n/ http://lois.di-qual.net/blog/django-unicodedecodeerror-using-i18n/#comments Mon, 30 Jul 2012 21:32:11 +0000 Loïs Di Qual http://lois.di-qual.net/blog/?p=83 ugettext With gettext: 12345from django.utils.translation import gettext as _ define my_view(request):     [...]]]> If you’re using i18n in your django website, you may encounter this issue. It took me two hours to find where the problem came from: you have to use ugettext instead of gettext if your translated strings contains non-ascii characters.

gettext => ugettext

With gettext:

1
2
3
4
5
from django.utils.translation import gettext as _

define my_view(request):
    print _("Here comes nothing") // Prints "Here comes nothing"
    print _("Here comes something spécial") // Raises a UnicodeDecodeError because "é" is not unicode

With ugettext:

1
2
3
4
5
from django.utils.translation import ugettext as _

define my_view(request):
    print _("Here comes nothing") // Prints "Here comes nothing"
    print _("Here comes something spécial") // Prints "Here comes something spécial"

ugettext or ugettext_lazy ?

Two simple rules:

  • Use ugettext_lazy in global scopes (model fields, django settings, everything not wrapped by a function or method, …)
  • Use ugettext everywhere else (in views, methods, functions, …)

That’s it !

]]> http://lois.di-qual.net/blog/django-unicodedecodeerror-using-i18n/feed/ 0