Re: Revert name change for North Sami in localechooser

[Petter Reinholdtsen <pere@hungry.com>]

[Christian Perrier]
> I indeed didn't pay enough attention and was thinking that only the
> *localized* name was changed (which is definitely the l10n team's
> privilege). As, indeed, the change is in the English version, I
> agree with Frans' comment.

I was not aware that an accent in the English name was a prolem.  I
thought it handled transcoding juts fine.

> If the English name has to be changed, then I suggest having the ISO
> 639 standard changed. Please note that, IIRC, ISO-639-3 is now out
> (we, iso-codes maintainers, are very late implementing it because of
> its size) and could maybe change the picture (I expect it to name
> languages like se to "Sami, North" or so...).

My source of information about Sami languages are made aware of the
discussion, and I have suggested to them that they try to get the
string changed in ISO-639-2 as well.  I hope they can provide their
input here.  I believe the North Sami is the correct string to use for
'se' instead of Northern Sami , but also see the point of passing the
maintainence responsibility from Debian to the library of congress, to
avoid having language name discussions in Debian, and leave it to ISO
to figure it out.

My belif that the 'North Sami' (with accent - missing the keyboard to
type it now) is the correct string was the reason I modified
localechooser svn.  I will not get upset If you decide to ignore this
and stick to the names from ISO-639-2 instead.  I have used the same
argument myself when people have asked for new locales in glibc. :)

Happy hacking,
-- 
Petter Reinholdtsen