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 multilingual
app would simply have to say
{{ date_var|date }}
to output a grammatically correct phrase (with month name in possessive case
for Greek, genitive in Slavic languages, "de" + month name for Spanish and
whatever else may be required). This is based on my (possibly incorrect)
assumption that canonical date clauses are uniform in a given language
(i.e., you would always use the same grammatical form for month name no
matter what date or year it follows or preceds). I would be very grateful if
someone could proof that in some language this is false.
What my approach is not good for is generation of ad hoc phrases
interpolating month names, such as "Users registered between March and May
2009"). This is a much more complex problem requiring non trivial NLP hooks,
and is in fact a part of much larger problem: interpolation in general.
Consider internationalizing of such string as "No {{object_name}} found". On
the other hand translation phrases can always be rewtiten so that
interpolated words would be in the nominative case (often with unfortunate
side effect of altificial albeit grammatically correct phrases).
Cheers
Sergiy
On Sat, Dec 5, 2009 at 1:35 AM, Orestis Markou <[email protected]> wrote:
> I have created a small app for this:
> http://code.google.com/p/django-localdates/
>
> On 5 Dec 2009, at 08:18, [email protected] wrote:
>
> > Hi all,
> > I have posted a patch for this ticket:
> http://code.djangoproject.com/ticket/12309. Minor changes were made to
> Russian and Ukrainian translations to be able to use the new format "E".
> Please take a moment to review if you believe this may affect you.
> >
> > To Polish (and possibly Belorussian, Czech and Slovak) translators:
> > Kindly take a moment to review the patch and to update your .po files if
> deemed necessary. It will allow you to generate grammatically correct full
> dates such as: "29 listopada 2009" (instead of "29 listopad 2009").
> >
> > Translators of other language might also benefit from this patch if
> alternative month names are required in your language. If you decide to do
> so please drop me a line so that I can include this into documentation
> specific to your locale.
> >
> > Cheers
> > Sergiy
> >
> >
> > On 2009-12-03 10:41pm, Sergiy <[email protected]> wrote:
> > > Hi all,
> > >
> > >
> > >
> > > I have submitted a proposal to extend date format with alternative
> > >
> > > locale specific long month names:
> > >
> > > http://code.djangoproject.com/ticket/12309
> > >
> > >
> > >
> > > This is primarily to accommodate month names in such phrases as
> > >
> > > "January 1 2010" where a genitive case would be required to make
> > >
> > > grammatically correct phrases in some Slavic languages.
> > >
> > >
> > >
> > > I wonder if there can be any use for alternative month names in other
> > >
> > > languages? I know Romanian has popular month name (e.g., "brumar" as
> > >
> > > opposed to the standard word "noembrie" for "November"). But
> > >
> > > incorporating this into Django translations would probably be a
> > >
> > > stretch.
> > >
> > >
> > >
> > > Cheers
> > >
> > >
> > >
> > > Sergiy
> > >
> > >
> > >
> > > --
> > >
> > >
> > >
> > > You received this message because you are subscribed to the Google
> Groups "Django I18N" group.
> > >
> > > To post to this group, send email to [email protected].
> > >
> > > To unsubscribe from this group, send email to
> [email protected]<django-i18n%[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 I18N" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> [email protected]<django-i18n%[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 I18N" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<django-i18n%[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 I18N" 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.
