My two cents:
1. Plural translation should output a fully translated phrase, e.g.:
ungettext('%(count)d poll', '%(count)d polls, count) % {'count': count, }
instead of noun alone, as in:
ungettext_lazy('poll', 'polls', count)
The advantage is that we provide translators with a complete translation
string and thus there is no need to do stitching in the template with a
specific word order in mind. Numeral + noun is not the universally
acceptable word order [1].
2. I'm not very clear why we need both verbose_names and get_verbose_name.
If get_verbose_name is going to be the published interface we probably
don't need additional class methods, do we?
[1] http://wals.info/chapter/89
Thanks
On Mon, Nov 28, 2011 at 7:36 AM, Vladimir Macek <[email protected]> wrote:
> On 28.11.2011 11:49, Ramiro Morales wrote:
> > Any kind of feedback is welcome!
>
> Wonderful! Thanks for making verbose_names's really plural friendly!
>
> --
> : Vladimir Macek : http://macek.sandbox.cz : +420 608 978 164
> : UNIX && Dev || Training : Python, Django : GPG key 1F059424
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django internationalization and localization" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/django-i18n?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Django internationalization and localization" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-i18n?hl=en.
