Translation to all supported language

[Baldhor]

I think the app is almost ready to ask for a wide translation.

1. Need clean up en.json

2. Publish a translation request for each language

   Excluding legacy driver which is not anymore supported anyway

[Baldhor]

Step 1 done.

I'm adding more steps to process first:

• [x] Avoid requirement of a translation for every specific esphomeenum capability
• [x] Setup a description for all capabilities, currently it's just a copy of the label ...
• [x] Add all languages files
• [ ] deviceClass translate should be available from Homey itself, at least copy it from the SDK
• [ ] wizard2 translation is not bad, but is it clear enough for peoples not using the app?
  • [ ] dialog message should be marked as "dialog-error", "dialog-warning" or "dialog-confirm", ...
  • [ ] help, warning and error message should be reviewed to ensure consistancy
  • [ ] sometimes "done", sometimes "apply", why?
  • [ ] (low priority) some pages have translation organized in sections, but other not, it should reflect the page view to make support easier

Remark: Translators will have access to a fully detailed wiki ... which seems to be rare ...

[RoadXY]

Maybe it is an idea to integrate with something like Crowdin? https://store.crowdin.com/github

Or POeditor? https://poeditor.com/

I've used these in the past (with Android app project, though) and this way it isn't necessary for translators to know how Git and Github an PR's work which might lead to more translations.

I'm willing to dive into this and led you know?

[Baldhor]

I'm willing to dive into this and led you know?

Sure please Seems going through Homey community is outdated