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-20 15:56:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

Changes the terms Custom Component to Custom Integration in the translation documents (#1755)

Browse Source
This commit is contained in:
dougiteixeira 2023-05-09 08:06:22 -03:00 committed by GitHub
parent 1b5a7916b5
commit d8623da199
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/internationalization/custom_integration.md
View File

@ -1,12 +1,12 @@
--- ---
title: "Custom Component Localization" title: "Custom Integration Localization"
--- ---
## Translation Strings ## 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 `<language_code>.json` in the `translations` directory, e.g., for the German translation `de.json`. Unlike localized strings merged in the `home-assistant` repository, custom integrations cannot take advantage of Lokalise for user-submitted translations. However, custom integration authors can still include translations with their integrations. These will be read from the `translations` directory, adjacent to the integration source. They are named `<language_code>.json` in the `translations` directory, e.g., for the German translation `de.json`.
This file will contain the different strings that will be translatable for different things that the custom components offers that need to be translated. These files follow the same formatting as [backend translation string files](internationalization/core.md), but a copy will exist for each translated language. This file will contain the different strings that will be translatable for different things that the custom integration offers that need to be translated. These files follow the same formatting as [backend translation string files](internationalization/core.md), but a copy will exist for each translated language.
The language codes follow the [BCP47](https://tools.ietf.org/html/bcp47) format. The language codes follow the [BCP47](https://tools.ietf.org/html/bcp47) format.