mirror of
https://github.com/home-assistant/developers.home-assistant.git
synced 2025-05-01 16:57:14 +00:00
bf33376221
* 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
13 lines
1.2 KiB
Markdown
13 lines
1.2 KiB
Markdown
---
|
|
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 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.
|
|
|
|
The language codes follow the [BCP47](https://tools.ietf.org/html/bcp47) format. The [frontend translation files](https://github.com/home-assistant/home-assistant-polymer/tree/master/translations) can also be referred to if you are unsure of the correct language code to use.
|
|
|
|
The frontend will serve these files after Home Assistant is restarted.
|