That's a good solution. Tell them not to use those tools would be great whenever they are chosen for the job :).

I have been involved in translations for a long time now and I also did a translation CCS before

I'm the one that really believe translators should never use deepL or any tool other then a dictionary and the terminology guides we provide

Because it's inefficient and the result can't be compared with a normal human translation

In sum, I think it's always easier (and probably cheaper) to redo the work from the ground up instead of trying to fix poor quality work

poor and low effort

If this guys are seriously interest in translating these resources, let them redo it with quality. If its not delivered, move the funds to general fund and we can move on

Yeah, it's better to redo. I once tried with someone who did that and took me longer to change than redoing it myself, and we both got so frustrated that we closed the Pull Request only missing one last paragraph to finish :P. It was a terrible experience but at the same time we learned a lot :).

.merge+ 1350

Added

.merges

.merge+ 1351

Added