Mediawiki-i18n

mediawiki-i18n@lists.wikimedia.org

568 discussions

Localisation fallback between Slovak and Czech languages
by Sébastien Santoro 21 Aug '16

21 Aug '16

Hello, Until MediaWiki 1.27, any message not translated in Slovak or in Czech is printed in English. For MediaWiki 1.28, we plan to offer a fallback between Slovak and Czech languages, as these languages are easier to understand to contributors than English. The fallback is currently committed on our master branch. Than means any message not translated in Slovak on a MediaWiki installation in Slovak will be printed in Czech and inversely. This change has been prepared by Federico Leva. If you approve this change or has concerns with it, your opinion is welcome at https://phabricator.wikimedia.org/T143474. If you don't have a Phabricator account, you can use e-mail and I'll forward your opinion. -- Best Regards, Sébastien Santoro aka Dereckson

1 1

Fwd: Grant for Strengthening Indigenous-Language Wikipedias in Latin America
by Federico Leva (Nemo) 16 Aug '16

16 Aug '16

-------- Messaggio inoltrato -------- Oggetto: [Languages] Wikimedia Grants Proposal - Strengthening Indigenous-Language Wikipedias in Latin America Data: Mon, 15 Aug 2016 18:13:22 -0400 Mittente: Eddie Avila Hi all - I’m reaching out to this list to those that might be interested in the proposal submitted by Global Voices to the Wikimedia Grants program. We’re very much open to improving the proposal and your feedback is welcome during this community input phase. https://meta.wikimedia.org/wiki/Grants:Project/Strengthening_Indigenous-Lan… Looking forward to your thoughts on the Discussion Page or by email: eddie [at] globalvoices [dot] org Thanks! Eddie

1 0

Wiki Conference India 2016 (Chandigarh hackathon)
by Santosh Shingare 12 Aug '16

12 Aug '16

Hello all, I am happy to announce, chandigarh hackathon WCI2016, close with 7 application, which is useful to all community. *1)* *WikiSpeak with native language :* (Hindi) (*Web Application* + *Android Mobile application*). *2)* *Edit Tamil Wiktionary **(Tamil community request)** :* - (*Android application*) *3)* *Audio file upload to WikiData (Punjabi community request) :* (*Android application*) *4) Wikipedia articles on google map :* find wikipedia articles on google map (with latitude and longitude) as per city. *5) OCR (Native Application) *: Convert scanned book copy to Indian language text with google doc (Tested for Hindi and Malayalam). *6) Communication platform[WebRTC] (Web Application)* : Community used this to talk or conference (Audio/video web conferencing application) *7) Notification (Event based)* : showing popup on event eg (If recent changes happen, It will show popup which article was updated) Thank you all participant. who participate in hackathon and deliver a big success *Note : I will share code, links and other details very shortly.* Thank you *Santosh Shingare.* *User:cherishsantosh*

1 0

Wiki Conference India 2016 (Chandigarh hackathon)
by Santosh Shingare 11 Aug '16

11 Aug '16

1 0

Sorting order in categories on mk.wiki
by Bojan Jankuloski 06 Aug '16

06 Aug '16

Hello guys, I wonder if someone can help me get to the right place to submit a request regarding the sorting order in categories on mk.wiki. We have had a problem with the Cyrillic Ј <https://en.wikipedia.org/wiki/Je_(Cyrillic)>, (Ј) which belongs after И <https://en.wikipedia.org/wiki/I_(Cyrillic)> in Macedonian, but our categories place it as the very first letter, even before А. The sorting order is obvious from the article about the alphabet <https://en.wikipedia.org/wiki/Macedonian_alphabet>. Is there someone who could help us with this? It goes without saying that you should be careful not to confuse the letters such as Ј, А and others that are same as in the Latin alphabet, but actually have different coding. Thanks a lot, Bojan -- Бојан Јанкулоски I Bojan Jankuloski Главен програмски раководител I Chief Program Manager Споделено знаење I Shared Knowlege тел. | tel. +38978 282 698

2 1

Improve selection of interwiki links in your country
by Federico Leva (Nemo) 02 Aug '16

02 Aug '16

You may have heard that "compact language links" are expanding across the wikis these days:* https://www.mediawiki.org/wiki/Universal_Language_Selector/Compact_Language… A crucial piece of this system is data on which languages are most spoken in each country: https://www.mediawiki.org/wiki/ULS/FAQ#language-territory Please look at the CLDR data for the countries you know best; if you see something clearly wrong or missing, please follow the "bug" link to report it, and mention some official source. Nemo (*) Since at least 2010 there was a feature request to make the users see more relevant list of interwiki links/interlanguage links on each article. It takes up to 30 days for all articles on a wiki to be updated to the new display, as the cache slowly expires for unregistered users.

1 0

Providing the effective language of messages
by Adrian Heine 28 Jul '16

28 Jul '16

