jscheffl commented on code in PR #62363:
URL: https://github.com/apache/airflow/pull/62363#discussion_r2849789221


##########
.github/translations/airflow-translations/locales/de.md:
##########
@@ -0,0 +1,190 @@
+<!-- SPDX-License-Identifier: Apache-2.0
+     https://www.apache.org/licenses/LICENSE-2.0 -->
+
+# German (de) Translation Agent Skill
+
+This file contains German language specific guidelines for German translations 
in the Airflow UI.
+
+---
+
+## 1. Core Airflow Terminology
+
+The following terms **must remain in English unchanged** (case-sensitive):
+
+- `Dag` / `Dags` — Airflow concept; never write "DAG". The term is treated as 
neutral in German ("das Dag").
+- `Pool` / `Pools` — Untranslated.
+- `Provider` / `Providers` — Untranslated.
+- `Operator` / `Operatoren` — Technical implementation term; remains 
"Operator" in singular and "Operatoren" in plural.
+- `ID` — Universal abbreviation (capitalized).
+- Log levels: `CRITICAL`, `ERROR`, `WARNING`, `INFO`, `DEBUG` — **must remain 
unchanged**.
+
+### Code & Technical Identifiers (Never Translate)
+
+- Python class names
+- Function names
+- Variable names
+- Configuration keys (e.g., `dag_id`, `task_id`)
+- CLI flags
+- File paths
+- URLs
+- Environment variable names
+
+---
+
+## 2. Standard Translations
+
+The following translations **must be used consistently**.
+
+### Core Concepts

Review Comment:
   I think it would be beneficial for the future to add a column to the table 
with the German rationale why a term has been translated like with - including 
a discussion why alternatives close by have not been selected. As in README.md.
   
   This document now is 90% redundant and rather than keeping both README and 
this I think it might be better to transfer missing content into this structure 
here if normalized.
   
   In case of core concepts I'd recommend to take the description from the 
translated terms into a third column in this table... and then the REAMDE can 
be removed/replaced by this document.



-- 
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