(request copied from T151186 )
- language item: https://www.wikidata.org/wiki/Q7976 : native label writing system speakers
(request copied from T151186 )
|Open||None||T124286 [Epic] Wikidata language support|
|Open||None||T144272 new monolingual language code requests for Wikidata (tracking)|
|Open||Lea_Lacroix_WMDE||T154589 evaluate creation of en-us for Wikidata monolingual strings|
en is en-ambiguous. en-gb is "standard English" in that it is English spoken by persons living in England and the other countries in Great Britain. User appears to have a battleground mentality on what he believes English is and what the rest of the world thinks English is.
And in fact, appears to be edit-warring on wiki, which suggests to me that administrative action may be necessary therein.
This discussion may be relevant to the request to add en-us; I like the suggestion to make it so that we can "tag" the aliases of relevance with a particular English variation. (I might suggest that would be low priority work.)
It might be worth keeping in mind the difference (or the absence of a difference) between the following:
She does Community communications on WikiData dev stuff. There is an outline of the process at https://www.wikidata.org/wiki/Help:Monolingual_text_languages . Apparently she doesn't think it's answered by that and needs some feedback for the community. In any case, it's not about fr-ca.
I replied to https://meta.wikimedia.org/wiki/2017_Community_Wishlist_Survey/Wikidata/Add_en-us_as_a_separate_language which is linking here as follow:
While I share the concern about the symptom, I'm not sure it's really a technical problem, but more an editorial one about accepted language granularity. That is, the problem surely go far beyond en-US, as I would expect that even within US you will find regional linguistic variations. Actually, even in small town you might find notable dialectal variations. So surely recognize en-US would be fine, but this wouldn't solve the underlying problem.
To give a more concrete example and take some distance with the American English concern which highly mix the linguistic granularity concern with the hegemony concern, I propose to look at the case of Alemannic. It gathers a lot of problematic that arise when trying to categorise discourse practices under the abstract notion of language.
First, the English Wikipedia article presents it as a group of dialects of the Upper German branch of the Germanic language family. ISO 639-3 distinguishes four languages for this group: gsw (Swiss German), swg (Swabian German), wae (Walser German) and gct (Alemán Coloniero, spoken since 1843 in Venezuela).
Additionally, Alsatian dialect is clearly a part of this group. Under the ISO 639-3 segmentation it is coded under gsw. There is a Alemannic version of Wikipedia, but hosted under the als subdomain, which obviously come from Alsatian.
Finally, a dialect of Alsatian German is spoken in Amish communities of the United States and Canada.
I'm curious to know how the language committee deals with that kind of problem, and eager to read any documentation you might point me to regarding this topic, and processes used by the language committee.
The Alsatian issues precedes the language policy and as such it is a "fait
accompli". We have to live with it. A similar situation will no longer come
into being because it will not be approved.
@Liuxinyu970226 I don't think so; GerardM didn't clearly indicate that, and presumably "similar situation" would refer to new wikis for macrolanguages, of which English isn't one.
The situation with en-us is different to the situation for Alemannic, and the granularity issue is different for Wikidata because it's a multilingual project to begin with. (I also think the LangCom decision – wherever it is, because I can't find it – was wrong, but that's not why I think the task shouldn't be declined.)