Skip to content
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

Make copybutton messages translatable #27

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ccwang002
Copy link
Contributor

This PR implements #23 which make the messages of copybutton (>>>) translatable.

When I tested my change using the master branch of Python (branch 3.7 doesn't seem to use python-docs-theme), I couldn't get it read my modified layout.html. However, if I manually introduced the change, the pot files would include the new strings and the translation worked.

I think it is better to have someone more familiar with the project structure of PEP 545 to test my implementation before it is merged.

@JulienPalard
Copy link
Member

There's a little issue, the command gathering translations strings:

sphinx-build -Q -b gettext -D gettext_compact=0 Doc pot/

won't pick it up, so translation teams won't see it as a sentence to translate. I don't have the time right now to check if there's a simple way to solve this, maybe Sphinx has a way to look for translations strings in configured theme?

@theacodes
Copy link
Collaborator

These resources might be helpful:

  1. Add localization language support readthedocs/sphinx_rtd_theme#403
  2. Added localization language support readthedocs/sphinx_rtd_theme#405

@septatrix
Copy link
Contributor

I think I looked into this in the past and it was possible to directly translate the strings in the javascript file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants