[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: FW: [Future] i18n errors
From:       Gaute Hvoslef Kvalnes <ai98ghk () stud ! hib ! no>
Date:       1999-12-15 12:56:48
[Download RAW message or body]

David Faure wrote:
> 
> And another language mispelling (no_NY), together with
> a reference on how to name languages :-)

Correct, "no_NY" doesn't follow any standards as such. We couldn't find
any ;-)

However, the first error was made when the first "Norwegian" translation
was done. It was given the "no" locale, which is wrong because Norwegian
(bokmal) isn't any more "Norwegian" than Norwegian (nynorsk). These are
both Norwegian languages, and _one_ Norwegian language doesn't exist.
The initial Norwegian version is now renamed Norwegian (bokmal), but the
locale remains "no". Is this because it's too difficult to change?

"no@nynorsk" is a variant I've seen as said under. However, I'm strongly
against using this, since it implies that nynorsk is a variant of bokmal
("no"). If "no@nynorsk" is to be used, the existing "no" should be
"no@bokmal". No language should then have the locale "no".

Another variant (not mentioned below, but I've seen it used) is
no_NO_NY. This keeps the ll_CC syntax, but adds a last code to identify
the variant. In this case, the Norwegian locales should be no_NO_NY and
no_NO_BM (or similar).

Regards,
 Gaute Hvoslef Kvalnes
 Coordinator of the Norwegian (nynorsk) translation

> > Kaixo!
> >
> > On Tue, Dec 14, 1999 at 03:56:42PM -0000, David Faure wrote:
> >
> > >> it should be 'no@nynorsk' instead of 'no_NY' (if it is, as I
> > >> supose, for Nynorsk variant of Norwegian language)
> > >
> > > no@nynorsk ?
> > > Now _that_ is a funny looking language abbreviation ! :-)
> > > I suppose it's because it's a variant and not a country...
> >
> > Yes; the syntax is:  ll[_CC[.EEEE]][@vvvvv]
> >
> > with: ll: language 2 letters iso code, in lowercase.
> >       CC: country 2 letters iso code, in uppercase.
> >       EEEEE: the charset encoding, nothing is standardized here :-( so
> >               it is better avoided; zh_TW.Big5 is the only one that
> >               really set a fixed way for 'EEEE' (and maybe zh_CN.GB2312)
> >       vvvvv: a variant when none of the above can be enough to distinguish
> >               them. 'no@nynorsk' is really the only one that is widely
> used.
> >               There are also the *@euro, intended for LC_MONETARY in fact
> >               (eg 'fr_FR' uses FRF as monetary unit, but 'fr_FR@euro'
> >               uses EUR as monetary unit).
> >               And es@tradicional, intended to force sorting order
> >               to the tradtional order ( LC_COLLATE=es_ES uses so called
> >               'modern' ordering: a,b,c,d,e,...,k,l,m,n,ñ,...; while
> >               LC_COLLATE=es@tradicional uses traditional sorting:
> >               a,b,c,ch,d,e,.....,k,l,ll,m,n,ñ,...).
> >               I think a similar sorting order duality exists for a baltic
> >               language.
> >
> > > But then, how should British English be named ? People speak "en_GB" in
> > > a lot of islands, and even in Australia (which was BTW the reason for
> > > en_GB in KDE, though unmaintainned those days).
> >
> > In NZ for exemple a setting like LANGUAGE=en_NZ:en_AU:en_GB:en
> > would be a good choice.
> >
> > > I thought _XX was the only way to refer to language variants,
> >
> > Problem is when variants happen inside of the same country;
> > as for Norwegian.
> >
> > --
> > Ki ça vos våye bén,
> > Pablo Saratxaga
> >
> > http://www.ping.be/~pin19314/         PGP Key available, key
> > ID: 0x8F0E4975
> 
> --
> David Faure
> faure@kde.org - KDE developer
> david@mandrakesoft.com - Mandrake
> david.faure@cramersystems.com - Cramer Systems

[prev in list] [next in list] [prev in thread] [next in thread]