Commons:Translators' noticeboard

SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 2 days and sections whose oldest comment is older than 60 days. For the archive overview, see Archive/. The latest archive is located at Archive/2017.

Translators' noticeboard

This is a noticeboard for all matters regarding translation of pages, and a meeting place for the translation administrators. Useful links: Documentation for the translation extension, Tutorial for translators. See also the sisterpage m:Meta talk:Babylon.

Start a new discussion

Commons discussion pages (index)

Commons Help desk Community-wide general discussion Copyright Proposals Graphics and photography discussion Image improvement Photography critiques Categories for discussion Deletion requests OTRS noticeboard Translators' noticeboard Work requests for bots Contact administrators Vandalism User problems (Dispute resolution) Blocks and protections Bureaucrats' noticeboard CheckUser requests #wikimedia-commons webchat Commons mailing list (archive) Commons' bugs on Phabricator

Shortcut: COM:TN

Commons:Photo challenge - edit links

Hello,
not sure where I should post this question, but somebody pointed out to me that the edit links of integrated subpages don't appear on translated pages - which is a bit of a problem in this case, as that's one of two possibilities to reach the submitting page for the challenges (even though I have to admit that I don't know if it's a new problem or not).
Does anybody know why that happened and if it's possible to have the sections of the subpage editable in translated versions?
Best wishes, Anna reg (talk) 08:46, 12 February 2015 (UTC)

Do you think about the [edit] links? They are missing because you can’t edit the page directly (editing the whole page also gives an error message). Just click on the Translate tab at the top of the page, and you can edit translations by translation units. I hope I answered your question. --Tacsipacsi (talk) 18:05, 12 February 2015 (UTC)

Not really, as the missing link isn't on the page itself, but on the integrated subpage that doesn't use the translation tool (we use {{LangSwitch}} there) - and we don't want to change the text, people want to submit pictures to the challenges (which they do by editing the gallery). Further, El Grafo's answer here (in German) shows that there was a time when those [edit]-links did exist... Anna reg (talk) 18:34, 12 February 2015 (UTC)

I don’t know what the problem was, but see them now. --Tacsipacsi (talk) 19:35, 12 February 2015 (UTC)

Really? I still don't see them on the translated pages (e.g. Commons:Photo_challenge/de)... Anna reg (talk) 08:15, 13 February 2015 (UTC)

Translation issues

Hello

I am working on Commons:WLA and have an issue. I have moved the main page of WLAf2014 to Commons:Wiki Loves Africa 2014. But the translations in various languages are still "attached" to the original page Commons:Wiki Loves Africa. How to "move" the translations so that they stay with the original page ? Anthere (talk)

What does {{original uploader}} mean?

For me it means "the person who uploaded the work for the first time was…" – but I am not fluent in English. On the other hand, Polish (and AFAIK German) translation of this message means "the original work was uploaded by…" which IMO is wrong (BTW there is {{original uploaded by}} for this). Am I right? --jdx ^Re: 11:11, 16 February 2016 (UTC)

Parisan French, Metropolitan French or Paris accent?

Can anyone tell me which would be the most politically correct? I am asking so that I can be correct when adding Template:Pronunciation to a set of files that the uploader noted "Fr-Paris" on. Here is an example file for reference; File:Fr-accélérateurs de particules (des).ogg

• French pronunciation for "Speravir" - Paris accent.

• French pronunciation for "Speravir" - Metropolitan French accent.

• French pronunciation for "Speravir" - Parisian accent.

Any help appreciated! Riley Huntley (talk) 20:29, 5 April 2016 (UTC)

Well, it's not a matter of political correctness. There is no "Metropolitan French accent" per se. Someone from Marseille will not speak like someone from Toulouse, Paris or Lille. Like someone from London will not speak like someone from Manchester or Sussex.

I think that something like "Speaker from XXXXX" would be a good solution. Furthermore, this information should be in the name of the file. Say we have Fr-Poulet.oga from a parisian speaker. If a toulousan speaker wants to upload his version (which is different, the et ending would be spoken like é instead of è), how is going to name his file ? And how the reuser will see the difference easily ?

Following this idea, we should also take the sex and age (somtehing like child, teen, adult) into account for the name.

Pleclown (talk) 08:47, 6 April 2016 (UTC)

@Pleclown: Very good point about Metropolitan French accent. "Speaker from XXXX" is a good solution for {{Pronunciation}}, I'll put that to use if there is no objections. You seem to be wanting to name all the files for French pronunciation different than the style we have in use for any other pronunciation language (that i know of, at least). My question is, what's wrong with simply Fr-Poulet? The description will clearly say the accent, and the image will be categorized based on the accent. Between the two, the file (if it existed) can be found via search and categorization. Yes, perhaps in wiki context you cannot see the difference in the links File:Fr-Poulet.oga and File:Fr-Poulet 2.oga but this is why categorization and descriptions exist. While it may be possible for an original uploader to put sex and age into the file name, I have yet to seen it done thus far and I do not want to see people renaming the files guessing if someone is a teen or an adult (the difference in age can be as small as a year, unlike child and adult). That sounds like a disaster. I would however support creating Category:Pronunciation by gender, Category:Female pronunciation and Category:Male pronunciation (or whatever sounds good) and categorizing the files accordingly. This way, an error can be fixed in a simple edit. Can you give me an example of how you'd name a french toulousan speaker, adult, female for amphithéâtre? File:Fr-Toulouse-amphithéâtre-adult-female.oga? I feel we are then going to get conflicts of the language of what the gender and age should be. Regardless of what we decide on, if we put it to use we may get files uploaded as Femelle (which is easy for a non-english speaker to identify) but then if this moves over to the Spanish pronunciation and half are uploaded as "Hembra" and the other as "Female", there will no doubt be confusion and per the language policy, it'd be inappropriate to rename them to Female. This is why I think all around categorization for accent, gender and age is the best result. I apologize if I'm coming off strong, I've yet to have my morning coffee! :) Riley Huntley (talk) 20:25, 6 April 2016 (UTC)

Commons:WikiProject Pronunciation

Hey all, I've been bold and created Commons:WikiProject Pronunciation. Commons has over 500,000 pronunciation files and they need a LOT of work! Any help would be appreciated, especially with foreign languages. Check out Commons:WikiProject_Pronunciation#Open_tasks, find your favourite language at Commons:WikiProject_Pronunciation#Categories and help out. Anything helps. :) Riley Huntley (talk) 04:46, 13 April 2016 (UTC)

MediaWiki:Mwe-upwiz-license-cc-subhead

We've updated this system message to apply this proposal.

Translations of this message are welcome. --Dereckson (talk) 13:31, 14 April 2016 (UTC)

@Dereckson: The text which I can see at the moment in MediaWiki:Mwe-upwiz-license-cc-subhead differs from the text in the proposal, so before I start translation I would like to know if it is “official version” (or a mistake). --jdx ^Re: 17:20, 14 April 2016 (UTC)

I'd suggest to fix it according the proposal but keep it short and if too long, ask again on the village pump for feedback. --Dereckson (talk) 17:30, 14 April 2016 (UTC)

@Dereckson: Just a note about English text from a person who is far from being fluent in English. IMO it does not sound clearly. Eg. what does “these” mean in the following context: Not all Creative Commons licenses are good for this site. Make sure the copyright holder used one of these licenses.? Does it mean “good licenses” or “not good licenses”? IMO the 2nd sentence should sound like Make sure the copyright holder used suitable license. Or “acceptable”, “proper”, etc. Next, If the work is already published online, but not under that license online, also does not sound well. Which license? OK, I know that when a reader reads the whole text, (s)he can figure it out that “these/that” mean “good license(s)”, but IMO it should be stated clearly. --jdx ^Re: 22:42, 14 April 2016 (UTC)

Commons:Project scope/de

Can a translation admin patrol rcid 246290378, which is this edit? I cannot patrol translated pages. Thanks, ★ Poké⁹⁵ 02:56, 16 July 2016 (UTC)

I am tanslation admin and I cannot mark it as patrolled either. To be more specific, I am quite sure that it was I who marked this edit as patrolled under RTRC a few days ago. The "mark as patrolled" message disappeared (however I am not sure if it ever was there), but for an unknown reason the file/edit still "hangs" in RTRC. BTW. A few minutes ago I reverted this edit, but it "hangs" in RTRC just like de version. --jdx ^Re: 07:31, 16 July 2016 (UTC)

