You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At first, I was skeptical of opening this issue, but I think it needs to be addressed.
The problem
The website has amazing content, and its very cool PY4E is dedicated to being available in as many languages as possible. However, I think currently the steps needed to start translating the website are either too hard, or not clear, from the TRANSLATIONS.MD file one can understand which files you can translate, but not how to send the contribution back to this repo, if there even is a way to do it correctly. In addition to this confusion, the google translate widget on the website makes so people will probably never know there's actually a translated version of the website with translated slides and other materials, as the translated slides will only be available in the translated mirror.
Example
For instance, the repository in Spanish has translated most if not all the slides available, however when selecting the Spanish language on the website you'll not find the correct translated slides. How should one know they need to visit another URL for their language if the PY4E website has that little Google translate widget at the bottom? It's intuitive to think that selecting the language should also redirect to the Spanish mirror, which will have the translated slides.
Proposal
My proposal is that the repository is updated to have more in-depth instructions, an explanation on how to translate the slides, and have the PY4E website actually integrate those translated slides, instead of having multiple subdomains for that.
Another much simpler option is to redirect users to the translated mirror of the website when they choose to use a certain language, for instance when selecting Spanish, the user would be redirected from https://www.py4e.com/ to https://es.py4e.com/. This could cause problems though if the repository owner is not actively merging and translating changes from the upstream.
Reason
I'm creating this issue because I was interested in translating the slides to Brazilian Portuguese, but I found the instructions unclear, and the final result ineffective because of the need for a different URL. I feel this is how other people who would've otherwise contributed to translating the website felt, but I didn't see any issues relating to this topic.
The text was updated successfully, but these errors were encountered:
At first, I was skeptical of opening this issue, but I think it needs to be addressed.
The problem
The website has amazing content, and its very cool PY4E is dedicated to being available in as many languages as possible. However, I think currently the steps needed to start translating the website are either too hard, or not clear, from the TRANSLATIONS.MD file one can understand which files you can translate, but not how to send the contribution back to this repo, if there even is a way to do it correctly. In addition to this confusion, the google translate widget on the website makes so people will probably never know there's actually a translated version of the website with translated slides and other materials, as the translated slides will only be available in the translated mirror.
Example
For instance, the repository in Spanish has translated most if not all the slides available, however when selecting the Spanish language on the website you'll not find the correct translated slides. How should one know they need to visit another URL for their language if the PY4E website has that little Google translate widget at the bottom? It's intuitive to think that selecting the language should also redirect to the Spanish mirror, which will have the translated slides.
Proposal
My proposal is that the repository is updated to have more in-depth instructions, an explanation on how to translate the slides, and have the PY4E website actually integrate those translated slides, instead of having multiple subdomains for that.
Another much simpler option is to redirect users to the translated mirror of the website when they choose to use a certain language, for instance when selecting Spanish, the user would be redirected from https://www.py4e.com/ to https://es.py4e.com/. This could cause problems though if the repository owner is not actively merging and translating changes from the upstream.
Reason
I'm creating this issue because I was interested in translating the slides to Brazilian Portuguese, but I found the instructions unclear, and the final result ineffective because of the need for a different URL. I feel this is how other people who would've otherwise contributed to translating the website felt, but I didn't see any issues relating to this topic.
The text was updated successfully, but these errors were encountered: