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
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
Hello,
I am interested in Multilingual, usable and effective captchas project listed in https://www.mediawiki.org/wiki/Summer_of_Code_2014 and figured out few solutions to encounter the solution
Way we can approach the project:
1)Alphabetical order captcha:We can use Html5's drag and drop Api to list a particular Set of images into one category .for example in the example mentoined in the demo here ,i made a collection of diff words starting with letters A,B,C ....as an output i grouped up words with starting letter A diff from words with starting letter B,C....As,i used text in this example we can use images of diff animals such as cat's and dog.....and by drag and drop we can group images of cat and that of dog in diff categories.
2)Annotation captcha:We can use Images With annotations from commons determine the subcategoriy the annotations belongs to and then give relevant options to the users ;for example in the file we can search from names of different annotations to which they corresponds to from wikipedia(names given here are those of mountain) and then give the the option's much relevant to the image.
3)Effect captcha:We can use image as a question which are changed by the effect produced php's gd library and the use the same file with another effect and then ask user to match the two files.....for example:the image1 can be used as a question asking user to click on the image that matches with the question image and as an answer we can give this spiral image of the original image.Similarly we can give filters to different images producing different options asking user for right answer.
4)Direct captcha:We can ask to user direct questions like ask for selecting cat out of options consisting of images of cats and humans.....an example by pginer demonstrate this example
5)Ask User to click on given effect: Asking user to click on images consisting of spiral effect's out of options which consist of images with spiral and other effects(example:grey scale).
6)Drag and Drop character in Correct Place: We can use drag and drop api of html5 to ask user to form an particular alphabet or no out of the pieces of character provided .Here is an example to form an character "A" and an digit "8" out of the same pieces of character.
This drag and drop capability can be further enhance to form a particular shapes.For example form a clip art from a particular set of piece of shapes....for example the image given here inserts the correct nose as asked in the in the questions out of the possible options provided.
Most,Importantly i think creation of an index system would be fruitful since it would rank the inappropriate images on the basis of users response (rank is negative for an image if user needs to reload a captcha) to a provided captcha.This as the time passes will provide us with relevant images which are user friendly and equivalently secure to use.......
In addition i sincerely appreciate a point mentioned by Gmansi of creation of jigsaw puzzle for the images but in my view point there will be listing of some particular category of images and those ranked higher in indexing system to be used as jigsaw puzzle.
As an additonal help we can use Extension Assira to make our extension smarter.
I request all members to please give your valuable suggestions as we can work to improve this amazing project. at https://www.mediawiki.org/wiki/Talk:CAPTCHA :)
Thank YouAalekh Nigam"aalekhN"
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2014.02. This bundle is compatible with MediaWiki 1.22.2 and
MediaWiki 1.21.5 releases.
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.02.tar…
* sha256sum: 5c5636332b38a7ce9ac12fac74f0402afdc592aa58795b51dc4747877db340da
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 ==
* Only localisation updates.
== LocalisationUpdate ==
* README was updated to include better installation instructions.
== Translate ==
=== Noteworthy changes ===
* Allow capital letters in MediaWiki style variables (insertables)
* Bug 60500: Added AppleFFS module for iOS/Mac OS X Localizable.strings files
* Remove shortcut activated from "paste source". It's similar to
"revert changes" button, which does not have the insertable class and
thus the number indicating shortcut key won't be visible.
* Added new hook TranslateMessageGroupPathVariables
* Bug 61459: Removed $wgTranslateExtensionDirectory option.
* The magic-export.php was updated to handle failures more gracefully.
* Bug 50954: In the translation interface, 'Add documentation' link
now changes to 'Edit documentation' as soon as documentation is added.
* Bug 54194: The ApiQueryMessageCollection module no longer throws
exceptions on invalid input.
== UniversalLanguageSelector ==
=== Noteworthy changes ===
* Detect tofu before applying any default fonts. See:
https://www.mediawiki.org/wiki/Universal_Language_Selector/WebFonts#How_web…
for technical documentation about how tofu detection works in ULS.
* Bug 60304: Added enableWebfonts preference. Each wiki can be
configured to load the fonts by default using the new global variable
$wgULSWebfontsEnabled. Its default value is true (to load fonts).
* ULS is now much lighter for the browser thanks to many changes:
** Bug 56292: All SVG images were optimized to reduce their size even
50% in some cases.
** I18n related jquery.i18n and messages code is now loaded only later
after user interacts with ULS.
** We removed a dependency to a big JavaScript module which was no
longer needed to support anonymous preferences.
* Bug 60815: Add Marwari (rwr) and Ottoman Turkish (ota) to the
languages supported by ULS.
=== Fonts ===
* Add Iranian Serif and Iranian Sans Bold fonts.
* Removed Amiri font from Persian.
* Replaced Xerxes font with Artaxerxes.
=== Input methods ===
* Bug 53695: For languages which have no input methods, the "Use
native keyboard" option is now shown as selected by default.
* Added Venetian input method.
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
FYI.
---------- Forwarded message ----------
From: Erik Moeller <erik(a)wikimedia.org>
Date: Fri, Feb 21, 2014 at 2:35 PM
Subject: Language Engineering team changes
To: All Wikimedia Foundation Staff
Hi folks.
After some internal conversations, we've implemented the following
changes on the Language Engineering team:
- Amir Aharoni is currently the Acting Product Manager;
- Runa Bhattacharjee is the ScrumMaster.
Siebrand Mazeland is no longer part of the Wikimedia Language
Engineering team. We're maintaining a part-time contract relationship
with Siebrand to support MediaWiki developers with i18n/l10n-related
questions, to provide continuous review of MediaWiki changes from an
i18n/l10n perspective, and to support translatewiki.net requirements
which intersect with Wikimedia Foundation priorities and ongoing
localization updates.
I want to thank Siebrand for serving as the team's Product Manager
since July 2011, and for continuing to partner with us on i18n/l10n
issues and on translatewiki.net, which is an essential part of the
Wikimedia localization process.
Thanks,
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Hello,
A quick reminder that the IRC office hour for Language Engineering is
happening later today at 1700 UTC on Freenode #wikimedia-office. More
details at the end of the mail.
See you there!
Thanks
Runa
Event Details:
==========
# Date: February 12, 2014 (Wednesday)
# Time: 1700-1800 UTC, 0900-1000 PDT (Check for local time:
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140212T1700)
# IRC channel: #wikimedia-office on irc.freenode.net
Agenda:
======
1. Universal Language Selector (ULS) update and developments
2. Q & A
---------- Forwarded message ----------
From: Runa Bhattacharjee <rbhattacharjee(a)wikimedia.org>
Date: Thu, Feb 6, 2014 at 2:49 PM
Subject: Language Engineering IRC Office Hour on February 12, 2014
(Wednesday) at 1700 UTC
To: MediaWiki internationalisation <mediawiki-i18n(a)lists.wikimedia.org>,
Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>, Wikimedia
developers <wikitech-l(a)lists.wikimedia.org>,
wikitech-ambassadors(a)lists.wikimedia.org
[x-posted]
Hello,
The Wikimedia Language Engineering team will be hosting the monthly IRC
office hour on February 12, 2014 (Wednesday) at 1700 UTC/ 0900 PDT on
#wikimedia-office.
This time we would be talking about the recent changes made to the
Universal Language Selector (ULS) - the MediaWiki extension that provides
unified language configuration[1] - and the impact on the Wikimedia wikis.
We look forward to addressing any questions you may have about this. Please
see below for the event details.
Questions can also be sent to me before the event. See you all at the IRC
office hour!
Thanks
Runa
[1] https://www.mediawiki.org/wiki/Universal_Language_Selector
Event Details:
==========
# Date: February 12, 2014
# Time: 1700-1800 UTC, 0900-1000 PDT (
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140212T1700)
# IRC channel: #wikimedia-office on irc.freenode.net
Agenda:
======
1. Universal Language Selector (ULS) update and developments
2. Q & A
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
[x-posted]
Hello,
The Wikimedia Language Engineering team will be hosting the monthly IRC
office hour on February 12, 2014 (Wednesday) at 1700 UTC/ 0900 PDT on
#wikimedia-office.
This time we would be talking about the recent changes made to the
Universal Language Selector (ULS) - the MediaWiki extension that provides
unified language configuration[1] - and the impact on the Wikimedia wikis.
We look forward to addressing any questions you may have about this. Please
see below for the event details.
Questions can also be sent to me before the event. See you all at the IRC
office hour!
Thanks
Runa
[1] https://www.mediawiki.org/wiki/Universal_Language_Selector
Event Details:
==========
# Date: February 12, 2014
# Time: 1700-1800 UTC, 0900-1000 PDT (
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140212T1700)
# IRC channel: #wikimedia-office on irc.freenode.net
Agenda:
======
1. Universal Language Selector (ULS) update and developments
2. Q & A
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation