This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 13be653089b Clarify translation key change when test is re-phrased
(#54847)
13be653089b is described below
commit 13be653089b64ba553032241fb82408ced27e5c6
Author: Jens Scheffler <[email protected]>
AuthorDate: Fri Aug 22 22:59:16 2025 +0200
Clarify translation key change when test is re-phrased (#54847)
---
airflow-core/src/airflow/ui/public/i18n/README.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/airflow-core/src/airflow/ui/public/i18n/README.md
b/airflow-core/src/airflow/ui/public/i18n/README.md
index 536eb3013d0..e667ceb6023 100644
--- a/airflow-core/src/airflow/ui/public/i18n/README.md
+++ b/airflow-core/src/airflow/ui/public/i18n/README.md
@@ -133,7 +133,8 @@ Translation conflicts MUST be resolved according to the
procedures outlined in s
### 5.5. Adding or rephrasing terms
- When new terms are added to the default locale, all translation owners
SHOULD create a follow-up PR to comply with the changes in their assigned
locale.
-- When existing terms are rephrased in the default language (key is the same
but value changed), all translation owners SHOULD do the same as above, if the
change in the intent or meaning affects the translation.
+- When existing terms are rephrased in the default language (key is the same
but value changed), all translation owners SHOULD do the same as above.
+- As the change of the default language might be un-noticed by translators
(translation keys would stay valid) it is recommended to rename the translation
key to force a detection of language gaps (translations would have 1 orphan
(old) key and a missing (new) key).
- In busy times with many parallel UI changes it is acceptable to batch
changes together. Differences SHOULD be cleared prior to a release at the
latest.
> [!NOTE]
