[Feature Request]: Better localization support for extensions

[Pikachamp]

Tell us about your request

As the tracker offers multi-language support, custom code extensions that display text might want to do the same. Currently there is no dedicated callback for a language change, so the current language has to be checked in another event like a redraw. This introduces inefficiencies as extensions cannot use the same preloading mechanism the tracker uses. Thus I propose to add a callback for language changes to custom code extensions so they can seamlessly integrate with the localization mechanism of the tracker and unnecessary checks and work can be kept out of more commonly executed callbacks.

Additional Information

No response

[UTDZac]

Thanks for opening this issue and sorry for the long delay in getting a reply to you.

Could you share some example code that demonstrates the issue? To my knowledge, it should be possible to use the existing language resource system that is already in place for the Tracker. The extension developer can add their own language keys similar to how the tracker does, then it can retrieve those as necessary for its own purposes and use-cases.

For example, on extension startup, it can add new entries to the language resource. Then, for the various UI elements that extension may want to use, it can reference those language resources.