Skip to content
This repository has been archived by the owner on May 7, 2020. It is now read-only.

[i18n] binding author is not resolved #6741

Open
hakan42 opened this issue Dec 27, 2018 · 3 comments
Open

[i18n] binding author is not resolved #6741

hakan42 opened this issue Dec 27, 2018 · 3 comments

Comments

@hakan42
Copy link
Contributor

hakan42 commented Dec 27, 2018

in my binding, I have the following

	<name>@text/binding.pushbullet.name</name>
	<description>@text/binding.pushbullet.description</description>
	<author>@text/binding.pushbullet.author</author>

and in the pushbullet_en.properties:

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.

@cweitkamp
Copy link
Contributor

cweitkamp commented Dec 28, 2018

If we need it I can reopen #5176. But I think the author-tag is kind of deprecated.

@hakan42
Copy link
Contributor Author

hakan42 commented Dec 29, 2018

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.

@maggu2810
Copy link
Contributor

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants