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
The intermediate Book object doesn't have much meta info about components, which is useful when going from Zhook -> EPUB.
Zhook will create the Cover and Table of Contents components automatically, but there's no way to communicate to the destination format that these components are non-linear and have a particular "guide" type.
If we can say what the "guide" attribute of a component is, EPUB will be able to derive the linearity of the component (in the spine) from that. Ie, if cover.html is 'cover' in the EPUB guide, then it has a linear value of "no" in the spine.
In general, for both components and metadata, the intermediate book object should perhaps work with Component and Metadata objects, rather than arrays of filenames or hashes of key/values.
The text was updated successfully, but these errors were encountered:
Just for the sake of adding meaning to my zhook's outline, I am giving articles that define sectioning components a class name equivalent to one of the valid guide types according to OPF 2.0.1.
If peregrin would take that value and use it for the guide section in the OPF document, that would just rock.
Edit: Just to be a bit more specific about the way I am coding the books:
The intermediate Book object doesn't have much meta info about components, which is useful when going from Zhook -> EPUB.
Zhook will create the Cover and Table of Contents components automatically, but there's no way to communicate to the destination format that these components are non-linear and have a particular "guide" type.
If we can say what the "guide" attribute of a component is, EPUB will be able to derive the linearity of the component (in the spine) from that. Ie, if cover.html is 'cover' in the EPUB guide, then it has a linear value of "no" in the spine.
In general, for both components and metadata, the intermediate book object should perhaps work with Component and Metadata objects, rather than arrays of filenames or hashes of key/values.
The text was updated successfully, but these errors were encountered: