Meta talk:Translate extension
Thank you for this page. I don't understand a thing: is this going to be only a help page, or is it going to be also the draft of the new translation process guideline? If this is the case, we could start from here to expand the workflow sections; this would also help identify issues. Siebrand told me that the extension is ready for use despite some improvement needed, but perhaps there's some anticipated use e.g. related to the fundraising for which a process is aleady in place/decided? Nemo 21:11, 30 October 2011 (UTC)
- The purpose of this document is to document the use of the Translate extension for translations on Meta. The existing community is very much ingrained with the current way of working. Spelling out what Translate allows for is intended to get some grip on what is a different way of working.
- Expanding this document is very much helpful as it allows for thinking through the complete process including parts like the translator template.. This CAN link to the Translate special page for instance OR it can link to a portal page for a language like we have it on translatewiki.net (my recommendation).
- It is realistic that texts will be translated through the Translate functionality. This has been set up for a single project; fundraising but not for others like the monthly reports.
Thanks, GerardM 08:42, 31 October 2011 (UTC)
I don't understand how this section is relevant: is it just a general info about the extension or does it apply to Meta as well? Are we going to hire professional translators on Meta? Or are you suggesting that users should use such "professional tools" (gettext?)? Thanks, Nemo 21:11, 30 October 2011 (UTC)
- The intention is to identify our past willingness to include modifications that allow for the use of external tools. As far as I know we do not plan to hire translators. We have had professional translators come along and do some work. Typically they backed out because they felt their time was wasted. GerardM 08:44, 31 October 2011 (UTC)
Publication of translations outside of Meta 
When translations of texts are to be published on other wikis, there may be a need for a process similar to the LocalisationUpdate functionality that ensures publication. As a rule, publications are more likely to be read locally than on Meta. GerardM 08:32, 31 October 2011 (UTC)
I've been thinking too long about it: at last I'm starting to write it, and design a migration strategy for the whole Meta. jsoby promised to contribute starting today; we should finish the first draft this week (too early to comment now), then input and discussion will be much appreciated and we hope it wil be a basis for useful discussions with l10n team and other developers at FOSDEM (very soon) so that we can start implementing it in a few weeks (perhaps after a new workshop). Nemo 10:02, 1 February 2012 (UTC)
Images on RTL languages 
Hi. I just tested the trasnlation extension on Wikimedia_Highlights,_February_2012/ar. As you notice, the translation extension adds images to the translated page without considering that images in RTL wiki pages need to be aligned to the "left" of the page. Would it be possible to consider solving this problem by customizing the extension code for RTL? --Ciphers (talk) 01:52, 23 March 2012 (UTC)
- Ask the translation administrator to include the |right or other relevant markup in the translated strings. --Nemo 20:23, 31 August 2012 (UTC)
Moving forward 
More than a year has passed since this page was mostly written, it's time to move forward. Thanks to massive work by a few translation administrators I don't need to tell you the names of ;) , dozens of pages (often very big) have been migrated or added (189 translatable + 99 discouraged), but it's still only a fraction of our pages. Sadly, in mw:Summer of Code 2013 nobody applied for the project Tools for mass migration of legacy translated wiki content, but our community has gained lots of experience with the extension in the last year. What we need, I think, is some programming:
- make a list of the pages to make translatable/migrate,
- find out who's going to help (translation administrators? a group of them, maybe under transcom hat?),
- decide a schedule (like, migrate a first list of translation pages within a year, 50 per week).
Then we can see, week by week, how we're doing, what we need from each of us (for instance I've slacked...), what we need to recruit help for, etc. --Nemo 07:11, 13 May 2013 (UTC)