Maybe you could mark it as patrolled using Special:ApiSandbox? It may be a bit complicated, but all you need is to set the action to patrol, then go to the "action=patrol" section, set rcid to 246290378, then get a patrol token by clicking the left arrow at the right of the bottommost field, and click Make request. I tried using API Sandbox and it doesn't work for me, maybe because I am not a translation admin. Thanks, ★ Poké⁹⁵ 23:40, 16 July 2016 (UTC)

I does not work: https://www.dropbox.com/s/yjjtfoi4niz76vu/API%20sandbox.png?dl=0. IMO the "tpt-patrolling-blocked" message suggests that patrolling of translated pages has been turned off and after some thought I think this is the right move because translated pages are edited by a bot on behalf of a translator. However such pages should not be shown in RTRC – only source pages (ie. usually in English) should be shown. --jdx ^Re: 10:11, 17 July 2016 (UTC)

help

where the page can be translate with manually(click edit) without translate tools? Thanks :)Murbaut (talk) 01:54, 29 August 2016 (UTC)

Why isn’t the Translate interface good for you? Each translation unit can be edited at its page (Translations:Page name/id/lang, where Page name is the translatable page’s full title (including namespace), id is the translation unit’s identifier (usually an integer, incrementing on the page; you can find it as <!--T:id--> on the English original page) and lang is the target language’s language code). --Tacsipacsi (talk) 11:37, 29 August 2016 (UTC)

Translations for gadget HotCat

Can someone help me in creating the page MediaWiki:Gadget-HotCat.js/mr. I want to translate the user interface text to Marathi language, to be used in Marathi Wikipedia. When tried, it says 'you do not have permission to create this page'. Also, in continuation, pl copy the contents of MediaWiki:Gadget-HotCat.js/en in it so that those can be edited by me. Thanks in advance. --V.narsikar (talk) 17:09, 16 September 2016 (UTC)

Pages in MediaWiki namespace can be edited – thus also created – only by administrators. So if somebody would create it, you won’t be able to edit it. You can create its talk page with an {{editprotected}} template (and, of course, the text you want to have on the content page), and then an administrator will create it (I’m not one). If you add the |technical=yes parameter, it can take a bit longer, but you can make sure that the admin won’t mess up anything even if you mistyped something. Further editing will also be possible through edit requests. --Tacsipacsi (talk) 11:37, 18 September 2016 (UTC)

Where is the message of "Subpages" on the left sidebar

Hi! In Japanese Commons pages, "Subpages" on the left sidebar is still not translated, but I can't find its source message at translatewiki. Does anyone know where it is? Darklanlan (talk) 12:21, 15 December 2016 (UTC)

@Darklanlan: I suspect that creating MediaWiki:Subpages/ja with appropriate content will do the trick – on my request Polish translation on Meta has just been done this way: m:MediaWiki:Subpages/pl. However, on Commons this message has been already translated into Polish, but MediaWiki:Subpages/pl doesn't exist. So translated message must be taken from other place, but I also was not able to find suitable message on translatewiki.net. The strange thing is that using ?uselang=qqx on Meta (e.g. https://meta.wikimedia.org/wiki/Main_Page?uselang=qqx) shows that the message is called "subpages" (text "subpages" starting with a small "S" closed in parentheses), but on Commons message name is not shown, just ordinary text "Subpages" (starting with a capital "S" and without parentheses, e.g. https://commons.wikimedia.org/wiki/Main_Page?uselang=qqx). --jdx ^Re: 21:53, 15 December 2016 (UTC)

@Jdx: I didn't know ?uselang=qqx suffix, it's useful for translation! Thank you! However, it seems the message is coded as a constant string. ... Oh, I found it was implemented by the extension mw:Extension:Gadgets/Scripts/SubPages.js. But it's difficult for me to modify it, so I have posted this request at mw:Topic:Tha1tu9ot7iumlma. Darklanlan (talk) 01:41, 16 December 2016 (UTC)

