Add blogpost about changing translation downloads #2136
Conversation
| With this change, we only download the strings that are verified. | ||
|
|
||
| A verified string is a translated string, and it becomes unverified when the original string changes. | ||
| So whenever someone changes something in the original string, the translated string becomes unverified and needs to be reviewed again. |
There was a problem hiding this comment.
"something" is a pleonasm. "reviewed" is another Lokalize concept. Suggestions:
| So whenever someone changes something in the original string, the translated string becomes unverified and needs to be reviewed again. | |
| So whenever someone changes the default value of a string (i.e. changes a `strings.json` file), all translations of that key becomes unverified and must be edited or marked as verified in Lokalise. |
There was a problem hiding this comment.
So whenever the English string is modified (i.e. changes a strings.json file), all translations which refers to the same translation key becomes unverified and must be edited or marked as verified in Lokalise.
|
|
||
| A verified string is a translated string, and it becomes unverified when the original string changes. | ||
| So whenever someone changes something in the original string, the translated string becomes unverified and needs to be reviewed again. | ||
| This is very beneficial for the translation keys that make use of translation key placeholders, since they can now never have a mismatch between the original and translated string. |
There was a problem hiding this comment.
I think this is better:
| This is very beneficial for the translation keys that make use of translation key placeholders, since they can now never have a mismatch between the original and translated string. | |
| This catches both significant changes to strings that may be hidden if the translation is not updated, and also avoids placeholder mismatches. Note that correcting typos in the default strings also will make translations "unverified". |
There was a problem hiding this comment.
This catches changes to English strings that may be hidden if the translation is not updated, and also avoids placeholder mismatches. Note that correcting typos in the English strings also will make translations "unverified".
| @@ -10,7 +10,7 @@ In Home Assistant Core 2024.4.2, we are changing the way translation keys are do | |||
| Previously the script would download every translated string. | |||
| With this change, we only download the strings that are verified. | |||
|
|
|||
| A verified string is a translated string, and it becomes unverified when the original string changes. | |||
| All translations are verified when saved, but a translation becomes unverified if the source string is changed | |||
There was a problem hiding this comment.
Nit: missing punctuation at end of sentence.
| title: "Changing the way translation keys are handled" | ||
| --- | ||
|
|
||
| In Home Assistant Core 2024.4.2, we are changing the way translation keys are downloaded. |
There was a problem hiding this comment.
I found "downloaded" in this context is confusing. From where to where?
In Home Assistant Core 2024.4.2, we are changing the way translation are included into builds from Lokalise.
|
|
||
| In Home Assistant Core 2024.4.2, we are changing the way translation keys are downloaded. | ||
|
|
||
| Previously the script would download every translated string. |
There was a problem hiding this comment.
Previously the build translation script would download every translated string.
| In Home Assistant Core 2024.4.2, we are changing the way translation keys are downloaded. | ||
|
|
||
| Previously the script would download every translated string. | ||
| With this change, we only download the strings that are verified. |
There was a problem hiding this comment.
With this change, we only download the translations that are verified in Lokalise.
Proposed change
Add blogpost about changing translation downloads
Type of change
Additional information