potiuk commented on code in PR #62066: URL: https://github.com/apache/airflow/pull/62066#discussion_r2938606591
########## .github/skills/airflow-translations/locales/hi.md: ########## @@ -0,0 +1,73 @@ +<!-- SPDX-License-Identifier: Apache-2.0 + https://www.apache.org/licenses/LICENSE-2.0 --> + + +# Hindi Translation Agent Skill + +This file defines terminology, tone, and translation preferences +for Hindi (hi) translations of Apache Airflow. + +## Tone and Style + +- Use formal and respectful language. +- Address the user as **"आप"**. +- Prefer clear and simple sentence structure. + +## Keep in English + +The following terms must remain untranslated: + +- XCom +- ID +- Log Levels (CRITICAL, ERROR, WARNING, INFO, DEBUG) + +## Preferred Translations + +| English Term | Hindi | +|-------------|------| +| Dag | डैग | +| Dag Run | डैग रन | Review Comment: **Bug / internal contradiction — `Task` translation.** The table maps `Task → कार्य` (a native Hindi noun), but Translation Principle #3 (line 55) explicitly holds up `टास्क` as the model example of transliteration for Airflow-specific terms: > _Use transliteration for Airflow-specific terms (e.g., डैग, **टास्क**)._ An agent reading both sections gets contradictory instructions. The source `hi/README.md` documents it as `Task → टास्क` (transliteration), not `कार्य`. Decide on one and make both sections consistent. If you want to keep the native-Hindi form `कार्य`, update Principle #3's example. If you want transliteration, update the table to `टास्क`. -- 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]
