I experienced the same with a test translation for "Lives and Opinions of Eminent Philosophers" from English to Spanish (translation ID: 629216). The trash button in the dashboard has no effect and the console shows no error.
This is working now. One related piece that was still pending is showing the additional details to better explain the situation (T203377), which can be a good follow-up.
Tue, Apr 23
The initial adjustment of the thresholds just went live (T221353). It would be very helpful if you could help us check the following aspects to better understand the impact on Indonesian content:
- Evaluate if the change is effective to avoid problematic translation. Review the translations created with Content translation focusing on those created after the change (April 23 7pm Jakarta time), and report cases of translations published with too much unreviewed machine translation, or the lack of them.
- Evaluate if it is still possible to create good translations. Try to create a proper translation using machine translation. For testing purposes you can publish under your user namespace by selecting the settings icon next to the publish button. After editing the initial translation enough to make it read natural in Indonesian you should be able to publish without errors.
Mon, Apr 22
Thu, Apr 18
As I mentioned above, what we are proposing is to disabling the use of machine translation for those users making a bad use of it. I think that is aligned with the request of the community.
@Mimihitam, I'll try to provide some clarifications below:
Thanks for the replies. I agree that the presence of “raw or lightly edited machine translation” is very problematic in the ways all of you described. We all want to prevent those bad translations. The main point of our proposal is precisely to prevent them, while not preventing also “heavily and carefully edited machine translation”.
Wed, Apr 17
Thanks for reporting this, @Aldnonymous. Getting feedback about how our tools work on different languages is very useful. Before considering disabling machine translation, which will affect also users making good use of it, we want to explore how to better adjust the current system to prevent the publication of contents that contain too much unreviewed machine translation. I started the conversation in Indonesian Wikipedia to get further feedback. The translated version of the message is shared below:
Tue, Apr 16
Mon, Apr 15
Fri, Apr 12
Thu, Apr 11
Wed, Apr 10
@Petar.petkovic are you planning to continue working on this beyond the work already done on the exclusion of references list from consideration as unmodified content?
Content translation relies in templateData to transfer templates across languages. In particular, templateData is used to check the names and aliases of the parameters of the corresponding templates across languages. The current issue makes the process of fixing this even more complex for editors as the case of T219346 illustrates.
Tue, Apr 9
Yes. The scope for this one is for content created with Content translation. So maybe the VisualEditor-related tags can be removed.
@Etonkovidova here we need to check that for a reference list added to the translation (when using MT, copying from source, or manually added) that users don't further edit, the tool (a) does not show a warning of too much unmodified content, and (b) when published the content does not get added to the tracking category (for each language you can search for the "cx-unreviewed-translation-category" category in their list of tracking categories).
Mon, Apr 8
This issue was mentioned here.
The issue has been mentioned in this comment.
T192316 seems related to this one. As I mentioned there, there is a new design for this particular dialog proposed in T217827: Update grey interlanguage links entry point popup.
Some aspects may still apply, but others such as the input may no longer be relevant. At least for this particular dialog.
@Petar.petkovic is there anything else pending in this front? I tried with an account that was using CX1 and was correctly migrated to CX2.