These ones?
https://github.com/mozilla-japan/translation/wiki/L10N-Guide...
Looking through that wiki there seems to be a lot of things that ML would get wrong.
Looking through that wiki there seems to be a lot of things that ML would get wrong.
I'm sure some translators were using ML before it was integrated, and those guidelines are here in particular to tell them about those problems.
Also, ML is now really good to translate between European languages, but Japanese is very different in its structure so ML from English to Japanese is not as good. I'm sure some people who only know English/French/Spanish/German saw that ML is pretty good, and don't realize that for some other language it just doesn't work.
As somebody who has to regularly bear "German" machine-translated UIs and manuals that originate in English, I can only say: No, it's not. It's atrocious.
Typically, when a new page is written in English, don't automatically generate a version in all languages. When a translator starts creating the page in their language, provide a button to pre-fill with ML translation if they want to.
And for users, you can display the English version with a message, "this is not translated in your language yet but you can read an ML version if you want".
The core issue here is the way the bot was deployed. The fact that they had the poor taste to make it auto-replace articles written by their own volunteers is idiotic and disrespectful in the extreme. A new bot should work entirely in the back end, sending proposals for translations to the volunteers, who can choose to accept them or ignore them. Once the rate of acceptance is very high, for a specific individual language, then you might consider automating further.
And yes, this effort needs to be done for each language separately. Just because the bot works well in Italian doesn't in any way guarantee that it will work well in Japanese. Machine translation quality varies wildly by language, this is a well known and obvious fact.