Meta talk:Babylon/Archives/2014

Improve the template translation

I experimented a new workflow for the translation of the templates, inspired from Commons and {{Translatable template}}. Namely, for a template called Template:Template name:

1. the template can be translated using the Translate extension, so the translations go to (e.g.) Template:Template name/hu, and
2. it can be specified in the template if it must be displayed in the user interface language (useful for Commons for instance) or in the page language (useful for "content" pages translated, on Meta or Commons), and
3. the user of the template can simply use it as {{Template name}} and the "correct" language is used (page or user interface); s/he can also retrieve a specific language version with (e.g.) {{Template name/hu}}.

I created a small experiment to show how all that works: Template translation experiment. I explained in the bottom of the page how it technically works.

What do you think about? (personally, I’m super happy of this :)

PS: I’m not translator admin here on Meta; could a translator admin activate the translation on the three pages: Template translation experiment, Template:Template translation experiment (page language), and Template:Template translation experiment (user language)? I will then translate into French for demonstrating the experiment. No further admin action will be needed; I already tested all that on a local test wiki.

~ Seb35 [^_^] 19:55, 23 December 2013 (UTC)

Marked for translation, but disabled for all languages except French. --MF-W 19:57, 23 December 2013 (UTC)

Thanks! Template:Template translation experiment (user language) and Template translation experiment don’t have the "/en" version (although they should). Perhaps some time or cache purging is needed (I try unsuccessfully the latter). ~ Seb35 [^_^] 21:09, 23 December 2013 (UTC)

For information, the problem encountered just above is bug 54579 (and associates). So this type of template translation should not be widely used before this bug is resolved (and bug 46925 also). I thought about activating this template tranlation on Meta:Sandbox/Please do not edit this line but even on this page Meta:Sandbox/Please do not edit this line/en doesn’t exist. ~ Seb35 [^_^] 10:22, 13 January 2014 (UTC)

Translation interface

Hi, I was advised to mention this here, my original post is at Help Forum#Translation interface. I have no idea how the new interface is supposed to work, I only know that I can't, well, translate things with it. Maybe someone can help. — Pajz (talk) 18:13, 1 December 2013 (UTC)

You can add &tux=0 to the end of the translation URL to get the better interface. Unfortunately, it will be removed soon. It's the only way to add edit summaries and change the status ("Ready"). PiRSquared17 (talk) 18:16, 1 December 2013 (UTC)

Thank you, PiRSquared17, let's move this here. Thanks a lot for your tip, I've done just that and I could translate again without any problems. However, if indeed this will be removed (whyever), I have no idea how I am supposed to contribute translations in a productive way (before you posted the info about how to get the old interface back, I eventually clicked on each message to retrieve the number of the item and then manually opened the message in a new window). Doesn't it work in Chrome? Am I the only one with these problems? — Pajz (talk) 18:19, 1 December 2013 (UTC)

Pajz, just for curiosity, what platform are you using? The new interface was not designed for screens under 1300 or so pixels wide nor for low-quality connections (which is sad), do you happen to have one of those? I, too, am almost forced to use the traditional interface because of a 1024x768 screen. --Nemo 18:26, 1 December 2013 (UTC)

Thanks for the reply. I'm regularly not at home and often use GSM to access the web (as today), so my connection here was / is currently low-quality indeed. I'll have to try again with a better connection. (Screen resolution is 1366x768.) Hmm. — Pajz (talk) 18:46, 1 December 2013 (UTC)

Now Special:Translate loads fast again, as Nikerabbit has fixed bug 53748 by making some internal requests it loads one or two order of magnitudes faster (!!) \o/. Workflow state selector now loads again with tux=1 and in general loading feels faster; group selector takes about 1 s when clicked. Now we can proceed to add boatloads of new translatable pages without worries. ;-) --Nemo 09:06, 3 December 2013 (UTC)

Re "it regularly doesn't save the edit", see also Bugzilla:53963 and the thread Translation extension just does not save translations above. Regards, Tbayer (WMF) (talk) 13:52, 3 December 2013 (UTC)

