Button Mapping - I2 Local. with ''2'' languages

Hi,
Sorry I haven't answered this yet. I read it a while ago in the phone, and I thought I already answered this, but I didn't, sorry about that!

1. Use it to localize our project. Which is pretty straightforward.

As you said, that's the default, and will work out-of-the-box.

2. Use it to ''localize'' the images of the button in the game depending on which kind of controller is plugged in.

If I understood you correctly, you want to have 2 language Sources:
I2Languages.prefab with English, Spanish, etc (holding all the translations for your (1.)
and
ControllersSource.prefab with Xbox, PS4, Touch, Oculus, Vive, etc (holding terms like "Action"="A", "A"(PS4-style), "Swipe-up", etc, so, the action with the image that correspond to each controller.

In general that its not easily supported. You could do set something like that, by placing both prefabs, and adding the second one to the GlobalSources array so that it gets loaded. And then, have call GetTermData to get your the structure with all the languages so you could manually get the one you need.

But that seems like a bit over-doing to me.

My advise would be a far simpler solution:

Make each of your images to have the controller as a prefix:
instead of "A.png",
make them: "Xbox_A.png", "PS4_A.png", "Oculus_A.png", "Touch_A.png" (<- this last one can have a swipe-up image)

Then, in the Language source, just place the term translated to "{[A]}".
And add a callback to the Localize component that replaces {[A}] with the name of the image for the current controller.
e.g. {[A]} -> PS4_A

What will happen is that the localize component will get the translation "{[A]}" do the callback, and replace the translation with "PS4_A", and then automatically load that image and assign it to the Image or RawImage component.

Furthermore, you could even use Global or Local parameters to do that automatically and avoid having to add a callback to each of those Localize components.

This approach works great even when using TextMeshPro and having the image inside the text:
"Press {[A]} to jump"

Here is some information about Callbacks and Parameters:
inter-illusion.com/assets/I2LocalizationManual/Callbacks.html
inter-illusion.com/assets/I2LocalizationManual/Parameters.html

Said that, the plugin will be supporting more general Input Specialization in one the upcoming versions:

It currently only has Touch/Normal, but will extend to any one (even custom)
inter-illusion.com/assets/I2Localization...tSpecialization.html

Please, vote for that feature in the roadmap!
trello.com/c/slJ2P9aM/3-extend-input-specialization

Hope that helps,
Frank

Hi,
Parameters and Callbacks can't change the translation into a Term. Instead, the modified translation is the one set into the targets.

In your case, you setup correctly the LocalParameter and its returning the corresponding string.
However, that string should be the name of the Sprite/Image and not the name of the Term holding the image.

For instance, your localParameters class when asked for "A" should return "PS4_A".
Then, the Localize component, takes that string ("PS4_A") and calls the DoLocalize_uGUI_Image function which tries first to convert that text into an image by:
- looking in the Referenced assets of the Localize component
- if not found, it looks in the Assets section of the I2Languages.prefab
- if not found then it looks in the Resources folder.

So, if you have a Sprite named "PS4_A" in your Resources folder, then the UI.Image component will load it and use it.
If you don't want to add those sprites to the Resources folder, you should add them to the Assets section of the I2Languages.prefab or Localize component. That way they will be referenced and found correctly.

Hope that helps,
Frank