aoelvp94 commented on code in PR #63405: URL: https://github.com/apache/airflow/pull/63405#discussion_r2925939691
########## .github/skills/airflow-translations/locales/es.md: ########## @@ -0,0 +1,239 @@ +<!-- SPDX-License-Identifier: Apache-2.0 + https://www.apache.org/licenses/LICENSE-2.0 --> + +# Spanish (es) Translation Agent Skill + +**Locale code:** `es` +**Preferred variant:** Neutral international Spanish (es) — inclusive across Latin America, Spain and Equatorial Guinea, consistent with existing translations in `airflow-core/src/airflow/ui/public/i18n/locales/es/` + +This file contains locale-specific guidelines so AI translation agents produce new Spanish 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" +- `XCom` / `XComs` — Airflow cross-communication mechanism +- `Asset` / `Assets` — Data dependency tracked by Airflow +- `Provider` / `Providers` — Airflow extension package name +- `Map Index` — Task mapping index +- `PID` — Unix process identifier +- `ID` — Universal abbreviation +- `UTC` — Time standard +- `JSON` — Standard technical format name +- `REST API` — Standard technical term +- `Schema` — Database term +- Log levels: `CRITICAL`, `ERROR`, `WARNING`, `INFO`, `DEBUG` + +### Kept in English by convention (Spanish-specific) + +The existing Spanish locale files leave these terms untranslated. +Keep them in English to stay consistent with established translations: + +- `Backfill` / `Backfills` — Airflow-specific retroactive execution concept +- `Catchup` — Airflow scheduling concept +- `Bundle` — Airflow bundle concept +- `Executor` — Airflow component name +- `Plugin` / `Plugins` — Airflow extensibility mechanism +- `Pool` / `Pools` — Resource constraint mechanism +- `Trigger` / `Triggerer` — As **component names and nouns** keep in English (e.g., "Clase del Trigger", "Triggerer Asignado"); as a **verb** translate as "Activar" (see section 2) +- `Upstream` / `Downstream` — Used as-is even within Spanish sentences (e.g., "Fallido en Upstream") +- `Heartbeat` — Used as-is in component health labels (e.g., "Último Heartbeat") + +## 2. Standard Translations + +The following Airflow-specific terms have established Spanish translations +that **must be used consistently**: + +| English Term | Spanish Translation | Notes | +| --------------------- | ----------------------------- | --------------------------------------------- | +| Task | Tarea | Plural: "Tareas" | +| Task Instance | Instancia de Tarea | Plural: "Instancias de Tarea" | +| Task Group | Grupo de Tareas | | +| Dag Run | Ejecución del Dag | Plural: "Ejecuciones del Dag" | +| Trigger (verb) | Activar | "Activado por" for "Triggered by"; as noun/component keep in English (see section 1) | +| Trigger Rule | Regla de Activación | | +| Schedule (noun) | Programación | | +| Scheduler | Programador | | +| Operator | Operador | Plural: "Operadores" | +| Connection | Conexión | Plural: "Conexiones" | +| Variable | Variable | | +| Configuration | Configuración | | +| Audit Log | Auditoría de Log | `dag.json` uses this form; `common.json` has "Auditar Log" — prefer "Auditoría de Log" | Review Comment: Registro might be confusing because it is used for rows in databases too -- 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]
