Sentences with phrase «svg content»

be constructed from text - based XHTML or SVG Content Documents (i.e., text content is not represented as images);

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

An EPUB Content Document conforming to the constraints expressed in SVG Content Documents [ContentDocs301].

And once again, since only XHTML and SVG content documents are allowed in the spine without fallbacks, you either have to wrap the resource up as XHTML or SVG or provide a fallback.

An instance of an XML document that conforms to this profile is a Core Media Type and is referred to in this specification and its sibling specifications as an SVG Content Document.

An instance of an XML document that conforms to this profile is a Core Media Type Resource and is referred to in this specification as an SVG Content Document.

All Publication Resources referenced from an SVG Content Document must conform to the constraints for Publication Resources defined in EPUB Publication — Content Conformance [Publications30]

' It must be an SVG 1.1 document fragment valid to the SVG Content Document schema as defined in SVG Content Document Schema and conform to all content conformance constraints expressed in Restrictions on SVG 1.1.

The use of the epub: prefix attribute is only valid on the root svg element in SVG Content Documents.

An instance of the [SVG] script element included in an SVG Content Document that is embedded in a parent XHTML Content Document using the [HTML] iframe element.

This section defines conformance requirements for SVG Content Documents.

This specification defines a restricted subset of SVG 1.1 to represent vector graphics inline in XHTML Content Documents and as standalone SVG Content Documents.

This specification restricts the content model of SVG Content Documents and SVG embedded in XHTML Content Documents as follows:

SVG included by reference is processed as a separate document, and may include its own CSS style rules just like an SVG Content Document would.

Unless explicitly defined by this specification as overridden, it must process SVG Content Documents using semantics defined by the [SVG] specification and honor any applicable user agent conformance constraints expressed therein.

SVG included by reference is processed as a separate document, and can include its own CSS style rules just like an SVG Content Document would.

It must use the dimensions as defined in Expressing the ICB in SVG to render SVG Content Documents.

Publication Resources referenced from XHTML and SVG Content Documents and CSS must now be Core Media Types unless referenced in a context that provides native intrinsic fallback capabilities.

When synthetic spreads are used in the context of XHTML and SVG Content Documents, the dimensions given via viewport / viewBox metadata represents the size of one page in the spread.

For both XHTML and SVG Content Documents, the dimension (viewport / viewbox) expressions define the CSS initial containing block (ICB) expressed in CSS Pixels [CSS].

Note that this method of retrieving content dimensions only applies when bitmap images are referenced directly from the spine (i.e. not embedded in XHTML or SVG Content Documents).

This section defines rules for the expression and interpretation of dimensional properties of XHTML and SVG Content Documents [ContentDocs30] and bitmap images.

' It must process SVG Content Documents as defined in SVG Content Documents — Reading System Conformance [ContentDocs301].

A conformant EPUB Reading System must meet all of the following criteria for processing SVG Content Documents and SVG embedded in XHTML Content Documents:

Reading Systems must process SVG embedded in XHTML Content Documents as defined in SVG Content Documents — Reading System Conformance.

Not exact matches

For the purposes of styling SVG embedded in XHTML Content Documents by inclusion, Reading Systems must apply applicable CSS rules of the containing document to the included SVG elements.

For the purposes of styling SVG embedded in XHTML Content Documents by reference, Reading Systems must not apply CSS style rules of the containing document to the referenced SVG document.

Refer to Embedded SVG for conformance requirements for SVG embedded in XHTML Content Documents.

' The [SVG] svg: foreignObject element must contain only valid XHTML Content Document Flow content, and its requiredExtensions attribute, if given, must be set to http://www.idpf.org/2007/oSVG] svg: foreignObject element must contain only valid XHTML Content Document Flow content, and its requiredExtensions attribute, if given, must be set to http://www.idpf.org/2007/osvg: foreignObject element must contain only valid XHTML Content Document Flow content, and its requiredExtensions attribute, if given, must be set to http://www.idpf.org/20Content Document Flow content, and its requiredExtensions attribute, if given, must be set to http://www.idpf.org/20content, and its requiredExtensions attribute, if given, must be set to http://www.idpf.org/2007/ops.

EPUB Content Documents may contain scripting using the facilities defined for this in the respective underlying specifications -LRB-[HTML5] and [SVG]-RRB-.

