ROFL Somewhere between 7mph and oh fsck that hurt, I believe. But I could be wrong.

Just plain old African bees. They are more aggressive. Just think of European and North American bees as docile.

Many companies are required by law to translate, if they had a choice they'd probably do what you suggest and leave it in English. Not sure how that impacts customers perception of the company though. Those errors don't look like auto translation, just lack of context and time pressure.

Almost certainly a lack on context to the translator (or it was a machine). I've seen a translator do the following: 1. Cold medication. "If you have a cold" translated to "If you feel cold". 2. South African constitution. "Citizens have access to a just judicial process" translated to "just the process" Granted the above is just bad translation as the whole body of work was available to those translator. But you can see how easily it can happen. Commercial translation are usually $N.NN per word, so choose the cheapest and you get things dones as fast as possible. Using tools that try help the translator but might not have the context either. Sure you can try get someone who is professionally certified, but those were also the very best translators who also messed up Microsoft's first Afrikaans translations. Iteration over time is the best way to iron out these things. Instead of hoping for perfection all the time. After all isn't that what we do with software? Somehow we want perfection from translators while we fix our buggy software in the background. TBH based on the volumes that need translating I'd take a "fix it when broken" attitude as the cost of getting it perfect just isn't worth it for products that might never sell a single unit. Focus on review and rereview on the top N products is probably the best approach. That will build up the translation memory and result in better and more consistent products going forward. It just takes time

Might relate also to Zero Tillage Farming. Applied in Zimbabwe commercial farmers where seeing massive yields by not ploughing. Ploughing would release carbon, kill the bugs and worms, create stratification in the soil. When they stopped ploughing the soil health improved and yields increased. I guess getting cows to be part of the process of converting the remnants from fields so that the bugs in soil can pull that into the underlying soil is part of the process of trapping carbon.

Probably more helpful to base that on some data points: US v China v India is the correct order for polluters per capita. With the US 8 times more of a polluter per capita vs India. https://www.google.com/publicd...

You're probably looking for something like Pootle. This is used by a number of projects doing localisation including: Creative Commons, OpenOffice.org and others

It allows online translation and management of translation projects. It translates Gettext PO (for software localisation) and XLIFF (XML Localisation Interchange File Format), by using standard localisation formats it makes it easy to manage both online and offline translations. The Translate Toolkit can be used to convert various formats into PO or XLIFF for online translation.

I'm not sure exactly what you need to do in the audio, do you want to overdub or use subtitles? If you want subtitles you can use sub2po from the Translate Toolkit to convert subtitle files to Gettext PO. You'd still need to subtitle the files, then you could put those on Pootle to allow anyone to translate them into their language.

If you have documents in OpenDocument Format (ODF) then you can use the Toolkits odf2xliff converter to allow those to be translated on Pootle.

Pootle allows people to translate online or offline and they can commit their work directly to a version control system from within Pootle. This allows you to automate most of the process for you and your users.