Subclassing LocalizeStringEvent

Unity Engine
,
1

Hi,

as the recommended way of localizing UI texts in the scene is using the “Localize” button on TextMeshPro, which creates a LocalizeStringEvent, I was thinking of creating several subclasses of LocalizeStringEvent for my needs.

However, when using a subclass of LocalizeStringEvent, it seems that the editor no longer picks up on changes to the language (i.e. I can’t preview languages with the Localization Scene Controls).

Is this supposed to work? If not, could it be made to work? I think subclassing LocalizeStringEvent would be a great way to deal with added string resolution logic.

Philip

2

Can you give me an example of how you are subclassing the LocalizeStringEvent?

3

I did the following:

  • Use Localize in the dropdown of a TextMeshPro Text, a LocalizeStringEvent was added. I add a new table entry, add a translation, and voila, I can switch the Active Locale to see the different localization values in the scene view.

  • I then remove the LocalizeStringEvent, and add a new script which is a subclass of LocalizeStringEvent, set the table entry again, and — nope, when I switch the Active Locale, the text in the editor does not reflect that.

The subclass is currently just this (planning to add methods and fields of course):

public class TestLocal : LocalizeStringEvent {}
4

Did you hook up the UpdateString events when you added the new subclass?
7483268--920491--Untitled.jpg

If you are doing something complex then you may want to consider just using LocalizedString in your own component. Inherit from LocalizedMonoBehaviour to get access to some additional editor features to mark properties driven https://docs.unity3d.com/Packages/com.unity.localization@1.0/manual/EditModeSupport.html?q=Driven#driven-properties

5

I did not. :frowning:

Thanks. In addition to your screenshot, to get it working in the editor, instead of “Runtime Only”, the value “Editor and Runtime” needs to be selected.

Thanks again, as always, for your detailed answer and fast reaction. It’s really great to see this level of support for the l10n framework.

I’ll take a look at LocalizedMonoBehaviour next and the driven properties, thanks for the heads up!

Philip

1 Like