Localization of WDX

[AkulaBig]

It is clear that the names of the columns in the settings file are all different. The logic itself makes us do so. But in the TCMediaimage Language Fields with the same names there is a lot. In the Mediainfo language file, the names are the same and only grouped into sections. Create user speakers with the same translation.
For example: g_codecid = Codeca identifier v_codecid = Codec identifier, add any field from any plugin to this set. Or just remove the line. The main thing is to perform some action. Now comment on the translation in the language file. And what do we see? Instead of v_codecid, it is written g_codecid. That is the first one in order. The same translation.
If you configure the speakers without translation, and then condemn the translation, everything works fine.

[AkulaBig]

2ghisler(Author)
I clearly described the problem? I think this is a mistake.

[ghisler(Author)]

Sorry, I do not understand what you are trying to achieve. Translations for plugins are generally handled like this:
[language identifier]
English phrase=Translated phrase

g_codecid is not an English phrase.

[AkulaBig]

Sorry, I do not understand what you are trying to achieve. Translations for plugins are generally handled like this:

Yes. I realized that I explained it is not clear. I give step -by -step instructions.
1. I created a set of user columns for the test:
[img]https://i.ibb.co/ksqkkP0w/2025-06-09-125550.png[/img]
2. I created a localization file for it:
[img]https://i.ibb.co/wZY9Ssst/2025-06-09-125839.png[/img]
3. The names of the columns are displayed from the localization file:
[img]https://i.ibb.co/hFCvmWzW/2025-06-09-125928.png[/img]
4. Be sure to produce any action. In this case, I added another column. But you can delete, etc.
[img]https://i.ibb.co/XZdfnFLt/2025-06-09-130113.png[/img]
After this action, the columns stop showing the correct data. For a long time I could not understand the reason. Then I figured it out.
We comment on the translation:
[img]https://i.ibb.co/0jGZSv08/2025-06-09-130355.png[/img]
We see that the columns have changed the names without our participation, automatically:
[img]https://i.ibb.co/xtKkK2Fz/2025-06-09-130421.png[/img]
Now everything is clear?

[ghisler(Author)]

The reason is that the translation needs to work both ways. Otherwise the plugin cannot know which of the two fields is meant when the user writes or chooses the translated name, and there are two fields with the same name.

[AkulaBig]

The reason is that the translation needs to work both ways. Otherwise the plugin cannot know which of the two fields is meant when the user writes or chooses the translated name, and there are two fields with the same name.

Then, to identify the field, use its name in English. What is the need to use a translation that may be, or maybe not? And if it is impossible to use the same translation, why is the error not issued? We must do something about it. Now it looks like a mistake.

[AkulaBig]

The reason is that the translation needs to work both ways

Is there any hope that this algorithm will be changed for use as an identifier only the name of the left field in the Latin? Or maybe tell me some kind of life, how to make a translation without using additional words?

[ghisler(Author)]

No, there are situations where this cannot be fixed, for example when using a field in the multi-rename tool. Therefore please make the two translations slightly different.