Yes, it loads fast, and currently I'm also using a fast internet connection. But it still doesn't properly save my edits. I made a change >1h ago, clicked on save, then the right column said something like "saving...", but it never did. I then searched for another message, made a change, clicked on save, nothing happened, clicked again on save, and then both edits were saved at the same time (https://meta.wikimedia.org/w/index.php?title=Privacy_policy/de&curid=2331082&diff=6670943&oldid=6642480). (Including a mistake: The first message is identical to the English default, "Definitions", instead of "Definitionen" [German]. I cannot completely rule out that I have made a mistake when saving, but I doubt it.) — Pajz (talk) 20:27, 9 December 2013 (UTC)

I don't even know how that worked, btw. I have only one contribution in the Translations namespace today so far, yet two messages were apparently changed (see the diff linked to above)?!? — Pajz (talk) 20:30, 9 December 2013 (UTC)

Still the same issues. I opened https://meta.wikimedia.org/w/index.php?title=Special:Translate&language=de&filter=&action=translate&group=page-Confidentiality+agreement+for+nonpublic+information, then checked the first item on the list, changed it, clicked on "Save translation" -> nothing happened. I checked my list of contributions and found that the edit was indeed saved. I went on to the second item, changed it, clicked on "Save translation" -> the item collapsed and it read "saving..." forever. In fact, nothing was saved. Just like last time when I used a different computer. — Pajz (talk) 15:02, 4 January 2014 (UTC)

That's sad to hear, especially because I have no way to help. You can only try appending &debug=true to the URL and opening the error/developer console (often at ctrl+shift+J) hoping to find some information there which you can then post in a bug report together with thorough info on your system. --Nemo 15:11, 4 January 2014 (UTC)

thanks, mediazilla:59648, — Pajz (talk) 20:36, 4 January 2014 (UTC)

Since a few days I noticed that the issue described here as well as in mediazilla:59648 no longer appears. At this moment (at least for me working on different Windows 7 sytems and using different browser versions of Firefox and Google Chrome) this issue seems to solved. If other users can confim this, the related bug could be closed.

P.S. Indeed the described issue made traanslations for me here on meta for some time nearly impossible.--Robby (talk) 09:24, 26 January 2014 (UTC)--www.karincaegitim.com

Grants:Start redesign going live on 1/30. updates will continue through 2/7

I've been working on a major redesign and expansion of the Grants:Start page here. The redesign contains the current matrix of grant programs, as well as a bunch of new information about the Grantmaking department, committees, process, goals, etc which wasn't available on-wiki before, or was hard to find. I plan to copy the page content over to the Grants namespace (and move all the sub-pages) on Thursday 1/30. Next week, User:Heatherawalls and I will continue to make refinements: there will probably be some significant changes made to both the design and the content during that time. When I copy the content over, it will remove the existing translation tags. I'll re-add them at the end of next week, when the design and content are more stable, and then re-mark the page for translation. In the meantime, the existing translations of Grants:Start will continue to be useful, since the details are still correct. But probably best to hold off on any new translation work until at least 2/10. Cheers, Jmorgan (WMF) (talk) 20:03, 28 January 2014 (UTC)

Why translating categories

Yes translating the categories is something new, it help categorizing many pages and avoids overpopulating the English source categories. I have initiated it first on a single category to try, then on a few ones, then I'm filling the most used ones. Translating them is still optional, but can be done in one click (but copying the proposed English name), but if you translate it, translate it completely and do not revert to English, and do not append language code suffixes as they are undesirable in page titles viewed.

But translating categories will also help users because they will be able to search for categories as well as in pages, within the search tool, and in their own language ! Visitors will then get a more global view about what is available in their own language on Meta, and the number of available translations will improve, and this will be beneficial for the global community of users (MEta is insufficiently visited by users except English readers, so decisions ae taken here by ignring the rest of the world that do not understand at all waht is discussed here, or how projects are managed globally).

Translatable categories also helps creators of contents on Meta, because they don't have to browse within categories overpopulated with hundreds or thousands translated pages. It was becoming a problem on categories frequently updated (e.g. Category:Tech News which is now easily navigatable, in English like in other languages in their own categories.

Categories also provide immediate synthetic statistics about which pages are at least partially translated for a given language, in one click on Category:Tech News/Translations you can know which languages are the most frequently translated, you can see the msising untranslated issues, translators can find a job to do there. There's also the special translation group "Categories" where you can easily find a list of categories whose titles that can be translated very fast.

If you find a red link on a category at bottom of content pages, now users can follow it and it will open the Translate tool to create the 2 or 3 needed items.

Categories can still be managed in articles, using the {{tlx|Langcat|{{subst:PAGENAME}} appended immediately to the English category name (keep the sort key simple in English, you don't need to change it, it will be the same sort key in all translated categories for the same source page, so their contents are easily comparable).

If you want to change the structure of categories, you only need to do it in the English base category (all other categories will be updated once a Translation admin will mark the category again for translation). You don't have to visit 200 categories and update them individually. All translated categories will also have updated descriptions where needed (but most categories need only a single paragraph to describe what they contain). You'll find examples already filled for most Wikimedia-supported languages in Category:Community.

The older structure used for translations (using the category with 2 or 3 capital letters for the language code) cannot work reliably (over time, it has become an unmanaged mess and many pages are created without it and are now difficult to adapt for translation, every topic is mixed in those categories) and as simply as with translated categories. especially now that we have support for the "Special:MyLanguage/" prefix to find matching pages in user's language. This prefix is used by the utility template {{Ll|full pagename in English|description in the current content language}}. But most translatable pages will hide the full page name in English and the prefix in a "tvar")

verdy_p (talk) 15:46, 8 February 2014 (UTC)

Translations of the ToU amendment banner

See Talk:CentralNotice/Calendar#ToU_amendment_banner. If any translator was notified in advance of the need to translate and review this banner, shown for a week to all unregistered users of all projects, I'd be curious to know there. --Nemo 13:39, 27 February 2014 (UTC)

Fix the Greek banner ASAP

Is there any way/anyone to commit the existing translation of the ToU change banner, or else deactivate the greek version? It was vandalised three days ago and fixed today, "Stfu" is on display on the wiki ALL DAY today - Badseed (talk) 20:11, 27 February 2014 (UTC)

@Badseed: Should be fixed. @Jamesofur and Jalexander: Please be more careful. Badseed, in the future, please notify ASAP. PiRSquared17 (talk) 20:18, 27 February 2014 (UTC)

@PiRSquared17: Thank you very much! - Badseed (talk) 20:20, 27 February 2014 (UTC)

Title-related magic words on translations

I realised the magic words as {{SUBPAGENAME}} and the whole family related to page titles would probably give unintended results on translated pages: one could expect the same value on the translatable page and the translated pages, for simplicity of use and for easier activation of the Translate extension on old pages.

So I created {{SUBPAGENAME-translation}} which results in the last non-language-tag subpage name: on both "Example/Page" and "Example/Page/hi" it will return "Page".

What do you think about that? Is the name of the template easy to remember? (I thought about SUBPAGENAME2 or SUBPAGENAME-mul).

~ Seb35 [^_^] 13:37, 22 January 2014 (UTC)

Actually we already have now the logic implemented in categories (using Template:Langcat) and with the "Special:MyLanguage/" prefix. Most translations are in the process of being migrated to the new Translation extension system. This is "titanesque", but huge progresses have already been done.~

Long reply follows (TL:DR).

When I have converted pages, I took care of keeping most existing translations found immediately after conferting them, using the page history to retrieve the existing strings, or using the translation memory (when they match at 100% or if I can find translations for example in Wikipedia categories liked from Wikidata).

We don't need new templated for getting subpagenames (notably because they are much more tricky than what you think)

I have never found any situation where it would be necessary to use your template (except possibly for transition, with pages still using the old manual system, something I take great care to avoid breaking links).

During this conversion I discovered lots of tricks (and sometimes this required converting pages in several steps using different methods until they can follow the new Translate system everywhere.

Some of the most tricky cases involve:

• translatable pages that transclude translatable pages. For this case the existing Template:TNT could not work and I documented it, and created the variant TNTN instead (which does not perform the template expansion itself, to avoid recursion in TNT) but only returns the resolved page/template name, to be expanded externally with its parameters also provided externally.
• complex templates which would have become extreley tricky to edit with the translate tags mixed everywhere : for them I converted these templates to use a "/layout" subtemplate which keeps all the trick wiki code, except translation of strings that are passed by parameter value from a translatable base template containing only these strings
• templates used that were autotranslated: depending on cases, they used the content language of the current page (see Template:Pagelang), but some other templates (most often status banners for editors) use the user's preferred language independantly of the page's content language. The user's UI language is returned from Template:uselang, which is almost like (but not completely) the "int:lang" quirks, with some exceptions
• directionality: beware of occurences of "left" and right" in CSS styles, in image alignment, in text alignment in table cells. The template:dir can be useful for that, but it needs a language code if it's not the content of the current page (so these templates receive a parameter that I have consistently named "uselang" that could optionally be passed to select another language, including the current user's UI language)
• BCP47 conformance for HTML : some Wikimedia language codes are deprecated.
  • deprecated codes (though not invalid or BCP47) include codes used by variants (that have been blocked in the translate tool, because they are now handled by transliterators, or the variant codes are not used by translations themselves but for other localization data such as date formats).
  • deprecated codes which are not invalid in BCP47 but no more recommanded as they ahve now standard codes. In some cases, the recommanded codes are still not accepted/recognized by Mediawiki and the Translate tool.
  • violating codes (such as "nrm" or "simple"): they are still supported by MediaWiki and the Translate tool, but for HTML and XML conformance we need an adaptation layer when using them in "lang=" attributes (this is needed so that these codes are correctly resolved by CSS selectors, or by browsers to select the correct script variant to render).
  • And in some cases codes not even supported for new translations (even if they are conforming to BCP47): those translations can only be frozen and their resources converted to supported and conforming language codes. But in some cases, the language codes won't be recognized at all and the few pages using these (rare) codes (or codes meant for discussions in Meta of new languages whose integration work is in progress in Translatewiki.net or later in Incubator) need sometimes to be converted manually, until they are fully taken in charge by MediaWiki and then become usable by the Translate extension.

There are other quirks that I progressively discover but the overall structure of translations is now working for almost all important pages (and at least all the active ones, little things have been done to convert old archived pages, except when they would conflict with the new system, in which case they may be renamed (creating redirects temporarily, until I resolve these redirects).

Lots of categories are showing red links since long eveywhere. I have resolved many of them, and recategorized pages which were difficult to locate. The new system tries to make a strictly parallel structure of pagenames and categories, using the "/langcode" suffixes consistantly everywhere.

What this means is that most contents in Meta are now much more easily translatable to many more languages, in a much faster way than before. This allows many translators to contribute their translations, and making Meta a really multilingual site, correctly indexed by search engines (internal ones such as CirrusSearch, or external ones like Google or Bing). Most users will now find their way in pages without having to look where pages in their language are located.

The language bar is still present, but we no longer need to fill them (specific templates with lists of languages for a specific page are deprecated). It can still be used to go easily to the page version in another language, but users should now be able to navigate in MEta using their own user language (their preferred language in their user settings, or the default language set in their browser preference if they are not connected). Allmost all pages will now be in sync everywhere instead of becoming outdated very fast due to lack of maintenance (most of the maintenance is made by editing the English version, and by a translate admin validating edits in the English page to synchronize all languages at the same time, even if this means that some translations may become "fuzzy" and would need some check : generally I check all these languages immediately when I have prepared another existing page to the new system, but there are cases where I will not update them because the situation is tricky).

There remains also pages whose "translations" are actually very different from the English version. To avoid breaking them, I may need to rename them to avoid collisions and offer a temporary navigation to their specific parts which will need rework and merging later to be compatible wit hthe English base version (a few pages are like this such as pages containing the long lists of Wikimedia projects).

Finally during the conversion, it is possible that some pages have some templates no longer working in some languages; but if those pages are old and unmaintained/obsolete since long, it will not be a priority to fix them : I4ve focused first on making the on-going activities in Meta to be first converted with usable translations (important pages includes all pages related to policies in discussion or their amendment : the proposals and drafts need to be translated, but not talk page theselves, except the transcluded navigational templates used typically at top of these talk pages).

I just hope that everyone (not speaking only English) will appreciate the efforts I did to open Meta-Wiki to these users that hafe difficulties with English: Meta is a project meant to coordinate all existing wikis in all languages, and to coordinate the efforts to promote contents and adoption by users living in minorities eveywhere in the world. Yes some translations will not be perfect, but by making most contents translatable, translators will focus on things that they are the most interested in and with which they have contacts wanting their help to translate things that Wikimedians in minorities do not understand.

Thanks. verdy_p (talk) 02:27, 2 March 2014 (UTC)

GSoC 2014 proposal for page migration under the Translate extension

Hello everyone!

I am Pratik Lahoti (User:BPositive) from Pune, India. I am willing to participate in the Google Summer of Code this year. I am interested in the project titled - “Tools for mass migration of legacy translated wiki content”.

My mentors for this project would be Niklas Laxström and Federico Leva.

With their help, I have drafted the first version of my proposal page. You can find it here:

https://www.mediawiki.org/wiki/Extension:Translate/Mass_migration_tools

This project is a blessing in disguise for all the translation administrators, as it completely automates the tedious manual task of preparing the pages for translation as well as importing the translations. The proposal page mentions the Project Outline and the approach/solution towards the problem statement. I am done with most of the sections and left with the Project Schedule (which I will finish off when everything is finalized).

Please have a look at the proposal and give your valuable feedback/suggestions. While I have no problems in replying to the suggestions put forth over here, I would appreciate if you can do the same on the discussion page of the proposal, so that all the feedback is at one single place. Looking forward to hearing from you, Thank you! BPositive (talk) 04:46, 4 March 2014 (UTC)

@Nemo bis, Nikerabbit, and BPositive: I really hope to see this become a reality! Marking up pages is sometimes quite tedious, and a tool to automatically do this would be awesome. I think I can represent most translation administrators when I say thank you for working on this. PiRSquared17 (talk) 16:24, 4 March 2014 (UTC)

Yeah, the problem being faced right now definitely needs to be automated, for that is what computers were born for :) Please go through the proposal and let me know any requirements you have in specific. BPositive (talk) 19:02, 4 March 2014 (UTC)

I don't have any specific suggestions, but maybe other translation admins do. I'm sure Nemo and Nikerabbit will tell you all the requirements. Could you please update us in the future? PiRSquared17 (talk) 19:08, 4 March 2014 (UTC)

Hey, the idea is that translation admins help prioritise what's most important and most likely to make a difference, not that we do everything on our own. :P Watchlisting the page at mediawiki.org should help you follow the discussion, but surely there will be updates. --Nemo 21:43, 4 March 2014 (UTC)

Translation of FDC templates

Hey i18n specialists,

With @Seb35: we are currently looking into i18n-ing the all FDC stuff. Today’s menu: templates! Please see my rambling thoughts on Grants:APG/Comments#Templates translation − roadmap and tell if this will float or not.

Thanks! :-)

Jean-Fred (talk) 23:25, 7 February 2014 (UTC)

Bumping the discussion :) Jean-Fred (talk) 12:09, 5 March 2014 (UTC)

Notify

Hi,

I’ve just used Special:NotifyTranslators for the first time. I hope I did fine and did not break anything, nor spammed users against policy. Please advise whether it was okay, or how I should proceed (or not proceed) in the future.

Thanks, Jean-Fred (talk) 10:38, 12 March 2014 (UTC)

The Wikipedia Adventure

Some italians are interested in translating this. Can someone please

• copy the JS pages to pages with the same name on this wiki (but in Template namespace),
• prepare and mark the linguistic content for translation?

So we can proceed without bothering to make devs learn about i18n of their code and everyone can just import on their wiki. :) --Nemo 12:16, 19 March 2014 (UTC)

How much of the strings needs to be translated? The whole thing (often including <br>s and files), or just the "linguistic content"? What if someone puts an apostrophe in a translation? (This could also inject malicious JS into the page, which could be unknowingly copied). I'm probably just being paranoid. PiRSquared17 (talk) 17:28, 19 March 2014 (UTC)

Only the linguistic content, strings scattered here and there. Well, you're right, the administrators importing such stuff into MediaWiki namespace will need to be very careful. But they would need to in any case; we could however make sure the script can't be hot-imported at all from the unprotected pages. --Nemo 17:33, 19 March 2014 (UTC)

This is key. The mediawiki code can make automated edits through the API, without the user knowing it's happening (in the game, we disclose that it is happening, of course). That's essential to simulating interaction, but it could be used for a multitude of inappropriate purposes if not in a protected namespace or page.

All pages are located here: W:EN:Wikipedia:TWA/Index. Let me know if I can help or if you have questions. Cheers, Jake Ocaasi (talk) 21:15, 19 March 2014 (UTC)

Translation activity stats by language now available

See Meta:Babylon/Translation stats. :) --Nemo 17:23, 19 March 2014 (UTC)

Translate-a-thon in Grenoble

Benvenuti a Grenoble! Bienvenue à Grenoble! Welcome to Grenoble!

Save the date: 13 april 2014, the day of the translate-a-thon of Grenoble to turn Wikipedia articles about "Grenoble & neighborhood" from French into Italian (from fr.wikipedia.org to it.wikipedia.org). I hope to see you soon at the CCSTI in Grenoble! :-) --Patafisik (talk) 16:28, 26 March 2014 (UTC)

