Sentences with phrase «xhtml content»

For example, if the XHTML Content Documents in an Packaged Object are identified as fixed layout using a global

If a Processing Agent renames files, it is responsible for also ensuring that all references to the original names are updated in all resources (all href and src attributes in XHTML Content Documents, any linked CSS and @import rules, etc.).

Note that the sidebar is a fragment of the chapter's XHTML Content Document.

The EPUB Navigation Document is an adaptation of an XHTML Content Document and is, by definition, a valid XHTML Content Document instance.

This attribute allows any element in an XHTML Content Document to include additional information about its purpose and meaning within the work, using controlled vocabularies and terms.

XHTML Content Documents also natively support the inclusion of ARIA role and state attributes and events, enhancing the ability of Assistive Technologies to interact with the content.

It must conform to the content conformance constraints for XHTML Content Documents defined in XHTML Content Documents — Content Conformance [Content Docs 3.1].

The rendition: page - spread - * properties take precedence over whatever value of the page - break - before property [CSS Snapshot] has been set for an XHTML Content Document.

As such, this specification requires that Scriptable Components be embedded using the [HTML5] iframe element whether they are embedded into an XHTML Content Document in an EPUB Publication or into another Scriptable Component.

The following example shows a reference to a remote audio file that has to be referenced from the manifest (the audio is rendered inline in the XHTML Content Document so it is a Publication Resource).

The following example shows a reference to a metadata record embedded in a script element inside an XHTML Content Document.

A specialization of the XHTML Content Document that contains human - and machine - readable global navigation information.

The lack of a rendering context means that the XHTML content model for this document is very restrictive, allowing only a single nav element in the body, to ease both authoring and processing.

XHTML Content Documents also include the means of annotating document markup with rich metadata, making them more semantically meaningful and useful both for processing and accessibility purposes (XHTML Semantic Inflection [ContentDocs301]-RRB-.

EPUB 3.1 supports audio and video embedded in XHTML Content Documents via the [HTML] audio and video elements, inheriting all the functionality and features these elements provide.

If it supports Text - to - Speech (TTS) rendering, it should support Pronunciation Lexicons [Content Docs 3.1], [CSS3 Speech] and SSML attributes [Content Docs 3.1] in XHTML Content Documents.

It must process XHTML Content Document as defined in XHTML Content Documents — Reading System Conformance [Content Docs 3.1].

A specialized XHTML Content Document that contains human - and machine - readable global navigation information.

A specialization of the XHTML Content Document, containing machine - readable mappings between equivalent content in different Renditions, conforming to the constraints expressed in Rendition Mapping.

The list items in each unordered list represent the set of equivalent link destinations across the available Renditions for that content (e.g., one link might point to a document representing one page of a fixed layout Rendition, while the equivalent link to a reflowable Rendition might point to the corresponding page break indicator within the XHTML Content Document containing the page).

For XHTML Content Documents, N would be an even number when referencing the alt text of an img element, and N would be odd when referencing XML character data within elements.

EPUB 3 includes two mechanisms for attaching descriptions to structures in XHTML Content Documents.

This element exists to enable the development of specialized content identification, processing and rendering features, such as the ability to define embedded preview content, or assemble an index or dictionary from its constituent XHTML Content Documents.

The use of [EPUBCFI] expressions is strongly encouraged over other fragment identifier schemes (particularly in the context of reflowable XHTML Content Documents), as they allow Reading Systems to ingest Rendition Mappings without any prior pre-processing.

EPUB 3.1 includes metadata that allows the creation of fixed - layout XHTML Content Documents [Packages 3.1], in addition to existing capabilities for fixed layouts in SVG.

Each Rendition of an EPUB Publication contains a special XHTML Content Document called the EPUB Navigation Document, which uses the HTML5 nav element to define human - and machine - readable navigation information.

XHTML Content Documents also include the means of annotating document markup with rich metadata, making them more semantically meaningful and useful both for processing and accessibility purposes (XHTML Semantic Inflection [Content Docs 3.1]-RRB-.

The Rendition Mapping Document is a compliant EPUB XHTML Content Document, but with the following restrictions on the [HTML5] content model:

The following example shows a reference to an audio file in an XHTML Content Document that is located outside the EPUB Container.

5 Double - click each html / xhtml content page to open and edit.

These additions do not affect the ability of an HTML5 User Agent [HTML5] to render XHTML Content Documents, but EPUB Publications might not render identically in all User Agents depending on their support.

An XML document that associates the XHTML Content Document with pre-recorded audio narration in order to provide a synchronized playback experience, as defined in [Media Overlays 3.1].

The following example shows a reference to an audio file in an XHTML Content Document that is located inside the EPUB Container.

If you wanted a table of contents to follow your cover image as the reader progressed through the book, for example, you had to include a separate XHTML content document in the spine.

The obvious way to include schema.org metadata is in XHTML content documents now that both RDFa and microdata attributes are in the soon - to - be-final 3.0.1 update.

By default, when you set an XHTML content document as pre-paginated, the dimensions of the page are obtained from the viewport property in the head of the document:

You can use them for EPUB 2 compliance (SVG with XHTML fallbacks, as SVG wasn't allowed in the spine previous), and even for script-less reading systems (fallback from an EPUB 3 - compliant XHTML content document marked as scripted to another EPUB 3 - compliant XHTML content document not marked as scripted).

The EPUB 3 XHTML Content Document definition includes both extensions to and restrictions on its HTML5 base, many of which are discussed below.

' As a conforming XHTML Content Document, it may be included in the Publication spine, but may also be provided independently of it.

Reading Systems must clip XHTML content to the initial containing block (ICB) dimensions declared in the viewport meta tag — content positioned outside of the initial containing block will not be visible.

This section defines a profile of [HTML5] for creating XHTML Content Documents.

' It must conform to all content conformance constraints for XHTML Content Documents as defined in XHTML Content Documents — Content Conformance.

It must use the dimensions expressed in the viewport meta tag to render XHTML Content Documents, as defined in Expressing the ICB in HTML.

The mathml property [Manifest Vocab] of the manifest item element indicates that an XHTML Content Document contains embedded MathML.

The following example shows two PLS Documents (one for Chinese and one for Mongolian) associated with an XHTML Content Document.

In the case of Publications that exclusively reference XHTML Content Documents from their spines, the toc nav will typically correspond to the aggregation of HTML5 outlines of those documents (excluding any subtrees that do not contribute to the primary Publication outline).

' Any included XHTML Content Document fragments must conform to the content model in which the ancestor m: math element occurs, such that if the m: math element is replaced by the given XHTML Content Document fragment the document remains valid.

' It must regard the mathml [Publications30] property of the Package Document manifest item element as the authoritative definition of whether an XHTML Content Document includes embedded MathML.

Note that all items have an appropriate media - type value and that the media type for the XHTML content is application / xhtml + xml.

A method for inflecting domain - specific semantics in XHTML Content Documents using attributes has been added.