Pixel Crushers Forum

Hi! I have a question about how to localize my dialogues for the next workflow:

How we work on dialogues:
- The game designer works on dialogues and quests in Articy
- then he/she import the result of the work to the DialogueSystem

How we translate texts:
- All translations are in Google Sheets (so translators could do their work online)
- Developer parse all translations from Google Sheets to local json-file
- Our own translation system parses json-file and applies localized strings to the UI labels, action descriptions, items title and description, etc. All, except dialogues and quests from the DialogueSystem

So, I need to translate dialogues and quests, but I have no idea where to start, because we have about 3 systems:
Articy -> Dialogue System -> Custom LocalizationSystem

I hope your advice can get off the ground

Are you using articy's localization plugin to create the Google Sheets? If so, you can import localization in the Dialogue System using these instructions.

Tony Li wrote: ↑Thu Nov 25, 2021 8:42 am Are you using articy's localization plugin to create the Google Sheets? If so, you can import localization in the Dialogue System using these instructions.

Hi! Yes, I read the article you show and did every step in your instruction. everything works perfectly, except for a few moments, so I'm gonna describe my steps. If I did something wrong, please, let me know

1) I've generated 4 *.xlsx files for each language: en, es, ru and cz with Articy:draft;
2) send them to Google Drive;
3) opened them in Google Sheets;
4) auto-translate every with Google Sheet formula (GOOGLETRANSLATE(E2; "EN"; "ES"));
5) downloaded translated files back (unfortunately, Google Sheets can't save own sheets in *.xlsx format, *.xlsm only available) to the origin folder
6) and, of course, DialogueSystem importer can't see *.xlsm files

but, before step 2, I imported translations to the Dialogue system, and everything works perfectly! Check the picture bellow

Hi,

It looks like all of the translations are in Russian. Is that what you intend? Or is it only because you hadn't added the translations yet because this is from step 2?

You can use an online tool to convert .xlsm files to .xlsx files. Or you can use a free spreadsheet app such as Libre Office.

Tony Li wrote: ↑Fri Nov 26, 2021 8:14 am Hi,

It looks like all of the translations are in Russian. Is that what you intend? Or is it only because you hadn't added the translations yet because this is from step 2?

You can use an online tool to convert .xlsm files to .xlsx files. Or you can use a free spreadsheet app such as Libre Office.

Yeah, it's okay. I created 3 copies from the original one (in Ru), just to check everything works fine.

I know I can use converters, but, you know, it sounds like: "hey! you should do some extra action before getting the result!"
and one or two extra actions - is a potential place for human factors. I'm afraid game designers can make some mistakes with converters and ruin translations... so... don't you think to add support for *.xlsm files for the future?

The localization importer uses Unity-QuickSheet, which doesn't import .xlsm.

If you remove the formulas in your Google Sheets document, it should download as .xlsx.

Tony Li wrote: ↑Fri Nov 26, 2021 8:48 am The localization importer uses Unity-QuickSheet, which doesn't import .xlsm.

If you remove the formulas in your Google Sheets document, it should download as .xlsx.

Oh, I see. Thanks!