-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Converting Epub with noteref to any format drops <a ... epub:type="noteref"> in result #7884
Comments
See #5531. |
Original: example.docx
I had to zip the example files because of unsupported file formats. |
when parsing `<a epub:type="noteref">` and the identifier doesn't correspond to anything in the note table. Previously we just silently skipped these cases. See #7884.
OK, I see the problem now and have a path to fixing it. |
Excellent. I built from source now and the issue is resolved. When do you expect this fix to be released? |
Really? It's not resolved in my tests. |
I could see the warnings while converting. Still the <a> tag is present in the final html output. There is however a new block at the end which does not seem complete I omitted the -s for simplicity, but the result is the same. |
The problem is that we aren't finding the id in the note table. |
I can't tell you when the next release will be. For now you can use a nightly. |
Explain the problem.
When I convert any epub3 file with footnotes
<a ... epub:type="noteref">
to html, pdf or docx the entire <a> element is removed from the body in the resulting file. The actual note itself at the end of the document is present. If I remove theepub:type="noteref"
attribute before converting it comes through.pandoc -o org.html -s -f epub org.epub
FYI: The document starts out as a docx, then we store them as epub internally, and offer pdf exports. So the source epub file is also generated by Pandoc.
Pandoc version?
pandoc 2.17.1.1
Compiled with pandoc-types 1.22.1, texmath 0.12.4, skylighting 0.12.2,
citeproc 0.6.0.1, ipynb 0.2
The text was updated successfully, but these errors were encountered: