Sentences with phrase «spine item»

The rendition: orientation - landscape, rendition: orientation - portrait and rendition: orientation - auto properties [Rendition Vocab] may be specified locally on spine itemref elements, and will, in such cases, override the global value for the given spine item.

When the property is set to pre-paginated for a spine item, its content dimensions must be set as defined in Fixed Layouts [Content Docs 3.1].

Similarly, when a pre-paginated spine item follows a reflowable one, the pre-paginated one should start on the next page (as defined by the page - progression - direction) when it lacks a rendition: page - spread - * property value.

If the reflowable spine item has a rendition: page - spread - * specification, it must be honored (e.g., by inserting a blank page).

The rendition: flow - auto, rendition: flow - paginated, rendition: flow - scrolled - continuous and rendition: flow - scrolled - doc properties [Rendition Vocab] may be specified locally on spine itemref elements, and will, in such cases, override the global value for the given spine item.

When a reflowable spine item follows a pre-paginated one, the reflowable one should start on the next page (as defined by the page - progression - direction) when it lacks a rendition: page - spread - * property value.

The rendition: spread - landscape, rendition: spread - both, rendition: spread - auto and rendition: spread - none properties [Rendition Vocab] may be specified locally on spine itemref elements, and will, in such cases, override the global value for the given spine item.

If the pre-paginated spine item has a rendition: page - spread - * specification, it must be honored (e.g., by inserting a blank page).

The rendition: page - spread - left property indicates that the given spine item should be rendered in the left - hand slot in the spread, and rendition: page - spread - right that it should be rendered in the right - hand slot.

For reflowable content, this is why each new spine item's content begins at the top of a new page.

specified an optional extension mechanism enabling a spine item to be a «custom module» XHTML or arbitrary XML styled with CSS.

Specifies the intended Reading System synthetic spread behavior for this Publication or spine item.

Specifies which orientation (s) the Author intends for the given Publication or spine item to be rendered in.

The rendition: layout property may also be specified locally on the Package Document spine itemref element, and will, in this case, override the global value for the given spine item.

The rendition: orientation property may also be specified locally on the Package Document spine itemref element, and will, in this case, override the global value for the given spine item.

Each XHTML and SVG spine item which has the «pre-paginated» value set for its rendition: layout property must contain the viewport (for XHTML) or viewBox (for SVG) dimension expressions as defined below.

Specifies the Reading System should render a synthetic spread for the spine item only when in landscape orientation.

Specifies the Reading System can determine when to render a synthetic spread for the spine item.

The Reading System should render all Content Documents such that overflow content is scrollable, and each spine item should be presented as a separate scrollable document.

Specifies the Reading System should render a synthetic spread for the spine item only when in portrait orientation.

The initial implementation has several limitations, including that the fixed layout decision is made on a per book basis rather than per spine item, so it only works if fixed layout is specified globally via the rendition: layout metadata property.

Reading Systems should render a Synthetic Spread for spine items only when the device is in portrait orientation.

Reading Systems should render a Synthetic Spread for spine items only when the device is in landscape orientation.

Reading Systems may render spine items by their own design.

When the rendition: layout property is specified on the Package Document meta element, it indicates that the paginated or reflowable layout style (refer to Allowed values below) applies globally for the given Publication (i.e. for all spine items).

When the rendition: orientation property is specified on the Package Document meta element, it indicates that the intended orientation applies globally for the given Publication (i.e. for all spine items).

Refer to Fixed - Layout Properties [Packages 3.1] for information on how to designate that a Rendition, or its individual spine items, are to be rendered in a pre-paginated manner (i.e., with fixed width and height dimensions).

You also don't have to worry about all the manual work to make the standalone publication valid, like removing manifest and spine items and tweaking the table of contents and links.

You can copy and paste manifest and spine items from the publication and just tweak them to be links.

When the rendition: spread property is specified on a meta element, it indicates that the intended Synthetic Spread behavior applies globally for the given Rendition (i.e., for all spine items).

When the rendition: layout property [Rendition Vocab] is specified on a meta element, it indicates that the paginated or reflowable layout style applies globally for the Rendition (i.e., for all spine items).

To indicate that two consecutive pages represent a true spread, Authors should use the rendition: page - spread - left and rendition: page - spread - right properties on the spine items for the two adjacent EPUB Content Documents, and omit the properties on spine items where one - up or two - up presentation is equally acceptable.

When the rendition: orientation property [Rendition Vocab] is specified on a meta element, it indicates that the intended orientation applies globally for the given Rendition (i.e., for all spine items).

When the rendition: flow property [Rendition Vocab] is specified on a meta element, it indicates the Author's global preference for overflow content handling (i.e., for all spine items).

When the rendition: spread property is specified on the Package Document meta element, it indicates that the intended synthetic spread behavior applies globally for the given Publication (i.e. for all spine items).

Not exact matches

But we forgive amaranth of these spines, because it is a healthful bulk item staple, and it's easy to cook.

Just a few examples of items made to torture the spines of tall parents and turn us into the Hunchback of Notre Dame.

I assume that items in the NCX should behave like items in the spine and use the fallback attribute, but I don't remember reading about it in the specs.

In practice, all the items in the spine appear in the NCX, but the NCX can be more granular than the spine.

Conforming EPUB reading systems will open the book to the first item in the spine that's not set as linear = no.

Refer to Manifest item Properties [Publications30] and Spine itemref Properties [Publications30] for more information.

The linear attribute in the spine indicates whether the item is considered part of the linear reading order versus being extraneous front - or end - matter.

The new properties attribute on the Package Document manifest item and spine itemref elements allows for the declaration of metadata about individual Publication Resources.

There are fallbacks for items in the spine, content switching fallbacks at the markup level, element intrinsic fallbacks, manifest fallbacks for content elements, and even binding of media types to scripted fallbacks (before reaching intrinsic fallbacks!).

The expectation with items in the spine is that a page break is assumed before each.

Authors also need to ensure that they identify whether items in the spine contain primary or supplementary information using the linear attribute [Packages] so that the Reading System can optimally present such content.

When this property is used in the spine within an itemref, the property is defined immediately following the item id.

Reading Systems must not show list item numbering on these lists when presenting the Navigation Document outside of the spine, regardless of their support for CSS.

Defined reading order — an EPUB publication has a «spine» that determines a start - to - end reading order for its top - level content items (though nothing requires that the publication to be consumed in that order)

If this property is used in the spine within an itemref, the property is defined immediately following the item id.