Translations: A first place to discuss missing translation keys and general translation issues

[mkerstner]

We just added a new way to contribute: translations. The Device Database can now be localized, and we would love your help making it available in more languages. 🌐

If you want to help translate the Device Database into your language - use this sign-up link to join the project as a translator: https://app.lokalise.com/public/743837856a6c57e1405707.10709861/

Once you are in, check whether your language is already available. If it is, you can start translating right away. If it is not listed yet, let us know here and we will get it added.

We'll show a language toggle in one of the upcoming releases based on the translation progress.

This discussion is focused on missing translation keys and general questions and issues regarding translations. It's a first step
to facilitate your contributions.

[breti]

These texts are missing translation keys:

Some of the texts in this screenshot:

The headline only:

At least two of the four, maybe all:

[mkerstner]

CC @stvncode

[breti]

Numbers are sometimes not localized at all, sometimes localized incorrectly, and sometimes localized correctly.

Not localized at all (thousands separator is missing):

Seems to be localized according to browser's language (?):

Seems to be localized into EN:

[breti]

Splitting sentences that contain links into multiple translation keys is very unfortunate. Would it perhaps be possible to put the text - including the <a> HTML markup for the link - back into a single translation key and add the actual https://xxx link using a {variable}?

e.g.

==>

hiw_contribute
For now, the best way to contribute is to <a href="{link}">opt in to Device Analytics in Home Assistant</a>. Every submission helps grow the database and improve the data available to everyone.

Here's another idea: Assign the opening and closing HTML elements of the link to separate variables, e.g.,

hiw_contribute
For now, the best way to contribute is to {startoflink}opt in to Device Analytics in Home Assistant{endoflink}. Every submission helps grow the database and improve the data available to everyone.

[WaterInTheLake]

I agree with this one. Quite a headache to translate.

[breti]

May I suggest using icons instead of the text “is/is not”?

e.g. some of these

I think the German phrases “entspricht / entspricht nicht” are simply too long to fit into the dialogue; other languages will face similar problems.. We could keep them as a tooltip.

That's what it would currently look like in German:

Faked with Unicode characters:

[WaterInTheLake]

I disagree with this one. I think using words makes it more clear and is more user friendly.
I really like the way the is / is not-function is implemented. Good work! 👍

[breti]

Yes, I understand. But then we'll probably need a different layout so that longer words can be displayed.

[mkerstner]

CC @matthiasdebaat

[matthiasdebaat]

Icons have to be learned first, and people usually guess wrong. Only a few icons are universal enough to stand alone. For example, close, search, back/forward, play/pause, settings. Everything else needs a label.

I do see your issue that longer words don't fit. Will try to find a solution for this. Maybe to remove it from the main page and only show it in the dialog.

[mkerstner]

I agree with the current approach to retain words instead of icons. We can revisit at a later point in time as well once more. Also, it probably makes more sense to have that discussion again once work on the visual design (#175) has progressed / been done and the branding also fit it. From a UX perspective, we can park it from now and thus I'll close this discussion. Feel free to re-open at a later point in time again if needed. Thanks everyone!