Help talk:Contents/Translation Rules

RecentChanges filtering

Is it possible to filter out translations in Recent Changes? Because the option isn't working at the moment. --Hiccup (talk) 04:46, 24 December 2013 (EST)

It's currently working for me, though it's only filtering out articles in the Translations: namespace. The Pagename/cc edits still show up. If those are the edits you don't want to see, I would expect them to slow down as soon as most of those pages get translated, so if you can live with it a little bit longer, the activity rate will likely drop soon.

Bast (talk) 05:19, 24 December 2013 (EST)

According to Zerojay, it should be fixed by default. --AquaBat (talk) 11:04, 24 December 2013 (EST)

Translation problem

I've got a problem on the page Super Mario Bros. 3:the compare function haven't worked because the translation add-on have cut it.So,there is now a great {{compare|| leftt = Hidden Tile| rightt= In-Game On the french page. So,is there a way to delete it?Please.— The preceding unsigned comment was added by Darkluigi1808 (talk • contribs)

Done. -Einstein95 (talk) 06:54, 28 May 2014 (EDT)

Thanks.The only problem now is the fact that the add-on don't let us translate if there is links in it(excepted the TheCuttingRoomFloor links).Also,I can't translate the part just after that compare function without making it appearing again.So the translation cannot be complete at 100%.--Darkluigi1808 (talk) 08:57, 28 May 2014 (EDT)

I managed to fix the template problem. If you could translate the untranslated sections and put them on pastebin or somewhere like that, I could try and fix the problem. -Einstein95 (talk) 14:18, 28 May 2014 (EDT)

Here's the link:http://pastebin.com/tyenJgA8 . It's for testing purpose,to see how the problem can be fixed. But if needed,I can translate the last part of this page. Also,the Super Mario Bros. article create pages for translation but is empty on mobile,whatever is done.--Darkluigi1808 (talk) 02:59, 30 May 2014 (EDT)

That is odd as it works fine for me as you can see here, so it seems to be a problem with the plugin on mobile devices then. Sorry about this, but if you have any more problems feel free to contact me via IRC. -Einstein95 (talk) 03:15, 30 May 2014 (EDT)

It appear to be a problem with links: I think it needs a captcha in order to make the change. And because the add-on doesn't handle the captcha, it will never translate, and only Admin can do the changes.Next time I promise I'll use the IRC.--Darkluigi1808 (talk) 08:37, 30 May 2014 (EDT)

Problems with subpages for many translated articles and alternative solution

I noticed a problem on MANY (and possibly ALL?) translated pages, an issue that I have experienced myself when creating a translation for the French version of the very first Mega Man:

• despite attemps to follow the guidelines, some original English pages use something that appears as "namespaces" in the subpage category of the page and it doesn't show anything in the localized article if translators carry it over as-is, leaving the localized "subpages" section blank.

• When there are indeed fully-written subpages links instead of the mysterious "namespaces" function, trying to follow the guideline and carry over the original subpage link followed by the "|tr=" code to display a translation actually results in a fake solution: instead of linking to the original subpage, the link tries to search for a non-existant subpage of the same name INSIDE the localized page and therefore fails to link to the original subpage as it supposedly should do.

• The solution I found was to avoid using the subpage template mark for localized articles: you need to consider them normal links presented in a list where you copy the title of the actual subpage (for example "Prerelease:Mega Man (NES)"), between the double "[" and double "]" signs and add a vertical bar (|) to display another text instead (in this case, the translation). The presentation looks like a simple list compared to the original "subpages with big letters inside rectangles" presentation of the original English page, but it is fully functionnal.

If this issue turns out to be true, the guideline about translating subpages needs to be updated as it actually does not really work or leads to unexpected problems as such, resulting in a blank space in the "subpage" section or misdirected dead links on many translated pages (and perhaps all of them, the numerous ones I checked at least...). Instead, if there is no solutions, translators should be told to replace the subpage marks with regular link marks, as if the subpage they link to was a main page, and just adding a vertical bar to translate the name of the page and adding some description if the original page shows some. Hope this can help in any case. --Cold Skin (talk) 17:37, 27 February 2022 (UTC)

Howdy, a fellow translator here. Let me help clear this up. The {{namespaces}} template is designed to create links to sub-categories of pages in the sub-pages section, such as a Proto: page or a Prerelease: page. When doing translation of pages that don't have any normal subpages but do have {{namespaces}}, the idea is to translate the namespaces template so it will point to any such namespace pages that have been translated, with translated names (an example can be seen here). It is normal it will not show any pages if you use it on the page as is and none of the namespace pages that go with the game page have been translated (as it's looking for a translated page there). It's preferred if the section is left as is with the template, and will fill out as you translate the namespace articles relating to the game (if they're marked for translation). Any dead links created by people messing with the templates and attempting to get the {{subpage}} template to point to the namespace articles will fail, because they cannot be pointed to that way. I'd like to make a mention I will add this to the page here to help clear up potential future confusion for new translators, and would also like to say I'm always here and happy to help with questions about the translation tool or how to do certain things, I have lots of experience with using it. Feel free to send me a talk page message or ping me on the TCRF discord (I'm Luna 🌸#5707). -- Luna (talk) 20:13, 27 February 2022 (UTC)

Hi, thanks for the quick reply! I understand a bit better what the "namespaces" is now, but this brings me to a new question for the future: if it doesn't show anything until the subpages are translated (if ever), isn't it better to just put direct links to the English pages that actually show on the page? Because otherwise, it leaves readers of the localized versions the strange impression of having a section where they expect subpages, but then it looks like there's no subpages at all since it's just blank, as if the section was created for nothing.

As far as I'm concerned, I'll put back the "namespaces" function on the two articles I've translated since it seems to be the way to go, but I'm a bit worried it might leave potential readers perplexed as they'll see an empty section, believing no subpage exists at all and that the subpage section of that article was created for nothing except a blank space. I'm wondering if it wouldn't be better to have the guideline tell people to check if subpages have been translated in their language when they choose to translate an article and then follow one of two instructions depending on the answer: either they haven't been translated and they put direct links (with the "tr=" system) to at least lead to the English pages instead of having an empty section OR they keep the "namespaces" or original links intact if subpages have indeed been translated. And people translating subpages would be told to check the main page after their translation to simply convert the subpages section to "namespaces" if it is time to do so.

But don't worry, all of these are just thoughts in case there's a way to improve things in the future (so that it never leaves sections empty for pages that are supposed to be 100% translated but which actually show either a blank section or dead links in most cases), but be sure I'll go with the flow and keep following the rules without any fuss anyway! :-D --Cold Skin (talk) 23:24, 27 February 2022 (UTC)

It's perhaps something that could be looked into in the future, as the rules are a little wibbly-wobbily and some aren't fully set in stone. I'm planning on doing a rewrite of the rules for full page translation (as one of the more experienced translators here) and at that time we can try and set some new rules in stone. Generally it seems the consensus is for pages with namespace subpages, you would just end up leaving it blank (as a reader in that language would be able to see the original page and just note the translations for the namespace articles isn't done yet), and then for pages that actually use the subpage template, do the "tr=" thing, it'll leave a dead link until the subpage is translated. We could also look into re-writing the namespaces template so it checks for non-translated versions of namespace subpages, but that's a future thing, I think. I did also want to note, if you run into a page that has subpages that aren't marked for translation (no translation button shows up at the top, nor a language bar) you can ask a moderator politely to mark the page for translation, so it can be added to the translated page (in the form it is to be done). -- Luna (talk) 00:24, 28 February 2022 (UTC)