From 5d7a4ce0d372c9fd07954e6fa76b6f13ada3fa5a Mon Sep 17 00:00:00 2001
From: Matt Garrish Whether a reading system has to support a feature is mentioned at the beginning of its section. To be
+ conformant with this specification, reading systems MUST support all required features as well as all
+ applicable conditionally-required features (e.g., to support image rendering if the reading system has a
+ [=viewport=]). When support for a feature is only recommended, reading system developers can typically ignore all the
+ normative statements in its section. In some cases, however, there may be alternative requirements when
+ not implementing a feature (e.g., to process fallbacks when
+ scripting is not supported). EPUB publications typically contain more information than there are support requirements for in this
+ specification (e.g., [=package document=] metadata). Reading systems may use this additional
+ information for any purposes (e.g., to improve the user interface). MUST support [[truetype]],
- [[opentype]], [[woff]], and [[woff2]] font resources referenced from
- Relationship to SVG
+ Reading system conformance
+
+ Publication resource processing
@@ -1152,8 +1171,8 @@ Cascading Style Sheets (CSS)
@font-face
rules
+ [[opentype]], [[woff]], and [[woff2]] font resources referenced from @font-face
rules
[[css-fonts-4]].Change log
>Working Group's issue tracker.
EPUB publications typically contain more information than there are support requirements for in this +
EPUB publications frequently contain information not required by this specification (e.g., [=package document=] metadata). Reading systems may use this additional information for any purposes (e.g., to improve the user interface).
Whether a reading system has to support a feature is mentioned at the beginning of its section. To be conformant with this specification, reading systems MUST support all required features as well as all - applicable conditionally-required features (e.g., to support image rendering if the reading system has a + applicable conditionally required features (e.g., to support image rendering if the reading system has a [=viewport=]).
When support for a feature is only recommended, reading system developers can typically ignore all the
From 886a6871c71a81b7daabbef8cb581d78615f31b3 Mon Sep 17 00:00:00 2001
From: Matt Garrish Whether a reading system has to support a feature is mentioned at the beginning of its section. To be
conformant with this specification, reading systems MUST support all required features as well as all
applicable conditionally-required features (e.g., to support image rendering if the reading system has a
- [=viewport=]).Reading system conformance
When support for a feature is only recommended, reading system developers can typically ignore all the - normative statements in its section. In some cases, however, there may be alternative requirements when - not implementing a feature (e.g., to process fallbacks when - scripting is not supported).
+When supporting recommended and optional features, reading systems MUST meet all normative requirements + as defined in their respective sections.
+ +When reading system developers opt not to support a recommended or optional feature, it does not always + mean none of the normative requirements of the section apply. In some cases, there may be alternative + requirements when not implementing a feature (e.g., to process + fallbacks when scripting is not supported). Reading systems MUST meet these alternative + requirements when not supporting a feature.
EPUB publications typically contain more information than there are support requirements for in this