Hi,
I received a few requests to check the status of Western Balochi incubator
(bgn).
The code bgn is legit, the translation of most-used messages is complete,
and the activity in the incubator is reasonable. A lot of pages are
written; many are just one or two lines long, but I don't think that I mind.
Do we want to verify that it's the right language?
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: Michael Everson
2. E-mail address of requester: everson @ evertype.com
3. Record Requested:
Type: variant
Subtag: wpsimple
Description: Wikipedia Simple English
Prefix: en
4. Intended meaning of the subtag:
The subtag is intended to represent the controlled language used on http://simple.wikipedia.org. This language is a mix of Basic English, VOA Special English, and some more guidelines.
5. Reference to published description of the language (book or article):
Wikipedia:Simple English Wikipedia https://simple.wikipedia.org/wiki/Wikipedia:Simple_English_Wikipedia
Wikipedia:How to write Simple English pages https://simple.wikipedia.org/wiki/Wikipedia:How_to_write_Simple_English_pag…
6. Any other relevant information:
Problem: The Simple English Wikipedia uses "simple" for the domain (simple.wikipedia.org) and "en" for its language. This is a problem because:
* The domain is different from the language code.
* The language code is the same as in the English Wikipedia.
These two problems definitely create several issues for the ContentTranslation extension and possibly other components. It's possible to work around them, but it's better to straighten things out by changing the language code.
This will lead to en-wpsimple.wikipedia.org
Hi,
A question for the respected language code experts in the audience.
Apparently, the Simple English Wikipedia uses "en" as its language code in
the HTML lang attribute, etc.
I never noticed it until recently, when it started causing various bugs
with the ContentTranslation extension of which I am a developer. I somehow
assumed that it uses something like "en-simple" without ever checking it,
and that assumption was wrong - it's just "en".
I believe that the code should be different from what is used by the
English Wikipedia, like it is with other wikis in language variants, such
as be-tarask.
Do you have any suggestions about what code should it be?
en-simple?
en-x-simple?
Something else?
Should I register anything new with any standards organization? (If I
recall correctly, this was done for be-tarask?)
Can I reuse any existing code that would be appropriate?
Is it a bad idea in general and it should be just "en"?
Thanks!
(PS: If you're curious what are the issues, see
https://phabricator.wikimedia.org/T110190 )
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
Hi,
Trying to revive this discussion, because the previous one got stuck.
Problem: The Simple English Wikipedia uses "simple" for the domain (
simple.wikipedia.org ) and "en" for its language. This is a problem because:
* The domain is different from the language code.
* The language code is the same as in the English Wikipedia.
These two problems definitely create several issues for the
ContentTranslation extension and possibly other components. It's possible
to work around them, but it's better to straighten things out by changing
the language code.
The last time I tried to bring this up some people thought that I am
proposing to create a new top-level ISO 639-3 language code for it, but
this is definitely not my intention. Rather, I suggest to go forward with
something like "en-simple". The language in question is a variant of
another one, so a subtag makes sense, but I'd love it to be standardized.
Should it be proposed as a new entry to the IANA language subtag registry?
I couldn't find anything appropriate at
http://www.iana.org/assignments/language-subtag-registry/language-subtag-re…
and I am not familiar with the proposal process.
Is "en-simple" a good suggestion? Or should be something like
"en-wpsimple", like "en-oxendict" (an actually registered variant of Oxford
English dictionary)?
If I recall correctly, Wikipedians already got be-tarask registered
successfully, so this sounds possible to do, but I'd love your advice
before going forward.
Thank you!
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
A couple of months ago I was asked to push code change for Samogotian. (At
the time I hadn't have regulated my membership on this mailing list, then I
forgot it.)
But Samogotian is not the only code to be fixed. Basically, we should make
the decision and suggest to the Board/staff/Phabricator to proceed with
that. I see that None of the cases I am suggesting is in any way
problematic, as well as those names are already implemented into the
interwiki codes.
bat-smg => sgs
be-x-old => be-tarask
fiu-vro => vro
roa-rup => rup
zh-classical => lzh
zh-min-nan => nan
zh-yue => yue
I don't know if you already did or not this, but I think it's time to push
it.
In relation to the old codes, I think they should stay as "permanent
redirects" as long as there is a traffic to them. They won't be used in any
other case, so we don't need to hurry in relation to their removal.