The Wikimedia Language Engineering team is pleased to announce the
first release of the MediaWiki Language Extension Bundle. The bundle
is a collection of selected MediaWiki extensions needed by any wiki
which desires to be multilingual.
This first bundle release (2012.11) is compatible with MediaWiki 1.19,
1.20 and 1.21alpha.
Get it from https://www.mediawiki.org/wiki/MLEB
The Universal Language Selector is a must have, because it provides an
essential functionality for any user regardless on the number of
languages he/she speaks: language selection, font support for
displaying scripts badly supported by operating systems and input
methods for typing languages that don't use Latin (a-z) alphabet.
Maintaining multilingual content in a wiki is a mess without the
Translate extension, which is used by Wikimedia, KDE and
translatewiki.net, where hundreds of pieces of documentation and
interface translations are updated every day; with Localisation Update
your users will always have the latest translations freshly out of the
oven. The Clean Changes extension keeps your recent changes page
uncluttered from translation activity and other distractions.
Don't miss the chance to practice your rusty language skills and use
the Babel extension to mark the languages you speak and to find other
speakers of the same language in your wiki. And finally the cldr
extension is a database of language and country translations.
We are aiming to make new releases every month, so that you can easily
stay on the cutting edge with the constantly improving language
support. The bundle comes with clear installation and upgrade
installations. The bundle is tested against MediaWiki release
versions, so you can avoid most of the temporary breaks that would
happen if you were using the latest development versions instead.
Because this is our first release, there can be some rough edges.
Please provide us a lot of feedback so that we can improve for the
next release.
-Niklas
--
Niklas Laxström
Hello,
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)
Updates
* 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
merged
** oyb (+jeg, +skk)
** bmf (+krm)
Kind regards
Danny B.
Hello,
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
Engagement.
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.
Cheers,
Srishti
--
Srishti Sethi
Developer Advocate
Technical Collaboration team
Wikimedia Foundation
https://www.mediawiki.org/wiki/User:SSethi_(WMF)
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
subscribed.
On Fri, Feb 10, 2017 at 2:31 AM, Yuri Astrakhan <yuriastrakhan(a)gmail.com>
wrote:
> 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
> language?
>
> 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
> "readability".
> * 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, ...?)
>
> Thanks!
>