Hi all,
You know as a concept usage of Google SpreadSheets for multilanguage support is great. You just write =Googletranslate($A1,“en”,“it”) and vala!
However, it is not the case.
Intentionally or not intentionally Google SpreadSheet translate gives you the “Second” close meaning not the actual translation. ( Google spreadsheet translations not correct - Google Translate Community )
Be aware, you can ruin your game translation by using it!
1 Like
Generally, you probably should want to hire a professional translator instead.
Never use Google Translate anyway. There are various localization service providers out there that provide a better job because actual native speakers are translating your texts.
(Interesting, though, because I didn’t knew you could do that GOOGLETRANSLATE thing in Spreadsheets.)
That’s all very well if you have the budget to cover translation services. If you haven’t, like most indie devs, you need some free service to approximate until your creation generates enough profit to be able to afford a professional service.
1 Like
Found this thread while researching, and title got me confused 
Speaking of spreadsheets, you can use them, but if you will involve some volunteers or hired translators to translate your game. As said above, Google Translate is not recommended for games. I recommend using localization software with the Unity localization package integration with translators in the project. I linked an article so that you could check it out.
I think Google uses an older translator model for sheets. The results are much more “primitive” compared to what you get from using the web translate UI.
Maybe it’s done for performance reasons? After all, you need to actually pay to use the translate API for batch translations, while using sheets you can do it for free. An older (and simpler) translator would use less server resources.