Hi everyone, as some of you might know, I'm a software developer at Wikimedia Deutschland, working on Wikidata. I'm currently focusing on improving Wikidata's support for languages we as a team are not using on a daily basis. As part of my work I stumbled over a shortcoming in MediaWiki's message system that – as far as I see it – prevents me from doing the right thing(tm). I'm asking you to verify that the issue I see indeed is an issue and that we want to fix it. Subsequently, I'm interested in hearing your plans or goals for MediaWiki's message system so that I can align my implementation with them. Finally, I am hoping to find someone who is willing to help me fix it. == The issue == On Wikidata, we regularly have content in different languages on the same page. We use the HTML lang and dir attributes accordingly. For example, we have a table with terms for an entity in different languages. For missing terms, we would display a message in the UI language within this table. The corresponding HTML (simplified) might look like this: <div id="mw-content-text" lang="UILANG" dir="UILANG_DIR"> <table class="entity-terms"> <tr class="entity-terms-for-OTHERLANG1" lang="OTHERLANG1" dir="OTHERLANG1_DIR"> <td class="entity-terms-for-OTHERLANG1-label"> <div class="wb-empty" lang="UILANG" dir="UILANG_DIR">  </div> </td> </tr> </div> </div> This works great as long as the missing label message is available in the UI language. If that is not the case, though, the message is translated according to the defined language fallbacks. In that case, we might end up with something like this: <div class="wb-empty" lang="arc" dir="rtl">No label defined</div> That's obviously wrong, and I'd like to fix it. == Fixing it == For fixing this, I tried to make MessageCache provide the language a message was taken from [1]. That's not too straight-forward to begin with, but while working on it I realized that MessageCache is only responsible for following the language fallback chain for database translations. For file-based translations, the fallbacks are directly merged in by LocalisationCache, so the information is not there anymore at the time of translating a message. I see some ways to fix this: * Don't merge messages in LocalisationCache, but perform the fallback on request (possibly caching the result) * Tag message strings in LocalisationCache with the language they are in (sounds expensive to me) * Tag message strings as being a fallback in LocalisationCache (that way we could follow the fallback until we find a language in which the message string is not tagged as being a fallback) What do you think? [1] https://gerrit.wikimedia.org/r/282133 Thanks, -- Adrian Heine né Lang SOFTWARE DEVELOPER Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30 219 158 26-0 http://wikimedia.de Imagine a world, in which every single human being can freely share in the sum of all knowledge. That‘s our commitment. Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.

5 5

Fwd: Language detection for Special:Search queries
by Federico Leva (Nemo) 20 Jul '16

20 Jul '16

-------- Messaggio inoltrato -------- Oggetto: [discovery] Better search results on wiki via TextCat Data: Tue, 19 Jul 2016 19:42:27 -0600 Mittente: Deborah Tankersley A: A public mailing list about Wikimedia Search and Discovery projects <discovery(a)lists.wikimedia.org> We're happy to announce that after numerous tests and analyses[1] and a fully operational demo[2], the Discovery Team is ready to release TextCat[3] into production on wiki. What is TextCat? It detects the language that the search query was written in which allows us to look for results on a different wiki. TextCat is a language detection library based on n-grams[4]. During a search, TextCat will only kick in when the following three things occur: 1. fewer than 3 results are returned from the query on the current wiki 2. language detection is successful (meaning that TextCat is reasonably certain what language the query is in, and that it is different from the language of the current wiki) 3. the other wiki (in the detected language) has results Our analysis of the A/B test[5] (for English, French, Spanish, Italian and German Wikipedia's) showed that: "...The test groups not only had a substantially lower zero results rate (57% in control group vs 46% in the two test groups), but they had a higher clickthrough rate (44% in the control group vs 49-50% in the two test groups), indicating that we may be providing users with relevant results that they would not have gotten otherwise." This update will be scheduled for production release during the week of July 25, 2016 on the following Wikipedia's: * English [6] * German [7] * Spanish [8] * Italian [9] * French [10] TextCat will then be added to this next group of Wikipedia's at a later date: * Portugese[11] * Russian[12] * Japanese[13] This is a huge step forward in creating a search mechanism that is able to detect - with a high level of accuracy - the language that was used and produce results in that language. Another forward-looking aspect of TextCat is investigating a confidence measuring algorithm[14], to ensure that the language detection results are the best they can be. We will also be doing more[15] A/B tests using TextCat on non Wikipedia sites, such as Wikibooks and Wikivoyage. These new tests will give us insight into whether applying the same language detection configuration across projects would be helpful. Please let us know if you have any questions or concerns, on the TextCat discussion page[16]. Also, for screenshots of what this update will look like, please see this one[17] showing an existing search typed in on enwiki in Russian "первым экспериментом" and this one[18] for showing what it will look like once TextCat is in production on enwiki. Thanks! [1] https://phabricator.wikimedia.org/T118278 [2] https://tools.wmflabs.org/textcatdemo/ [3] https://www.mediawiki.org/wiki/TextCat [4] https://en.wikipedia.org/wiki/N-gram [5] https://commons.wikimedia.org/wiki/File:Report_on_Cirrus_Search_TextCat_AB_… [6] https://en.wikipedia.org/ [7] https://de.wikipedia.org/ [8] https://es.wikipedia.org/ [9] https://it.wikipedia.org/ [10] https://fr.wikipedia.org/ [11] https://pt.wikipedia.org/ [12] https://ru.wikipedia.org/ [13] https://ja.wikipedia.org/ [14] https://phabricator.wikimedia.org/T140289 [15] https://phabricator.wikimedia.org/T140292 [16] https://www.mediawiki.org/wiki/Talk:TextCat [17] https://commons.wikimedia.org/wiki/File:Existing-search_no-textcat.png [18] https://commons.wikimedia.org/wiki/File:New-search_with-textcat.png -- Deb Tankersley Product Manager, Discovery IRC: debt Wikimedia Foundation

