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
MinervaNeue contains various message keys prefixed with mobile-frontend-
https://github.com/wikimedia/mediawiki-skins-MinervaNeue/blob/master/i18n/e…
I'd like to move away from this as it's confusing.
Nemo pointed out that when Cologne Blue was moved out of core no messages
were renamed.. but then none of those were prefixed.
My concern is that leaving these message keys in Minerva adds confusion and
inconsistency for developers and translators about where the messages are
used and sourced from. It also means that new developers are likely to
prefix new message keys with mobile-frontend- and that will lead to
unnecessary review.
My preference would be to take the short term pain of renaming all message
keys from `mobile-frontend-` to `minerva-` for the long term happiness.
Is there any strong reason not to do this?
--
Jon Robson
Senior Software Engineer