>
> Problem is that the replacement for `Meta.verbose_name` and
> `Meta.verbose_name_plural` we finally come up with also needs to:
>
> * Maintain backward compatibility
>
> * Not change verbose names behavior when i18n isn't being used. IMHO
> disrupting the workflow native English developers (es
On Mon, Nov 28, 2011 at 9:45 PM, Sergiy Kuzmenko wrote:
> 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)
>
I
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 translatio
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 rec
Hi fellow translators,
I've been working that new-feature ticket starting with an idea Jannis
Leidel had posted in a GitHb [0]Gist some months ago and would like to
get some feedback from developers with real i18n experience about this
first iteration of a [1]patch for it.
Solving this would allo
