Removing some Bulgarian translations

CLOSED This issue is closed by siebrand

A way forward has been told, reopen if there are updates?

I really don't know the procedure about the adminship here, but I would ask for admin rights on this wiki to be able to delete the messages/translations made in Bulgarian which are total nonsense, machine translations and so on, that I can't figure out (yet) how to fix. I'll use the right to delete only for Bulgarian translations and not on other pages on the wiki. It's better to have the original and not translated string in the software than a misleading or confusing translation.

Deleting the translations' pages won't delete the translations, that needs to be done by a developer on the code directly and then also on the wiki.

Fixing translations is usually much easier. If you're speaking of MediaWiki, I'd suggest you to directly commit a patch removing the wrong messages, see also mw:Developer access.

Also, if translations are really that wrong, please also find out what translators made them, discuss it with them and report the result of the discussion so that their translator access can be reconsidered, if needed.

My point is to remove translations before they're commited. I am trying to discuss the issues and to fix the messages, but the Bulgarian "wisdom of the crowd" is: Let's have it in Bulgarian, no matter it's a machine translation, misleading or confusing. If it really is, someone will fix it.

I think that's totally wrong. I spend hours and hours with MediaWiki and other software, trying to replicate the messages and see them in context, trying to figure out how to better present the message in Bulgarian. It takes time. Can't do it quickly enough with many translations, sometimes with extensions or other software I don't use and don't know.

Hello, if this is about future translations you have only two options:

1. add !!FUZZY!! to the dubious translations so that they're not exported;
2. do what suggested above with translators who are really problematic.

Deletion is not used for this in general, sorry. Thanks,

Adding !!FUZZY!! might work, I'll try it, thanks :-)

Fuzzy translations are also exported. It's only a tag, not a block.

Sorry, I always get confused about this point. :-( It's nevertheless useful to add it in those cases and the rest I said is still valid (I hope).

Okay, I need another solution, then. Because the translator, which rights ware once removed, is back and contibuted tons of nonsense and machine translations. No evolution of thinking, no improvement in contributions, just the same old song. (his current activity is due to the needed requirements as localization to start a Wikitravel wiki in Bulgarian, manipulating the non-Bulgarian speaking community)

I'd suggest again removal of translator rights for Stanqo, this time permanently.

Plus granting such rights in future after careful discussions with the local/language community, probably after some period of discussions with the applicant for translator rights. It's really important to have volunteers recruited, that's true. But it's of no less importance to have them (1) truly involved in the processq, its technical issues, adopted conventions and style, a well as (2) aware of the responsibilities related to localization of so heavily used software as MediaWiki.

I don't know whose idea it was to bind having a new sister project (in the case, BG WikiVoyage) to the condition of having all system messages translated, but this stipulation opens the door for misuses, when translation rights are given to people who don't care to exercise them reasonably...

It's pretty much lame to loose 2 days trying to figure out and fix the machine translations, discussing the best possible ways to fix them, while that time we could spend for new translations and improvements and simply delete the shitty ones. Sorry, I can't assume good faith in this case, where the only (sick) ambition for the user is to be proud that Bulgarian community have another dead on arrival sister project (most of the others are inactive or full of vandalisms). And what... we have to deal with that issue every single time Wikimedia decides to launch another sister project?

I have again reviewed this case, and I really don't want to block the user. This user has contributed seemingly without ill intent for the past few years. I have advised the user to no longer contribute by translating, but by reviewing or recruiting new translators.

I hope that ends the issue with the user's translation quality. Please inform me if any future issues arise.