Localization not affecting all string elements on enable

[jbotha404]

This being my first post on the forum…Hi.
If I missed any posting rules and such, apologies (Promise to be better next time)

I have been bestowed the privilege of being in charge of localizing an app a touch input (ie Keyboard), thus far, the preview version of the Localization has been working swimmingly…except for one problem child that I seem to fail being able to handle(see below)

Some background:

• This seems to only be affecting the one scene
• In this scenario its a keyboard (with TextMeshPro elements) that is hidden (disabled), and when brought into view (enabled) only some elements are localized correctly
  
  
  
  These are the Inspector values for the text that have been successfully localized
  
  
  
  Inspector value of one of the elements that hasn’t localized successfully
  
  

Now, if I were to disable, the n re-enable the keyboard object, everything is localized properly (see below)

Now, of the 362 (ish) translated element, this is the only one screen that has been giving this kind of issues
Any ideas/thoughts/suggestions/etc that I can try to solve this particular conundrum would be greatly appreciated.

[karl_jones]

Hi,
Thats strange. Are you able to share the project so I can take a look and see whats going wrong?

[jbotha404]

So, we solved the issue (Thanks karl_jones for your assistance)

For anyone in the future with a similar issue…answer is probably something silly like ours:
This is a shared Keyboard across our system.
In one of the game modes, we had a script manually set the key values (instead of using the keyboards own script) via the inspector.

This was a silly and basic mistake.