language statistics

I've wanted to ask: how is translation statistics calculated? For example, we have Tech/News/2014/04 that shows that Russian translation is completed for 97%. At the same time, there are no untranslated or outdated messages - so, what does 97% show? How can it be fixed? rubin16 (talk) 14:18, 2 February 2014 (UTC)

• for example, the same is with russian translations of Template:Tech header and Template:Tech news/header rubin16 (talk) 14:19, 2 February 2014 (UTC)

Usually null-editing one of the translation units fixes it. PiRSquared17 (talk) 14:22, 2 February 2014 (UTC)

Ok, it's cache, thank you :) rubin16 (talk) 14:27, 2 February 2014 (UTC)

This is a current bug/limitation of the Translate tool used on Wikimedia sites (not just Meta, but Commons as well): the last edit being performed in a translation unit is not reported to the translated page with its statistics.

FuzzyBot runs too early by updating translated pages and statistics before the new saved items are visible in the database cache he uses indirectly via the API, so it uses the version just before the last change for which it attempts to perform its updates (the last edited item will not be visible, it will still remain fuzzy, or untranslated, or uncorrected and counted as such, but all previosu edits will be counted). FuzzyBot needs a correction by either instructing to bypass the cache when getting the contents of wiki pages (in the "Translate:" namespace), or by delaying its actions so that they will occur only 1 minute later (it should be enough...) instead of performing them immediately (the task will be started by MediaWiki in its job queue with an empty cache, and the actual page contents will be read instead of the old version currently being in the version being updated when we save things in the Translate tool).

