Apologies for using this category, there doesn’t seem to be one specifically for ‘Catalog’.
Regarding the latest GenAI policy for Catalog, AI Disclosure :
We no longer accept titles that use generative AI for art, audio, music, text, or dialog.
It’s the “(but not limited to)” in the followup text that has me puzzling.
Context: I’ve looked into professional localization services, they cost roughly US 10-cents per word. For a large RPG that can add up fast (back of the envelope for my particular case is excess of USD$1000 per language). I was intending to support 5 or 6 languages (or more) for my upcoming title (Under The Tree 2), but if I can’t use machine translation then based on my estimated sales it’s not practical to launch with more than one non-English language - right now I use the proceeds from the previous title to pay my artist for her work for the current title, there’s not enough left over for professional translation into multiple languages as well.
I was intending to use Google Translate to generate localization files for various languages based on my ‘en.strings’ content, with an invitation to players to submit suggestions/corrections to be applied post-launch. Is this ‘still allowed’? If not Google Translate, is there a different machine translation method that’s acceptable? If not, then it would be helpful to know up-front, as this will allow me to concentrate on other areas of the game rather than extending internal support for additional languages that won’t actually be added.
Edit: note that I’m not intending to use machine translation to create game text (I write that myself), but translate it… just like I don’t use AI to generate my game code (I write that myself), but the compiler is what translates that code into the executable form. tl;dr: “en.strings→machine_translate→xx.strings” is analogous to “souce_code→compiler→machine_code”.
I realize that things are getting blurrier and blurrier lately.
So, please clarify.
Thanks!
– Tengu