I found it was written in MediaWiki:Common.js, so requested a modification on its talk page. Thank you, @Jdx and @Tacsipacsi replying me at Mediawiki. Darklanlan (talk) 16:38, 17 December 2016 (UTC)

 Done --jdx ^Re: 17:46, 17 December 2016 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. Speravir 20:19, 24 June 2017 (UTC)

Delete translation

Just came across Commons:Deletion_requests/no, but the "no" language code shouldn't be used ("nb" is used for norsk bokmål, like here). Can it be deleted? – Danmichaelo (δ) 13:07, 29 December 2016 (UTC)

 Done --jdx ^Re: 00:07, 31 December 2016 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. Speravir 20:19, 24 June 2017 (UTC)

An edit war

Hi. Please take a look at Commons:Village pump#An edit war --Piramidion (talk) 19:47, 2 January 2017 (UTC)

By now archived for months: Commons:Village pump/Archive/2017/01#An edit war. — Speravir – 20:26, 24 June 2017 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. Speravir 20:26, 24 June 2017 (UTC)

Revert the translation

Tracked in Phabricator
Task T155158

I tried to correct one wrong letter in the title of the Czech version of Commons:Project scope (Záměření → Zaměření) but some unwanted other changes were made unintentionally. However, to revert the changes is impossible for a common user. Please help. --ŠJů (talk) 07:13, 12 January 2017 (UTC)

A change in Translate Extention was introduced a few days ago. I bet that because of this change, and as a side effect of your edit, Czech translation of translation unit #78 has been "restored", which accidentally is a vandalism. You can't revert it, just provide a proper translation. --jdx ^Re: 10:37, 12 January 2017 (UTC)

Mark Archive of Reynosa's city hall for translate

Hi! I'm a GCI student and I'm marking and importing translations on some templates as part of a GCI task that can be seen here: GCI Task. GCI or Google Code-in is a competition runned by Google and Wikimedia is a part of it.

This is what I currently have: Archive of Reynosa's city hall, and I'm wondering if this is the correct way to do it? If so can the i18n subpage be marked for translation please?

Thank you--SacredWKnight (talk) 12:08, 12 January 2017 (UTC)

Thanks for your help in that area :) Generally yes, it's Ok. There was one little mistake ("language" instead of "languages"), and some untranslatable stuff usually should be hidden in the "tvar" tags, like this: Revision of 229476879. After everything has been done, the parameter "base" on the main template page should be changed to /i18n, like this: Revision of 120201572--Piramidion (talk) 12:58, 12 January 2017 (UTC)

Thanks for the help! I'm probably going to ask for some more marking after this but I want to ask first, is what I'm doing (moving the old translation before marking) is right? Since the guide while descriptive doesnt really tell if I'm being correct or not.--SacredWKnight (talk) 13:21, 12 January 2017 (UTC)

Yes, the old translations should be moved before marking the main i18n page for translation, that's correct.--Piramidion (talk) 14:54, 12 January 2017 (UTC)

And now I'm stuck, apparently something about move abuse. Can this be undone?--SacredWKnight (talk) 13:37, 12 January 2017 (UTC)

Idk what that means, that filter is hidden. Perhaps that's a temporary measure. And it might be you need an "autopatrolled" flag to overcome it (some admin might help you with that). Btw, for me there's some limit of pagemoves too – I can do only 2-3 moves, then have to wait for a minute or so, then I can proceed. --Piramidion (talk) 14:54, 12 January 2017 (UTC)

It means that new users, with low edit count, can do only one move per 10 minutes. --jdx ^Re: 15:26, 12 January 2017 (UTC)

Interface group (wiki-translatable) is not translatable for common commons users

