On 19 Sep 2009, at 15:59 , Joshua Russo wrote: > I was working through some regression tests and saw a scenario I > thought > wasn't allowed/recommended. I was under the impression that if you > specified > UTF-8 encoding at the top of the file you where not suppose to use u > decorated unicode static string. So instead of u'prédio' I use > 'prédio' in > files where I specify the encoding in the file. > Now in regressiontests/admin_views/models.py I see u'¿Chapter?'. > Does it not > matter if I use the u decorator on static strings with the encoding > specified? I was initially told that it could create problems.
I don't see why it would create problems. From my tests, in an utf-8 encoded file: * a bytestring 'foo' will generate an utf-8 encoded bytestring, so 'prédio' will yield 'pr\xc3\xa9dio' (in utf-8, 'é' is encoded as 0xC3A9) * a unicode string u'foo' will generate a unicode (decoded) string, so 'prédio' will yield u'pr\xe9dio' (\xe9 is the codepoint for 'é') Both work as they should, their usage depends whether you want (encoded) byte sequences or (decoded) unicode strings. --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
