You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't dug into what it specifically doesn't like, but I can see right away that it will never match the language and it's more complicated than needed for epub processing.
The big issue here is that it is looking for a lang attribute but the package document only allows xml:lang.
But there are also only two locations where you can get the language of a metadata element: on the element itself or from the root package element. You don't need to inspect the ancestor chain because the only other element in the ancestor chain is metadata and it's not allowed to have an xml:lang declaration.
In other words, for getting the language, you only need to check:
I haven't dug into what it specifically doesn't like,
For anyone interested, it looks like it's any expression using features above xpath 1.0. Most of the processing is easily implemented in javascript, but there are a couple of sticking points.
Ignoring #503 for now, the javascript xpath resolver also reports the expression to get the language of the summary is invalid:
I haven't dug into what it specifically doesn't like, but I can see right away that it will never match the language and it's more complicated than needed for epub processing.
The big issue here is that it is looking for a
lang
attribute but the package document only allowsxml:lang
.But there are also only two locations where you can get the language of a metadata element: on the element itself or from the root package element. You don't need to inspect the ancestor chain because the only other element in the ancestor chain is
metadata
and it's not allowed to have anxml:lang
declaration.In other words, for getting the language, you only need to check:
or:
The text was updated successfully, but these errors were encountered: