This is a common difficulty with localizing inflecting languages, such as
Polish. Adding a special field for accusative might do the trick for your
particular case but poses a number of challenges:
There are 7 cases in Polish (okay we may probably safely exclude vocative,
so it's 6) and potentiall
FYI. In Italian Wikipedia short dates are formatted as "d M Y" (e.g., 21
gen 2012).
On Fri, Feb 10, 2012 at 12:45 PM, Craig Blaszczyk wrote:
> That's what I thought. I've opened
> https://code.djangoproject.com/ticket/17670
>
> --
> You received this message because you are subscribed to the Goo
Yes. I'd call it a bug. Should be small "m" in SHORT_DATE_FORMAT.
On Fri, Feb 10, 2012 at 9:39 AM, Craig Blaszczyk wrote:
> Hi all,
>
> I've noticed an inconsistency in the `it` locale formats.py file
> (django/conf/locale/it/formats.py) both in Django 1.3.1 and trunk.
>
> The file contains:
>
>
>
> 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
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
I agree. We are getting nested translations here which does not work
equally well in all languages. Translation strings have to be fully spelled.
On Nov 25, 2011 7:25 PM, "Vladimir Macek" wrote:
> Hello translators,
>
> there's a new `naturaltime' template tag coming with the Django dev
> version
It would be useful to have a consistent interface between localflavor
modules. Something in the line of the following:
SUBDIVISION_NAME - top level subdivision name, e.g., "state", "province",
"county", "parish" etc. or None if there are no subdivisions.
POSTAL_CODE_NAME - "zip", "postal code", "p
s, even in English? Is there a
> reason to start a message with lowercase? I think it's a bit intrusive to
> capitalize all messages.
>
> /Erik
>
> [1] https://code.djangoproject.com/ticket/16973
> [2] https://code.djangoproject.com/ticket/16350
>
>
>
> On Sun, Oct
I believe you should file a bug report.
Cheers
On Sat, Oct 1, 2011 at 7:09 PM, Erik Wognsen wrote:
> Ok. Does the i18n group have the possibility of deciding and committing
> this or should it go through a regular bug report?
>
> On Sun, Oct 2, 2011 at 01:00, Sergiy Ku
> According to gettext manual[1] one can use \u to uppercase the next char.
> > But I have no idea whether "\u%(name)s" works. If it does not, a small
> patch
> > for Django admin to fix this would be nice.
> > [1]
> http://www.gnu.org/software/gettext/manual/gettext.html#Interpolation-I
>
> That
e.g. "msg = msg[0].upper() + msg[1:]" after msg is set in
> contrib/admin/options.py.
>
> Regards,
> Erik Wognsen
> On Tue, Sep 27, 2011 at 20:47, Sergiy Kuzmenko wrote:
>
>> In general noun interpolation is a non trivial task. It might be possible
>> that for
In general noun interpolation is a non trivial task. It might be possible
that for a limited subset of messages (addition, deletion and modification)
there is a common denominator for an "alternative" verbose model name that
will do the trick in all languages. But it might not be so. Different
lang
Hi Orestis,
your project is very interesting and ambitious one. My goal however is
rather simple: to achieve a canonical (or "dictionary from") date display in
a given locale without additional overhead and complicated language-specific
hooks. With my approach a programmer or designer working on a
13 matches
Mail list logo
