For elements defined in main/resources/OH-INF/thing/thing-types.xml openHAB does automatic translation, when a file src/main/resources/OH-INF/i18n/SOMETHING_LANGUAGE.properties is present. There is no need for the binding/thing to instantiate TranslationProvider; channel names, values of a set (selection) appear translated in the UI. However properties are not translated, leading to sub-optimal user experience.
- It would be good if property names of a thing are implicitly translated, using the src/main/resources/OH-INF/i18n/SOMETHING_LANGUAGE.properties file.
My proposal at https://community.openhab.org/t/translating-thing-s-property-names/ is that if a property with name aBc is added to a thing, and in a _LANGUAGE.property file a key preperties.aBc = exists, then the value of that key (the translation) is shown in MainUI as the name of the property.
The translation of properties can be achieved also by other means. openhab/openhab-docs#2605 (comment) states that property names are not supposed to be translated. From users’ perspective the more things are translated, the better.
For elements defined in main/resources/OH-INF/thing/thing-types.xml openHAB does automatic translation, when a file src/main/resources/OH-INF/i18n/SOMETHING_LANGUAGE.properties is present. There is no need for the binding/thing to instantiate
TranslationProvider; channel names, values of a set (selection) appear translated in the UI. However properties are not translated, leading to sub-optimal user experience.My proposal at https://community.openhab.org/t/translating-thing-s-property-names/ is that if a property with name
aBcis added to a thing, and in a_LANGUAGE.propertyfile a keypreperties.aBc =exists, then the value of that key (the translation) is shown in MainUI as the name of the property.The translation of properties can be achieved also by other means. openhab/openhab-docs#2605 (comment) states that property names are not supposed to be translated. From users’ perspective the more things are translated, the better.