XHTML Content Documents support the embedding of SVG 1.1 document fragments by reference (embedding via reference, for example, from an img or object element) and by inclusion (embedding via direct inclusion of the svg: svg element in the XHTML Content Document)[SVSVG 1.1 document fragments by reference (embedding via reference, for example, from an img or object element) and by inclusion (embedding via direct inclusion of the svg: svg element in the XHTML Content Document)[SVsvg: svg element in the XHTML Content Document)[SVsvg element in the XHTML Content Document)[SVGSVG].

SVGs are typically only used in certain special circumstances, such as when final - form page images are the only suitable representation of the content (e.g., in the context of manga or comic books).

This specification, EPUB Content Documents 3.0, defines profiles of HTML5, SVG, and CSS for use in the context of EPUB ® Publications.

EPUB defines a means of representing, packaging and encoding structured and semantically enhanced Web content — including XHTML, CSS, SVG, images, and other resources — for distribution in a single - file format.

XHTML Content Documents support the embedding of SVG document fragments by reference (embedding via reference, for example, from an img or object element) and by inclusion (embedding via direct inclusion of the svg element in the XHTML Content Document)[SVSVG document fragments by reference (embedding via reference, for example, from an img or object element) and by inclusion (embedding via direct inclusion of the svg element in the XHTML Content Document)[SVsvg element in the XHTML Content Document)[SVGSVG].

The recent update fixes several issues relating to missing content, improper width and height to render SVG images, incorrect top margin, etc. iPhone / iPad book opening issue is also addressed in the fixes.

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).

Internal (or relative) links — ones that don't start with a protocol like http: or https: — are expected to reference only EPUB content documents in the spine by default (the XHTML or SVG restriction I mentioned).

This content is built on the Open Web Platform and comes in two flavours: XHTML and SVG.

Content Switching allows you to include fallbacks for special content like MathML, JavaScript, and SVG that can help your file be read in older reading systems or in systems that have unique support for non-standard Content Switching allows you to include fallbacks for special content like MathML, JavaScript, and SVG that can help your file be read in older reading systems or in systems that have unique support for non-standard content like MathML, JavaScript, and SVG that can help your file be read in older reading systems or in systems that have unique support for non-standard markup.

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.

EPUB strives to treat content declaratively — as data that can be manipulated, not programs to be executed — but does support scripting as defined in HTML5 and SVG (refer to Scripted Content Documents [ContentDocs301] for more informcontent declaratively — as data that can be manipulated, not programs to be executed — but does support scripting as defined in HTML5 and SVG (refer to Scripted Content Documents [ContentDocs301] for more informContent Documents [ContentDocs301] for more information).

EPUB Content Documents 3.0.1 [ContentDocs301], which defines profiles of XHTML, SVG and CSS for use in the context of EPUB Publications.

A Publication Resource that conforms to one of the EPUB Content Document definitions (XHTML or SVG).

Foreign Resources may be included in an EPUB Publication without a fallback provided they are not referenced from spine itemref elements [Packages 3.1] or directly rendered in their native format in EPUB Content Documents (e.g., via [HTML] embedded content and [SVG] image and foreignObject eleContent Documents (e.g., via [HTML] embedded content and [SVG] image and foreignObject elecontent and [SVG] image and foreignObject elements).

A Publication Resource that conforms to one of the EPUB Content Document definitions (HTML or SVG).

These are XHTML or SVG documents that describe the readable content and reference associated media resources (e.g., images, audio and video clips).

EPUB strives to treat content declaratively — as data that can be manipulated, not programs to be executed — but does support scripting as defined in [HTML] and [SVG](refer to Scripting [Content Docs 3.1] for more informcontent declaratively — as data that can be manipulated, not programs to be executed — but does support scripting as defined in [HTML] and [SVG](refer to Scripting [Content Docs 3.1] for more informContent Docs 3.1] for more information).

It also defines mechanisms to express the intended rendering dimensions of fixed - layout XHTML and SVG [ContentDocs30] content, as well as bitmap images.

The specification can not guarantee that the Distributable Object will pass validation in this state, however, as the entities that compose the Distributable Object might not constitute valid Content Documents on their own (e.g., shared SVG components, or fragments of HTML not valid as body markup).