I don't know if the Translate tool an submit background jobs to do that (in my opinion, it should do that, and manage its own "todo" job queue to perform them in a grouped way, just like it uses a job queue when it renames base pages and translated subpages: we have to wait for the completion in its own history log, but it does not take long even when renaming base pages with 200 translated subpages and renaming all translations items, even in a page that has more than 200 items, renaming such a big base page translated in so many languages would rename 40 000 items in the Translate: namespace).

There's no such bug of the Translate tool in Translatewiki.net because it does not use page cache (or its local page cache correctly monitors changes and invalidates cached pages automatically), so every action of its scripts actually will read the current actual content of the database, even if it was modified by the same user in the same task in the previous line of code. As long as this cache is purely read-only and ignores ongoing changes, it will reflect old versions that were just read before performing any change and the rest of the script will not see that saved change.

The Translate tool has other bugs more critical than this one for which the null-edit is a working work-around, not complicate to do:

• if you are a translator, a null-edit in a single translation unit is enough:
  • reopen the last item you edited in the Translate tool;
  • in the editor window press SPACE (the Save button is enabled), and BACKSPACE to cancel it (the Save button remains enabled even if there's no actual change);
  • then click on the Save button (now the translated page will be reflecting your last edit).
• Reflecting changes is a bit more tricky for translation admins when they mark a new version of a page for translation: they need either:
  • null-edit one item in every existing language (this is really lengthy to do), or
  • generally it is enough to reedit the base English version by inserting or removing a single space (generally the space in the middle of <languages /> as it plays no visible role on the page and its placement in the page is easy to predict and will be visible in the diffs; this would allow a bot monitoring changes to see this edit as being really safe and ignorable), save this pseudo-change, and mark again that version a second time: all translated pages will reflect the change that occured in your real version, but not the change in the second version for the pseudo null-edit performed on the base page (with the added or removed space) (but it does not matter if there's only this space difference).

verdy_p (talk) 14:18, 8 February 2014 (UTC)

I was looking for a solution to same problem and I came across your answer. Very well explained Verdy_p. Your explanation should be written into a help instruction page for this bug :) --WikiBronze ^[T] 00:18, 31 March 2014 (UTC)

Medicine Translation Project Community Organizing

I'd like to ask of you to take a look at a Wikimedia IEG grant a few of us over at Wikiproject Medicine are behind. You may already have heard of the translation of medical articles that is being done (if not please take a look at w:Wikipedia:WikiProject Medicine/Translation Task Force). The goal of the grant is to get the translation and integration process to run smoothly, and to assess which articles are the most important to translate. We've come far at w:Wikipedia:WikiProject Medicine/Translation task force/RTT, but to get further there is need for some form of organization, preferably by someone who can devote significant time to the task.

I'm very hopeful that I can provide real benefit with this grant, as there are so many articles on Wikipedia that could help people all over the world.
It's even more important when you take into account drives such as Wikipedia Zero, and readers who might not have access to any medical information at all can benefit.

Please take a look at the grant page: Medicine Translation Project Community Organizing, and add a comment or give your ideas on how we can best benefit the Wikipedia communities.
Thanks, -- CFCF (talk) 21:19, 2 April 2014 (UTC)

Tagging Texas Wikimedians and Wikimedia Egypt for translation

At Talk:Texas Wikimedians I was told I should contact a translation administrator to tag the page for translation of Texas Wikimedians (English to Spanish). On top of that I notice Wikimedia Egypt has no content in Arabic. May I contact any translation administrator or does it have to be one who knows the particular language?

Thanks WhisperToMe (talk) 14:29, 8 April 2014 (UTC)

Thank you! What is the protocol for tagging other pages? Do you need permission from the coalitions/chapters before tagging the pages for translation? I had also started Spanish versions of:

• Wikimedia United States Coalition
• Wikimedia District of Columbia
• Wikimedia New York City

I also found Wikimedia Colombia which has Spanish and English on the same page and a message in Spanish which is not yet in English. Also I want to make an English version of Wikimedia Colombia/Grupo de usuarios.

Thanks WhisperToMe (talk) 05:28, 9 April 2014 (UTC)

@WhisperToMe: Oops, sorry. Forgot to post here. :/ I tagged the Texas page for translation. We do not need explicit permission before tagging (at least in practice), but it would be nice if someone from these groups would recommend that we mark it up. PiRSquared17 (talk) 14:51, 9 April 2014 (UTC)

Ok. I do participate a little bit in the US Wikimedia Council family of projects, but do you want me to notify them of the possibility of the change happening first? I personally started the Spanish pages of all three US WikiProject family pages. WhisperToMe (talk) 04:36, 10 April 2014 (UTC)

I went ahead and notified the groups WhisperToMe (talk) 05:56, 10 April 2014 (UTC)

Should I Just Do It™? PiRSquared17 (talk) 20:58, 20 April 2014 (UTC)

I am fine with the "Just Do It™" :) WhisperToMe (talk) 15:31, 22 April 2014 (UTC)

