8000 remove linear=no from <itemref idref="cover" linear="no" /> · Issue #1609 · jgm/pandoc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to con 10000 tent
remove linear=no from <itemref idref="cover" linear="no" /> #1609
Closed
@ousia

Description

@ousia

As already discussed in #1593, linear=no makes the <itemref> auxiliary. Breaking the linearity of an <itemref> allows the reading system to present its content in a different order from that one specified in the <spine>.

From the ePub 2 spec:

Specifying whether an OPS Content Document is primary or auxiliary is useful for Reading Systems which opt to present auxiliary content differently than primary content. For example, a Reading System might opt to render auxiliary content in a popup window apart from the main window which presents the primary content. (For an example of the types of content that may be considered auxiliary, refer to the example below and the subsequent discussion.)

Reading Systems are not required to differentiate between primary and auxiliary content, and for the requirements and recommendations given in this section may consider all OPS Content Documents in spine to be primary, regardless of the value of the linear attribute.

Or the ePub 3 spec:

The itemref element linear attribute indicates whether referenced item is considered primary (yes) or auxiliary (no) in the spine. This attribute may be used to enable Reading Systems to distinguish presentation of body content from supplementary content which might be, for example, presented in a popup window or omitted from an aural rendition.

From both descriptions, I think it is important to remove linear=no from <itemref idref="cover" linear="no" /> in both ePub 2 & 3 formats.

As far as I understand, the book cover is no axiliary content. Either way, it shouldn’t be presented in a popup window.

Many thanks for your help.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0