-
Notifications
You must be signed in to change notification settings - Fork 400
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
Properties "endnotes" and "endnote" not defined #714
Comments
It's another change made during the 3.1 revision that hasn't yet been updated in epubcheck. |
¿Is it safe to use endnotes despite the error message or, for security, should I still use rearnotes? Epubcheck error messages are so intimidating ... |
If you're distributing through a vendor who requires strict conformance, go with rearnote(s). They won't see it as a deprecated term, since everyone is using the version that doesn't account for the latest changes right now. If it's just for your own peace of mind, ignore the message knowing that you have the future on your side... |
I'll stay with rearnotes. |
@gitito the EPUB Standard 3.1 is not yet finished and therefore the EpubCheck project hasn't started to include/update checks for EPUB 3.1. I will add a label to this issue so it will get fixed when EPUB 3.1 is officially released. |
Similar to #531, with validation of epub:type removed in 3.2 this issue is no longer applicable. |
I don't have the ability to close issues that aren't my own, so if someone else can close this... |
When I run epubcheck-4.0.1 using 3.0.1 rules validation, error OPF-27 occurs. It says Property not defined with “endnotes” and “endnote”.
All other epub types (toc, noteref, preface, chapter, etc) works fine.
Now I’m using rear notes (passes validation) instead of endnotes. but not feeling comfortable with that deprecated tag.
In my OPF I use version 3.0.
I saw something similar with “page-list” property and turkish locale. My locale is spanish (es)
The text was updated successfully, but these errors were encountered: