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 2014.04. This bundle is compatible with MediaWiki 1.22.6 and
MediaWiki 1.21.9 releases.
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.04.tar…
* sha256sum: f20631d2629e0cf80df8ca022e6eec4d6d784e0cd39799f9fd46f338f4a7381a
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://bugzilla.wikimedia.org
* Talk with us at: #mediawiki-i18n @ Freenode
Release notes for each extension are below.
-- Kartik Mistry
== Babel, CleanChanges and CLDR ==
* Only localisation updates.
== LocalisationUpdate ==
* Make sure that older MediaWiki versions also get updates for core messages.
== Translate ==
=== Noteworthy changes ===
* Added ElasticSearch support for translation memory and translation search.
* Set JSON message format as default for MediaWiki extensions.
* Add tracking (mw.track) for primary events: translation and proofread.
* Removed SingleFileBasedMessageGroup.
* Removed classes used for supporting the old MediaWiki core format
and updated related maintenance scripts.
* Localisation updates.
== UniversalLanguageSelector ==
=== Noteworthy changes ===
* Allow always logging tofu detection in EventLogging.
* Bug 62981: Fixed RTL positioning for compact interlanguage links.
* Localize the number in the "more languages" message in the compact
links feature.
* Bug 60815: Set Arabic as the writing system for Ottoman Turkish (ota).
* Bug 63718: Allow overriding the header styles from typography refresh.
* Add loading of messages using $wgMessagesDirs
=== Input Methods ===
* Added Batak input method.
* Fixed the Odia Lekhani method, as well as the InScript methods for
Hindi, Odia and Malayalam.
Thanks!
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
Gergo Tisza, 26/04/2014 04:32:
> If you absolutely had to cut some functionality out in order to roll
> this out more broadly, what would you eliminate?
>
>
> IMO we could get rid of the users, imageusage and globalusage calls
> without much trouble. The first one is only used for gender-correct
> translations.
Degrading i18n is never an option.
Nemo
Hi,
when displaying messages containing usernames in Javascript code, one needs
to pass the gender of the given user. This usually means sending a userinfo
API query, possibly sending it to a different domain and forcing a DNS
lookup (since the given user sometimes resides on another wiki, e.g. in the
case of images transcluded from a repository such as Commons), which can be
quite slow. The time and bandwidth spent on this is often wasted, since not
all languages have the concept of gender; for such languages, the API
request should be omitted.
So,
- how can I tell from Javascript code whether the current language supports
genders? (I guess relying on that is not 100% failsafe, since even if it
doesn't, a fallback language still might, but that sounds unlikely enough
to ignore.)
- how can I tell whether a given message depends on the gender? I suppose I
could grep for '{{gender', or use mw.language to parse it with all genders
and check if the output differs, but both of those are ugly and fragile. Is
there a better option?
thanks
Gergő
Hello,
A reminder that the Language Engineering IRC office hour will be
happening later today at 1700UTC/1000PDT on #wikimedia-office. Please
see below for the original announcement, local time and other details.
Thanks
Runa
Monthly IRC Office Hour:
==================
# Date: April 9, 2014
# Time: 1700 UTC/1000PDT (Check local time:
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140409T1700)
# IRC channel: #wikimedia-office
# Agenda:
1. Translation file format changes
2. Other project updates
3. Q & A (Questions can be sent to me ahead of the event)
---------- Forwarded message ----------
From: Runa Bhattacharjee <rbhattacharjee(a)wikimedia.org>
Date: Fri, Apr 4, 2014 at 9:09 PM
Subject: Language Engineering IRC Office Hour on April 09, 2014
(Wednesday) at 1700 UTC
To: MediaWiki internationalisation
<mediawiki-i18n(a)lists.wikimedia.org>, Wikimedia developers
<wikitech-l(a)lists.wikimedia.org>, Wikimedia Mailing List
<wikimedia-l(a)lists.wikimedia.org>,
wikitech-ambassadors(a)lists.wikimedia.org
[x-posted]
Hello,
The Language Engineering team will be hosting the next monthly IRC
office hour on Wednesday, April 9 2014 at 1700 UTC at
#wikimedia-office.
We will be discussing about our recent work and provide updates
related to changes in the translation file format (PHP to JSON) for
MediaWiki core and extensions. As always, we will be taking questions
during the session.
Please see below for event details and local time. See you at the office hour.
Thanks
Runa
Monthly IRC Office Hour:
==================
# Date: April 9, 2014
# Time: 1700 UTC/1000PDT (Check local time:
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140409T1700)
# IRC channel: #wikimedia-office
# Agenda:
1. Translation file format changes
2. Other project updates
3. Q & A (Questions can be sent to me ahead of the event)
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
Hi,
after a user reported a discrepancy between two versions of the autonym for
the Czech language used in different contexts in MediaWiki, I noticed it
comes from a difference between the MediaWiki core Names.php and CLDR data
(via the CLDR extension’s CldrNames). Originally, I just intended to submit
a patch to Names.php unifying those two to the CLDR version, but then I
thought the problem might exist in other languages, too.
So, I compiled a list [1][2] of 39 differences in language names between MW
core and the CLDR extension. Some of those differences are just case
changes, some of them might be errors in one of the sources, some of them
just random choices between two equally valid versions (like in the Czech
case, it’s not like one of them is generally better than the other, it’s
just that consistency would be better).
I definitely do not intend to change all those languages I do not
understand, but maybe other people could be interested in checking their
language in the list…
-- [[cs:User:Mormegil | Petr Kadlec]]
[1]
http://translatewiki.net/wiki/User:Mormegil/CLDR_language_names_differences
[2] https://gist.github.com/mormegil-cz/7240262
[x-posted]
Hello,
The Language Engineering team will be hosting the next monthly IRC office
hour on Wednesday, April 9 2014 at 1700 UTC at #wikimedia-office.
We will be discussing about our recent work and provide updates related to
changes in the translation file format (PHP to JSON) for MediaWiki core and
extensions. As always, we will be taking questions during the session.
Please see below for event details and local time. See you at the office
hour.
Thanks
Runa
Monthly IRC Office Hour:
==================
# Date: April 9, 2014
# Time: 1700 UTC/1000PDT (Check local time:
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140409T1700)
# IRC channel: #wikimedia-office
# Agenda:
1. Translation file format changes
2. Other project updates
3. Q & A (Questions can be sent to me ahead of the event)
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
Hello. VERY sorry for not going through the process. What I know about
mediawiki would fit in a thimble.
I'm a bit of a hack with unix, and php/mysql.
Old school VMS guy, actually.
So anyway.... REAL quick.
I was trying to add MLEB to my wiki setup for my non-profit (Relay For Life
of Second Life) and got
wiki/includes/MagicWord.php: Error: invalid magic word 'babel'
I thought what I had done with the
for ext in Babel cldr CleanChanges LocalisationUpdate Translate
UniversalLanguageSelector
do
if [ ! -d "$ext" ]
then
git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/$ext.git
fi
cd $ext; git fetch --tags; git checkout 2014.03; cd ..
done
automatically does the tar steps? Because I didn't see the files in
the top level directory for the wiki (with LocalSettings.php).
Apologies for coming to you directly, any help you can be would be appreciated.
Dwen