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
If you version an iBook and submit updates Apple expects you to increment the version. In the current ePub metadata there's no way to specify a version. The suggested approach is:
Perhaps the thing to do is to allow YAML metadata to contain an ibooks
field, which is a map:
ibooks:
version: 1.3.4
If this is included, meta tags are created in the ibooks namespace,
like
<meta property="ibooks:version">1.3.4</meta>
We might also restrict the fields that are included to the ones
that are explicitly allowed.
We'd also have to add the ibooks prefix to the containing package tag
if any ibooks fields are included.
Nodes of the form
<meta name="calibre:series" content="Classics on War and Politics"/>
are now included from an epub XML metadata file. You can also
include this information in your YAML metadata, like so:
calibre:
series: Classics on War and Policitics
In addition, ibooks-specific metadata can now be included via
an XML file. (Previously, it could only be included via YAML
metadata, see #2693.)
Closes#5098.
If you version an iBook and submit updates Apple expects you to increment the version. In the current ePub metadata there's no way to specify a version. The suggested approach is:
Perhaps the thing to do is to allow YAML metadata to contain an ibooks
field, which is a map:
If this is included, meta tags are created in the ibooks namespace,
like
We might also restrict the fields that are included to the ones
that are explicitly allowed.
We'd also have to add the ibooks prefix to the containing package tag
if any ibooks fields are included.
(From this discussion).
The text was updated successfully, but these errors were encountered: