Translators-l April 2013

translators-l@lists.wikimedia.org

7 participants
7 discussions

Help update invalidated translations on Meta
by Federico Leva (Nemo) 28 Apr '13

28 Apr '13

As a result of a recent software update, a change requested by some Wikidata users has been enabled on Meta.[1] Now the outdated translations, marked by the !!FUZZY!! markers in translation units pages, are hidden from the translation pages: where you used to see pink-coloured paragraphs, there's now the English text. We have about 700 such translations on Meta, because some hard-working users are migrating several pages to Translate: updating them is often very quick, and you'll restore readers with sometimes crucial pages in their language; just remember to remove the !!FUZZY!! tag when you're done. You can see the pages that need updating LanguageStats for your language: <https://meta.wikimedia.org/w/index.php?title=Special:LanguageStats#sortable…> Thanks, Nemo [1] https://bugzilla.wikimedia.org/show_bug.cgi?id=44328

1 1

Request: French FAQ :)
by Joseph Seddon 27 Apr '13

27 Apr '13

Hey guys, I could really do with some help from some french speakers. I am trying to give the FAQ on foundation an update in the major languages and the one I am struggling with is french. I know its a very big document but if people have the time then your help would be really appreciated. Here's the link: http://meta.wikimedia.org/wiki/Fundraising_2012/Translation/FAQ/fr Thanks guys :) -- -- Joseph Seddon Fundraiser Translation Coordinator Wikimedia Foundation

3 3

Fwd: Deploying alpha of VisualEditor to non-English Wikipedias
by James Forrester 23 Apr '13

23 Apr '13

I believe my first message didn't go through for some reason; re-sending. Yours, James. ---------- Forwarded message ---------- From: James Forrester <jforrester(a)wikimedia.org> Date: 18 April 2013 18:35 Subject: Fwd: Deploying alpha of VisualEditor to non-English Wikipedias To: translators-l(a)lists.wikimedia.org Forwarding to highlight the request for translators for the VisualEditor interface, in particular into Arabic and Hindi. ---------- Forwarded message ---------- From: James Forrester <jforrester(a)wikimedia.org> Date: 18 April 2013 17:32 Subject: Deploying alpha of VisualEditor to non-English Wikipedias To: Coordination of technology deployments across languages/projects <wikitech-ambassadors(a)lists.wikimedia.org> All, TL;DR: VisualEditor will be deployed on 14 new Wikipedias next week as an opt-in alpha. Your assitance is requested to inform your wikis about this and help get the software translated. Next week (on 25 April) we are going to deploy the alpha opt-in version of the VisualEditor to some non-English Wikipedias in the same way that it has been on the English Wikipedia since December 2012. This will let users get familiar with the VisualEditor, give us feedback on what works and what is broken, and help us prioritise further work ahead of the planned deployment as a 'default' editor for all users which we intend to do in a few months' time. Due to a number of issues we have been unable to release VisualEditor to non-English wikis until now, and we would very much like to get some great feedback from as many wikis as possible - especially for extended Unicode and RTL languages, but also other languages. Does the VisualEditor work in your language? Does it gel with your wiki's workflow? The initial languages we want to target are the "top 10" Wikipedias by way of scale - de, nl, fr, it, ru, es, sv, pl, ja - plus selected others to help us discover issues we anticipate: ar, he, hi, ko, zh. These will let us test most of the locales we are concerned about. If this goes well, we hope to deploy the opt-in alpha to all Wikipedias. Please tell your wiki colleagues that this is coming, especially if your wiki is in this list! Additionally, you can see how fully-translated the software is into your language in the stats at TranslateWiki.Net[0] - please encourage wiki colleagues to help translate the messages ahead of the deployment! As a note, we have just updated the VisualEditor integration so that the "Edit" tab goes to VisualEditor, and there is an "Edit source" tab to go to the wikitext editor. This change (which affects the English Wikipedia opt-in deployment and MediaWiki.org as well as the new deployments mentioned above) moves the way that VisualEditor integrates with the wiki's workflow to be closer to how it will appear when it is the 'default' editor. It is still easy to use the wikitext editor if that is what you want to do - the "Edit source" tab (at least for now) will be "above the fold" and not in the drop-down menu on Vector. [0] - https://translatewiki.net/w/i.php?title=Special%3AMessageGroupStats&x=D&gro… Happy to answer any questions you might have! Yours, -- James D. Forrester Product Manager, VisualEditor Wikimedia Foundation, Inc. jforrester(a)wikimedia.org | @jdforrester -- James D. Forrester Product Manager, VisualEditor Wikimedia Foundation, Inc. jforrester(a)wikimedia.org | @jdforrester -- James D. Forrester Product Manager, VisualEditor Wikimedia Foundation, Inc. jforrester(a)wikimedia.org | @jdforrester

3 2

FAQ - French
by Joseph Seddon 19 Apr '13

19 Apr '13

I was wondering if we could get some french translators to take a look at the following page: http://meta.wikimedia.org/wiki/Fundraising_2012/Translation/FAQ/fr The notification didn't seem to get a lot of response. Thanks Guys :) Seddon -- -- Joseph Seddon Fundraiser Translation Coordinator Wikimedia Foundation

1 0

Fwd: Temporarily disabling l10n update
by Federico Leva (Nemo) 11 Apr '13

11 Apr '13

<https://www.mediawiki.org/wiki/Localisation#Update_of_localisation> will not be true for a short while. Nemo -------- Messaggio originale -------- Oggetto: [Wikitech-ambassadors] Temporarily disabling l10n update Data: Wed, 10 Apr 2013 13:01:12 -0700 Mittente: Rob Lanphier Hi folks, We've had at least a couple of site outages which we believe are due to l10nupdate. The root cause is identified in a fairly old ResourceLoader bug that seems to be biting us a little harder than it normally does: https://bugzilla.wikimedia.org/show_bug.cgi?id=27320 Disabling l10nupdate means that changes from Translatewiki.net will not propagate to our websites as quickly as they normally do. Depending on how long it takes us to fix this, it could be multiple days. Brad Jorsch is going to take a closer look at this issue today/tomorrow, and hopefully identify the root cause. If he's able to find the cause quickly, we may not need to disrupt the service, but we're going to plan for the worst here. Thanks (in advance) for your patience! Rob _______________________________________________ Wikitech-ambassadors mailing list Wikitech-ambassadors(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors

1 0

Multilingual links, for external hyperlinks
by Brian McConnell 10 Apr '13

10 Apr '13

Hello. i am the founder of Der Mundo (www.dermundo.com), a multilingual link sharing and cross language search service. I thought our approach might be useful to Wikipedia for external links, as a way of automating translation when linking to foreign language links (for the reader). It would be easy enough to implement a multilingual link in Wikipedia using language detection (from request headers) and redirection. If there's interest in doing so, I would be happy to share information about the machine translation tools in use, and how to link to them in an automated fashion. Best regards, Brian McConnell Der Mundo PS - feel free to check out Der Mundo, we're looking for testers. It's a handy way to share interesting web pages, blog posts, etc with a global audience.

1 0

New translation editor + Fwd: summary of WMF engineering in March: Visual editor, notifications, mobile, & more
by Federico Leva (Nemo) 10 Apr '13

10 Apr '13

Translations needed! <https://www.mediawiki.org/w/index.php?title=Special:Translate&group=page-Wi…> After you translate it, you may also want to link it from the wikis in that language. Among the news: the new translation interface was enabled by default last wednesday. <https://blog.wikimedia.org/2013/03/25/redesigning-the-translation-experienc…> There are some bugs being worked on, but more reports of specific problems or things you're unhappy with are very welcome, see <https://translatewiki.net/wiki/Thread:Support/So_called_"new"_interface_completely_unusable/reply_(7)>. Bugzilla is quickest way to get a response, but translatewiki.net is also quite safe, see that thread. :) Nemo -------- Messaggio originale -------- Oggetto: [Wikitech-ambassadors] summary of WMF engineering in March: Visual editor, notifications, mobile, & more Data: Mon, 08 Apr 2013 23:53:13 -0400 Hi, The report covering Wikimedia engineering activities in March 2013 is now available. Thanks to Guillaume Paumier and Tilman Bayer and the engineers who helped me put this together. Wiki version: https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2013/March Blog version: https://blog.wikimedia.org/2013/04/04/engineering-march-2013-report/ We're also providing a shorter, simpler and translatable version of this report that does not assume specialized technical knowledge. It's onwiki at https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2013/March/summ… and I thought you might like to have it in an email. As always, feedback is appreciated about the usefulness of the report and its summary, and on how to improve them. -- Sumana Harihareswara Engineering Community Manager Wikimedia Foundation *This content is prepared for inclusion in the March 2013 Wikimedia Foundation report<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Report,_March_2013>. It is a shorter and simpler version of the full (and English-only) Wikimedia engineering report for March 2013<https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2013/March>that does not assume specialized technical knowledge.* VisualEditor <https://www.mediawiki.org/wiki/VisualEditor> *(Accessible introduction to what the Visual Editor is<https://blog.wikimedia.org/2012/12/07/inventing-as-we-go-building-a-visual-…>)* In March, part of the team worked on infrastructure for the major new features that they'll be adding in the coming months. We aim for VisualEditor to be the default way all users edit our sites by July 2013, so it needs to let everyone edit the majority of content without needing to use the usual "wikitext" editor. This will mean adding support for references, (at least) basic templates, categories and images, each of which is a very large piece of work. This month the team primarily worked on draft designs and initial code to ensure users can edit categories and templates. The Visual Editor team undertook its first ever "Quarterly Review<https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings/Quarterly_r…>", whose slides<https://www.mediawiki.org/wiki/File:VisualEditor-Parsoid_-_2012-13_Q3_quart…>detail these designs, the work done to date and expectations for the near future. The alpha version of VisualEditor on mediawiki.org and the English Wikipedia was updated twice, adding better input and selection support, fixing a number of bugs, and restructuring the back-end so that the new features will be simpler to create. The Parsoid <https://www.mediawiki.org/wiki/Parsoid> team (who are creating the parsing program <https://en.wikipedia.org/wiki/Parsing> that translates plain wikitext into HTML annotated for easy editing, and *vice-versa*) continued writing specifications, fixing bugs, and improving how Parsoid deals with different human languages, newlines and whitespace, and transclusion. And late in March, C. Scott Ananian joined us as a contractor. Welcome! Editor engagement <https://www.mediawiki.org/wiki/New_editor_engagement> In March, the editor engagement features team worked on three projects: Notifications <https://www.mediawiki.org/wiki/Echo_%28Notifications%29>, Article Feedback <https://www.mediawiki.org/wiki/Article_feedback/Version_5> and Flow <https://www.mediawiki.org/wiki/Flow>. For Notifications <https://www.mediawiki.org/wiki/Echo_%28Notifications%29>(formerly called 'Echo'), we developed a range of new features, including: the 'thanks<https://www.mediawiki.org/wiki/Echo/Feature_requirements#Thank_you_notifica…>' and 'user rights<https://www.mediawiki.org/wiki/Echo/Feature_requirements#User_rights>' notifications, as well as HTML email notifications<https://www.mediawiki.org/wiki/Echo/Feature_requirements#HTML_email_digests>. We also started to collect our first metrics<https://www.mediawiki.org/wiki/Echo/Metrics>and prepared a socialization plan for our upcoming release on the English Wikipedia later this month. You are welcome to test our work-in-progress here on MediaWiki.org <https://www.mediawiki.org/wiki/Echo/Testing>. For Article Feedback<https://www.mediawiki.org/wiki/Article_feedback/Version_5>, we deployed a new version of the tool on the and, for evaluation by their communities. Final features include 'discuss on talk page<https://www.mediawiki.org/wiki/Article_feedback/Version_5/Feature_Requireme…>' and 'auto-archive<https://www.mediawiki.org/wiki/Article_feedback/Version_5/Feature_Requireme…>'. The tool was temporarily turned off on the English Wikipedia, where we expect to re-deploy it on an opt-in basis as soon as practical, as described on this talk page<https://en.wikipedia.org/wiki/Wikipedia_talk:Article_Feedback_Tool/Version_…>. Design work continued on Flow <https://www.mediawiki.org/wiki/Flow>, the upcoming user-to-user discussion system. We continued creating a 'Portal' that will engage discussion about Flow at three locations (mediawiki.org<https://www.mediawiki.org/wiki/FlowPortal>, meta, and the English Wikipedia), and performing research<https://www.mediawiki.org/wiki/Flow_Portal/Research>. The Editor Engagement Experiments<https://www.mediawiki.org/wiki/Editor_Engagement_Experiments>team largely placed other projects – such as guided tours <https://www.mediawiki.org/wiki/Guided_tours>, EventLogging<https://www.mediawiki.org/wiki/EventLogging>, and others – on hold to focus on two key initiatives: the "Getting Started<https://www.mediawiki.org/wiki/Extension:GettingStarted>" process for onboarding new Wikipedians<https://www.mediawiki.org/wiki/Onboarding_new_Wikipedians>, and on making the redesign of account creation and login<https://www.mediawiki.org/wiki/Account_creation_user_experience>a permanent, internationalized part of MediaWiki core. For the Getting Started project, the team launched a new version on English Wikipedia, which included a new landing page with additional types of tasks suggested for brand new editors to try. The list of tasks is now generated by a basic recommender system<https://www.mediawiki.org/wiki/Onboarding_new_Wikipedians/Recommender_system>built by Ori Livneh, which gathers, filters, and delivered a fresh list of tasks automatically for every editor. This new backend paves the way for releasing the "getting started" feature on other projects, after we've completed data analysis and testing to understand which kinds of tasks are ideal for first time editors. Additionally, Matt Flaschen collaborated with the Editor Engagement Features team to build notifications<https://www.mediawiki.org/wiki/Echo>to welcome new editors and invite them to contribute via the Getting Started. For the account creation and login work, S Page, Munaf Assaf, and the rest of the team rebuilt our design to work with MediaWiki core, and solicited reviews from outside the team. We currently plan to launch both interface redesigns on an opt-in basis in April, to have editors test the localization and other functional aspects of the forms via a URL parameter, before we enable them as default. Mobile <https://www.mediawiki.org/wiki/Wikimedia_Mobile_engineering> We have a stable version of the mobile-optimized website, which everyone on a smartphone uses by default, and we have a beta version that logged-in Wikimedia users can opt to use to see features we're still building. When functionality is polished enough, we promote it from the beta site to the stable site. In March, we added the ability to easily upload<https://blog.wikimedia.org/2013/03/11/putting-commons-contributions-in-your…>a lead image<https://blog.wikimedia.org/2013/03/28/add-an-image-to-this-article-uploads-…>to articles that lack one in the stable version of the mobile site. We also helped users by giving them a temporary fix to an issue we discovered that made logging in hard or impossible for some users of newer mobile web browsers; that problem had prevented a number of users from being able to upload photos via the mobile site. We are now well on our way to reach our goal of 1000 unique uploaders/month by the end of June 2013. Check out the mobile app dashboard <http://mobile-reportcard.wmflabs.org/> to see mobile contributions via the website and via apps. Also: we've added thumbnails of lead images from articles in the mobile watchlist view, as well as a "last modified" timestamp on articles in the stable version of the mobile site. We are currently focusing on some performance enhancements for the mobile site. In April we will graduate the "uploads dashboard" feature from beta to stable, will further refine our photo upload features, and will let beta site users see and use a feature to identify articles on subjects near your current location. The Mobile team that makes dedicated Wikimedia mobile apps have created an initial version of the Commons photo uploader app for Android; it is available for download in Google Play. The iOS version is still in beta, but should be available in the Apple app store next month. In March, Wikipedia Zero (explanation<https://wikimediafoundation.org/wiki/Mobile_partnerships>) added new telecom partners (such as Axiata Group Berhad<https://blog.wikimedia.org/2013/03/19/axiata-wikipedia-zero-partnership/>), fixed some technical problems, and helped teach new staff how we do things. We also won an SXSW Interactive "Activism" award for Wikipedia Zero<https://blog.wikimedia.org/2013/03/13/wikipedia-zero-wins-2013-sxsw-interac…> . Max Semenik, Arthur Richards and Faidon Liambotis held an OpenStreetMaps mini-hackathon at Open Source Days 2013 in Copenhagen<https://www.mediawiki.org/wiki/Events/Wikimedia_Mapping_Event_2013>. During the event, they agreed on an implementation strategy for a future WMF mapping cluster. The cluster would serve OSM "tiles" and thus help integrate OSM functionality better into Wikimedia sites, and help with our mobile apps which already make use of OSM data. Other useful engineering news - Lua scripting<https://blog.wikimedia.org/2013/03/11/lua-templates-faster-more-flexible-pa…>has launched on all WMF wikis, making templates faster and making pages more flexible. You can read that post to understand what to do on your wiki to take advantage of this, and you can also read about the implications for Wikimedia's future<https://blog.wikimedia.org/2013/03/14/what-lua-scripting-means-wikimedia-op…>. - We redesigned the Translate interface<https://blog.wikimedia.org/2013/03/25/redesigning-the-translation-experienc…>and made other progress<https://blog.wikimedia.org/2013/03/12/new-release-of-the-mediawiki-language…>on translation and language-related tools. - We have fresh, friendly instructions on reporting a technical problem<https://blog.wikimedia.org/2013/03/18/how-to-create-a-good-first-bug-report/>and invite you to help prioritize problems to fix<https://blog.wikimedia.org/2013/03/19/help-wikimedia-squash-software-bugs/>. - Our designers are collaborating with the Noun Project<https://blog.wikimedia.org/2013/03/13/the-noun-project-and-the-wikimedia-fo…>towards creating an "Encyclopedia Collection" of free icons. - Our Operations group (the systems administrators who keep our servers running) has started a twice-monthly meeting with other engineering teams, to keep communication flowing about requirements and possible upcoming problems or server needs. - The User Metrics API <https://www.mediawiki.org/wiki/User_Metrics>launched; it's a service that allows researchers to perform cohort analysis <https://en.wikipedia.org/wiki/Cohort_study> on various data sets, making it easier to measure the effects of programs and platform experiments among discrete sets of users. The Analytics group<https://www.mediawiki.org/wiki/Analytics>, which works on software to make statistics about Wikimedia available, is currently working on improving the web-based user interface, to make it available for use outside of Wikimedia Foundation staff in the coming months. _______________________________________________ Wikitech-ambassadors mailing list Wikitech-ambassadors(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Translators-l April 2013