search

zachowj / hass-node-red

Companion Component for node-red-contrib-home-assistant-websocket to help integrate Node-RED with Home Assistant Core
MIT License
465 stars 182 forks source link

HA version 0.109 log error #22

Closed vMeph closed 4 years ago

vMeph commented 4 years ago

on HA version 0.109 getting the flowing error nodered: the '.translations' directory has been moved, the new name is 'translations', starting with Home Assistant 0.111 your translations will no longer load if you do not move/rename this

McGiverGim commented 4 years ago

Maybe is a good moment to ask about translating this. It is only two phrases, but what is the correct way to do it? Make a PR with the translations? I see it difficult to maintain. It will be a great idea to upload it to some free web for translations, I think getlocalization closed, but maybe there are others. I use Crowdin (free for open source) but I don't know if such small project will be accepted.

robinsmidsrod commented 4 years ago

What about the translation web frontend that HA has for their components? Frenck mentioned in the 0.109 release notes that you don't even need to know any coding/git to use it. Can it be utilized for custom compontents, or do custom components have to setup their own service?

McGiverGim commented 4 years ago

Yes, I translate Home Assistant to Spanish in lokalise. I don't know if it is free but only official addons are there.

zachowj commented 4 years ago

Yes, there are only two strings that would need to be translated for this integration and I don't really see it increasing as almost everything UI based is handled by the NR nodes package. Something like lokalise.co, that HA uses, might be overkill but I could see about getting it set up for the NR package and then might as well run it for both of the projects.