i18n(te): automated Crowdin translation import (part 09 of 13)

[minimalsm]

Summary

• Part 09 of 13 — te translation import split from i18n: automated Crowdin translation import (te) #17219
• 23 files

Context

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

[netlify]

✅ Deploy Preview for ethereumorg ready!

Name	Link
🔨 Latest commit	c639e7a
🔍 Latest deploy log	https://app.netlify.com/projects/ethereumorg/deploys/698fbe161284c10008457b7b
😎 Deploy Preview	https://deploy-preview-17503.ethereum.it
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	7 paths audited Performance: 58 (🟢 up 3 from production) Accessibility: 94 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: 59 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[minimalsm]

Translation review: Telugu (te) - Part 9 of 13

Reviewed 23 changed files using automated scans.

Scan Results

1. Crowdin artifacts ('')

No issues. The contentPreview='' occurrences in guides/how-to-id-scam-tokens/index.md match the English source. The '' in waffle-say-hello-world is legitimate test output (empty string).

2. Telugu brand transliterations

Informational (not blocking). Found transliterated brand names:

• ఇథీరియం (Ethereum) — used extensively in non-technical pages (foundation, defi, governance, eips, gaming)
• సాలిడిటీ (Solidity) — used in tutorial titles and descriptions
• హార్డ్‌హ్యాట్ (Hardhat) — used in waffle-say-hello-world tutorial
• ఇతీరియము (alternate Ethereum spelling) — found in transfers and the-graph tutorials

These are stylistic choices by translators for non-code contexts.

3. Telugu inside code fences

Warning — 141 instances across 8 files. Crowdin translators translated code comments, Solidity require() string literals, JavaScript test descriptions, and console output inside code blocks. Affected files:

File	Hits	Severity
uniswap-v2-annotated-code	66	Comments in Solidity
waffle-say-hello-world-with-hardhat-and-ethers	29	Solidity strings, JS tests, console output
transfers-and-approval-of-erc-20-tokens-from-a-solidity-smart-contract	18	require() strings, Python comments
waffle-test-simple-smart-contract	9	require() strings, JS test names
waffle-dynamic-mocking-and-testing-calls	8	JS test descriptions, shell comments
the-graph-fixing-web3-data-querying	8	Solidity comments, GraphQL comments
stealth-addr	2	Rust comments
token-integration-checklist	1	Shell comment

This is a known Crowdin pattern — the same behavior exists in other merged translations (e.g., Chinese zh has 19 instances in the same file). Not build-breaking since code fences are rendered as raw text, but the translated code examples would not compile/run as shown.

4. Cross-script contamination (Devanagari in Telugu)

Clean. No Devanagari characters found in any Telugu files.

5. Broken markdown links

Clean. No broken links in the 23 changed files.

6. Split inline HTML (MDX risk)

Clean. No split inline HTML tags that would break MDX rendering.

7. JSON validation

N/A. No JSON files in this PR.

Verdict

No blocking issues found. The Telugu-in-code-fences issue (141 instances) is a known Crowdin artifact that does not break the build. It affects code readability in tutorials but matches patterns already accepted in other language translations. Fixing this would require a separate pass to restore code blocks from English sources.