Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Translating License #64

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.

Sign up for GitHub

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

Jump to bottom
Closed
StanFromIreland opened this issue Jan 31, 2025 · 3 comments
Closed

Translating License #64

StanFromIreland opened this issue Jan 31, 2025 · 3 comments

Comments

@StanFromIreland
Copy link
Collaborator

How do we go about translating license.po? It is a copy of a legal document. Do we translate it or do we leave it in the official state?
@m-aciek
Copy link
Collaborator

m-aciek commented Jan 31, 2025 •
edited
Loading

I think we shouldn't translate the content of the licenses, but everything else in the docs chapter, like titles, comments and descriptions, similar like in Brazilian Portuguese: https://docs.python.org/pt-br/3/license.html.

Note that there are five usages of `` as opening quotes in licenses content, that triggers sphinx-lint warnings. I think it's ok to change it regular '' quotes. Also it would be worth to start discussion about changing those quotes upstream.

@StanFromIreland
Copy link
Collaborator Author

The Br license is a bit of a mess I think. Maybe we should stick with one?

@StanFromIreland
Copy link
Collaborator Author

As for the quotes I will open a PR. The goal is to be consistent from what I know.

@m-aciek m-aciek closed this as completed Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@m-aciek @StanFromIreland