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
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2017.07. This bundle is The bundle is compatible with MediaWiki
1.27 and 1.28 or above and requires PHP 5.5.9 or above.
Next MLEB is expected to be released in 3 months. 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-2017.07.tar…
* sha256sum: c050c326bfa56d326fece072bed5e4be3e3ad3289b0a449313a2e7dbc4514c55
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
== Highlights and upgrade notes ==
== Babel ==
* Information about the languages that the user knows is now cached to
improve performance. To load the data from the cache, use
getCachedUserLanguageInfo() instead of getUserLanguageInfo(), and
getCachedUserLanguages() instead of getUserLanguages().
* Language code are normalized when they are stored in the database.
So, for example, "ZH" and "zh" are now stored as the same code.
* It is now possible to load Babel information from a Babel box on a
global user page.
== CLDR, CleanChanges and LocalisationUpdate ==
* Localisation and maintenance updates only.
== Translate ==
* Translate extension no longer bundles spyc library. If you need
support for parsing and generating YAML files, and you don't have
phpyaml extensions installed (HHVM provides it in PHP compatibility
mode), then you can install spyc using composer update. (T75945)
* Niklas Laxström fixed a broken error propagation in translator
sandbox user creation in case of an invalid password. (T164912)
* User TerraCodes removed redundant dialog title from the message
group selector. (T165241)
* Niklas Laxström added informative warning message that warns about
non-existent message groups.
* Niklas Laxström fixed a bug that could cause translation completion
statistics to not update in some situations (e.g. translatable pages
within an aggregate message group).
== UniversalLanguageSelector ==
* Amir Aharoni added to Compact Language Links the ability to show
languages that logged-in users specified in the Babel box. (T135371)
* Amir Aharoni improved the language database by making sure all
language autonyms are unique.
* Amir Aharoni fixed misaligned icons in the jquery.ime selector in
RTL. (T164474)
* Amir Aharoni added five African languages and one Asian language to
the language database.
* Amir Aharoni added five language of Taiwan to the language database.
* Amir Aharoni added Rangi language to the language database.
* Federico Leva added four new languages for translatewiki.net to the
language database.
* Federico Leva added variants for Hakka language to the language database.
=== Input methods ===
* Amir Aharoni added an input method for the Fula, Wolof language and
improved the keyboard for the Dagbani language.
* Amir Aharoni added input methods for Dinka, Bambara and Dagbani languages.
* Amir Aharoni renamed Akan keyboard and made it usable also for Twi.
* Kartik Mistry and Amir Aharoni merged numerous pull requests from volunteers:
** Kannada language input methods now also work for the Tulu language.
** Added Tarandine language keyboard by User:Joetaras
** Added Piedmontese language keyboard by User:GatoSelvadego
** Fixes to the Odia transliteration keyboard by User:Psubhashish
** Added the Tulalip input method for the Lushootseed language by
[https://github.com/jcrowgey jcrowgey].
** Added Sambhota input method for Tibetan language by
[https://github.com/eroux Elie Roux].
** Added a Gothic input method by User:Bokareis
** Added added mm3 input method for the Burmese language by User:Lionslayer.
** Added input methods for the Mongolian language by
[https://github.com/hfl Feilong Huang].
** Fixes to the Tamil 99 input method for the Tamil language by
User:Balajijagadesh
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
Hi,
Somehow, jquery.uls never had its own description page in translatewiki, so
I created one:
https://translatewiki.net/wiki/Translating:Jquery.uls
Even though it's a small project, it's used a lot on Wikimedia sites as
part of the ULS extension, and this must be documented somewhere.
As far as I can recall, it's the first time I wrote a page in the
Translating namespace, so review and fixes are welcome.
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
[apologies for the double-post, forgot to add a subject line the first
time!]
[cross-posted to mediawiki-i18n, languages@ and language committee mailing
lists. let me know if there's a better list to use for LanguageConverter
users.]
We're about ready to deploy initial support for LanguageConverter to
Parsoid and Visual Editor (see https://phabricator.wikimedia.org/T43716 and
https://phabricator.wikimedia.org/T49411 for background).
A naming issue has come up. In https://www.mediawiki.org/
wiki/Writing_systems/Syntax there are two categories of rules:
"bidirectional" and "unidirectional".
First, before I ask more: if you are a user of LanguageConverter on your
home wiki, did you know that there was more than one type of rule? And if
so, do you call them "bidirectional"/"unidirectional" or something else?
These names appear in the HTML DOM emitted by Parsoid (see
https://www.mediawiki.org/wiki/Specs/HTML/1.5.0#Language_conversion_blocks).
There was concern that "bidir" as a field name would be confusing; in
particular that people would confuse this with RTL/LTR issues or the
Unicode "bidi" algorithm; neither of which are related at all.
As a user of LanguageConverter, do you find this naming confusing? If
Visual Editor described these types of rules with a different name (say,
"symmetric"/"asymmetric") would that be a help or harm or neither?
The history of the "bidirectional" name in the PHP code appears to date
back to 2008 as far as I can tell ( https://github.com/wikimedia/
mediawiki/commit/69dbeb97f15b65dd5773852d76c3bc93caefc862 ) but they
haven't been strongly exposed in the UI AFAIK. Perhaps they are present in
the UI for the noteTA gadget ( https://zh.wikipedia.org/wiki/
MediaWiki:Gadget-noteTA.js )?
At any rate, I'm be interested in any thoughts or comments from folks who
use LanguageConverter regularly.
--scott
--
(http://cscott.net)
[crpss-posted to mediawiki-i18n, languages@ and language committee mailing
lists. let me know if there's a better list to use for LanguageConverter
users.]
We're about ready to deploy initial support for LanguageConverter to
Parsoid and Visual Editor (see https://phabricator.wikimedia.org/T43716 and
https://phabricator.wikimedia.org/T49411 for background).
A naming issue has come up. In
https://www.mediawiki.org/wiki/Writing_systems/Syntax there are two
categories of rules: "bidirectional" and "unidirectional".
First, before I ask more: if you are a user of LanguageConverter on your
home wiki, did you know that there was more than one type of rule? And if
so, do you call them "bidirectional"/"unidirectional" or something else?
These names appear in the HTML DOM emitted by Parsoid (see
https://www.mediawiki.org/wiki/Specs/HTML/1.5.0#Language_conversion_blocks).
There was concern that "bidir" as a field name would be confusing; in
particular that people would confuse this with RTL/LTR issues or the
Unicode "bidi" algorithm; neither of which are related at all.
As a user of LanguageConverter, do you find this naming confusing? If
Visual Editor described these types of rules with a different name (say,
"symmetric"/"asymmetric") would that be a help or harm or neither?
The history of the "bidirectional" name in the PHP code appears to date
back to 2008 as far as I can tell (
https://github.com/wikimedia/mediawiki/commit/69dbeb97f15b65dd5773852d76c3b…
) but they haven't been strongly exposed in the UI AFAIK. Perhaps they are
present in the UI for the noteTA gadget (
https://zh.wikipedia.org/wiki/MediaWiki:Gadget-noteTA.js )?
At any rate, I'm be interested in any thoughts or comments from folks who
use LanguageConverter regularly.
--scott
--
(http://cscott.net)