locales/hi.md
461 tokens · o200k_base · 2,235 bytes
Source excerpt starting at line 1.<!-- 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 preferencesfor 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 | डैग रन || Task | कार्य || Task Instance | टास्क इंस्टेंस || Asset | एसेट || Asset Event | एसेट इवेंट || Configuration | विन्यास || Connections | कनेक्शन || Operator | ऑपरेटर || Variable | वेरिएबल || Plugins | प्लगइन || Pools | पूल || Provider | प्रोवाइडर || Trigger | ट्रिगर || Backfill | बैकफ़िल || Bundle | बंडल || Scheduled | निर्धारित || Map Index | मैप इंडेक्स || Try Number | प्रयास संख्या || Key | कुंजी || Home | मुख्य पृष्ठ | ## Translation Principles 1. **Formal UI language** - Maintain politeness and clarity suitable for professional software. 2. **Pure Hindi for common UI words** - Prefer words like *विन्यास* instead of transliteration where clarity is high. 3. **Transliteration for technical concepts** - Use transliteration for Airflow-specific terms (e.g., डैग, टास्क). 4. **Avoid ambiguity** - If a literal translation could confuse users, prefer transliteration. 5. **Context awareness** - Ensure translations match technical meaning rather than dictionary meaning. ## Notes - Use **"कुछ नहीं"** for `states.none`.- Use **"कोई स्थिति नहीं"** for `states.no_status`. These conventions are derived from the existing Hindi locale guidelinesto ensure consistency across future translations.