As much as I despise the splurge of appalling so-called "AI" tools, is there any mileage in using the machine translation engines available in CrowdIn for doing pre-translations that can be checked and tweaked by human translators? Or is there too much scope for the machine tools getting it wrong and providing bad or potentially embarrassing out-of-context translations?

Just wondering if this would give us a leg-up to completing some of the pophelp packs, since it may seem a daunting task to create from scratch or from a sparsely-populated pack, but might seem less daunting if it just needs a sweep to check for accuracy and then tweak. Assuming of course, the tools are freely available. If there's cost involved, it's probably not worth it.

To be clear, I would only (potentially) advocate this usage on strings where no translation has been provided yet. No way would I want a machine tinkering with what we've already translated.

The setup wizard allows the tool(s) to "learn" context from other strings in the project at varying levels of granularity, but I'm not sure how accurate it would be.

Not sure also on the efficacy of using the tool(s) for individual textpack strings. The context there might be more difficult for a machine to ascertain.

Thoughts?