Thread history

From User talk:Metalhead64
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
20:55, 6 June 2019 StanProg (talk | contribs) New reply created (Reply to Wrong "machine" translations)
12:55, 5 June 2019 Nike (talk | contribs) New reply created (Reply to Wrong "machine" translations)
12:43, 5 June 2019 StanProg (talk | contribs) New reply created (Reply to Wrong "machine" translations)
12:38, 4 June 2019 Metalhead64 (talk | contribs) New reply created (Reply to Wrong "machine" translations)
11:17, 4 June 2019 StanProg (talk | contribs) New thread created  

Hi, I saw that you're solving such cases and I would like to ask how to proceed with them. In the Bulgarian translations we are having a bunch of translations 3000+ done by an contributor that does not have any knowledge of Bulgarian and translated most of them with "Machine" or based on similar translations in Bulgarian or other Slavic languages. I'm working on fixing this for some time, but there are translations from the "MediaWiki:Apihelp-****" category, that require deeper knowlege, which I don't have in some cases. Is there an easy way to remove the current translation, so the system to use the English one? Maybe to mark them somehow with template for deletion? Reporting every single one will take time and I don't think I can invest days in fixing other contributors mess.

StanProg (talk)11:17, 4 June 2019

It is possible to automatically delete all pages created by the user.

\m/etalhead 12:38, 4 June 2019

I found the {{delete}} template. Is it ok to replace the content of the specific pages/messages with this tempalte, passing as first parameter an explanation why this message should be deleted? --StanProg (talk) 12:43, 5 June 2019 (UTC)

StanProg (talk)12:43, 5 June 2019

No, don't use the template because it will be exported as-is.

I have a script that can fuzzy all translations by a given user.

Deletion of translations is very time consuming process, especially if they span across multiple repositories.

Nike (talk)12:55, 5 June 2019

The problem is that I have alrady reviewed and fixed a lot of those translations and if they are all marked as fuzzy, I will have to review them again. What I need is a simple way to remove the wrong translations that I can't fix at the moment. They are API related translations and are pretty much useless for developers and will just confuse them, if they are even used. If this is not possible, I will ignore them for now and will try to find a solution later.

StanProg (talk)20:55, 6 June 2019