Repository navigation
glossary property in the manifest is not allowed on content documents #1170
Description
Tested on epubcheck 4.2.4.
At Standard Ebooks we're trying to add a glossary according to the EPUB Dictionaries and Glossaries 1.0 spec.
In the manifest file, we add two items:
<item href="glossary-search-key-map.xml" id="glossary-search-key-map.xml" media-type="application/vnd.epub.search-key-map+xml" properties="search-key-map glossary"/>
<item href="text/glossary.xhtml" id="glossary.xhtml" media-type="application/xhtml+xml" properties="glossary"/>According to the spec, we should be able to add the glossary property both to the search key map file to to indicate that the file applies to a glossary, and to the XHTML content document file to indicate that it contains the actual glossary.
However epubcheck outputs:
ERROR(OPF-015): /path/to/glossary.xhtml(-1,-1): The property 'glossary' should not be declared in the OPF file.
It seems to allow glossary for the search key map, but not for the XHTML file.
Activity
[-]glossary property in the manifest is not allowed[/-][+]glossary property in the manifest is not allowed on content documents[/+]rdeltour commentedon Aug 4, 2020
Have you checked that your
glossary.xhtmlXHTML Content Document includes at least an element with theepub:typeglossary? This is mandatory for theglossaryproperty to be allowed on the manifest item.If that's not the issue, then it's possibly a bug in EPUBCheck 😊
acabal commentedon Aug 4, 2020
Yes,
glossary.xhtmlhas an element withepub:type="glossary", though it's on a<section>element inglossary.xhtml, not a<dl>element.rdeltour commentedon Aug 5, 2020
OK, thanks for your answer 😊
Are you running EPUBCheck with the
dictprofile?Would you be able to share a test EPUB?
rdeltour commentedon Aug 5, 2020
I was able to reproduce, so no need to send a test EPUB after all 😉
I'll dig deeper, but it does seem like a bug. Thanks for the report!
fix: allow the 'glossary' manifest item property
fix: allow the 'glossary' manifest item property