Hello,
I've been playing with these functions and finally I've become totally
confused.
I've expected that there would be some difference in behaviour, but I
was not able to create such use case in which these two functions
produces different results. More precisely, I haven't find place where
would be better to use ugettext_lazy. In documentation is said to use
this function in models.py everywhere. But for me it looks that ugettext
makes the same work. All text marked to translation is translated
accordingly to locale set by user via browser with both of them.
Furthermore i was not able to use template strings and stay in __proxy__
mode. anything like ugettext_lazy('xyz %s') % 'some_text' comes to
unicode string representation immediately. So, it looks there is no way
to use template strings with *_lazy. From my view it is little bit
painful to use it.
But I think I must be completely missing something important in this
area. Can anybody enlighten me, please?
--
Tomas Kopecek
e-mail: permonik at mesias.brnonet.cz
ICQ: 114483784
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
