alliasgher commented on code in PR #65115:
URL: https://github.com/apache/airflow/pull/65115#discussion_r3089087278


##########
.github/skills/airflow-translations/locales/de.md:
##########
@@ -0,0 +1,240 @@
+<!-- SPDX-License-Identifier: Apache-2.0
+     https://www.apache.org/licenses/LICENSE-2.0 -->
+
+# German (de) Translation Agent Skill
+
+**Locale code:** `de`
+**Preferred variant:** Standard German (de), using formal "Sie" register, 
consistent with existing translations in 
`airflow-core/src/airflow/ui/public/i18n/locales/de/`
+
+This file contains locale-specific guidelines so AI translation agents produce
+new German strings that stay 100% consistent with the existing translations.
+
+## 1. Core Airflow Terminology
+
+### Global Airflow terms (never translate)
+
+These terms are defined as untranslatable across **all** Airflow locales.
+Do not translate them regardless of language:
+
+- `Airflow` — Product name
+- `Dag` / `Dags` — Airflow concept; never write "DAG"
+- `PID` — Unix process identifier
+- `ID` — Universal abbreviation
+- `UTC` — Time standard
+- `JSON` — Standard technical format name
+- `REST API` — Standard technical term
+- Log levels: `CRITICAL`, `ERROR`, `WARNING`, `INFO`, `DEBUG`
+
+### Translated by convention (German-specific)
+
+The existing German translations translate many Airflow terms into native 
German.
+These established translations **must be used consistently**:
+
+- `Asset` / `Assets` → `Datenset (Asset)` / `Datensets (Assets)` — includes 
English term in parentheses

Review Comment:
   Done — added §7 "Rationale for Translation Choices" to the skill file with 
all the reasons from the README. The README itself is now replaced with a short 
German-language pointer to the skill file so there is a single source of truth.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to