-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help translate the Python Package Guide into Spanish #313
Comments
Working on this! #SciPy2024! --> Working mostly on CONTRIBUTING.md |
Same here! |
@RobPasMue @yardasol We are currently rewriting the English file in issue #310, so it's NOT the best one to work on! |
Some of the files are very big, but you don't need to translate it all! Feel free to work on as few strings as you want. If you both decide to work on the same file, you will need to coordinate to avoid double work. |
I opened independent PRs for all the files in the packaging guide. This will take time to review but I'll be as responsive and active as possible. Just want to help you all! |
This is awesome! Thanks everyone 😍 |
I updated the text of the issue with the stats as of today (pending a few PR waiting review). We are about 27% done. |
We are currently working on translating the Python Package Guide into Spanish and we could use the help of new contributors. This is a great issue to work on if you speak Spanish and you are new to open source contributions!
How to help
The guide is divided in sections. The English text in each section is extracted and stored in a
.po
in the folder./locales/es/LC_MESSAGES
. Next to each of the original English string, you will find a place to enter the Spanish translation for that string.Start by looking at the Translation Guide, it describes the translation workflow and has instructions about how to set up your local environment to work on translations.
If you are new to open source contributions, you can also contribute directly in the GitHub website. In that case you will need to fork the repository into your personal GitHub and make the changes on your forked copy before making a Pull Request. Some sections of the Translation Guide will still be useful, like Editing the Translation Files and Frequently Asked Questions (FAQ).
Look at the table below and choose a translation file to work on. The files are named after the sections of the guide.
Look at the comments to this issue and check if someone else is already working on that file. If nobody is, add a comment to this issue indicating that you will start working on that file.
If someone else is already working on the file, you will need to coordinate with them to make sure you don't duplicate work.
If you want to see an example of a file that already has been translated, take a look at ./locales/es/LC_MESSAGES/index.po. It contains the strings for the landing page of the guide.
Translation Status as of 09/14/2024
We are about 27% done!
The table below shows the number of strings in each translation file. Strings marked 'fuzzy' indicate that the original text has changed and the translation needs to be reviewed and fixed if necessary.
The text was updated successfully, but these errors were encountered: