airflow-translations

Source excerpt starting at line 1.

1<!-- SPDX-License-Identifier: Apache-2.02     https://www.apache.org/licenses/LICENSE-2.0 -->3 4# Dutch (nl) Translation Agent Skill5 6**Locale code:** `nl`7**Preferred variant:** Standard Dutch (Netherlands), consistent with existing translations in `airflow-core/src/airflow/ui/public/i18n/locales/nl/`8 9This file contains locale-specific guidelines so AI translation agents produce10new Dutch strings that stay 100% consistent with the existing translations.11 12## 1. Core Airflow Terminology13 14The following terms **must remain in English unchanged** (case-sensitive):15 16- `Dag` / `Dags` — Airflow concept; never write "DAG"17- `XCom` / `XComs` — Airflow cross-communication mechanism18- `Asset` / `Assets` — Data dependency tracked by Airflow19- `Plugin` / `Plugins` — Airflow extensibility mechanism20- `Pool` / `Pools` — Resource constraint mechanism21- `Provider` / `Providers` — Airflow extension package name22- `Run` / `Runs` — When used standalone (e.g., "Laatste Run")23- `Map Index` — Task mapping index24- `PID` — Unix process identifier25- `ID` — Universal abbreviation26- `UTC` — Time standard27- `JSON` — Standard technical format name28- `REST API` — Standard technical term29- Log levels: `CRITICAL`, `ERROR`, `WARNING`, `INFO`, `DEBUG`30 31## 2. Standard Translations32 33The following Airflow-specific terms have established Dutch translations34that **must be used consistently**:35 36| English Term          | Dutch Translation          | Notes                                      |37| --------------------- | -------------------------- | ------------------------------------------ |38| Task                  | Taak                       | Always translate Task to "taak" / "Taak"   |39| Task Instance         | Taak Instance              | Plural: "Taak Instances"                   |40| Task Group            | Taak Groep                 | Plural: "Taak Groepen"                     |41| Dag Run               | Dag Run                    | Plural: "Dag Runs"                         |42| Backfill              | Backfill                   |                                            |43| Trigger (noun)        | Trigger                    | e.g. "Asset Triggered"                     |44| Trigger Rule          | Trigger regel              |                                            |45| Triggerer             | Triggerer                  | Component name                             |46| Scheduler             | Scheduler                  |                                            |47| Schedule (noun)       | Planning                   |                                            |48| Executor              | Executor                   |                                            |49| Connection            | Connectie                  | Plural: "Connecties"                       |50| Variable              | Variabele                  | Plural: "Variabelen"                       |51| Audit Log             | Audit Log                  |                                            |52| Log                   | Log                        | Plural: "Logs"                             |53| State                 | Status                     | e.g. "Totaal {{state}}" -> "Totaal Status" |54| Queue (noun)          | Wachtrij                   |                                            |55| Config / Configuration| Configuratie               |                                            |56| Operator              | Operator                   | Plural: "Operators"                        |57| Asset Event           | Asset Event                | Keep as in English                         |58| Catchup               | Catchup                    | Keep as in English                         |59 60## 3. Task/Run States61 62| English State       | Dutch Translation     |63| ------------------- | --------------------- |64| running             | Lopend                |65| failed              | Mislukt               |66| success             | Succesvol             |67| queued              | Wachtend              |68| scheduled           | Gepland               |69| skipped             | Overgeslagen          |70| deferred            | Uitgesteld            |71| removed             | Verwijderd            |72| restarting          | Herstartend           |73| up_for_retry        | Wachtend op een nieuwe poging |74| up_for_reschedule   | Wachtend op herplanning |75| upstream_failed     | Upstream mislukt      |76| no_status / none    | Geen status           |77| planned             | Gepland               |78 79## 4. Dutch-Specific Guidelines80 81### Tone and Register82 83- Use **informal Dutch** ("je/jouw" form). Avoid the formal "u" unless specifically requested.84- Use a professional yet accessible tone.85- Keep UI strings concise — they appear in buttons, labels, and tooltips.86 87### Gender and Number88 89- Dutch nouns have grammatical gender, but for technical terms, focus on common usage:90  - "Taak" is generally **de-word**: "de taak"91  - "Run" is **de-word**: "de run"92  - "Process" is **het-word**: "het proces"93 94### Plural Forms95 96- Dutch uses i18next plural suffixes `_one` and `_other`.97  Most technical terms add "s" or "en":98  - "Connectie" -> "Connecties"99  - "Variabele" -> "Variabelen"100  - "Taak" -> "Taken"101 102### Capitalization103 104- Use **Sentence case** (Zinvallende hoofdletters) for descriptions.105- Use **Title Case** or **Initial Capital** for labels and buttons if the English source does so.106- Always capitalize "Dag", "Taak" (when referring to the object), "Asset", "XCom", etc.107 108## 5. Examples from Existing Translations109 110**Common UI Patterns:**111 112```113Add    → "Toevoegen"114Delete → "Verwijderen" (or "Verwijder" on buttons)115Edit   → "Wijzigen" / "Bewerken"116Save   → "Opslaan"117Cancel → "Annuleer"118Search → "Zoeken"119Filter → "Filter"120```121 122**Interpolation:**123 124```json125"delete_confirmation": "Weet je zeker dat je {{resourceName}} wilt verwijderen?"126```127 128## 6. Agent Instructions (DO / DON'T)129 130**DO:**131 132- Maintain the "je" (informal) address style.133- Preserve all i18next placeholders: `{{count}}`, `{{dagId}}`, etc.134- Use "Wachtrij" for technical queues.135- Use "Planning" for schedules.136- Provide both `_one` and `_other` plural forms.137 138**DON'T:**139 140- Use "u" (formal).141- Translate "Dag" as "DAG".142- Translate terms listed in Section 1.143- Use inconsistent terms for "State" (always use "Status").144 145---146 147**Version:** 1.0 — derived from existing `nl/*.json` locale files (March 2026)148