Hello everyone, I’m Divya, a Senior Software Engineer at Microsoft in Seattle, working on distributed storage in Azure. I’m a patent holder and have published research and IEEE paper.
About three months ago I started a Telugu translation of the Python docs, and I’m aiming to wrap up the initial translation in the next two weeks. Telugu is the 16th most spoken language in the world according to [source, e.g. Ethnologue], with tens of millions of speakers, and there is currently no Python documentation in it.
The work is in a private repo for now. I plan to move it to a public python-docs-te repo once it’s ready, and I’m happy to give reviewers access sooner if that helps. I’d like to get it listed as an official translation under PEP 545, and I’d appreciate guidance on the remaining steps (coordinator process, publishing to docs.python. org).
I’ll share updates in this thread as things move forward!
Hello Divya,
That’s great! I’m curious as to where you’re working on this, is the a repository on GitHub? Also, please note that PEP 545 is outdated, we now have a more up-to-date guide in the Devguide: Starting a new translation
If you have any questions, feel free to ask, I’ll be happy to help.
Hey Stan,
Yes, it’s on my private GitHub repo for now. I originally started it for a different purpose, to fine-tune a local language model, but now I’d like to make it available to the broader Python community. The initial translation was machine-generated and is being reviewed by a 3 people. I’m happy to follow whatever review process the community expects for Telugu, and I’d welcome other Telugu reviewers. I’ll follow the Devguide for the next steps.
It’s great to see we have Transifex at no cost now (Transifex subscription renewal · Issue #196 · python/docs-community).
Could you please accept my invite for Telugu (te) in Transifex?
-Divya
Thanks for the update, and for your efforts on the Telugu translation!
Could you please clarify why the repository is currently private? Since Python is an open-source project, we follow the same principle for our translations. Keeping the work public allows the community to review, contribute, and collaborate openly. I don’t think we would be able to move forward with integrating a translation maintained in a private repository (Transifex, for example, requires it be open-source for our project).
Hey Stan,
The repo is private because it’s part of my work at my company. I expect to get sign-off easily to make it public. If not, I’ll start a new project and publish that instead. I’ll update here either way.
@Stanfromireland Here is the public repo
Telugu (te) translation of the Python documentation:
GitHub - divya0795/python-docs-te: Telugu (te) translation of the Python documentation · GitHub (branch 3.15).
The core resources are complete: bugs.po, all of tutorial and builtins/functions.po. A CI workflow mirrors the dashboard’s core-completion check against the latest 3.15 sources every week, and terminology and conventions are documented in GLOSSARY.md.
I’ve opened a devguide PR to add Telugu to the list of translations (python/devguide#1978). Could you advise on the next steps for moving the repository to the python organization and adding it to docsbuild-scripts?
Transifex user name : divya0795
Going forward I will find some volunteers that will help with more translation and multi-person review.
@Stanfromireland Devguide says to translate both comments and strings as well it that accurate ?
In context of code example snippets this was set as a recommendation, especially not to translate variables’ and classes’ names. Feel free to adapt it to whatever would best fit Telugu readers.
If you decide to modify this rule for your project, I’d suggest to put it in contribution notes, for uniformity across whole translation.
Transalations are ready and verified by @thejesh23 . Please let me know next steps.
Transifex user name : divya0795
Hi Divya, congratulations
![]()
As next step I recommend translating sphinx.po resource which holds parts of templates, i.e. the main page of the documentation. Then also the theme (navigation).
I’ve run Codex (GPT-6.1-Sol) over the translation, let me share it’s review, I hope it will be helpful (I’m not a Telugu speaker, so unfortunately I cannot verify it myself):
The reviewed translations in
tutorial/,bugs.po, and
builtins/functions.poare generally faithful and usable. Technical terminology
is consistent with the project glossary, and the straightforward instructions
are easy to follow. Some longer explanations would benefit from less literal
wording.There is one clear meaning error to correct. The other points below are
suggestions for improving precision and readability. Please review the Telugu
wording and adjust it in your own words where appropriate.
Correct the reference to the empty dictionary.
Location:
tutorial/datastructures.po:962, in the paragraph beginning
“Curly braces or the set function can be used to create sets.”The translation mentions
{}first andset()second, then says
రెండోది ఖాళీ డిక్షనరీని సృష్టిస్తుంది(“the second one creates an empty
dictionary”). After the order has changed, “the second one” refers to
set(), which creates an empty set.Please replace that reference with an explicit statement that
{}creates
an empty dictionary. For example, the relevant reST fragment could be:``{}`` ఖాళీ డిక్షనరీని సృష్టిస్తుందిClarify the explanation of rounding ties.
Location:
builtins/functions.po:3294, in the description ofround().The phrase
సరి సంఖ్య వైపుcan be read as “toward an even number.” With
ndigitsspecified, the rule concerns the last retained digit, rather than
requiring the result to be an even integer. For example,
round(2.25, 1)returns2.2, whileround(2.75, 1)returns2.8.Consider saying explicitly that, when the two candidates are equally close,
Python chooses the one whose last retained digit is even. This is a
clarification suggestion; the English source is also quite compact here.Use more concrete wording for object identity and passing costs.
Location:
tutorial/classes.po:113andtutorial/classes.po:119, in the
paragraph beginning “Objects have individuality.”
వ్యక్తిత్వంfor “individuality” can suggest personality, whileచౌక
for “cheap” can suggest a monetary price. The surrounding explanation
provides context, but these literal choices may distract from the concepts.Consider wording that expresses that each object has its own identity and
that passing an object reference has a low computational cost. These are
editorial suggestions rather than definite technical errors.Make the effect of opening a file in write mode explicit.
Location:
builtins/functions.po:2533, the table entry for mode'w'.
ముందుగా ఫైల్ను కత్తిరిస్తుందిconveys “truncates the file first,” but
may leave a learner unsure how much is removed. Saying that the existing
contents are removed would make the consequence clearer. The file itself
remains; its contents are cleared.Simplify the invitation to provide additional information.
Location:
bugs.po:160, in the paragraph about checking whether a problem
has already been reported.
ఆ సమాచారం అందించడానికి మీకు స్వాగతంclosely follows “you are welcome
to provide it.” A more direct invitation may read more naturally in this
practical instruction. One possible replacement for the parenthetical is:(అలాంటప్పుడు మీకు వీలైతే ఆ సమాచారాన్ని అందించండి!)The intended meaning is “In that case, please provide the information if
you can.” This is a style suggestion.The reviewed explanations of mutability, shared default argument values, and
short-circuit evaluation preserve the important distinctions. The use of
transliterated technical terms is consistent with the glossary.
Thanks @maciek though the fifth one is optional. The first four make a lot of sense to address.
I used the NLLB-200 (No Language Left Behind) model for the initial translation, followed by a Sonnet review. NLLB-200 got most of the translation right, but I still had to make hundreds of corrections because some of its output didn’t make sense during human review.
@maciek sphinx.po (113 strings) is translated on both branches.
- Devguide PR #1978 ( Add Telugu to the list of translations by divya0795 · Pull Request #1978 · python/devguide · GitHub ) (adds Telugu to the translations list):
- Theme PR python-docs-theme#336 ( Add Telugu translation by divya0795 · Pull Request #336 · python/python-docs-theme · GitHub ):
Sphinx’s own Telugu labels. “Contents”, “Index”, “next” and so on are 0% translated, and we can use Sphinx’s Transifex project as we have the free/sponsored subscription .