Requirements for mass migration tools project

Hi all,

I have been accepted into the Google Summer of Code 2014 and will be working on the "Tools for mass migration of legacy translated wiki content" project.

As per the project timeline, I have drafted the requirements for this project after discussing with my mentors - Nikerabbit and Nemo_bis. It would be great if the translation admins and translators have a look at the requirements and let us know if they have any other requirements from their side.

Please mention them on the corresponding discussion page. I would like to get some feedback on the importance of requirements mentioned as optional in that page.

I need to get done with this by the next couple of days, so I would appreciate if you can give this a quick look. :)

Thank you! BPositive (talk) 19:41, 23 April 2014 (UTC)

Useful Wiki for all translators

There is a site based on MediaWiki software including WikiData now on its own that with your support may join the great community of WikiMedia Foundation. For details see Adopt OmegaWiki. We handle 400+ languages More about on our main page: OmegaWiki

IIRC it's covered somewhere in Writing clearly or maybe Translating Dictionary. --Nemo 20:02, 6 June 2014 (UTC)

Area of Expertise

I have just signed up as a translator. Is there a way that I can receive translation requests filtered by my areas of expertise? For example, I have (modestly) rated myself as "fr-2", but I have considerable experience in translating computer UI dialog and Canadian government jargon into French. D A Patriarche (talk) 01:28, 11 May 2014 (UTC)

You can select in Special:LanguageStats the aggregate group "Help", or go to mw:Special:LanguageStats. --Nemo 20:02, 6 June 2014 (UTC)

Proposal to not translate /en/ to /en-gb/ ... /en-xx/ with <translate>

I am wondering why there is an effort to translate from /en/ to something like /en-gb/. While I understand the difference with regards to keyboards and certain keys of preference, eg. $ vs £, and maybe dates (never quite sure on that baby), I don't see the difference here at meta or in the vast expanse where we undertake translations. In fact, to me, as a native reader and writer of English, the /en-us/ (which is seemingly the default for /en/ anyway) and /en-gb/ don't represent me properly anyway. I also do not believe that there is any clear dictionary definition in available spellings, and one in which we would either bother or particularly care, especially with the subset and vague use of /en-xx/. Therefore I would like to propose that at meta, and if possible for the predominant part of our translation efforts that we do away with /en-xx/ translations unless there can be a clear, rational and demonstrated set of reasons for why we are doing it.  — billinghurst sDrewth 10:48, 11 June 2014 (UTC)

As all translations fallback to "en" anyway, it would be sufficient if en-ca/en-gb is only translated if there is indeed a difference in spelling or meaning in the respective dialects (which I believe is already done that way). Stopping en-ca/en-gb adjustments entirely would be wrong in my opinion as there are indeed not only a few cases where the meaning of words differs significantly. Also, in British English the letter "s" is preferred over the letter "z", which is almost excessively used in American English which I personally don't like and thus I am glad that there is a possibility to change the interface language to "en-gb" :-) Regards, Vogone (talk) 21:27, 11 June 2014 (UTC)

I am not talking about interfaces and the like, I am talking about when we have <translate> tags placed. This was brought due to a deletion request where someone had started a translation of a grant application from /en/ to /en-gb/. Thanks for allowing me to clarify.  — billinghurst sDrewth 13:41, 12 June 2014 (UTC)

Yes, I also meant both. My opinion is that we should not disable the possibility to add en-gb translations entirely but I agree doesn't make any sense to add new translation sections in cases where en and en-gb are 1:1 identical. As en is the default fallback language for en-gb, such pointless translation section additions don't even have the slightest effect, anyway. Though, I don't feel too strong about this and if there is indeed the problem that too many users add en-gb translations where it is definitely not required I would not object to the en-gb language being disabled. Though, if that was done, it would require unambiguous language by the authors of content pages in English language, meaning only vocabulary which is dialect-independent should be used. Regarding the available spellings, there is the Oxford English Dictionary which tries to include as many langauge variations as possible, including vocabulary for the British or the American English dialect. Vogone (talk) 14:27, 12 June 2014 (UTC)

One current problem in the translate extension is that if a language code is "supported" by MediaWiki, and you have marked a base page for translation, nothing forbuds you to translate to that language code; except globally for the whole site. If the language code is disabled on the whole site (e.g. "zh-hant" because it is technically not considered a language by Mediawiki but as a variant within "zh", supported by aitomated transliterators).

The "en-gb" however is not a simple tansliteration, it is meant to be specialization from a source language only for a few entries, the rest should fallback automatically to "en". However tehe Transalte extension still does not know what is a language fallback; not even for standard fallbacks described alogorithmically in BCP47 from the locale code format, and then from data in the IANA database (e.g. with properties like "Suppress-Script", or "Replaced"). It also does not know the additional CLDR data about specific tailorings of fallbacks.

