Skip to content

Added Telugu translations for article#3679

Open
Yugenjr wants to merge 1 commit into
github:mainfrom
Yugenjr:telugu-translation
Open

Added Telugu translations for article#3679
Yugenjr wants to merge 1 commit into
github:mainfrom
Yugenjr:telugu-translation

Conversation

@Yugenjr
Copy link
Copy Markdown

@Yugenjr Yugenjr commented May 29, 2026

  • Have you followed the contributing guidelines?
  • Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.


Adds full Telugu translations by adding a "te" folder containing exact-structure translations of the core guides (same front-matter and content in Telugu) and a te.yml" file .

no changes to the othersources, ready for Jekyll validation and review.

@Yugenjr Yugenjr requested a review from a team as a code owner May 29, 2026 15:19
Copilot AI review requested due to automatic review settings May 29, 2026 15:19
@Yugenjr
Copy link
Copy Markdown
Author

Yugenjr commented May 29, 2026

@kenyonj kindly review for the change

@Yugenjr
Copy link
Copy Markdown
Author

Yugenjr commented May 29, 2026

I added Telugu translations to extend the guide’s accessibility to Telugu-speaking users and contributors. Telugu is a major regional language with a large and growing online population localizing the core guides lowers barriers to entry, helps attract contributors from the Telugu-speaking community, and improves inclusivity for people particularly around south India... Cause we all Indians don't speak in a single language as our language culture is diverse .

Hope this pr meets the requirements of those people . And also , marathi is also an very well known language spoken by Indian people , and if required , let me raise another pr for the same . ThankYou

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

Copy link
Copy Markdown
Contributor

@kenyonj kenyonj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for kicking off Telugu support, @Yugenjr! Telugu has been requested a few times historically (#2714, #3484, #3486 were all closed without merging) so this is welcome work.

The locale file (_data/locales/te.yml), the index.html, and the directory layout under _articles/te/ all look structurally correct. Where I want to flag a concern is the depth of the article translations themselves: each of the 13 article files looks much shorter than the English original, which suggests the content was summarized rather than fully translated. A few examples:

article English source (lines on main) Telugu in PR coverage
how-to-contribute.md 527 22 ~4%
starting-a-project.md 356 22 ~6%
accessibility-best-practices-for-your-project.md 301 36 ~12%
building-community.md 276 26 ~9%
best-practices.md 280 59 ~21%

The other locales in this repo (be, bn, hi, ja, ru, zh-hans, etc.) translate each article more or less paragraph-for-paragraph, including the <aside class="pquote"> blocks, code samples, and cross-article anchor links. The Telugu versions here are missing most of those: I do not see the maintainer quotes (e.g. @lord, @mikeal, @captainsafia), the contributor-funnel images, the section-link anchors back to other articles, etc.

A couple of smaller things I spotted while reading:

  • _articles/te/building-community.md line 4: the description contains sustentable, which is Spanish/Portuguese, not Telugu or English. Probably an LLM-handoff leak.
  • _articles/te/best-practices.md line 58 ends with a Chinese full-stop rather than a Devanagari/Telugu/Latin period ..

Heads-up: I am not a native Telugu speaker, so I have leaned on AI to spot-check structure rather than verify fluency end-to-end.

Given the size, would you be open to landing this in smaller per-article PRs, each with a full translation of one article (matching the structure and depth of the existing locale articles)? That way the team can review carefully, and partial work is not blocked on the rest of the set. Happy to help if you have questions about expected article structure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants