Created attachment 6755 [details]
Patch to add Interlingua locale from Nik Kalach (firstname.lastname@example.org)
The current glibc package and the upstream glibc do not include Interlingua locale for any region. A lot of Fedora programs like Anaconda, system-config-language and Publican depend from the presence of the correct locale in the system. For these programs it is not enough just to set up the LANGUAGE environment variable to localize the interface. Anaconda and system-config-language perform system locale configuration themselves and do not support setting of the LANGUAGE variable in /etc/locale.conf or /etc/sysconfig/i18n.
Anaconda, Firstboot, system-config-language, s-c-time and s-c-keyboard are translated to Interlingua but the lack of the Interlingua locale creates usability problem or, in case of Anaconda and s-c-language, it does not allow the programs to operate as expected.
Fedora documentation and Web-site use Publican for formatting. All necessary Interlingua localizations are available but Publican cannot use them without the locale. As a result, Fedora documentation in Interlingua cannot be built in the standard Fedora Project build environment.
To solve these problems I propose to add an attached patch to the glibc package. It adds the ia_FR locale.
Supporting information for this locale is following:
1. The ISO-639-1 code for the language: "ia"
2. Languages of France:
3. The leading Interlingua association "Union Mundial pro Interlingua"
is registered as a French non-profit association. Registration #0911004931
4. The locale data are available in CLDR.
5. The ethnological information is available here:
Gordon, Raymond G. (ed.). 2005. Ethnologue: Languages of the World, 15 edn.
http://www.ethnologue.com/15/web.asp (09 July, 2008.)
This source specifies the geography for this language as "France"
6. Interlingua is registered by IANA with subtag "ia".
7. General information about the language and its history is available here:
The developers of glibc have repeatedly stated that artificial languages will never be supported. See bugs #711, #2135 and #13190 for details. However, it could be requested that the decision is overturned, at least for the artificial languages with a code established by the ISO 639 (namely Esperanto [EO], Ido [IO], Novial [NV], Interlingua [IA], Interlingue-Occidental [IE], Lojban [JBO] and Volapük [VO]). The only issue would be to assign these a country.
Please, consider this BZ report as a request to overturn the decision not to support Interlingua just because this is an artificial language. Interlingua satisfies the criteria you have mentioned: it has the ISO code. Moreover, it has CLDR data, dictionaries for multiple languages, published grammar, literature, periodics, and active users. It was not invented by some random people, it was derived from 7 major natural languages by the group of professional linguists after 20 years of work. The language is based on the international vocabulary and the minimal grammar common to the most of the source languages. As a result, texts in Interlingua are easy to read and Interlingua can be used as a gateway language to study other languages and as a pivot language in the educational project like Sugar.
As you can see from the initial submission, Interlingua is listed as one of the languages of France by the well respected source of the ethnological information.
I will also take this space to highlight that the three major auxiliary languages (Esperanto, Ido, and Interlingua) all have active speaking communities worldwide, as well as several books, periodic publications and active websites and communities. Also, each of these languages have over a century of history each, with organized active authorities for the evolution of each language, and stable grammar and vocabulary based upon the most important languages of their time. By means of this request, I also ask the developers to reconsider the related bugs that I quoted.
I second the request to reopen the issue. Obviously toy artificial languages like Klingon should not be under discussion to be added, but the unilateral rule against "artificial" languages being added at all is not only misguided; it's inconsistently enforced. I'm pretty sure at least a few "real" languages would have to be removed if we insisted on banning any language that was created by linguists for sociopolitical purposes (in the sense of uniting or dividing peoples) -- and even more if you look back far enough into their histories. If a language has an ISO code and any significant number of speakers, I see no reason it should be treated as less-acceptable for inclusion than any other language with the same number of speakers.
Jeff, I would be fine with adding this but let's discuss on libc-alpha.
Please send a patch (including ChangeLog entry and changes for SUPPORTED) and ask for comments.
Created attachment 6760 [details]
Patch for ChangeLog, SUPPORTED and the ia_FR locale
Added the complete patch with changes to ChangeLog, SUPPORTED and the content of the locale.
Thanks, committed for glibc 2.17
Author: Nik Kalach <email@example.com>
Date: Thu Nov 29 08:31:13 2012 +0100
Add Interlingua locale
* locales/ia_FR : New file
* SUPPORTED (SUPPORTED-LOCALES): Add appropriate entry.
That is outrageous.
First, you are adding crap made-up languages which no one speaks, and yet refuse to add a locale for the RUSSIAN language which alone has more text data written in it than all these interlingua clowns will be able to produce together for 100 years?
The decision on the bug 12624 reeks of Russophobia in this case.
(In reply to comment #8)
> That is outrageous.
No, this is offtopic, please do not bring it here.
> First, you are adding crap made-up languages which no one speaks,
First of all, you shall avoid telling blatant lies, otherwise you will not be listened here.
> The decision on the bug 12624
This bug is not bug 12624, you see. If you like to discuss bug 12624, please bring your arguments there.