From d8623da199c0a997438a9c4b1b3dbec9821ffa46 Mon Sep 17 00:00:00 2001 From: dougiteixeira <31328123+dougiteixeira@users.noreply.github.com> Date: Tue, 9 May 2023 08:06:22 -0300 Subject: [PATCH] Changes the terms Custom Component to Custom Integration in the translation documents (#1755) --- docs/internationalization/custom_integration.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/internationalization/custom_integration.md b/docs/internationalization/custom_integration.md index 8308e50a..5cbdd578 100644 --- a/docs/internationalization/custom_integration.md +++ b/docs/internationalization/custom_integration.md @@ -1,12 +1,12 @@ --- -title: "Custom Component Localization" +title: "Custom Integration 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 `.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 `.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.