You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 7, 2020. It is now read-only.
binding.pushbullet.author = Hakan Tandogan
binding.pushbullet.name = Pushbullet Binding
binding.pushbullet.description = This is the binding for Pushbullet.
after compiling the bindig and loading it into a fresh openHAB2 instance, when I look at Configuration -> Bindings -> my-new-binding, I see that the binding.name and binding.description are resolved from the property name, but not the author, even though it follows the same naming convention.
Having a "translated" author name would be useful if the author wants his/her name differently written in, say, english and arabic, or english and chinese.
The text was updated successfully, but these errors were encountered:
If the author tag, from which data source it might come, will still be displayed in the Paper UI, I would love it to be translateable. As a reason, please see my example with arabic and chinese versus the englishified transliterations.
I still assume the author information can be moved to a technical meta-information and removed from the binding XML (and so from the Paper UI).
I assume we just need someone that comes with a PR.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
in my binding, I have the following
and in the pushbullet_en.properties:
after compiling the bindig and loading it into a fresh openHAB2 instance, when I look at Configuration -> Bindings -> my-new-binding, I see that the binding.name and binding.description are resolved from the property name, but not the author, even though it follows the same naming convention.
Having a "translated" author name would be useful if the author wants his/her name differently written in, say, english and arabic, or english and chinese.
The text was updated successfully, but these errors were encountered: