jeans/developers.home-assistant
jeans/developers.home-assistant
1
0
Fork 0
mirror of https://github.com/home-assistant/developers.home-assistant.git synced 2025-07-28 11:46:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update internationalization_custom_component_localization.md (#202)

Browse Source 
* Update internationalization_custom_component_localization.md

After creating a custom sensor implementation and trying to translate the returned states to Dutch, I noticed that Hass is looking for a file called sensor.nl.json instead of platformname.nl.json in the .translations folder.

* Minor changes
This commit is contained in:
galsom 2019-04-29 10:00:57 +02:00 committed by Fabian Affolter
parent 0f59916a5b
commit bf33376221
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/internationalization_custom_component_localization.md
View File

@ -3,7 +3,7 @@ title: "Custom Component Localization"
---
## Translation Strings
Unlike localized strings merged in the home-assistant repository, custom components cannot take advantage of Lokalise for user submitted translations. However, custom component authors can still include translation with their components. These will be read from the `.translations` directory, adjacent to the component source file. They are named `<component/platform name>.<language_code>.json`, unless the custom component exists in its own directory, in which case the file is simply named `<language_code>.json` in the `.translations` directory.
Unlike localized strings merged in the `home-assistant` repository, custom components cannot take advantage of Lokalise for user submitted translations. However, custom component authors can still include translations with their components. These will be read from the `.translations` directory, adjacent to the component source. They are named `<platform name>.<language_code>.json`, e.g., for the German translation of a sensor `sensor.de.json`, unless the translation is for the custom component only, in which case the file is simply named `<language_code>.json` in the `.translations` directory.
These files follow the same formatting as [backend translation string files](internationalization_backend_localization.md), but a copy will exist for each translated language.