1 0

Announcements from Wikimedia Language team
by Niklas Laxström 17 Jun '16

17 Jun '16

The Wikimedia Language team has been assembling monthly reports about language support activities for one year. You can read the latest report at: https://www.mediawiki.org/wiki/Wikimedia_Language_engineering/Reports/2016-… Highlights for May include: Special:Translate got an edit summary field and modernization of web font formats: woff2 is in, eot is out. Due to the nature of our work, the Language team [1] (Amir, Kartik, Pau, Runa, Santhosh, and myself) alone cannot adequately support all the languages of the Wikimedia movement. That is why the report includes work by volunteers. We have bolded the names who we believe are contributing as volunteers. This report focuses on technical activities. You wont find future plans or high level roadmap items on it. There is currently a major omission: the i18n work of MediaWiki core itself. That is lacking because it is more difficult to filter those activities and also because we have not had much time for MediaWiki core i18n work. To acknowledge the work of volunteers and to support them better, the Language team released a statement of intent for code review [2] about six months ago. To summarize: we attempt to review patches not by us within a week, and patches stalled due to no updates after review for three months will be abandoned -- unless we feel they are worth fixing ourselves. When we released the statement, we also agreed to reduce the existing backlog of open patches. The results so far are positive, even though it is easy to find examples where we have not been able to follow our intent. Translate extension had 35 open patches when we started in February -- at end of May it had only 12 open patches [3]. Universal Language Selector had gone from 10 to 6, and fewer of them unreviewed. Content Translation had gone from 15 to zero. Our jquery repositories in GitHub have not fared as well, but we hope to achieve similar results there in the future. We excluded many repositories from the statement of intent in the fear that we would add too much of a burden to ourselves. To our delight, except MediaWiki core i18n, all those repositories have had swift reviews and I count only two open patches in them. - Niklas (on behalf of the Language team) [1] https://www.mediawiki.org/wiki/Wikimedia_Language_engineering [2] https://www.mediawiki.org/wiki/Wikimedia_Language_engineering/Code_review_s… [3] The numbers change constantly. As of 2016-06-17 Translate has 23 open patches, but only 10 of them not from our team. Universal Language Selector has 13 patches, 5 of them not from our team. Content Translation currently has 6, one of them not from our team.

1 0

[x-post] WMF Language team office hour and online meeting on June 15th, 2016 (Wednesday) at 1300 UTC
by Runa Bhattacharjee 13 Jun '16

13 Jun '16

[x-posted announcement] Hello, The next online office hour session of the Wikimedia Language team is scheduled for next Wednesday, June 15th, 2016 at 13:00 UTC. 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 (on the event page <https://plus.google.com/u/0/events/cd1bfs8111cbd4lmegqthma65c8>) if you would like to join in the Hangout. The IRC channel #wikimedia-office and the Q&A channel for the youtube broadcast will be open for interactions during the session. Our last online round-table session was held in March 2016. You can watch the recording here: https://www.youtube.com/watch?v=0FrowkpBEnQ I would also like to mention that our team is currently inviting feedback for Content Translation via a community consultation <https://www.mediawiki.org/wiki/Content_translation/Community_Consultation_J…> which will conclude on June 22nd, 2016. We will make a note of any related feedback received during this session and review it along with the other comments received on-wiki. Please read below for the event details, including local time and do let us know if you have any questions. Thank you Runa == Details == # Event: Wikimedia Language team's office hour session # When: June 15, 2016 (Wednesday) at 13:00 UTC (check local time http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160615T1300) # Where: https://plus.google.com/u/0/events/cd1bfs8111cbd4lmegqthma65c8 and on IRC #wikimedia-office (Freenode) # Agenda: - Updates from the Language team and Q & A. - Content Translation community consultation: https://www.mediawiki.org/wiki/Content_translation/Community_Consultation_J… -- Language Engineering Manager Outreach and QA Coordinator Wikimedia Foundation

2 4

← Newer
1
...
8
9
10
11
12
13
14
...
57
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Mediawiki-i18n