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 all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2015.10. This bundle is compatible with MediaWiki 1.24.x and
MediaWiki 1.25.x releases.
Next MLEB is expected to be released in 3 months. We are trying less
frequent releases due to low number of changes per month in the
included extensions. If there are major changes or important bug
fixes, we will do intermediate release. Please give us your feedback
at [[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]].
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.10.tar…
* sha256sum: 482595d35ab02fdc40c6ae54d2cf21aa22360f7021d498c054624ccdbf721237
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to: https://phabricator.wikimedia.org/
* Talk with us at: #mediawiki-i18n @ Freenode
Release notes for each extension are below.
-- Kartik Mistry
== Babel ==
* Extension is no longer automatically loaded when installed via composer.
* Support for extension registration was added.
* Configuration options for CDB file locations were removed.
== CleanChanges and LocalisationUpdate ==
* Localisation updates only.
== CLDR ==
* Extension is no longer automatically loaded when installed via composer.
* Updated to CLDR 28.
== Translate ==
* MediaWiki 1.23 is no longer supported. Extension is no longer
automatically loaded when installed via composer.
* If local TTMServer translation memory is marked as public, it will
not automatically take advantage of TranslationWebServices query
parallelization.
* Allows a user to easily access search operators with autocompletion
on Special:SearchTranslations.
* Language and group selectors now interact better on Special:Translate
* Results are always shown when searching for a full page title on
Special:SearchTranslations for a known message.
* Special:Translate now says explicitly that it needs JavaScript to function.
* TranslationWebServices now display correct error message for query
failures in the logs.
* Minor display fix on Special:Translate page mode that was caused by
rounding errors.
* TTMServer translation memory can be used with wikimedia extra
elasticsearch plugin version 1.7.1 to avoid enabling scripting in
ElasticSearch.
* Flash of unstyle content no longer happens or is reduced on
translatable pages, on Special:SearchTranslations and on
Special:Translate.
* $wgTranslateSupportUrl can now contain a full URL ('url' key).
$wgTranslateSupportUrlNamespace is added to override the general
configuration for specific namespaces.
== UniversalLanguageSelector ==
* MediaWiki 1.23 is no longer supported. Extension is no longer
automatically loaded when installed via composer.
* Language change is now done in two phase: first changed with API,
then page is reloaded. The 'setlang' URL parameter is no longer used,
although it still works. Due to the change, language switching might
take a slightly longer than previously.
* Previous language selection is now stored in localstorage instead of cookies.
* Support added for Livvi-Karelian (olo) language.
* Input Methods:
** Various fixes in bo-ewts (Tibetan EWTS) keyboard layout.
** Fixed name of gu-transliteration (Gujarati Transliteration) input method.
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
Milos Rancic, 20/05/2015 10:36:
> May somebody clarify that Unicode data is free? PD or CC-BY-SA
> compatible.
Sure. The license __for data and software__ is
http://unicode.org/copyright.html#Exhibit1 which is a BSD 3-clause
license with trivial changes to make it even clearer and freer, such as
the removal of the term "binary form" and "other materials".
CLDR data is embedded in most free software, e.g. via ICU, packages for
which are available e.g. in Debian which is notoriously restrictive as
regards licenses. https://packages.debian.org/search?keywords=icu
Besides, language names are evidently not copyrightable and Unicode
makes no attempt to state the contrary. (Their license is still useful
for sad places like EU where the set of names could be considered
subject to sui generis database rights.)
Nemo