-
Notifications
You must be signed in to change notification settings - Fork 196
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 "local id not found in doc" in translated docs since MyST-parser 0.19.0 #844
Comments
local id not found in doc
in translated docs since MyST-parser 1.0.0local id not found in doc
in translated docs since MyST-parser 0.19.0
local id not found in doc
in translated docs since MyST-parser 0.19.0
This seem to be duplicate of #839 |
I don't think so, but I think you have the same as mine. This one is specifically about this issue with translated documents only. I don't have the issue with untranslated documents. |
By the way @thorge, if you have a way to reproduce this issue on a smaller/simpler repository than mine, it would probably help locating the issue. |
This works for me, thanks you @n-peugnet |
I can not reproduce this on our latest As it is related to translations, I tested the |
What version of
myst-parser
are you using?>=0.19.0
What version dependencies are you using?
Any version compatible with the version of MyST Parser used.
What operating system are you using?
Linux
Describe the Bug
Since MyST-parser, I get the
local id not found in doc
when I compile the docs in another language, but the links are correctly produced.These happen only with links with anchors and the setting
myst_heading_anchors
enabled. But some of these links do not produce warnings:These warning do not happen with untranslated version.
Expected Behavior
There should be no warnings.
To Reproduce
I could not make a smaller reproducer as the bug only happens chen there are a lot of files somehow. For instance on the branch
no-issue
I removed almost all the files but the problem does not arise.The text was updated successfully, but these errors were encountered: