Re: Django Translation: Why is there no pgettext_noop or npgettext_noop?

HI Ramiro,

Perhaps I am confused.  I just want to mark these strings for extraction by makemessages(xgettext) in one component of my system and store them in a database.  Another component will do the actual translation by calling pgettext.    I can probably use the _lazy methods to achieve the same thing but I'll need to serialize these lazy proxy objects to my database and that just seems more complicated. Why not just use the original string and invoke pgettext at the right time?  Does the _lazy version do something else for me?  

-Bob

On Tuesday, July 9, 2013 4:10:42 PM UTC-7, Ramiro Morales wrote:

On Tue, Jul 9, 2013 at 7:02 PM, Bob Barcklay <bbar...@thuuz.com> wrote:
> I want to use contextual markers and plural forms in strings with deferred
> translation.  I'm curious why _noop versions of pggettext and npgettext
> don't appear anywhere.

What do _noop-suffixed version(s) of gettext function(s) have to do with
contextual markers, plural forms and deferred translation?

Are you confusing _noop with _lazy?

> My plan is to modify the xgettext invocation found
> in django/core/management/commands/makemessages.py to include new --keywords
> for pgettext_noop and npgettext_noop.  Is this the correct approach?

--
Ramiro Morales
@ramiromorales

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.