Release the PT and ES translations of the guide#671
Merged
Conversation
… to be built twice
flpm
added
translations
willingc
approved these changes
May 25, 2026
Collaborator
willingc
left a comment
willingc
left a comment
There was a problem hiding this comment.
Thank you to everyone who worked on this effort. Let's get these translations to readers 🧑🏼🤝🧑🏼
Contributor
|
Hell yeah!!!!!! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After the nice translation contributions we had in the PyCon US 2026 sprints we are ready to release the guide in two additional languages!
Thanks to @KarinaS0uza and @Humanberto work, we now start a Portuguese translation of the guide! And thanks to @OlmosDeAguilera contribution, we made additional progress in the Spanish translation!
A few notes:
i18n.inconsistent.referencesbecause Sphinx does not seem to find the translated terms (marked with{term}in the English source in the glossary, even after we translate them. In order to build cleanly and release, I added the option to suppress these warnings inconf.pyalong with a comment. See issue investigate: Why Sphinx generates i18n.inconsistent.reference warnings when building translations #670