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.08. This bundle is compatible with MediaWiki 1.23.x and
MediaWiki 1.22.x releases.
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.08.tar…
* sha256sum: f4663910facd2b34d4afb1af930f66adad22b2746f9395f7706f07751e633857
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 ===
* Breaking change: Dropped support for MediaWiki 1.21 (2014.05 is the
latest version of MLEB as a whole which supports 1.21)
* Avoid losing translators' edits: improved handling of expired
sessions ({{bug|69314}}).
** Status has yellow background if the translation has not been saved.
** Show an alert to the user if session has expired.
** Prevent saving translations as an anonymous user accidentally.
* Restore progress icon for the current translation page (regression
from MLEB 2014.07).
* Update associated translation pages when moving translation units.
* Show definition diff for all messages if available, not just for
outdated messages.
* Special:AggregateGroups: Group selector is now input field with
autocompletion instead of combobox.
* Special:PageMigration: Don't add the created pages to watchlist.
* Special:PagePreparation: This is a new special page to assist in
preparing pages for translation
== UniversalLanguageSelector ==
* Change the autonym for Algerian Arabic.
* Localisation updates.
==== Input Methods ====
* Tibetian-ewts: Use of unicode NFC instead of NFD.
* Fixed description in Bengali Probhat layout.
==== Fonts ====
* Added Comic Neue font. It is available for English and other
languages using the latin alphabet.
* Updated UnifrakturMaguntia font to the latest version.
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
I think I found a bug and wanted to check if I'm doing it wrong, or if
it is indeed a bug and if so if there is somewhere I can track it?
{{PLURAL:$1|$3 started this topic|A|0=B|2=C|3=$3}}
> mw.msg( "flow-topic-participants", 3 )
> 'A'
However
{{PLURAL:$1|$3 started this topic|A|0=B|2=C|3=D}}
> mw.msg( "flow-topic-participants", 3 )
> 'D'
Is there any workaround I can use?
I want to use programatic scripts to work with the i18n files across
MediaWiki. I wrote a script to allow me to add messages, and easily
update message keys as well as scan for missing qqq codes [1]
The problem I am running into is that an object is an unordered set of
name/value pairs and in Python (at least to my knowledge) key order
varies across Python implementations.
So if I programmatically like in my script [1] I want to manipulate
the JSON, when re-writing it, I'm struggling to maintain the original
order.
I wonder if thus it would be useful to sort all our i18n messages in
alphabetical order.
I feel this would be a good thing as it would encourage naming
messages in such a way that they appear in the same order.
E.g for an editing interface you might have
myeditor-button-save
myeditor-button-edit
How does translatewiki build the i18n files? Is this just a python problem?
[1] https://github.com/jdlrobson/WikimediaMessageDevScript