-
Notifications
You must be signed in to change notification settings - Fork 201
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
🐛 FIX: Fix translation for prev/next #384
🐛 FIX: Fix translation for prev/next #384
Conversation
Merging this in so that others can give this a shot |
if this works then that is absolutely fine, but I would note that this is not sphinx’s standard for extensions, it is the internal standard for their own documentation and I think not really meant for external use. This is because it is not possible for extensions to extend the available translations (happy to be corrected though) |
@chrisjsewell yeah I was trying to figure this out as well. Here I took some inspiration from @jpmckinney who was adding i18n support to the pydata theme in https://github.com/pydata/pydata-sphinx-theme/pull/399/files In that PR he's just using the |
@choldgraf so basically this is the full explanation:
|
right - maybe this only works because we are just re-using translations for words that are already in the Sphinx catalog ("page" and "next" and "previous")? Either way this is a helpful write-up, I've added it to #382 ! |
yep thats exactly the case; anything you can find in one of their translation files you could use with But obviously it is better if we are consistent in using our own translation files (and thus the |
This uses lowercase
previous
andnext
entries, which is the reason that Sphinx wasn't translating them before. Also reverts back to the_(
translation text since that's the Sphinx standard.It also sets previous/next to lowercase so they take up less visual attention, per @pfelber's comments
may address #359 if others confirm