Localizing Item fields with import/export

[Jamez0r]

Hey Tony and everyone

I'm doing some research and planning for localization, and I believe I understand the overall process but the one thing I can't find is how/where the fields for Items and Locations are to be exported/imported for the translator.

(Note: I'm not using any 3rd party stuff like I2 Localization, and would just be using the "Database" tab -> Localization Export/Import. I am using version 2.2.13 and can update if anything has been changed)

For example, on my Item template I've added the "Description es" and "Display Name es" localization fields, but as far as I can tell they do not show up in the exported Dialogue_es.csv or the Quests_es.csv.



Is there a separate place for import/export CSV for the Items, Locations, etc?

Also, if I were to use a Text Table in order to localize UI stuff, what is the workflow for getting that translated? Is there any sort of import/export CSV workflow for that?

Basically TLDR of what I'm trying to do is to figure out what I am to supply our translators with, in order for them to translate the following:
1) Conversation dialogue (already solved with the Dialogue_es.csv export/import)
2) Fields on items, locations, etc - how to export/import that?
3) UI labels/etc - I see that there is the Text Table, but is there an export/import workflow for that?

Thanks a lot for the help, and apologies if this has been explained before, I've read the "Localization" section of the documentation and I also searched the forums, but didn't find this specifically.

Edit: Just wanted to add that I'm not at all against using I2 Localization or any other 3rd party stuff if that would help make the process easier! (Although Chat Mapper seemed a bit too expensive)

[Tony Li]

Hi,

To localize text tables, use the Text Table editor window's gear menu to export to a CSV spreadsheet. Then translate the spreadsheet and use the gear menu again to import the updated spreadsheet.

The Dialogue Editor's Localization Export/Import feature localizes quests and conversations. It doesn't localize items or locations.

You can use i2 Localization to localize all dialogue database content as well as text tables.

[Jamez0r]

Hi,

To localize text tables, use the Text Table editor window's gear menu to export to a CSV spreadsheet. Then translate the spreadsheet and use the gear menu again to import the updated spreadsheet.

The Dialogue Editor's Localization Export/Import feature localizes quests and conversations. It doesn't localize items or locations.

You can use i2 Localization to localize all dialogue database content as well as text tables.

Thanks for the info Tony!

I've got one hopefully quick follow-up question:

Lets say I have 1000 Items in my database, and the Items have a custom text field for "Lore Text", which is a unique sentence that describes the lore for that Item. If I understand correctly, for me to translate those Lore Text sentences using Text Table, I'd have to manually add entries for each of the 1000 Lore Text sentences.

If I were to get I2, would the integration allow me to simply add the "Lore Text" field itself, instead of individually adding all 1000 of the unique sentences? (Sorry I would just test it myself to find out, but I don't want to drop $45 on I2 just to find out it couldn't do it, lol)

I'm basically trying to figure out how to import/export those Lore Text sentences without having to manually list all 1000 of them, because doing it manually would be prone to a lot of human error.

Thanks a lot for the help!

[Tony Li]

Hi,

Yes, you'll be able to select Lore Text as a field to localize:

loreText.png (35.41 KiB) Viewed 397 times

Make sure to import the i2 Localization Support package that's provided in DS version 2.2.25+. It has enhancements over previous versions.

[Jamez0r]

Thanks so much Tony!

Gonna give it a go