Interface group is not translateble by Special:Translate interface (https://commons.wikimedia.org/w/index.php?title=Special:Translate&group=wiki-translatable&language=ml&filter=%21translated&action=translate), because the group contain mediawiki messages. Moving to translatewiki may be useful--Praveen:talk 15:58, 26 February 2017 (UTC)

Afaik, these are local mediawiki messages, they cannot be moved to translatewiki because of narrow scope. And the interface group is actually translatable, it's just that it needs admin rights for that. I've translated some of the messages using {{editrequest}} on the relevant talk pages, but I'll need to find some admin eager to implement my translations.--Piramidion (talk) 00:41, 27 February 2017 (UTC)

In its current form, this is pretty unusable for non-admin commons users--Praveen:talk 04:23, 27 February 2017 (UTC)

{{Stdrf.ru/i18n}}

I changed the format of the strings on this template {{Stdrf.ru/i18n}}. It was previously formatted like {{#ifeq:{{NAMESPACE}}|{{ns:File}}|This file is|These files are}}. I believe that 2x whole-sentence strings will allow for more accurate sentences. I made the change [1] and just wondering if it could be marked as ready. Await any thoughts or insights. Cheers. Seb26 (talk) 19:04, 20 April 2017 (UTC)

Marked. After updating all existing translations came it to my mind that we could have used PLURAL: {{PLURAL:<tvar|1>{{#ifeq:{{NAMESPACE}}|{{ns:File}}|1|2}}</>|This file is|These files are}}. Using it, the currently two messages could have been reduced to one, and this is also the way MediaWiki localization works. --Tacsipacsi (talk) 19:51, 20 April 2017 (UTC)

Thanks for that. Will keep it in mind for future templates but I guess the solution we have now also works appropriately. Seb26 (talk) 20:36, 20 April 2017 (UTC)

{{Scan}}

I noticed that this template only contains 3 strings with a large number of translations for use on artwork images with {{Artwork}}, but it has been fully protected since 2011. Rightfully so, considering it has 110,500+ transclusions. Personally I'd like to add strings in Spanish for this but I figured it might be better to address an ongoing problem. See Template talk:Scan for a history of admin protected requests going back quite a number of years, with some requests still currently pending (I think).

For this reason, I'd like to propose that this template be updated to use a better method of localisation. One that allows the main template to be protected but allows translators to make their changes freely. Note that the strings are "Scan from the original work", "Scan of a photocopy of the original work" (xerox) and "Scan from a facsimile of the original work". Two versions I made designs for:

• Autotranslate: {{Scan/sandbox}}, with {{Scan/sandbox/en}} and {{Scan/sandbox/es}} (example), each language has its own template page with the switch for (Original/Xerox/Facsimile) directly on this page
• Translate extension: Scan/sandbox, with the strings stored at {{Scan/i18n}} which would generate strings at Translations:Template:Scan/i18n/1/en. (For testing purposes, this sandbox revision points to the template namespace instead: Template:Scan/i18n/1/en, etc.)

I prefer the Autotranslate variation, because from my interpretation of the situation code-wise, it is probably less performance intensive because of Autotranslate itself (which uses Module:Fallback). My /i18n version for Extension:Translate has to make use of {{SuperFallback}} which is still currently a parserfunctions-based template, and I feel it is a little bit 'hacky'.

Then the other argument is if new strings are added more frequently, or are new languages added more frequently: judging from the history, there's really only been 3 strings (xerox/photocppy/facsimile) over the last few years and it's more about adding/changing the languages for those 3. So Autotranslate works better (keeps the strings together per language) than Translate, the way that I look at it.

What do translation admins & others think?

seb26 (talk) 15:24, 9 May 2017 (UTC)

I think it should use the Translate extension—it doesn’t have to work in the way you used it, the subpages themselves can be embedded. Translating using the extension is much more convenient, and new messages can easily be added to all translations at once (i.e. it doesn’t cause error, of course nothing will be translated “by itself”). The master version cannot be embedded directly (it generates garbage output), but the translation subpages can. --Tacsipacsi (talk) 15:48, 9 May 2017 (UTC)

Good idea. In this scenario, {{Scan}} would use autotranslate which would use Module:Fallback naturally to produce a transclusion of {{Scan/i18n/es}} or the appropriate language, which itself would then do the #switch for the 3 strings. As a result the #switch code is stored centrally, English strings are displayed in scenarios where there is no translation, and everyone can edit the strings while the template stays protected -- cool. I support this, thank you for suggesting. seb26 (talk) 16:03, 9 May 2017 (UTC)

I marked the translation subpage for translation—the next step is migrating the existing translations to the new system, and then we need a “regular” admin to edit the main template (I am only a translation admin). --Tacsipacsi (talk) 16:11, 9 May 2017 (UTC)

Ok, I updated {{Scan/sandbox}} so it reflects exactly what should be the new code of {{Scan}} for the admin's convenience. I think I will get started on moving the translations, but @Tacsipacsi: what do you think about Template_talk:Scan#.22Book.22_in_the_text indicating that some of the translations still refer to the word "book" instead of "work" as in work of art? Should these just be excluded for the moment? Unless there is some way to add a translation but with the extension deliberately mark it as outdated. seb26 (talk) 16:54, 9 May 2017 (UTC)

The only way I know of is changing the English version to “book”, importing these translations, and then changing the English back. This way outdated translations are marked with a pink background—I think that also while including. I’m not sure if it’s worth using this hack. First of all, I would wait a couple of days before hacking, hoping that most of the translations will be corrected soon. (When a language is partly translated, like Persian, there is no need, of course, to store the English texts as Persian, English automatically appears when there is no translation.) --Tacsipacsi (talk) 18:19, 9 May 2017 (UTC)

Seb26, Tacsipacsi, there is only one active edit request on this talk page – the one started by me. It took some time, but is now in the works. It is just so, that for old edit requests the template is not deleted, but deactivated, so you can see something like {{editrequest}}. You should in my opinion better wait, that is solved, before you walk on. Seb: You could also ask a Spanish speaking admin to translate the three needed strings for {{Scan}}. Cambalachero or Cookie seem both to be very active here and to have enough English skills. — Speravir – 22:47, 11 May 2017 (UTC)

What I forgot to add: When the latest edit request is solved, then there is actually no need for conversion to translation extension, I think. — Speravir – 23:18, 11 May 2017 (UTC)

Hi Speravir, yes it is looking good and people are responding well to the request. Also pardon my mistake for not linking this discussion to the actual talk page of Template:Scan and informing you of this sooner. I believe the translation extension will still be needed as in the future other translators will look to add their own languages, some main ones which are missing still like Arabic (there are only 21 available now but of course Commons supports much more). Alas as Tacsipacsi advised we will wait some more time before making any big changes. seb26 (talk) 00:04, 12 May 2017 (UTC)

I am fluent in Spanish, but my understanding of templates is limited. Please make a clear request on what needs to be translated and where. --Cambalachero (talk) 02:20, 12 May 2017 (UTC)

Hi Cambalachero, this template has 3 text lines which I added Spanish for here: [2] with the Translate extension. You can review or edit in that link if desired. Here we are discussing the need for this template to use the Translate extension. So technically at the moment we have most languages stored in the current way (directly inside the page of Template:Scan) or within the Translate extension (my first link in this message). I have suggested the extension method should be used here because Template:Scan is an admin-protected template but Speravir suggests that this may not be necessary. seb26 (talk) 02:41, 12 May 2017 (UTC)

Commons:Country specific consent requirements/table

I have prepared Commons:Country specific consent requirements/table for translation using the Translate extension. To implement, it would need the following modifications by a translation admin/admin:

1. Delete Commons:Country specific consent requirements/table/value/i18n/en as a placeholder example
2. Mark Commons:Country specific consent requirements/table/value/i18n for translation
3. Copy the code from (old)this revision of my sandbox into Commons:Country specific consent requirements/table
4. Mark Commons:Country specific consent requirements/table for translation

The reason for the conversion to translation is to eventually enable Commons:Country specific consent requirements for translation, which is the actual guideline page. The table is also used at Commons:Photographs of identifiable people, where on at least 7 completed translation pages, the table is currently the only thing that appears in English.

For an explanation of what templates/pages are involved where, I made an explanation list at: Commons:Country specific consent requirements/table/doc. Any thoughts or suggestions on the structure before we would go ahead, are of course welcome.

seb26 (talk) 15:26, 13 May 2017 (UTC)

A question for @Tacsipacsi: (in case you are interested, but anyone else can comment): I made this change on COM:PHOTO [3]. Do you think it will be necessary for the project page to communicate to the table what language it is in? The goal is on /fr to show the French table. A English user viewing the /fr project page should not see the table in English, and vice versa, which is what I imagine might happen if some part of the process along the line is checking for the user's interface language. How could this be alleviated/better designed? Let me know if I didn't explain this well. seb26 (talk) 15:26, 13 May 2017 (UTC)

On translatable pages, {{TNT}} should be used—it’s similar to {{Autotranslate}}, but selects the appropriate language based on the page language instead of the user interface language (a file description page’s language is always English, this is why {{TNT}} cannot be used there). --Tacsipacsi (talk) 15:54, 13 May 2017 (UTC)

Funny coincedence. I intended to ask myself, whether this could be made translated. Seb, regarding your mentioned change (Special:Diff/242549320/243965468), in my opinion this code would be better:

{{ {{#ifexist: Commons:Country specific consent requirements/table/{{int:lang}} | Commons:Country specific consent requirements/table/{{int:lang}} | Commons:Country specific consent requirements/table/en}} }}

Though the code is longer, you do not need any translation tag here. At least it worked fine in this kind with testing COM:PEOPLE language versions in the Sandbox.

— Speravir – 17:37, 14 May 2017 (UTC)

But why would we display the table in interface language? If I have German interface language set and open the English page, I expect everything to be in English, including any templates used on the page. This is what {{TNT}} is for. --Tacsipacsi (talk) 17:49, 14 May 2017 (UTC)

Ah, I understand. But a test in the Sandbox (only preview) showed the right transcluded content according to chosen language subpage, resulted in an error message of a template loop, though. The template is poorly documented in my opinion – this is the test code:

{{TNT|namespace=Commons|Commons:Photographs of identifiable people}}

--Speravir 20:26, 14 May 2017 (UTC)

I'm not sure in what circumstance it is throwing an error message Speravir, as I didn't encounter any in my own testing, even with TNT. However, I'd imagine a proper test of TNT versus another method would need the /table to actually have translated subpages, pending the completion of the steps I listed above. But I think what Tacsipacsi in principle is saying is correct, interface language serves a purpose for "no-language" pages (like how a File page itself has no language but contains multilingual elements) but not typically so in the case of these policy pages (which do have a defined language).

Back to topic: Does anyone have any other comments about the method for converting this table outlined above? seb26 (talk) 20:55, 14 May 2017 (UTC)

Seb, see above: “I understand”. And I just tested with a page, which already has existing language subpages. — Speravir – 23:00, 14 May 2017 (UTC)

I made a small fix in User:Seb26/sandbox (semantically, if something's starting with a colon it is supposed to belong to the main namespace). Additionally all country names must be made translatable, which leads to another issue: Commons:Country specific consent requirements is itself not translated, but if so, the section titles serving as anchors would depend on the active language. — Speravir – 23:00, 14 May 2017 (UTC)

Yes, country names. I wish there was a less resource intensive way to call country names in a language. Currently using {{Afghanistan|lang=xx}} for example, uses a module to query Wikidata for the entire file for Afghanistan including all its relationships and associated data, and then filters it down to just the name labels. As a result, doing this multiple times on a page like in this version of my sandbox means there is a noticeable delay in loading the page. It reported about 3 seconds and it used ~48 MB out of the 50 MB Lua memory limit. While we shouldn't preemptively concern ourselves with performance, I think in this scenario it is common sense to try and find another way.

Of course, the other simplest way is that we put <translate> around the country names. The downside of that is that we'd be creating like 50 strings worth of extra work for translators, but I think in the end unless there's anything else, this is the best option.

Finally, in the case that there is some discrepancy with the table anchors pointing to for example "#Estados Unidos" (Spanish for the US) when no such section exists, only a header with "id=United States", then I imagine it can be resolved by using {{anchor}} in each section header. Like so:

== {{anchor|United States}} <translate>United States</translate> ==

Then each country in the table has a hardlinked anchor for United States while the link label reads Estados Unidos

seb26 (talk) 00:10, 15 May 2017 (UTC)

┌───────────────────┘
Translation units should contain the section header markup, so it could look like this:

{{anchor|United States}}
<translate>
== United States ==
</translate>

--Tacsipacsi (talk) 19:46, 15 May 2017 (UTC)

Though this is semantically not fully correct, if there is no other way I would favour this, too. The translate extension needs some notes which are shown on translation, but not on the actual pages. So, here a note could be added not to translate the anchor. — Speravir – 17:05, 16 May 2017 (UTC)

Hmm, in what semantic context do you mean? At least, in the markup examples for Extension:Translate, this is the recommended method. Only text in translate tags creates strings that are accessible to translators, so technically the anchor tag in Tacsi's example falls out of their reach. seb26 (talk) 18:14, 16 May 2017 (UTC)

The anchor is for the following section and therefore belongs into the section title, not to the end of content of the previous section. Remember, that one can edit sectionwise. But I understand the reason, why it is set before. — Speravir – 00:00, 17 May 2017 (UTC)

Update. Could a translation admin & a regular admin please take a look at this discussion? The 4 steps in order at the top still need to be completed. The last two issues were about the country labels and the anchors, which now have solutions: I added <translate> to country labels so we will translate each country name individually for performance reasons; and the anchors, we will use the code example provided by Tacsipacsi above. seb26 (talk) 19:38, 6 June 2017 (UTC)

 Done--Piramidion (talk) 22:53, 6 June 2017 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. Speravir 20:28, 24 June 2017 (UTC)

Commons:Translation administrators

Please, add this page, Commons:Translators' noticeboard, to Commons:Translation administrators, at least to the "See also" section. In fact, I could it simply add myself, but a bit translatable explanation would be helpful, I think. — Speravir – 21:47, 25 May 2017 (UTC)

 Done --jdx ^Re: 05:40, 26 May 2017 (UTC)

@Jdx: what for did you change the tvar values? To add more unnecessary work for translators or what?--Piramidion (talk) 09:33, 27 May 2017 (UTC)

Thx, Jdx. @Piramidion: Actually, $link1 (as it is shown to translators) is way better than $1, and it was an easy fix. — Speravir – 23:11, 27 May 2017 (UTC)

Well, names such as "link1" are a bit more descriptive than naked numbers. --jdx ^Re: 05:22, 28 May 2017 (UTC)

An "easy fix" to make the tvars more descriptive (which is completely pointless in this tiny article) has contributed to incorrect statistics for 15 translations and forced the translators to do unnecessary work. As for me, if I want to do such visual adjustments, I update the translations as well, for the volunteer translators to not waste time because of my sense of aesthetics.--Piramidion (talk) 09:07, 28 May 2017 (UTC)

@Jdx: Shouldn’t it be possible to replace all $<number> with $link<number> in all subpages of Translations:Commons:Translation administrators with a bot or similar tools? Perhaps Steinsplitter’s bot? — Speravir – 18:13, 28 May 2017 (UTC)

Commons:Locator-tool

Please, mark Commons:Locator-tool for translation. (signature forgotten:) — Preceding unsigned comment added by Speravir (talk • contribs) 18:56, 24 June 2017 (UTC) (UTC)

 Done --Tacsipacsi (talk) 05:43, 26 June 2017 (UTC)

THX, Tacsipacsi. --Speravir

Alas, there has been some updates by Simon and me, hence it has to be marked, again. Please, also check for correct translation marks. It looks right in English, but I’m not sure, especially around T:13 to T:15: The image in T:14 was formerly marked for translation without any description, so the full embedding code appeared for translation. I’ve changed this now. — Speravir – 17:01, 29 June 2017 (UTC)

Tacsipacsi, I noticed two more small issues, so I made again changes, but the {{tnt}} use does not seem to work. Did I do something wrong there? — Speravir – 18:17, 6 July 2017 (UTC)

There is no need for {{TNT}} when there are no translation subpages, it’s for translated templates like message boxes, navboxes etc. For me, it works (at least on the original English page), but why use it if it doesn’t make things better? (You don’t have to write here if you just made some changes to the page, it’s on my watchlist.) --Tacsipacsi (talk) 19:14, 6 July 2017 (UTC)

Ah, I misunderstood the function. And thank you, of course. — Speravir – 20:24, 6 July 2017 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. Speravir 20:24, 6 July 2017 (UTC)