Best practices for UI heavy dynamic localization?

Trying to figure out the best way to add localization to a UI-heavy scene essentially containing a dynamic spreadsheet – see attachment.

Localizing the buttons and column headings is trivial, however the data rows is my concern.

Scroll view contains rows of prefabs with dynamically assigned data; and could potentially have a few hundred entries, each with a string requiring localization.

At present, each “list item” has a LocalizeStringEvent component co-located with the Text component; and the “spreadsheet” control script is using TableEntryReference to set applicable localization table keys to each list item. The table reference is set in the editor and does not change at runtime. Specifically, something along the lines of:

foreach (LocalizeStringEvent t in listItemLocolizedText)

{

        t.StringReference.TableEntryReference = $"{tableKeyPrefix }_{tableKeySuffix }";

}

tableKeyPrefix and tableKeySuffix being a pair of strings getting concatenated to form a Localization Table Key … something to the effect of “EXPORT_REGION15”.

The LocalizeStringEvent components are cached by the controller, so no concerns about mass GetComponent() calls. Additionally, the localized part of the data is only updated when the list needs to be fully rebuilt – so no localization in the Update() loop.

While functionally this seems to work fine, the idea of having a few hundred LocalizeStringEvent components in a single scene, each registering its own listener and such, seems like a naïve implementation.

Is there perhaps a better way to handle this?

 

I think using LocalizedStringTable to get the entry strings in bulk is the way to go!
Thanks for pointing me in the right direction Karl!

Having implemented the above, do I need to listen to any other events other than LocalizationSettings.SelectedLocaleChanged? (assuming my own code doesn't make changes to table entries, of course)

 

That's perfect, thanks for another great explanation Karl!

 

Hi, what do you mean by:

The cache part.