gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] should translation 'languages' be language_COUNTRY (l


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] should translation 'languages' be language_COUNTRY (la_CO) or just language (la)?
Date: Sun, 20 Nov 2011 00:55:42 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Sat, Nov 19, 2011 at 09:37:38PM +0000, Jim Busser wrote:

> On this wiki page
> 
>       http://wiki.gnumed.de/bin/view/Gnumed/BackendI18N
> 
> the example given is
> 
>       where translation teams will find it and provide a translation for, 
> say, German like so:
> 
>       insert into i18n_translations(lang, orig, trans) values ('de_DE', 
> 'sister', 'Schwester');
> 
> however would this better be
> 
>       insert into i18n_translations(lang, orig, trans) values ('de', 
> 'sister', 'Schwester');
> 
> thus making it more widely available?

Yes, that way Austrian and Swiss will see some sort of
translation, too, via the fallback from de_AT/de_CH to plain de.

If they desire to add a better one for their flavour of
German they can always add a specific de_AT/de_CH
translation which would be returned first.

> We do not anywhere in the wiki define
> 
>       xx_XX

That's pretty standard in i18n IT.

> so maybe in between the headings
> 
>       Concepts
>       ...
>       Database objects
> 
> I can add a heading
> 
>       Convention
> 
> with a description of xx_XX if anybody cares to provide one along

It is language_VARIANT.

> with an answer of when to use
> 
>       xx_XX
> 
> vs
> 
>       xx
> 
> ??

See above.

Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346



reply via email to

[Prev in Thread] Current Thread [Next in Thread]