ecodina commented on code in PR #62557: URL: https://github.com/apache/airflow/pull/62557#discussion_r2891505318
########## .github/skills/airflow-translations/locales/ca.md: ########## @@ -0,0 +1,38 @@ +<!-- SPDX-License-Identifier: Apache-2.0 +https://www.apache.org/licenses/LICENSE-2.0 --> + +# Catalan (ca) Translation Guidelines +# Catalan (ca) Translation Guidelines + +This document provides basic guidelines for translating Apache Airflow UI content into Catalan (ca). +The goal is to maintain clarity, consistency, and alignment with existing Airflow terminology. + +## General Principles + +- Core technical terms such as **DAG**, **XCom**, **TaskInstance**, and **Operator** should remain in English. Review Comment: I'd say: Some core technical terms such as **Dag** or **Xcom** should remain in English unless otherwise noted in this skill. ########## .github/skills/airflow-translations/locales/ca.md: ########## @@ -0,0 +1,38 @@ +<!-- SPDX-License-Identifier: Apache-2.0 +https://www.apache.org/licenses/LICENSE-2.0 --> + +# Catalan (ca) Translation Guidelines +# Catalan (ca) Translation Guidelines + +This document provides basic guidelines for translating Apache Airflow UI content into Catalan (ca). +The goal is to maintain clarity, consistency, and alignment with existing Airflow terminology. + +## General Principles + +- Core technical terms such as **DAG**, **XCom**, **TaskInstance**, and **Operator** should remain in English. +- Avoid translating class names, identifiers, or code-related terminology. +- Keep translations clear and easy to understand for end users. + +## Consistency + +- Follow the same terminology across the entire UI. +- If a term is already translated elsewhere in the project, reuse that translation. +- When unsure, prioritize consistency over literal translation. + +## Style + +- Use natural, user-friendly phrasing. +- Prefer clarity over word-by-word translation. +- Avoid overly complex sentence structures. + +## Notes + +If there is ambiguity in translation, check existing locale files for reference +or align with the terminology used in official Airflow documentation. + +## Airflow-Specific Notes + +- Keep terminology consistent with existing Airflow documentation. +- Do not translate DAG-related identifiers such as `dag_id`, `task_id`, or parameter names. +- When referring to Airflow components (Scheduler, Webserver, Executor), ensure naming matches official documentation. +- UI labels should remain concise and consistent with other locale files. Review Comment: I'd add, based on what I remember the AI had more difficulty on generating consistent translations (not a complete list, I'll update the doc in a future PR if I see other terms): - Ensure the translation aligns with the following terms: 1. Backfill: reompliment 2. Task Instance: instància de tasca 3. Dag bundle: col·lecció de Dags 4. Parse Dag: analitzar Dag 5. Dag Processor: Processador de Dags 6. Scheduler: Planificador 7. Triggerer: Triggerer 8. Asset: asset 9. Asset event: esdeveniment d'asset 10. Pool: pool 11. Audit log: registre d'auditoria 12. Provider: proveïdor 13. Plugin: extensió 14. Schedule: programació 15. Trigger (a task or a dag run): executar -- 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]
