Quantcast
Channel: Questions in topic: "localization"
Viewing all articles
Browse latest Browse all 210

How should I structure my localization string tables?

$
0
0
I'm about to add localization to my game! This is the first time I've ever done localization, and I'm trying to figure out how to structure my string tables. I have a Weapon ScriptableObject with hundreds of instances (Club, Pickaxe, Scimitar, etc.) and multiple localized fields (name, description, etc.). There are two options that make sense to me: **A single "Weapons" string table with multiple entries per weapon**. This would look like: * Weapons_en.asset * CLUB.name = "Club" * CLUB.description = "A thick, solid lump of wood." * PICKAXE.name = "Pickaxe" * PICKAXE.description = "Tool of sturdy miners." **One string table per field.** This would look like: * WeaponNames_en.asset * CLUB = "Club" * PICKAXE= "Pickaxe" * WeaponDescriptions_en.asset * CLUB = "A thick, solid lump of wood." * PICKAXE = "Tool of sturdy miners." The single "Weapons" string table structure will result in fewer files (especially since I have a few other ScriptableObjects like Weapon), but each file will be messier. The per-field string table will result in more files, but each file will be cleaner and the structure feels more "atomic" which appeals to my programmer brain. Which structure would you pick? Or is there a better way of doing this that I'm missing?

Viewing all articles
Browse latest Browse all 210

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>