Kenneth,
It is indeed stored, I'm using a state machine
(http://www.djangosnippets.org/snippets/737/). Setting this up multilingual
could result in unusable orders states, when users change their locale during
the state/transition of an order.
The tricky thing is that the states (used for control) also have a meaning to
the user displayed in the template. So I would want to translate them at the
last moment, and not store them as such.
Regards,
Gerard.
Kenneth Gonsalves wrote:
> On Tuesday 30 September 2008 10:40:15 am Gerard Petersen wrote:
>> #~ msgid "quoted"
>> #~ msgstr "jaja"
>>
>> It's in the template like this "{% trans order.state %}" so it's not picked
>> up by the makemessages command. Then another option is putting the
>> translation in the view, and manipulate it there just before it goes into
>> rendering. But since there's no other actions to be performed there
>> data-wise, I really don't want it there.
>>
>> Anybody have any experience on this?
>
> The various states of an order must be defined somewhere? in choices or
> something? translate it there?
>
--
urls = { 'fun': 'www.zonderbroodje.nl', 'tech': 'www.gp-net.nl' }
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