In summary the translate extension just assumes all transaltion units will be in the same language (otherwise it just uses a single fallback, the site's default language like English here on Meta, but in fact it just uses the unidentified language of the base source page).

So wr would first need integration of real fallbacks in the Translate tool when it (re)generates updated translated subpages. But even then we would need a change in the UI to allow adding locale-specigic variants; ony where they may be useful (with a button or link "Add a variant transaltion".

So the best you can do is to let users add translated page in any variant as they wish. However these pages remain navigatable. And the Translate tool should not override some translations in a language that it refuses to edit. We can live with "en-gb". verdy_p (talk) 15:08, 12 June 2014 (UTC)

Medical translations to smaller languages, infobox issues!

I've been working to get some of our medical translations that are done onto the smaller Wikis, and I’ve been having some issues with infoboxes. There aren’t any templates, so I went ahead and copied from the English Template:Infobox disease entry and made new templates, but these aren’t working properly.

Examples:

• https://rw.wikipedia.org/wiki/Indwara_y%E2%80%99umusinziro_nyafurika
• https://rw.wikipedia.org/wiki/Template:Infobox_disease

Thanks for any help! -- CFCF (talk) 10:30, 12 June 2014 (UTC)

P.S. Also lacking interwiki links for this article en:African trypanosomiasis (same as translated above), how do I implement these?
Thanks, CFCF (talk) 10:32, 12 June 2014 (UTC)

To add interwiki links, look in the list of languages to the left of the page. At bottom you have a link which will drive you to Wikidata.

First look at a page where they are present; then go to the English page which is missing an interwiki link to your page ; add the mapping for your language code to point to your localized wiki page. Your wiki will see the English interwiki, and the English page (or other languages present in that list) will see your new page.

But before doing that, make sure your missing templates are prefilled with minimum data (there are too many redlinks for your page to be usable)

verdy_p (talk) 11:10, 12 June 2014 (UTC)

Thanks for that, I've already begun implementing it. CFCF (talk) 07:54, 13 June 2014 (UTC)

As for the infobox issue, I've come a little further, creating:

• https://rw.wikipedia.org/wiki/Template:Infobox
• https://rw.wikipedia.org/wiki/Module:Infobox

But I'm still only facing errors. If this is the wrong place to ask, where else should I go looking for help? Thanks, CFCF (talk) 07:54, 13 June 2014 (UTC)

Testers welcomed for new feature - Special:PageMigration

As a Google Summer of Code Intern, I have been working on the Mass Migration tools project for Wikimedia. We are now ready with a minimal working product. The tool helps translators and translation administrators import the old translations into the Translate Extension.

An instance of the same has been set up on labs. You can find some useful instructions on the main page.

Please test the tool and report bugs/suggestions using the link provided on the main page itself. You can have a look at the tracking bug to check already reported bugs.

Looking forward to hearing from you! Cheers. BPositive (talk) 13:34, 14 June 2014 (UTC)

Marking a wikitable for translation

Hello,

I add a wikitable to this page, but when I mark this version for translation, the whole table is in one big translation unit...

How can I have translation units only for colomn titles? Thanks for your help. Regards Benoit Rochon 17:00, 20 June 2014 (UTC)

You would need to add <translate></translate> tags before and behind every translatable part of the table. Furthermore, it would probably be easier and cleaner if you transfered that to a subpage. Regards, Vogone (talk) 18:37, 20 June 2014 (UTC)

Thank you Vogone. Regards, Benoit Rochon 20:24, 21 June 2014 (UTC)

Automatic translation workflow state changes

Hi, I'm trying to improve the workflow for page translation, specifically for WMF Fundraising's work. We would like to enable the automatic state changes used by some other sites (commons, otrs, and wikidata), here is the relevant patch. The commit message describes expected behavior after the patch is applied, please let me know if this is going to conflict in any way with your existing workflow!

Awight (WMF) (talk) 19:37, 6 June 2014 (UTC)

Sounds sensible, because users rarely use those manually. Occasionally, I do send a "ready" translation back to "proofreading" status, though I don't know how much this is noticed. I see on Commons that this is still possible for translation admins and normal users alike, all ok. --Nemo 20:02, 6 June 2014 (UTC)

@Awight (WMF):: Yes, that looks reasonable. (And I guess that this will also make it show up on one's watchlist when a translation reaches 100%, provided one watches the original page? That would be super useful.)

Just to double-check: I assume that status changes to "published" will still be manual, right? (Otherwise this might interfere with the CentralNotice integration, where setting a translation to "published" means that it is automatically imported into the live banners, see Help:CentralNotice/Translations.)

Regards, Tbayer (WMF) (talk) 03:16, 2 July 2014 (UTC)

Watchlist: not currently, because the "target" of the log action is set to a fake title you (probably?) can't watchlist, that is the URL where the group can be translated.[1] 1) It's surprising, but logs don't have feeds. 2) You could file an enhancement request in Translate asking an exception for translation review log action target to be set to an actual page when it's about a translatable page, but it's not obvious if it should be the source page (for translation admins) or the translation page (for translators).

Published: the patch does nothing about such state. --Nemo 07:55, 2 July 2014 (UTC)

Deployed, thanks for the input!

@Tbayer (WMF): Yes, Nemo_bis is right, CentralNotice translations are moderated by a workflow hack inside the extension, which restricts the publish action on banner message groups to only translation admins. Awight (WMF) (talk) 23:42, 2 July 2014 (UTC)

Signature

According to a RFC in German Wikipedia each user and bot have to sign comments on talk or project pages, but the user de:Benutzer:Translation Notification Bot doesn't follow this rule. Could you fix this (adding --~~~~ to the messages of the bot)? Thank you! --Filzstift (talk) 09:33, 26 May 2014 (UTC)

As far as I know, the bot does sign messages. Can you formulate your request more precisely? --Nemo 20:02, 6 June 2014 (UTC)

@Nemo bis: I believe he means the bot is using a wrong format (the "--" are missing before the signature and there is no page where the signature links to). Vogone (talk) 21:31, 11 June 2014 (UTC)

It could probably be mostly fixed in MediaWiki:Translationnotifications-talkpage-body de translation, assuming that it everyone on dewiki translates to de, but it would be overkill IMHO. Th current message seems fine. Do "--" really matter that much? PiRSquared17 (talk) 22:12, 11 June 2014 (UTC)

The problem is, there is no link to the bot's user page (that's the main part of the RFC). --Filzstift (talk) 21:18, 17 July 2014 (UTC)

Just to make it clear: It's not the missing "--", it's the missing link to the bot's user page! At the moment no one knows who actually made the talk page entry! a×p_de^Hello! 14:24, 20 October 2014 (UTC)

MediaWiki:Centralnotice-template-Wikimania2014Final

The current Centralnotice, MediaWiki:Centralnotice-template-Wikimania2014Final, already has plenty of translations which are ready for publishing. Why are they still not published? -- Yueman (talk) 14:48, 10 July 2014 (UTC)

I wonder, too. No banners appeare eg. in Ukrainian lately, though we translated and proofread them. Should we every time jerk specific admin as edits on Babylon or RFH are not enough? -- Ата ^(talk) 07:05, 19 July 2014 (UTC)

Replacing a translated page

I am currently working on completely replacing some pages in Grants:Evaluation in order to implement a redesign. Some of these pages have already been translated. Does anyone have recommendations for how to go about replacing an entire page? Do I simply delete all the translation tags and wait for fuzzybot to do its work? If there is a wiki page about this, that would be helpful as well - can't seem to find anything. Thanks so much! --EGalvez (WMF) (talk) 20:47, 22 July 2014 (UTC)

IIRC it works like this: When you remove (any number of) translation sections from a page, and mark it for translation, these sections will simply be removed from the Translate interface for that specific page. The existing translations are preserved; when you create new translation sections, they get numbers which are not yet used. --MF-W 22:10, 22 July 2014 (UTC)

Thanks MF-W! I may have answered my own question - I'm pretty sure I need to delete all the old translated pages using Special:PrefixIndex (For example, for Grants:Evaluation, I would delete only the pages above the /About pages). I did a test page in my sandbox, and the old version of the page is displayed when I click "español". Would this be a good approach? --EGalvez (WMF) (talk) 01:09, 23 July 2014 (UTC)

The old version was still displayed on the Spanish page because FuzzyBot didn't yet run over it. A subsequent edit to the original page now made that happen. I don't know the logic behind this delay, maybe User:Nemo bis knows. --MF-W 14:29, 23 July 2014 (UTC)

Thanks so muchMF-W! This answers my question. --EGalvez (WMF) (talk) 18:55, 24 July 2014 (UTC)

Translation tag mess up

Hi,
I don't know what happened, but could someone explain (and/or fix) me the mess up with the translation tags happened on the following pages?

• Chapters Dialogue/Project/Implementation
• Chapters Dialogue/Project/Methodology
• Chapters Dialogue/Project/Set-up
• Chapters Dialogue/Further Information/Site-map

I don't get it. Thanks in advance, --Jcornelius (talk) 16:07, 17 August 2014 (UTC)

@Jcornelius: Fixed all. See this diff. {{TNT}} should be used for translatable transcluded pages. --Glaisher (talk) 16:27, 17 August 2014 (UTC)

@Glaisher: Thanks a lot, Glaisher. --Jcornelius (talk) 16:32, 17 August 2014 (UTC)

Sorry again (still learning and trying to understand those translation tools), what happened here? I did use the TNT tag. --Jcornelius (talk) 12:32, 19 August 2014 (UTC)

Not sure why that happened but fixed it somehow after special:diff/9575005 (pretty sure that in CSS, things does not break just because there was a ; at the beginning). --Glaisher (talk) 18:00, 19 August 2014 (UTC)

Translation memory slowdown

Tracked in Phabricator:
Bug 69613

Because I see some people wondering about it: if you don't see suggestions from Translate's translation memory where you'd expect them, that's for a known bug which is being worked on by WMF sysadmins. In short, we've been too busy adding translatable pages and translations ;-) and the system became slower than expected. More updates will come in this area.[2] --Nemo 15:45, 22 August 2014 (UTC)

Mass migration tools approaching conclusion, feast now

It will be a tough ride to finish the project (if at all possible), but I highly recommend to use Special:PageMigration now: just today, with its help I managed to make almost a thousand edits and migrate several pages including some huge ones. Even in big pages it often works surprisingly well (almost nothing to do manually), while in others it fails spectacularly (but we have some ideas on how to fix it).

With only ten days of coding left, more than ever it's useful if you use the tool on at least one page and comment on the bugs to help us prioritise, or even better report new problems/ideas we've not identified yet. --Nemo 23:45, 8 August 2014 (UTC)

A fine example by MF-Warburg: [3]. --Nemo 08:46, 23 August 2014 (UTC)

It was a great pleasure to use this tool. Billinghurst suggested to convert the page to the Translate extension, so I finally had an opportunity to use this feature. After I understood that Special:PageMigration first wants the page to be already converted to the Translate extension, I found out about the existence of Special:PagePreparation and soon afterwards had 500 edits more \o/. This is really very helpful for converting old pages, I wish it had existed earlier. I will now file some bugs. --MF-W 18:42, 23 August 2014 (UTC)

Main Page translation

I tried to fix the translation for Korean main page, but page only redirected to {{Main Page/ko}}, and there, other template was there, without any translation message. So, where can I translate things in {{Main Page/Code}} (According to {{Main Page/ko}})? — revi^{^} 15:18, 2 October 2014 (UTC)

https://meta.wikimedia.org/w/index.php?title=Template:Main_Page/ko&action=edit at the end you will see "Templates used on this page:". Click on it and you can find the templates transcluded onto that page. Look for template titles ending with /ko and you will hopefully find what you're looking for. :P --Glaisher (talk) 15:25, 2 October 2014 (UTC)

Found it. I forgot about that - these days I am becoming silly :P — revi^{^} 15:33, 2 October 2014 (UTC)

Related Peeragogy Educational grant proposal

Dear Wikipedia Educators: We're advancing an Individual Engagement Grant here. If this is something you and your students might like to be involved with, please add an endorsement. Comments or questions in advance of the September 30th deadline would be most welcome on the proposal's talk page. In particular, our project involves translation work which we hope might be interesting to students.

--Fabrizio Terzi (talk)

Timestamp for archiving bots. — revi_msg 17:38, 23 October 2014 (UTC)

Upcoming IdeaLab Events: IEG Proposal Clinics

message

Idea Lab Idea Lab Hello, Babylon! We've added Events to IdeaLab, and you're invited :) Upcoming events focus on turning ideas into Individual Engagement Grant proposals before the March 31 deadline. Need help or have questions about IEG? Join us at a Hangout: Thursday, 13 March 2014, 1600 UTC Wednesday, 19 March 2014, 1700 UTC Saturday, 29 March 2014, 1700 UTC Hope to see you there! This message was delivered automatically to IEG and IdeaLab participants. To unsubscribe from any future IEG reminders, remove your name from this list

Timestamp for archiving bots. — revi_msg 17:38, 23 October 2014 (UTC)

Thank you for your help!

		The Translation Barnstar
		Thank you for your valuable contribution to the translation of the Global South Editor Survey questions! With my best regards, -- Haitham S. (WMF)

Timestamp for archiving bots. — revi_msg 17:38, 23 October 2014 (UTC)

Attribution in new TUX

How can we best attribute sources of translations in TUX, if not with edit summaries? Use the talk page of each translation? It would be so much easier if there were some way to cite the translation memory source. PiRSquared17 (talk) 21:54, 23 October 2014 (UTC)

I would also be in favour to enable edit summaries for TUX. Using &tux=0 cannot be a permanent solution. Vogone (talk) 22:49, 23 October 2014 (UTC)

Templates/$-functions

Hi; I just checked on Stewards/Elections_2015/Introduction/nl; the time references seem to still be in English; is there somewhere they can be translated too? I used to know it but after my absence of a few years, my memory hasn't caught up yet ;) - Kthoelen (talk) 22:15, 24 October 2014 (UTC)

In this case, it was due to an oversight in initially marking the page for translation. Only the English translation was within the tvar previously. On 23rd, PiRSquared17 made it localizable. The last edit to the nl translation was on 17th. All the translations need to be null-edited for the update to take effect. --Glaisher (talk) 08:57, 25 October 2014 (UTC)

Rename translated pages

Hi,

What is the process to renamed pages that have translations, and which user right is necessary? I have not been able to locate such documentation.

In particular, Woliff has asked me to move:

• Grants:APG/FDC_portal/FDC_recommendations/2013-2014_round2 to Grants:APG/FDC_recommendations/2013-2014_round2
• Grants:APG/FDC_portal/FDC_recommendations/2014-2015_round1 to Grants:APG/FDC_recommendations/2014-2015_round1

I find the interface very confusing as Special:MovePage tells me « This special page allows you to move pages which are marked for translation. » before telling me this is impossible.

Thanks! Jean-Fred (talk) 16:24, 10 December 2014 (UTC)

There isn't any process, move just works. In this case, existing subpages of the target title are in the way, namely Grants:APG/FDC recommendations/2013-2014 round2/Certification. You can try moving those subpages out and then move the basepage in; and/or file an enhancement request to ask move to be more permissive.

However, moving translatable pages is not advisable unless there are severe errors in the title, due to bugzilla:39023 and Don't delete redirects. --Nemo 09:45, 11 December 2014 (UTC)

I moved Grants:APG/FDC recommendations/2013-2014 round2/Certification because MovePage refused to move it, so I assumed it might be responsible. But if you try the other page (round1), I get tell

The translatable page cannot be moved to a new name because of the following errors:

This page cannot be updated manually. This page is a translation of the page Grants:APG/FDC portal/FDC recommendations/2014-2015 round1 and the translation can be updated using the translation tool.

With as many errors as there are translation subpages.

Jean-Fred (talk) 13:27, 11 December 2014 (UTC)

But this target title also has existing subpages. If you think it's a more general issue, you should test with entirely free source and target titles, IMHO. There are too many factors here and a bug report would probably not bring you anywhere before a few years. --Nemo 13:38, 11 December 2014 (UTC)

Need for someone with access to interface translations

Need for someone with access to interface translations to translate $wgTranslateWorkflowStates to greek:

• In progress‎ → Σε εξέλιξη
• Needs updating‎ → Χρειάζεται ενημέρωση
• Proofreading‎ → Ελέγχεται
• Ready‎ → Έτοιμο
• Published‎ → Δημοσιευμένο

The link to the translation page is https://meta.wikimedia.org/w/index.php?title=Special:Translate&group=translate-workflow-states&language=el

Thank you in advance. Ah3kal (talk) 20:30, 18 December 2014 (UTC)

Done. --MF-W 23:36, 18 December 2014 (UTC)

Problem in counting completed in the translation interface

Every translation I complete regardless whether I change status to proofreaing or in progress continues to show up in the untraslated having always 1 translation left? Is this a bug or am I doing something wrong? Ah3kal (talk) 11:44, 19 December 2014 (UTC)

Setting status doesn't affect counts. From logs and LanguageStats it's not entirely obvious to me what pages you're talking about: perhaps Superprotect and categories? In at least some categories the current count looks correct, but you're right that Superprotect shows 1 untranslated when all seems done.

It would be nice to identify clear steps to reproduce so that a bug can be filed. --Nemo 19:37, 19 December 2014 (UTC)

@Nemo It seems to happen always, i haven't found an example that didn't happen. At the time I asked here, all my contributions which I had finished 100% showed incorrectly 1 more translation to be done. The same stands for the interface translation I asked above. But a couple of hours ago everything was fixed for the old contributions while anything I did after that "refresh" continues with the same pattern (like the pages you mention).—Ah3kal (talk) 19:57, 19 December 2014 (UTC)

I also made this report, the interface is not displayed more correctly and the translation is nearly impossible. I believe that it must be a bug, or I am the only one to make this report. You can find a shortscreen on testwiki link --Grind24 (talk) 20:14, 19 December 2014 (UTC)

Oh good this issue is now resolved, i see it.--Grind24 (talk) 20:30, 19 December 2014 (UTC)

@Nemo bis:Same thing here. I've been translating categories recently, and I can reproduce the steps. I start and complete the translation, then I have to go from "Untranslated" to "All" to see that bot has changed the state from (unset) to in progress (note, the translation is complete, but recognized as "in progress"), then I make null edit (add whitespace or other symbol, delete it and press save button) and the bot changes state to proofreading. Now translation is 100% complete. I have to repeat all these steps with every category or any other page I edit to make it 100% translated.

One more thing. If I set status to published, but translation shows as if "ninety something % complete", I simply make null edit (not an edit, actually, it doesn't even show in history) and bot changes state to proofreading. I have to change status to published once more, but now it is 100% complete.

And yet something else that could be somehow connected to this problem. Today I have completed the translation of two message groups in Special:LanguageStats (for Ukrainian), namely VisualEditor and Wikimedia Highlights. All translations are 100% complete, but both on the special page and in the translation interface they show as if they are not. I know that VisualEditor group has got all subgroups 100% translated. But it shows that there are nearly 27% of untranslated messages. Though there are neither untranslated nor outdated. You can check it yourself, provided that the issue is due when you read this (I just suppose it could just need some more time to update).-- Piramid ion  05:34, 24 December 2014 (UTC)

I think this is the bug: phab:T49864. And too bad, it hasn't been solved yet... FYI, the best way to purge is to do a null or a real edit. Then the translation becomes 100% complete. -- Piramid ion  06:34, 24 December 2014 (UTC)

Pehaps it is somehow related to the job that bot does. If you take a category with two messages to be translated, and translate only one of them, translation page is created, the bot sets state to in progress, but the percentage of translation done shows 0%, (like in Category:Greece/uk while it should be 50%. Which means you need to hard purge (with an (fake) edit) the page you'd created first. If you don't, and just translate the second message, it will show only 50% done, although both messages are translated. This is the point. And it is very easy to reproduce.-- Piramid ion  08:29, 24 December 2014 (UTC)

Transclusion magic of translated pages (twice)

Hi,

I may have been a bit ambitious with this but ah well.

• Grants:APG/Proposals/2014-2015 round1/FDC staff assessments overview (1) is Translate-enabled
• It is included by Grants:APG/Proposals/2014-2015 round1/FDC staff assessment template (2), itself Translate-enabled, through {{Grants:APG/Proposals/2014-2015 round1/FDC staff assessments overview/{{SuperFallback|Grants:APG/Proposals/2014-2015 round1/FDC staff assessments overview|{{CURRENTCONTENTLANGUAGE}}}}}}
• Itself included in Grants:APG/Proposals/2014-2015 round1/Amical Wikimedia/Staff proposal assessment and Grants:APG/Proposals/2014-2015 round1/Wikimedia Österreich/Staff proposal assessment (themselves Translate-enabled) via {{Grants:APG/Proposals/2014-2015 round1/FDC staff assessment template/{{SuperFallback|Grants:APG/Proposals/2014-2015 round1/FDC staff assessment template|{{CURRENTCONTENTLANGUAGE}}}}

But contrast Grants:APG/Proposals/2014-2015 round1/Amical Wikimedia/Staff proposal assessment/fr and Grants:APG/Proposals/2014-2015 round1/Wikimedia Österreich/Staff proposal assessment/fr : for me, the former has the bits from (2) in French but not (1), and the reverse for the latter.

If anyone has any idea :)

Jean-Fred (talk) 19:09, 23 December 2014 (UTC)

Talk page redirects?

I noticed that this is a problem with translations. Translated Meta:Babylon, for example, doesn't have Meta talk:Babylon. To enter this discussion you need to go to English version first. Shouldn't there be a redirect on the talk page (and may I create it?). Same thing with pages discussing something, they often have links that lead to the discussion page, and if translated - they lead to an empty talk page, where there is no discussion at all. So, two questions: may we, translators, create these pages with redirects to the source talk page? And shouldn't it be somehow enabled by default (make bot create it automatically)?-- Piramid ion  17:33, 24 December 2014 (UTC)

You can create redirects where the discussion needs to be central, sure. In general, the talk page of each subpage may be used to discuss the translate itself, or for language-specific discussions of a topic. It's not an easy matter. --Nemo 21:22, 24 December 2014 (UTC)

OK, thanks.-- Piramid ion  22:10, 24 December 2014 (UTC)

Help with a LUA module?

Hi everyone, I'd appreciate some help with this page. When I copy/paste it into MassMessage and hit Preview, part of the "switch" code is in plain sight, and all the various versions of the newsletter are shown. Thank you for your support, --Elitre (WMF) (talk) 17:29, 26 December 2014 (UTC)

Nevermind, someone was super quick in finding out what was wrong! --Elitre (WMF) (talk) 19:09, 26 December 2014 (UTC)