i18n(te): automated Crowdin translation import (part 12 of 13)#17506
Conversation
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
minimalsm
left a comment
There was a problem hiding this comment.
Translation Review: Telugu (te) - Part 12
Files: 23 JSON files in src/intl/te/
Translation rate: 96.9% (3,051/3,149 keys translated, 98 identical to English)
Scans Performed
- Crowdin
''artifacts - Brand name transliterations
- Cross-script contamination (Devanagari in Telugu)
- HTML tag mismatches (EN vs TE)
- Interpolation variable mismatches
- JSON validity
- Broken inline HTML
Results
No critical/blocking issues found.
Minor observations (non-blocking):
-
Inconsistent Ethereum transliteration: Two variants used — "ఇతీరియము" (275 occurrences, dominant) and "ఎథేరియం" (27 occurrences). Plus 445 strings keep the English "Ethereum" untranslated. This is a consistency issue best addressed upstream in Crowdin's translation memory rather than in this PR.
-
Extra
<strong>tag inpage-ethereum-vs-bitcoin-bitcoin-section-1: TE has 3<strong>pairs vs EN's 2 — translator wrapped the verb "సృష్టించబడింది" in an extra<strong>. Non-breaking for JSON i18n but slightly divergent from source markup. -
Orphaned files:
page-developers-learning-tools.jsonandpage-developers-local-environment.jsonhave no corresponding EN source files ondev. These keys appear to have been removed from the English namespace. The files are harmless dead weight but could be cleaned up in a future Crowdin sync. -
Crowdin
''artifact inpage-contributing-translation-program-acknowledgements-translation-leaderboard-1— matches the English source exactly (''winning''), so this is not a translation error.
Verdict
Clean import. LGTM.

Summary
Context
Split from the original large import PR for easier review and independent merging.