Text table localization with categories and I2

[Kaizen]

Hello, is it possible to have subcategories while using text tables to translate quest machine quests texts?

Screenshot 2022-01-25 113530.png (28.99 KiB) Viewed 750 times

I tried using multiple text tables (1 per level). That would have solve the problem of having a very long dropdown. But in the end the terms are not categorised in different categories (by text table in I2). Problem is when importing (From i2) with DS to I2, we need to choose a texte table and all the I2 text table terms are imported to this specific text table. (to summarize, 100% of text table terms are now in level 1 text table for example)

I also tried adding / (slash) in the key but the / were replaced by dots at export (to i2). example "Level1/toilet_active_heading" were replaced to "Level1.toilet_active_heading" and wasn't in a sub category even if I created the category beforehand.

Any idea what's the best workflow/setup to avoid long dropdowns and to keep terms organized?
My game won't have a ton of terms but still it will be a pretty much long dropdown. Imagine a RPG with a ton of quests, how would they do?

Thanks in advance

[Tony Li]

Hi,

The next update to the i2 Localization integration supports multiple text tables. You will be able to assign multiple tables to the DS To I2 window. They will all go into the same category in the i2 asset, but when you bring them back into the text tables, each text table will only pull the translations for its own fields. If the i2 asset has any new fields that are not in any text tables, those new fields will be created in the first text table.

[Kaizen]

Hi,

The next update to the i2 Localization integration supports multiple text tables. You will be able to assign multiple tables to the DS To I2 window. They will all go into the same category in the i2 asset, but when you bring them back into the text tables, each text table will only pull the translations for its own fields. If the i2 asset has any new fields that are not in any text tables, those new fields will be created in the first text table.

Thanks for the answer, can't wait for the next update!

[Kaizen]

Hi,

The next update to the i2 Localization integration supports multiple text tables. You will be able to assign multiple tables to the DS To I2 window. They will all go into the same category in the i2 asset, but when you bring them back into the text tables, each text table will only pull the translations for its own fields. If the i2 asset has any new fields that are not in any text tables, those new fields will be created in the first text table.

Any approximative timeframe for this new awesome update?

[Tony Li]

The release date for the next update is February 7, but I'll try to get the i2 Localization integration package out before that.

[Kaizen]

The release date for the next update is February 7, but I'll try to get the i2 Localization integration package out before that.

wonderful!

Sorry I have an additional question about that category for quest machine text tables. I know text tables are also used with DS but for me, it would be nice to be able to choose that category. The reason is, when we look at the generated spreadsheet, all my quest lines are located in the dialog system Sheet, after my long list of dialog entries. Could be confusing for the translators. Could it be something you let us choose? Or can you automatically differentiate text tables from quest machine and DS and put them in different categories?

[Tony Li]

There will be an option to include the text table name in the i2 term instead of "Dialogue System". If you have these assets, for example:

• Dialogue Database
• Text Table for DS named "DSTable"
• Text Table for QM named "QMTable"

Then the DS To I2 window will add 3 categories: "Dialogue System", "DSTable", and "QMTable".

[Kaizen]

There will be an option to include the text table name in the i2 term instead of "Dialogue System". If you have these assets, for example:

• Dialogue Database
• Text Table for DS named "DSTable"
• Text Table for QM named "QMTable"

Then the DS To I2 window will add 3 categories: "Dialogue System", "DSTable", and "QMTable".

Perfect! Thanks!