In my opinion the main problem here, is that the original words appear
in global_settings.py with a dummy translation, so there's no place in
Django itself where those strings are used.
What I would do is translating the strings in lowercase when it's the
correct form for the language, without duplicating or anything like
that, and then the user will have to capitalize it if creating a drop
down list (what isn't a problem or something strange from my point of
view). For other uses of the language names, it will appear in lower
case by default, what it'll be probably the expected behavior for most
users, and them will be able to capitalize it when necessary.
PS: I'm not sure if a drop down list with languages should use any
translation, imagine that I've to select english from a language list
with chinese names...
On Jun 16, 11:44 am, mrts <[EMAIL PROTECTED]> wrote:
> All languages in my neighbourhood use lowercase language names:
> Estonian, Swedish, Finnish, Latvian, Lithuanian, Russian.
>
> Using separate msgids for lower- and uppercase looks attractive, but
> then the ids in source don't match natural English any more (e.g.
> explicit lowercase could be used in the ids where they don't start a
> sentence: _("estonian")). That is a problem in case i18n is not used
> at all.
>
> _("Estonian") would be translated to en as "Estonian" and to et as
> "Eesti", whereas _("estonian") would be translated to en still as
> "Estonian" but to et as "eesti".
>
> Currently, Finnish django.po uses lowercase for language names, but
> Russian and Latvian django.pos use uppercase (which look unnatural and
> incorrect for native speakers).
>
> On Jun 16, 11:49 am, Marc Fargas <[EMAIL PROTECTED]> wrote:
>
> > Hi all,
>
> > Due to ticket #7461 an issue was raised about uppercase language names.
> > In English, languages are written with the first letter being uppercase
> > while other languages like 'es' and 'ca' write them lowercased unless
> > they're the begining of a sentence or single words.
>
> > This is currently impossible to distinguish with the current msgid's. So
> > two questions for everybody:
>
> > * Which languages are affected by the same thing? (That is, which
> > languages type language names lowercase unless beggining sentences or
> > single words).
>
> > * Any idea on how to get that information from the msgid's?
>
> > For the idea, one option would be having both msgid's (lower and
> > uppercase) so translation would be easy, but that would need the 'en'
> > locale to be up-to-date and having both msgstr set to uppercase. But
> > it's one possible solution. Ideas?
>
> > Thanks,
> > Marc
> > --http://www.marcfargas.com--will be finished some day.
>
> > signature.asc
> > 1KDownload
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
