The language engineering monthly reports for September, October and
November 2017 are ready.
**Highlights for these months**
* Lots of usability and design improvements to the Content Translation
dashboard.
* There is now a way to link directly to a particular message in
Special:Translate.
* Mediawiki Language Extension Bundle 2017.10 was released.
* Style updates in Universal Language Selector and Translate to align
with WikimediaUI styleguide.
* Translatable pages are now editable with the 2017 wikitext editor.
* An issue that made it difficult to log in or save translations in
translatewiki.net was investigated and resolved.
* Translate recent changes filters now support the new filter user interface.
* The old Translate extension translation view interface was finally
removed after four and half years.
* Universal Language Selector search is much improved. It now returns
more consistent and comprehensive results and autocompletion
suggestions are more relevant.
* There is now a Latin-Cyrillic language converter for Crimean Tatar.
For more information about these and other updates, please see the full reports.
**Full reports**
https://www.mediawiki.org/wiki/User:Nikerabbit/Monthly_report/2017-09https://www.mediawiki.org/wiki/User:Nikerabbit/Monthly_report/2017-10https://www.mediawiki.org/wiki/User:Nikerabbit/Monthly_report/2017-11
For those unfamiliar with this report, its goal is to summarize all
technical changes to internationalization, translation tools and other
language support products. It also highlights the diversity of
contributors to this area and that many of them are volunteers.
-Niklas
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2017.10. This bundle is The bundle is compatible with MediaWiki
1.28 and 1.29 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.10.tar…
* sha256sum: 75eefff3bbf50f1f84232f45ab169d2eedea5f7a18994f85b43237f2145403b1
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 ==
=== Noteworthy changes ===
* Style updates.
== cldr ==
=== Noteworthy changes ===
* Localisation and maintenance updates only.
== CleanChanges ==
=== Noteworthy changes ===
* Localisation and maintenance updates only.
== LocalisationUpdate ==
=== Noteworthy changes ===
* Localisation and maintenance updates only.
== Translate ==
=== Noteworthy changes ===
* Special:Translate now accepts showMessage URL parameter that allows
linking to specific messages. This will be better accessible in a
future release.
* Special:LanguageStats and Special:MessageGroupStats now show the
total number of shown languages.
* Special:LanguageStats and Special:MessageGroupStats now handle the
sortable parameter correctly.
* Numerious compatibility and stability fixes:
** Translation editor shortcuts were not showing up in recent version
of MediaWiki.
** Compatibility fix for PHP 7.1.
** Compatibility fix for translatable pages and Visual Editor wikitext
editing mode.
** Compatibility fix for Elastica that broke translation memory.
** Compatibility fix for CxserverWebService which changed API.
* Style updates.
== UniversalLanguageSelector ==
=== Noteworthy changes ===
* Language searching is improved with new language name data and
better "no results found" view.
* Popup positioning should now work better in various skins.
* Style updates.
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
Google Code-in is an annual contest for 13-17 year old students. It
will take place from Nov28 to Jan17 and is not only about coding tasks.
While we wait whether Wikimedia will get accepted:
* You have small, self-contained bugs you'd like to see fixed?
* Your documentation needs specific improvements?
* Your user interface has small design issues?
* Your Outreachy/Summer of Code project welcomes small tweaks?
* You'd enjoy helping someone port your template to Lua?
* Your gadget code uses some deprecated API calls?
* You have tasks in mind that welcome some research?
Also note that "Beginner tasks" (e.g. "Set up Vagrant" etc) and
"generic" tasks are very welcome (e.g. "Choose & fix 2 PHP7 issues
from the list in https://phabricator.wikimedia.org/T120336 ").
Because we will need hundreds of tasks. :)
And we also have more than 400 unassigned open 'easy' tasks listed:
https://phabricator.wikimedia.org/maniphest/query/HCyOonSbFn.z/#R
Would you be willing to mentor some of those in your area?
Please take a moment to find / update [Phabricator etc.] tasks in your
project(s) which would take an experienced contributor 2-3 hours. Check
https://www.mediawiki.org/wiki/Google_Code-in/Mentors
and please ask if you have any questions!
For some achievements from last round, see
https://blog.wikimedia.org/2017/02/03/google-code-in/
Thanks!,
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
The language engineering monthly report for August 2017 is ready.
**Highlights for this month**
Language database is now an independent project to make reuse easier. It
used to be part of jquery.uls library. It contains over 500 entries
detailing basic information about languages, such as their autonym, their
writing script, and region(s) of the world where they are spoken.
https://github.com/wikimedia/language-data
August was, so far, the most active month of 2017 for translatewiki.net
with the highest number of translation updates (55k) and translation
reviews (15k) by over 350 translators.
**Full report**
https://www.mediawiki.org/wiki/User:Nikerabbit/Monthly_report/2017-08
For those unfamiliar with this report, its goal is to summarize all
technical changes to internationalization, translation tools and other
language support products. It also highlights the diversity of contributors
to this area and that many of them are volunteers.
Hello,
I asked this on IRC but didn't get a reply, so posting here. Anyone knows
the status of the CXServer? Specifically,
https://cxserver.wikimedia.org/v1/languagepairs used to work a couple of
weeks ago, but now it's giving me an error that reads "Cannot GET
/v1/languagepairs".
Any info / link to phabricator is appreciated.
Thank you,
Baha
[x-posted announcement]
Hello,
Wikimedia Foundation’s development team working on Content Translation -
the tool that helps you create new Wikipedia articles by translating from
another article, would like to invite you for an online office hour session
scheduled for Wednesday, September 20th, 2017 at 13:00 UTC. This will be an
open session to talk about recent changes to Content Translation and
ongoing development.
You can know more about Content Translation on the project page
<https://www.mediawiki.org/wiki/Content_translation> or even watch a short
video <https://www.youtube.com/watch?v=3btQ5fpn4sA>. We have discussed
Content Translation in the past as part of the office hours hosted by WMF
Language team. The last was in June and you can watch the recording at:
https://www.youtube.com/watch?v=8Euhu4Q7HF4 .
This session is going to be an online discussion over Google
Hangouts/Youtube with a simultaneous IRC conversation. Due to the
limitation of Google Hangouts, only a limited number of participation slots
are available. Hence, do please let us know in advance if you would like to
join in the Hangout. The IRC channel will be open for interactions during
the session.
Please read below for the event details, including local time, youtube
session links and do let us know if you have any questions.
Thank you
Runa
== Details ==
# Event: Content Translation office hour session
# When: September 20th, 2017 (Wednesday) at 13:00 UTC (check local time
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170920T1300)
# Where:On IRC #wikimedia-office (Freenode) and
https://www.youtube.com/watch?v=MD-BKoSj-oY
# Agenda:
Recent updates about Content Translation, and Q & A.
--
Engineering Manager, Global Collaboration (Contributors)
Wikimedia Foundation
We're tracking source/destination pairs generated by the ContentTranslation
tool, right? Could someone point me to that dataset? (I'm playing around
with some machine translation stuff to see if i can prototype a suggester
tool that would translate edits on wiki A to corresponding edits on wiki B.)
--scott
PS. There's some cool work being done on "zero-shot translation"; aka
bootstrapping translation tools for small languages by pre-training them on
a related language (or even an unrelated language). Apparently that works!
(Cf https://arxiv.org/pdf/1611.04558.pdf) It can greatly reduce the amount
of data required to build a translation model for the small language.
Is there a candidate "small wiki" that's been wanting to use
ContentTranslation which would be a good candidate for experimentation?
--
(http://cscott.net)
Hi,
(Cross-posting, because this can interest subscribers of several focused
mailing lists. This doesn't need much discussion on the mailing lists, and
the linked talk page can be used if any discussion is needed.)
Many wikis in the Wikimedia world give editors suggestions about the
correct usage of each respective language: orthography, register,
punctuation, and so on.
I started a page to list of such language guides:
https://meta.wikimedia.org/wiki/Language_guides
I added a bunch of links to Hebrew there because that's my home wiki. I
also added a few pages that I could find for Catalan, Indonesian, Russian,
and Bosnian.
Please add your languages there! Surely there are dozens and dozens of
missing links there.
Before you ask: The linked page explains why Wikidata is not very
convenient for maintaining such a list, but if you think that you can put
this nicely in Wikidata, be bold.
Thank you!
Also thanks to whoever maintains the Wikipedia Indonesia Twitter account
(@idwiki) for giving me the idea for starting this page!
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
The language engineering monthly report for July 2017 is ready.
*Highlights for this month*
Content Translation dashboard has received a major facelift that aligns it
with the Wikimedia style guide and makes it easier to use.
Translatewiki.net now imports new messages up to 9 times per day. New
messages are made available for translation automatically but any changed
messages must be checked by a human. We want to ensure that users get the
new features in their own language. Please contact me if you want to help
us to have a robust around-the-clock coverage.
*Full report*
https://www.mediawiki.org/wiki/User:Nikerabbit/Monthly_report/2017-07
For those unfamiliar with this report, its goal is to summarize all
technical changes to internationalization, translation tools and other
language support products. It also highlights the diversity of contributors
to this area and that many of them are volunteers.
-Niklas
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