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
Sorry for crossposting. CLDR data submission has started this week,
we're looking for more translators: so far I have added 23 new
translators who made over a thousands translations and seem happy with
the system.
Instructions are kept up to date at
<https://translatewiki.net/wiki/CLDR#Contribute_to_an_existing_locale>.
As you know, Wikimedia projects exist in almost 300 languages;
supporting them all is a big effort so we partner with other
organisations, also via Unicode. One small but visible thing we miss is
that many interwiki links in sidebar (among others) don't offer a
translation of the language name when hovered. This can be fixed: we're
now able to translate 100 more language names in your language.[1]
If you're interested, I can create you an account to submit translations
on the CLDR web tool (within June 14): please send an email[2] to ask
one and I'll follow up with instructions. On CLDR you can translate and
tweak many other things, if you desire; your work will impact hundreds
of software projects.[3]
Nemo
[1]
<https://translatewiki.net/wiki/Thread:Support/Language_names_not_in_Unicode…>
[2] <https://meta.wikimedia.org/wiki/Special:EmailUser/Nemo_bis>
[3] <http://cldr.unicode.org/index#TOC-Who-uses-CLDR->
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2014.06. This bundle is compatible with MediaWiki 1.23.x and
MediaWiki 1.22.x releases.
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.06.tar…
* sha256sum: 02721b25e8c8fe06889b825a1c03fc4c1b1e4268d1e56169815983b5e87e8932
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, CLDR, CleanChanges and LocalisationUpdate ==
* Only localisation updates
== Translate ==
=== Noteworthy changes ===
* New feature, Special:PageMigration page has been added and feedback
is welcome!
** Fetches and displays the translation units created by Translate for
the given page.
** Imports the old translations for given language on paragraph level
and displays them.
** Feature can be now conditionally enabled by setting
$wgTranslatePageMigration to true.
** Allows to edit or delete a translation as well as swapping with the
unit below.
** Allows to save the translations by creating corresponding pages.
** Enabled by default for translation admins.
* Special:AggregateGroups page is now visible to unprivileged users in
read-only mode.
* Email notifications are no longer sent upon translation review.
* Page title can be excluded from translation.
* Regression fix: Message checker live updates is working again with
this release.
== UniversalLanguageSelector ==
=== Noteworthy changes ===
* Bug 64741: Fix 'Add links' option in Monobook skin when page has no
interlanguage links.
* Added support for Khakas language.
Thanks!
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
[I'm checking this with Nuria now.]
--
Amir Elisha Aharoni ። אָמִיר אֱלִישָׁע אַהֲרוֹנִי
Language Engineering ። הַנְדָּסָה לְשׁוֹנִית
Wikimedia Foundation ። קֶרֶן וִיקִימֶדְיָה
2014-06-25 18:12 GMT+03:00 Nuria Ruiz <nuria(a)wikimedia.org>:
> Team,
>
> We had an spike on EL yesterday nite that was caught by our alarms. The
> spike can be seen here:
>
>
> http://graphite.wikimedia.org/render/?width=588&height=311&_salt=1403681192…
>
>
> We look at the data for a little while and we can see the schema
> 'UniversalLanguageSelector-tofu' logging at a higher rate than it normally
> does.
>
>
> Can you guys look into what there might have been going on? Looks like the
> "higher than normal logging" might have been triggered by a Localization
> update that happened yesterday.
>
> The event "02:50 logmsgbot: LocalisationUpdate ResourceLoader cache
> refresh completed at Wed Jun 25 02:48:53 UTC 2014 (duration 48m 52s)" from
> https://wikitech.wikimedia.org/wiki/Server_Admin_Log
> happened about at the same time we saw the spike.
>
>
> Thanks,
>
> Nuria
>
>
> ---------- Forwarded message ----------
> From: <icinga(a)neon.wikimedia.org>
> Date: Wed, Jun 25, 2014 at 4:46 AM
> Subject: ** PROBLEM alert - tungsten/Throughput of event logging events
> is CRITICAL **
> To: nuria(a)wikimedia.org
>
>
> ❤❤❤❤❤ Icinga ❤❤❤❤❤
>
> Notification Type: PROBLEM
>
> Service: Throughput of event logging events
> Host: tungsten
> Address: 10.64.0.18
> State: CRITICAL
>
> Date/Time: Wed Jun 25 02:46:22 UTC 2014
>
> Additional Info:
>
> CRITICAL: 7.14% of data exceeded the critical threshold [500.0]
> Love, Icinga
>
If I want to show anonymous users a message including "You can _login_ or
_create an account_ " with returnto support, what's the best way to do it?
Background:
All over MediaWiki we display messages to anonymous users with "_login_ or
_create an account_" links in them. In most cases we want the user to
easily get back to what they were doing, so Special:UserLogin supports
returnto and returntoquery parameters which after login or signup make it
display a link to go back to the page the user was on, or silently redirect
back to it.
The display of login/signup links seems haphazard:
1) Many messages don't bother with returnto, and just have wiki links to
the special page. E.g. anontalkpagetext has:
please [[Special:UserLogin/signup|create an account]] or
[[Special:UserLogin|log in]] ...
2) Some messages try to handle returnto with complicated magic word
processing, , e.g. https://en.wikipedia.org/wiki/MediaWiki:Anoneditwarning
has:
If you '''[{{fullurl:Special:UserLogin|returnto={{FULLPAGENAMEE}}}} log
in]''' or
'''[{{fullurl:Special:UserLogin/signup|campaign=anoneditwarning&returnto={{FULLPAGENAMEE}}}}
create an account]''' ...
This is fiddly, the magic words don''t work in JavaScript, and the
resulting HTML requires you put class=plainlinks on the enclosing tag to
disable the display of the external link icon. On the plus side it's
generated entirely in the message string, and wiki admins can tweak
parameters, like the signup campaign parameter in this example.
3) Often code builds the login/signup links in PHP and passes them to the
message.
3a) OutputPage-> showPermissionsPage() builds a login URL with
Linker:LinkKnown. It doesn't provide a sign up link, and the code to build
the login link can't be reused. Which may be why
WatchAction->checkCanExecute() and SpecialPage::requireLogin copy and paste
the code.
3b) SkinTemplate.php generates the Login / Create account URLs at the top
right of most skins using Skin::makeSpecialUrl. But you can't pass this to
a message because it may not start with //myserver.com and if it doesn't
then it won't work in a [$1 link text] link.
Thanks for any advice,
--
=S Page Features engineer
Hi all,
First of all, thanks Amir and Runa to release my email from the blacklist!
:)
Assamese Wikimedian Gunadeep (marked in this mail) had created a phonetic
keyboard method Rodali some time back. The method is now used by many users
and Gunadeep has been kind to change the copyright terms to CC-BY-SA 3.0.
It would be great if this could be added to the git as many of the Assamese
users use the offline version of the tool to type Assamese. Here is the
pull request: https://github.com/wikimedia/jquery.ime/pull/353
Please also guide us if anything else is required.
Thanks,
*Subha*