Yes that should cover the issue. How can I mark the task as duplicated?

As an addition to the task, the Autotranslation seems to convert multiple calls for a same reference to multiple identical references under the same name. That is properly handled by Mediawiki but is error prone, since any change will break the reference.

Thanks for the answer Pau. What I was trying to point is that this ticket seems to search a better metric to understand where the Translation tool is working and where it isn't working. Aggregated data suggest it is already useful (since the survival rate of the created article is comparable with new ones) but the task description properly pointed that it may hid local problem. E. g. Es <-> ca translations are very close and usually produce aceptable output, but it seem indonesian and telugu languages have specific problems (the available automatic translators may be worse, the templates/style may be different and thus messed more often, etc). Having desaggregated data is needed to isolate those problem or you'll get crazy checking the hundreds of languages supported by the foundation

As a comment, the deletion itself may be a biased metric. Different communities has different approachs regarding deletionism vs inclusionism (e. g. how to deal with problematic articles). The % of deletions will show if there is any problem only in projects that answer to bad articles by immediate deletion but will underestimate the problems in projects that move them to workshops or mark them with templates for improvements (something that may correlate with projects lacking adminship manpower or focusing in growth vs quality)