-
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
Warning about footnotes when building the Spanish version of the guide #390
Comments
I am not sure if this is helpful @flpm, but I did notice -- below is the English page in .md format. (Excuse me if you already noticed this!).
The translation files look like this
i tried this to ensure the footnote is included in the spanish version and it didn't work.
i just wonder if there is a bug in the sphinx translation extension or if we could ask over there about this issue? we can also ask other folks who have worked on translation with sphinx -- like maybe @melissawm . i'm just taking a wild guess. |
Hi all! Thanks for the ping ❤️ Unfortunately I am not that familiar with the sphinx extension and can't reproduce this failure locally - |
I think this is due to this issue in the myst-parser: executablebooks/MyST-Parser#690. There seems to be a workaround available in the issue itself but it hasn't been "upgraded" to a PR. I think maintainers of myst-parser/myst-nb are stretched quite thin and can't work much (or at all) on internationalization stuff. I do use sphinx for translations from time to time but there are several rough edges still and I don't really have the knowledge nor availability for in depth testing and fixing. I am interested on getting transaltions with sphinx+myst to work smoothly though so it would be gretlat to get some coordination going. I also have executablebooks/MyST-NB#600 which similarly to the issue above is waiting for maintainer availability. |
@all-contributors |
I've put up a pull request to add @melissawm! 🎉 I've put up a pull request to add @OriolAbril! 🎉 |
After @melissawm 's comment, I tried again and starting from a clean slate, it works without warnings on the main branch. I can't understand why, but I will investigate, but it does not seem to be a block for release at this point. Thank you so much @melissawm and @OriolAbril for taking a look! |
@melissawm @OriolAbril - thank you both so much for the help here! It seems like something has been magically fixed. A few of us now don't see the issue. Maybe there was a patch release somewhere? Regardless thank you all for the thought and effort 👐🏻 and thank you @tkoyama010 for being on top of all contributor additions!! |
I did some more research on this. On my computer, it works using the virtual env in the build-language session but not in the virtual env for the docs-test session. And there are some version differences:
The virtual env for build-language is newer, because it is a new session we created recently. So it looks like the problem might have solved itself with an update in the sphinx modules, but it persist in some places because the cached virtual env. Since we do not fix version in pyproject.toml, we should look into a way to tell nox to check for latest versions every time it runs a session, or we risk having these unexpected version differences across nox sessions in the same machine. |
🙌 @ucodery found an issue with our nox config that explains this behavior! |
Do we wanna use pdm to make/use a lockfile as well? |
@ucodery helped figure out what was happening, from a discussion in Slack: AH! I see the problem python-package-guide/noxfile.py Line 6 in cdbdf85
Will close this issue now and create another one to discuss removing this parameter. |
Solved. |
After merging PR 342, there is now a warning when building the Spanish version of the guide:
Here is the entire nox log:
The original file (/tutorials/add-license-coc.md) does have the footnotes defined at the bottom (line 199):
This will need to be solved before the Spanish translation can be release since the build in CI will fail.
The text was updated successfully, but these errors were encountered: