-
-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Binding settings not translated in Main UI #2641
Comments
I can see that Main UI is requesting /rest/config-descriptions/binding:netatmo to retrieve the binding parameters and the response is not localized. So the problem is in core framework. @wborn @jlaur : maybe there is a mismatch between "binding" and "addon" ? In our properties files, the entries are:
|
Exactly - Main UI only displays what it gets from the REST API. |
As I suspected, the core framework is inferring a key starting by "binding" and not "addon". I really do not know why we used "addon" in all bindings properties. To avoid changing all bindings, I will propose a fix in the |
Fix openhab/openhab-webui#2641 Signed-off-by: Laurent Garnier <lg.hc@free.fr>
…eters Fix openhab/openhab-webui#2641 Signed-off-by: Laurent Garnier <lg.hc@free.fr>
…eters Fix openhab/openhab-webui#2641 Signed-off-by: Laurent Garnier <lg.hc@free.fr>
…parameters Fix openhab/openhab-webui#2641 Signed-off-by: Laurent Garnier <lg.hc@free.fr>
Fix openhab/openhab-webui#2641 The i18n key for add-on configuration parameter should now start with "addon.config.". To maintain compatibility with thousands of existing translations, an alternative i18n key starting with "<type>.config" is accepted when the add-on type is either io, persistence, voice or ui. Signed-off-by: Laurent Garnier <lg.hc@free.fr> u#
Fix openhab/openhab-webui#2641 The i18n key for add-on configuration parameter should now start with "addon.config.". To maintain compatibility with thousands of existing translations, an alternative i18n key starting with "<type>.config" is accepted when the add-on type is either io, persistence, voice or ui. Signed-off-by: Laurent Garnier <lg.hc@free.fr>
Fix openhab/openhab-webui#2641 The i18n key for add-on configuration parameter should now start with addon.config.<param>. To maintain compatibility with hundreds of existing translations, an alternative key starting with <type>.config.<param> is also accepted when the add-on type is either io, persistence, voice or ui. Signed-off-by: Laurent Garnier <lg.hc@free.fr>
Fix openhab/openhab-webui#2641 The i18n key for add-on configuration parameter should now start with addon.config.<param>. To maintain compatibility with hundreds of existing translations, an alternative key starting with <type>.config.<param> is still accepted when the add-on type is either io, persistence, voice or ui. Signed-off-by: Laurent Garnier <lg.hc@free.fr>
Fix openhab/openhab-webui#2641 The i18n key for add-on configuration parameter should now start with addon.config.<param>. To maintain compatibility with hundreds of existing translations, an alternative key starting with <type>.config.<param> is still accepted for an add-on parameter Signed-off-by: Laurent Garnier <lg.hc@free.fr>
…key (#4305) Fix openhab/openhab-webui#2641 The i18n key for add-on configuration parameter should now start with addon.config.<param>. To maintain compatibility with hundreds of existing translations, an alternative key starting with <type>.config.<param> is still accepted for an add-on parameter Signed-off-by: Laurent Garnier <lg.hc@free.fr>
Closed by openhab/openhab-core#4305 |
…key (openhab#4305) Fix openhab/openhab-webui#2641 The i18n key for add-on configuration parameter should now start with addon.config.<param>. To maintain compatibility with hundreds of existing translations, an alternative key starting with <type>.config.<param> is still accepted for an add-on parameter Signed-off-by: Laurent Garnier <lg.hc@free.fr>
…key (#4305) Fix openhab/openhab-webui#2641 The i18n key for add-on configuration parameter should now start with addon.config.<param>. To maintain compatibility with hundreds of existing translations, an alternative key starting with <type>.config.<param> is still accepted for an add-on parameter Signed-off-by: Laurent Garnier <lg.hc@free.fr>
The problem
Main UI presents untranslated label and description for binding settings while the translation is present in the properties file.
It concerns certain bindings like netatmo or sonos for example.
It is ok for addons like openhabcloud or voiceRSS.
Expected behavior
Main UI should consider existing translations for binding settings.
Additional information
I am asking myself if the problem would be when the addon.xml file contains config-description tag (and so all config settings declared in the addon.xml file) instead of a config-description-ref tag (config settings declared in a separate config.xml file) ?
Or maybe the translations are considered for voice and io addons but not binding addons ?
The text was updated successfully, but these errors were encountered: