here is the summary of ISO 639-3 annual changes:
Retirements (= the following codes no longer exist)
* 5 simple retirements
** prb / Lua'
** puk / Pu Ko
** rie / Rien
** rsi / Rennellese Sign Language
** snh / Shinabo
* 3 merged retirements
** jeg / Jeng -> oyb /Oy
** skk / Sok -> oyb / Oy
** krm / Krim -> bmf / Bom-Kim
* 1 split language
** kgd / Kataang -> ncq / Northern Katang + sct / Southern Katang
Additions (= the following codes have been added)
* 8 newly created languages not previously associated with another language
in the code set
** gie / Gaɓogbo
** ibh / Bih
** lth / Thur
** npx / Noipx
** nql / Ngendelengo
** szs / Solomon Islands Sign Language
** ukk / Muak Sa-aak
** xdo / Kwandu
* 2 newly created languages created by splitting the previously existing
** ncq / Northern Katang (ex kgd / Kataang)
** sct / Southern Katang (ex kgd / Kataang)
* 8 name updates, either change to a name form or addition of a name form
** blv: Bolo -> Kibala
** bmf: Bom -> Bom-Kim
** cug: Chung -> Chungmboko
** klw: Lindu -> Tado
** krr: Kru'ng 2 -> Krung
** lgn: Opuuo -> T'apo
** ngt: Ngeq -> Kriang
** ovd: Övdalian -> Elfdalian
* 2 denotation updates of a language into which another variety or two was
** oyb (+jeg, +skk)
** bmf (+krm)
Almost two weeks ago, the Technical Collaboration team invited proposals
for the first edition of the Developer Wishlist survey!
We collected around 77 proposals that were marked as suitable for the
developer wishlist and met the defined scope and criteria
<https://www.mediawiki.org/wiki/Developer_Wishlist#Scope>. These proposals
fall into the following nine categories: Frontend, Backend, Code
Contribution (Process, Guidelines), Extensions, Technical Debt, Developer
Environment, Documentation, Tools (Phabricator, Gerrit) and Community
Voting phase starts now and will run until *February 14th, 23:59 UTC*. Click
here on a category and show support for the proposals you care for most
<https://www.mediawiki.org/wiki/Developer_Wishlist>. Use the 'Vote' and
'Endorse' buttons next to a proposal to do so.
*What happens next?*Proposals that will gather most votes will be included
in the final results which will be published on *Wednesday, February 15th*.
These proposals will also be considered in the Wikimedia Foundation’s
annual plan FY 2017-18.
Technical Collaboration team
Forwarding from wikitech-l to mediawiki-i18n, as it's of high relevance.
Please make sure to include Yuri in your reply, as I'm afraid he is not
On Fri, Feb 10, 2017 at 2:31 AM, Yuri Astrakhan <yuriastrakhan(a)gmail.com>
> TLDR: if browsing a map for French wiki, and a city only has a Russian and
> Chinese name, which one should be shown? Should the city name have
> different rules from a store or a street name? ...
> I have been hacking to add unlimited multilingual support to Wikipedia
> maps, and have language fallback question: given a list of arbitrary
> languages for each map feature, what is the best choice for a given
> I know Mediawiki has language fallbacks, but they are very simple (e.g. for
> "ru", if "ru" is not there, try "en").
> Some things to consider:
> * Unlike Wikipedia, where readers go for "meaning", in maps we mostly need
> * Alphabets: Latin alphabet is probably the most universally understood,
> followed by...? Per target language?
> * Politics: places like Crimea tend to have both Russian and Ukrainian
> names defined, but if drawing map in Ukrainian, and some feature has
> Russian and English names, but not Ukrainian, should it be shown with the
> Russian or Ukrainian name?
> * When viewing a map of China in English, should Chinese (local) name be
> shown together with the English name? Should it be shown for all types of
> features (city name, street name, name of the church, ...?)