Commons:Translators' noticeboard

From Wikimedia Commons, the free media repository
Jump to: navigation, search
Filing cabinet icon.svg
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
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)


Shortcut: COM:TN


Commons:Photo challenge - edit links[edit]

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[edit]

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?[edit]

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?[edit]

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 "Seb26" - Paris accent.
  • French pronunciation for "Seb26" - Metropolitan French accent.
  • French pronunciation for "Seb26" - 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[edit]

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[edit]

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[edit]

Can a translation admin patrol rcid 246290378, which is this edit? I cannot patrol translated pages. Thanks, Poké95 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é95 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[edit]

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[edit]

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[edit]

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)

Delete translation[edit]

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)

An edit war[edit]

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

Revert the translation[edit]

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[edit]

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[edit]

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}}[edit]

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)