--- a/ttml-ww-profiles/ttml-ww-profiles.html Fri Aug 01 12:24:20 2014 +0200
+++ b/ttml-ww-profiles/ttml-ww-profiles.html Sat Aug 02 10:31:33 2014 +0200
@@ -217,11 +217,11 @@
</p>
<h1 class="title p-name" id="title" property="dcterms:title">TTML Text and Image Profiles for Internet Media Subtitles and Captions 1.0</h1>
- <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-08-01T08:21:15.000Z" id="w3c-first-public-working-draft-01-august-2014"><abbr title="World Wide Web Consortium">W3C</abbr> First Public Working Draft <time class="dt-published" datetime="2014-08-01">01 August 2014</time></h2>
+ <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-08-02T06:30:29.000Z" id="w3c-first-public-working-draft-02-august-2014"><abbr title="World Wide Web Consortium">W3C</abbr> First Public Working Draft <time class="dt-published" datetime="2014-08-02">02 August 2014</time></h2>
<dl>
<dt>This version:</dt>
- <dd><a class="u-url" href="http://www.w3.org/TR/2014/WD-ttml-imsc1-20140801/">http://www.w3.org/TR/2014/WD-ttml-imsc1-20140801/</a></dd>
+ <dd><a class="u-url" href="http://www.w3.org/TR/2014/WD-ttml-imsc1-20140802/">http://www.w3.org/TR/2014/WD-ttml-imsc1-20140802/</a></dd>
<dt>Latest published version:</dt>
<dd><a href="http://www.w3.org/TR/ttml-imsc1/">http://www.w3.org/TR/ttml-imsc1/</a></dd>
@@ -356,19 +356,13 @@
<p>The text-only profile is a strict superset of [<cite><a class="bibref" href="#bib-SDPUS">SDPUS</a></cite>] and the image-only profile uses extensions specified in
[<cite><a class="bibref" href="#bib-ST2052-1">ST2052-1</a></cite>].</p>
</section>
-
- <section id="terms" typeof="bibo:Chapter" resource="#terms" rel="bibo:Chapter">
+
+ <section id="terms" typeof="bibo:Chapter" resource="#terms" rel="bibo:Chapter">
<!--OddPage--><h2 aria-level="1" role="heading" id="h2_terms"><span class="secno">2. </span>Terms and Definitions</h2>
- <p>
- <dfn id="dfn-presentation-processor">Presentation processor</dfn>. See Section 2.2 at [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>].
- </p>
-
-
- <p>
- <dfn id="dfn-transformation-processor">Transformation processor</dfn>. See Section 2.2 at [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>].
- </p>
-
+ <p><dfn id="dfn-presentation-processor">Presentation processor</dfn>. See Section 2.2 at [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>].</p>
+
+ <p><dfn id="dfn-transformation-processor">Transformation processor</dfn>. See Section 2.2 at [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>].</p>
</section>
<section id="conformance" typeof="bibo:Chapter" resource="#conformance" rel="bibo:Chapter"><!--OddPage--><h2 aria-level="1" role="heading" id="h2_conformance"><span class="secno">3. </span>Conformance</h2>
@@ -388,6 +382,8 @@
<p>A <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> that conforms to a profile defined in this specification <em class="rfc2119" title="SHALL">SHALL</em>:</p>
<ul>
+ <li>satisfy the Generic Processor Conformance requirements at Section 3.2.1 of [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>];</li>
+
<li>satisfy all normative provisions specified by the profile; and</li>
<li>be capable of presenting any subtitle document that conforms to the profile, i.e. if it implements all features and
@@ -397,12 +393,18 @@
<p>A <a href="#dfn-transformation-processor" class="internalDFN">transformation processor</a> that conforms to a profile defined in this specification <em class="rfc2119" title="SHALL">SHALL</em>:</p>
<ul>
+ <li>satisfy the Generic Processor Conformance requirements at Section 3.2.1 of [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>];</li>
+
<li>satisfy all normative provisions specified by the profile; and</li>
<li>be capable of transforming any subtitle document that conforms to the profile, i.e. if it implements all features and
provisions of the profile.</li>
</ul>
-
+
+ <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_1"><span>Note</span></div><p class="">The use of the terms <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> (<a href="#dfn-transformation-processor" class="internalDFN">transformation processor</a>) do not imply conformance
+ to the DFXP Transformation Profile (DFXP Transformation Profile) specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>]. In other words, it is not considered
+ an error for a presentation processor (transformation processor) to conform to a profile defined in this specification without
+ also conforming to the DFXP Transformation Profile (DFXP Transformation Profile).</p></div>
</section>
<section id="profiles" typeof="bibo:Chapter" resource="#profiles" rel="bibo:Chapter">
@@ -418,7 +420,7 @@
offered. In addition, the Text Profile subtitle document <em class="rfc2119" title="SHOULD">SHOULD</em> be associated with the Image Profile subtitle document such
that, when image content is encountered, assistive technologies have access to its corresponding text form.</p>
- <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_1"><span>Note</span></div><p class="">The <code>ittm:altText</code> element specified <a href="#ttm-altText" class="sec-ref"><span class="secno">5.5.4</span> <span class="sec-title">ittm:altText</span></a> also allows text equivalent
+ <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_2"><span>Note</span></div><p class="">The <code>ittm:altText</code> element specified <a href="#ttm-altText" class="sec-ref"><span class="secno">5.5.4</span> <span class="sec-title">ittm:altText</span></a> also allows text equivalent
string to be associated with an image, e.g. to support indexation of the content and also facilitate quality checking of the
document during authoring.</p></div>
@@ -597,15 +599,15 @@
on a specific frame of the related video object.</p>
<p>When mapping a media time expression M to a frame F of a related video object, e.g. for the purpose of rendering a
- subtitle document onto the related video object, the <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> <em class="rfc2119" title="SHALL">SHALL</em> map M to the frame F with the presentation
- time that is the closest to, but not less, than M.</p>
+ subtitle document onto the related video object, the <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> <em class="rfc2119" title="SHALL">SHALL</em> map M to the frame F with the
+ presentation time that is the closest to, but not less, than M.</p>
<aside class="example"><div class="example-title"><span>Example 1</span></div>
A media time expression of 00:00:05.1 corresponds to frame ceiling(5.1 × ( 1000 / 1001 × 30) = 153 of a related video
object with a frame rate of 1000 / 1001 × 30 ≈ 29.97.
</aside>
- <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_2"><span>Note</span></div><p class="">In typical scenario, the same video program (the related video object) will be used for subtitle document
+ <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_3"><span>Note</span></div><p class="">In typical scenario, the same video program (the related video object) will be used for subtitle document
authoring, delivery and user playback. The mapping from media time expression to related video object above allows the author
to precisely associate subtitle video content with video frames, e.g. around scene transitions. In circumstances where the
video program is downsampled during delivery, the application can specify that, at playback, the relative video object be
@@ -615,7 +617,7 @@
<p>If <code>ttp:frameRate</code> is specified, then the product of <code>ttp:frameRate</code> and
<code>ttp:frameRateMultiplier</code> <em class="rfc2119" title="SHALL">SHALL</em> be the frame rate of the related video object.</p>
- <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_3"><span>Note</span></div><p class="">A document can be made independent of the frame rate of the related video object by never using the
+ <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_4"><span>Note</span></div><p class="">A document can be made independent of the frame rate of the related video object by never using the
<em>frames</em> term in a time expression: as specified in <a href="#common-features" class="sec-ref"><span class="secno">5.8</span> <span class="sec-title">Features</span></a>, <code>ttp:frameRate</code> is
required only if the document includes one or more time expressions that uses the <em>frames</em> term.</p></div>
</section>
@@ -658,7 +660,7 @@
<p><code>ittp:aspectRatio</code> <em class="rfc2119" title="SHALL NOT">SHALL NOT</em> be present if <code>tts:extent</code> is present.<br></p>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_4"><span>Note</span></div><p class="">As specified in Section <a href="#common-features" class="sec-ref"><span class="secno">5.8</span> <span class="sec-title">Features</span></a>, <code>tts:extent</code> is present if the
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_5"><span>Note</span></div><p class="">As specified in Section <a href="#common-features" class="sec-ref"><span class="secno">5.8</span> <span class="sec-title">Features</span></a>, <code>tts:extent</code> is present if the
<code>px</code> length measure is used anywhere within the document.</p></div>
<p>Integer pixel positions on the related video object frame computed from real percentage length values <em class="rfc2119" title="SHALL">SHALL</em> use half-up
@@ -701,15 +703,14 @@
<p>The initial value of <code>ittp:progressivelyDecodable</code> shall be "false".</p>
- <p>A <code>ittp:progressivelyDecodable</code> attribute with value "false" may be present on the <code>tt</code>
- element if the subtitle document is not a progressively decodable subtitle document.</p>
+ <p>A <code>ittp:progressivelyDecodable</code> attribute with value "false" may be present on the <code>tt</code> element if
+ the subtitle document is not a progressively decodable subtitle document.</p>
<p>A <code>ittp:progressivelyDecodable</code> attribute is considered to be significant only when specified on the
<code>tt</code> element.</p>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_5"><span>Note</span></div><p class="">The placement and use of <code>div</code>, <code>region</code> and <code>span</code> that contain time
- attributes, and the use of <code>set</code> are constrained when <code>ittp:progressivelyDecodable="true"</code>
- .</p></div>
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_6"><span>Note</span></div><p class="">The placement and use of <code>div</code>, <code>region</code> and <code>span</code> that contain time
+ attributes, and the use of <code>set</code> are constrained when <code>ittp:progressivelyDecodable="true"</code> .</p></div>
</section>
<section id="tts-forcedDisplay" typeof="bibo:Chapter" resource="#tts-forcedDisplay" rel="bibo:Chapter">
@@ -718,10 +719,9 @@
<p><code>itts:forcedDisplay</code> allows the processor to override the computed value of <code>tts:visibility</code>
attribute in conjunction with an application parameter <code>displayForcedOnlyMode</code>.</p>
- <p>If the value of <code>displayForcedOnlyMode</code> is "true", a content element with a
- <code>itts:forcedDisplay</code> computed value of "false" shall be assumed to have a <code>tts:visibility</code>
- computed value equal to "hidden", even if <code>tts:visibility</code> would otherwise be computed to
- "true".</p>
+ <p>If the value of <code>displayForcedOnlyMode</code> is "true", a content element with a <code>itts:forcedDisplay</code>
+ computed value of "false" <em class="rfc2119" title="SHALL">SHALL</em> not produce any visible rendering, but still affect layout, regardless of the computed
+ value of <code>tts:visibility</code>.</p>
<table class="simple">
<colgroup>
@@ -773,19 +773,25 @@
<code>itts:forcedDisplay</code> to display translation subtitles always, independently of whether the hard of hearing
captions are displayed or hidden.</p>
- <p>The <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> <em class="rfc2119" title="SHALL">SHALL</em> accept an optional boolean parameter called <code>displayForcedOnlyMode</code>, whose
- value <em class="rfc2119" title="MAY">MAY</em> be set by a context external to the <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a>. If not set, the value of
+ <p>The <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> <em class="rfc2119" title="SHALL">SHALL</em> accept an optional boolean parameter called <code>displayForcedOnlyMode</code>,
+ whose value <em class="rfc2119" title="MAY">MAY</em> be set by a context external to the <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a>. If not set, the value of
<code>displayForcedOnlyMode</code> <em class="rfc2119" title="SHALL">SHALL</em> be assumed to be equal to "false".</p>
<p>The algorithm for setting the <code>displayForcedOnlyMode</code> parameter based on the circumstances under which the
subtitle document is presented is left to the application.</p>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_6"><span>Note</span></div><p class="">Although <code>itts:forcedDisplay</code>, like all the TTML style attributes, has no defined semantics on a
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_7"><span>Note</span></div><p class="">The background of a region is drawn even if the computed value of <code>tts:visibility</code> equals
+ "hidden" for all active content within. This can occur if <code>itts:forcedDisplay</code> equals "false" for all active
+ content elements within a region for which <code>itts:forcedDisplay</code> equals "true", and
+ <code>displayForcedOnlyMode</code> equals "true". Authors can avoid this situation, for instance, by ensuring that content
+ elements and the regions that they are flowed into always have the same value of <code>itts:forcedDisplay</code>.</p></div>
+
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_8"><span>Note</span></div><p class="">Although <code>itts:forcedDisplay</code>, like all the TTML style attributes, has no defined semantics on a
<code>br</code> content element, <code>itts:forcedDisplay</code> will apply to a <code>br</code> content element if it is
either defined on an ancestor content element of the <code>br</code> content element or it is applied to a region element
corresponding to a region that the <code>br</code> content element is being flowed into.</p></div>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_7"><span>Note</span></div><p class="">It is expected that the functionality of <code>itts:forcedDisplay</code> will be mapped to a conditional
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_9"><span>Note</span></div><p class="">It is expected that the functionality of <code>itts:forcedDisplay</code> will be mapped to a conditional
style construct in a future revision of this specification.</p></div>
</section>
@@ -819,7 +825,7 @@
<p><a href="#image-profile-constraints" class="sec-ref"><span class="secno">7.</span> <span class="sec-title">Image Profile Constraints</span></a> specifies the use of the <code>ittm:altText</code> element with images.</p>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_8"><span>Note</span></div><p class="">In contrast to the common use of <code>alt</code> attributes in [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>], the <code>ittm:altText</code>
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_10"><span>Note</span></div><p class="">In contrast to the common use of <code>alt</code> attributes in [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>], the <code>ittm:altText</code>
attribute content is not intended to be displayed in place of the element if the element is not loaded. The
<code>ittm:altText</code> attribute content can however be read and used by assistive technologies. .</p></div>
</section>
@@ -843,14 +849,12 @@
</li>
<li>
- <p>content is selected into the region or <code>tts:showBackground</code> is equal to "always" for the
- region.</p>
+ <p>content is selected into the region or <code>tts:showBackground</code> is equal to "always" for the region.</p>
</li>
</ol>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_9"><span>Note</span></div><p class="">As specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], the initial value of <code>tts:opacity</code> is "1.0", the initial
- value of <code>tts:showBackground</code> is "always", and the initial value of <code>tts:display</code> is
- "auto"</p></div>
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_11"><span>Note</span></div><p class="">As specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], the initial value of <code>tts:opacity</code> is "1.0", the initial value of
+ <code>tts:showBackground</code> is "always", and the initial value of <code>tts:display</code> is "auto"</p></div>
</section>
<section id="dimensions-and-position">
@@ -1320,7 +1324,7 @@
</tbody>
</table>
- <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_10"><span>Note</span></div><p class="">As specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], a <code>#time-offset-with-frames</code> expression is translated to a media time
+ <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_12"><span>Note</span></div><p class="">As specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], a <code>#time-offset-with-frames</code> expression is translated to a media time
M according to M = 3600 · hours + 60 · minutes + seconds + (frames ÷ (<code>ttp:frameRateMultiplier</code> ·
<code>ttp:frameRate</code>)).</p></div>
</section>
@@ -1422,8 +1426,8 @@
<tr>
<td><code>#displayAlign</code></td>
- <td><em class="rfc2119" title="MAY">MAY</em> be used. The initial value of <code>tts:displayAlign</code> <em class="rfc2119" title="SHALL">SHALL</em> be "after" for the default region.
- NOTE: This is consistent with [<cite><a class="bibref" href="#bib-ST2052-1">ST2052-1</a></cite>].</td>
+ <td><em class="rfc2119" title="MAY">MAY</em> be used. The initial value of <code>tts:displayAlign</code> <em class="rfc2119" title="SHALL">SHALL</em> be "after" for the default region. NOTE: This
+ is consistent with [<cite><a class="bibref" href="#bib-ST2052-1">ST2052-1</a></cite>].</td>
</tr>
<tr>
@@ -1436,9 +1440,8 @@
<tr>
<td><code>#fontFamily-generic</code></td>
- <td><em class="rfc2119" title="MAY">MAY</em> be used. A <code>tts:fontFamily</code> of either "monospaceSerif" or
- "proportionalSansSerif" <em class="rfc2119" title="SHOULD">SHOULD</em> be specified for all presented text content. A tts:fontFamily of
- "default" <em class="rfc2119" title="SHALL">SHALL</em> be equivalent to "monospaceSerif".</td>
+ <td><em class="rfc2119" title="MAY">MAY</em> be used. A <code>tts:fontFamily</code> of either "monospaceSerif" or "proportionalSansSerif" <em class="rfc2119" title="SHOULD">SHOULD</em> be
+ specified for all presented text content. A tts:fontFamily of "default" <em class="rfc2119" title="SHALL">SHALL</em> be equivalent to "monospaceSerif".</td>
</tr>
<tr>
@@ -1517,8 +1520,8 @@
<td><code>#lineHeight</code></td>
<td><em class="rfc2119" title="MAY">MAY</em> be used.<br>
- An explicit <code><length></code> <em class="rfc2119" title="SHOULD">SHOULD</em> be specified as there is no uniform implementation of the
- "normal" value at the time of this writing.</td>
+ An explicit <code><length></code> <em class="rfc2119" title="SHOULD">SHOULD</em> be specified as there is no uniform implementation of the "normal" value
+ at the time of this writing.</td>
</tr>
<tr>
@@ -1536,8 +1539,8 @@
<tr>
<td><code>#origin</code></td>
- <td>The <code>tts:origin</code> attribute <em class="rfc2119" title="SHALL">SHALL</em> use <code>px</code> units or "percentage" representation, and
- <em class="rfc2119" title="SHALL NOT">SHALL NOT</em> use <code>em</code> units.</td>
+ <td>The <code>tts:origin</code> attribute <em class="rfc2119" title="SHALL">SHALL</em> use <code>px</code> units or "percentage" representation, and <em class="rfc2119" title="SHALL NOT">SHALL NOT</em>
+ use <code>em</code> units.</td>
</tr>
<tr>
@@ -1585,8 +1588,8 @@
<tr>
<td><code>#textAlign</code></td>
- <td><em class="rfc2119" title="MAY">MAY</em> be used. The initial value of <code>tts:textAlign</code> <em class="rfc2119" title="SHALL">SHALL</em> be "center" for the default region.
- NOTE: This is consistent with [<cite><a class="bibref" href="#bib-ST2052-1">ST2052-1</a></cite>].</td>
+ <td><em class="rfc2119" title="MAY">MAY</em> be used. The initial value of <code>tts:textAlign</code> <em class="rfc2119" title="SHALL">SHALL</em> be "center" for the default region. NOTE: This
+ is consistent with [<cite><a class="bibref" href="#bib-ST2052-1">ST2052-1</a></cite>].</td>
</tr>
<tr>
@@ -1914,9 +1917,8 @@
<p>The model operates on successive intermediate synchronic documents obtained from an input subtitle document, and uses a
simple double buffering model: while an intermediate synchronic document E<sub>n</sub> is being painted into Presentation
- Buffer P<sub>n</sub> (the "front buffer" of the model), the previous intermediate synchronic document
- E<sub>n-1</sub> is available for display in Presentation Buffer P<sub>n-1</sub> (the "back buffer" of the
- model).</p>
+ Buffer P<sub>n</sub> (the "front buffer" of the model), the previous intermediate synchronic document E<sub>n-1</sub> is
+ available for display in Presentation Buffer P<sub>n-1</sub> (the "back buffer" of the model).</p>
<p>The model specifies an (hypothetical) time required for completely painting an intermediate synchronic document as a
proxy for complexity. Painting includes drawing region backgrounds, rendering and copying glyphs, and decoding and copying
@@ -1987,7 +1989,7 @@
P<sub>n-1</sub> at the presentation time of intermediate synchronic document E<sub>n</sub>, making the latter available for
display.</p>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_11"><span>Note</span></div><p class="">It is possible for the contents of Presentation Buffer P<sub>n-1</sub> to never be displayed. This can
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_13"><span>Note</span></div><p class="">It is possible for the contents of Presentation Buffer P<sub>n-1</sub> to never be displayed. This can
happen if Presentation Buffer P<sub>n</sub> is copied twice to Presentation Buffer P<sub>n-1</sub> between two consecutive
video frame boundaries of the related video object.</p></div>
@@ -2020,11 +2022,11 @@
</tbody>
</table>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_12"><span>Note</span></div><p class="">BDraw effectively sets a limit on fillings regions - for example, assuming that the root container is
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_14"><span>Note</span></div><p class="">BDraw effectively sets a limit on fillings regions - for example, assuming that the root container is
ultimately rendered at 1920×1080 resolution, a BDraw of 12 s<sup>-1</sup> would correspond to a fill rate of
1920×1080×12/s=23.7×2<sup>20</sup>pixels s<sup>-1</sup>.</p></div>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_13"><span>Note</span></div><p class="">IPD effectively sets a limit on the complexity of any given intermediate synchronic document.</p></div>
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_15"><span>Note</span></div><p class="">IPD effectively sets a limit on the complexity of any given intermediate synchronic document.</p></div>
</section>
<section id="paint-regions" typeof="bibo:Chapter" resource="#paint-regions" rel="bibo:Chapter">
@@ -2036,7 +2038,7 @@
<p>where CLEAR(E<sub>0</sub>) = 0 and CLEAR(E<sub>n | n > 0</sub>) = 1, i.e. the root container in its entirety.</p>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_14"><span>Note</span></div><p class="">To ensure consistency of the Presentation Buffer, a new intermediate synchronic document requires clearing
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_16"><span>Note</span></div><p class="">To ensure consistency of the Presentation Buffer, a new intermediate synchronic document requires clearing
of the root container.</p></div>
<p>PAINT(E<sub>n</sub>) <em class="rfc2119" title="SHALL">SHALL</em> be the normalized area to be painted for all regions that are used in intermediate synchronic
@@ -2287,15 +2289,15 @@
</tbody>
</table>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_15"><span>Note</span></div><p class="">NRGA(G<sub>i</sub>) does not take into account glyph decorations (e.g. underline), glyph effects (e.g.
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_17"><span>Note</span></div><p class="">NRGA(G<sub>i</sub>) does not take into account glyph decorations (e.g. underline), glyph effects (e.g.
outline) or actual glyph aspect ratio. An implementation can determine an actual buffer size needs based on worst-case
glyph size complexity.</p></div>
<aside class="example"><div class="example-title"><span>Example 3</span></div>
Setting a Glyph Buffer Normalized Size effectively sets a limit on the total number of distinct glyphs present in any
given intermediate synchronic document E<sub>n</sub>. For example, assuming a maximum Normalized Glyph Buffer Size of 1
- and the default tts:fontSize of 1c are used, the glyph's height as percentage of root container height is 1/15 , and
- the maximum number of distinct glyphs that can be buffered is 1÷(1÷15)^2=225 glyphs. In this example, an implementation
+ and the default tts:fontSize of 1c are used, the glyph's height as percentage of root container height is 1/15 , and the
+ maximum number of distinct glyphs that can be buffered is 1÷(1÷15)^2=225 glyphs. In this example, an implementation
rendering at 1920x1080 would need to allocate a glyph buffer no smaller than (1920÷32)×(1080÷15)×225=~1 Mpixels.
</aside>
@@ -2368,10 +2370,10 @@
</tbody>
</table>
- <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_16"><span>Note</span></div><p class="">Implementations can use use fonts other than those specified above. Two fonts with equal metrics can have a
+ <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_18"><span>Note</span></div><p class="">Implementations can use use fonts other than those specified above. Two fonts with equal metrics can have a
different appearance, but flow identically.</p></div>
- <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_17"><span>Note</span></div><p class="">proportionalSansSerif is not used in practice for Hebrew and Arabic captions and subtitles.</p></div>
+ <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_19"><span>Note</span></div><p class="">proportionalSansSerif is not used in practice for Hebrew and Arabic captions and subtitles.</p></div>
</section>
</section>
@@ -2719,9 +2721,8 @@
<p><a href="#fig-forced-content" class="fig-ref">Fig. <span class="figno">3</span> <span class="fig-title">
Illustration of the use of itts:forcedDisplay
</span></a> below illustrates the use of forced content, i.e. <code>itts:forcedDisplay</code> and
- <code>displayForcedOnlyMode</code>. The content with <code>itts:forcedDisplay</code>="true" is the French translation
- of the "High School" sign. The content with <code>itts:forcedDisplay</code>="false" are French subtitles
- capturing a voiceover.</p>
+ <code>displayForcedOnlyMode</code>. The content with <code>itts:forcedDisplay</code>="true" is the French translation of the
+ "High School" sign. The content with <code>itts:forcedDisplay</code>="false" are French subtitles capturing a voiceover.</p>
<figure id="fig-forced-content">
<img src="forced-example-figure-1.png" alt="Illustration of the use of itts:forcedDisplay">
@@ -2732,12 +2733,12 @@
</figure>
<p>When the user selects French as the playback language but does not select French subtitles,
- <code>displayForcedOnlyMode</code> is set to "true", causing the display of the sign translation, which is useful to
- any French speaker, but hiding the voiceover subtitles as the voiceover is heard in French.</p>
+ <code>displayForcedOnlyMode</code> is set to "true", causing the display of the sign translation, which is useful to any French
+ speaker, but hiding the voiceover subtitles as the voiceover is heard in French.</p>
<p>If the user selects French as the playback language and also selects French subtitles, e.g. if the user is hard-of-hearing,
- <code>displayForcedOnlyMode</code> is set to "false", causing the display of both the sign translation and the
- voiceover subtitles.</p>
+ <code>displayForcedOnlyMode</code> is set to "false", causing the display of both the sign translation and the voiceover
+ subtitles.</p>
<p>The algorithm for setting the <code>displayForcedOnlyMode</code> parameter and selecting the appropriate combination of
subtitle and audio tracks depends on the application.</p>
@@ -2762,15 +2763,14 @@
<p>For instance, in subtitling and captioning, italics can be used to indicate an off screen speaker context (for example a
voice from a radio). An author can choose to include this functional information in the text equivalent; for example, by
- including the word "Radio: " before the image equivalent text. It should also be noted that images in an Image
- Profile subtitle document that are intended for use as <em>captions</em>, i.e. intended for a hard of hearing audience, might
- already include this functional information in the rendered text.</p>
-
- <p>Guideline 1.1 of [<cite><a class="bibref" href="#bib-WCAG20">WCAG20</a></cite>] also recommends that accessible text alternatives must be "programmatically
- determinable." This means that the text must be able to be read and used by the assistive technologies (and the
- accessibility features in browsers) that people with disabilities use. It also means that the user must be able to use their
- assistive technology to find the alternative text (that they can use) when they land on the non-text content (that they
- can't use).</p>
+ including the word "Radio: " before the image equivalent text. It should also be noted that images in an Image Profile subtitle
+ document that are intended for use as <em>captions</em>, i.e. intended for a hard of hearing audience, might already include
+ this functional information in the rendered text.</p>
+
+ <p>Guideline 1.1 of [<cite><a class="bibref" href="#bib-WCAG20">WCAG20</a></cite>] also recommends that accessible text alternatives must be "programmatically determinable." This
+ means that the text must be able to be read and used by the assistive technologies (and the accessibility features in browsers)
+ that people with disabilities use. It also means that the user must be able to use their assistive technology to find the
+ alternative text (that they can use) when they land on the non-text content (that they can't use).</p>
</section>
<section class="appendix" id="features-and-extensions" typeof="bibo:Chapter" resource="#features-and-extensions" rel="bibo:Chapter">
@@ -2786,21 +2786,22 @@
<section class="appendix" id="progressivelydecodable">
<h3 aria-level="2" role="heading" id="h3_progressivelydecodable"><span class="secno">D.2 </span>#progressivelyDecodable</h3>
- <p>A <a href="#dfn-transformation-processor" class="internalDFN">transformation processor</a> supports the <code>#progressivelyDecodable</code> feature if it recognizes and is capable of
- transforming values of the <a href="#ttp-progressivelyDecodable"><code>ittp:progressivelyDecodable</code></a>.</p>
-
- <p>A <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> supports the <code>#progressivelyDecodable</code> feature if it implements presentation semantic
- support for values of the <a href="#ttp-progressivelyDecodable"><code>ittp:progressivelyDecodable</code></a> attribute.</p>
+ <p>A <a href="#dfn-transformation-processor" class="internalDFN">transformation processor</a> supports the <code>#progressivelyDecodable</code> feature if it recognizes and is
+ capable of transforming values of the <a href="#ttp-progressivelyDecodable"><code>ittp:progressivelyDecodable</code></a>.</p>
+
+ <p>A <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> supports the <code>#progressivelyDecodable</code> feature if it implements presentation
+ semantic support for values of the <a href="#ttp-progressivelyDecodable"><code>ittp:progressivelyDecodable</code></a>
+ attribute.</p>
</section>
<section class="appendix" id="aspectratio">
<h3 aria-level="2" role="heading" id="h3_aspectratio"><span class="secno">D.3 </span>#aspectRatio</h3>
- <p>A <a href="#dfn-transformation-processor" class="internalDFN">transformation processor</a> supports the <code>#aspectRatio</code> feature if it recognizes and is capable of transforming
- values of the <a href="#ttp-aspectRatio"><code>ittp:aspectRatio</code></a>.</p>
-
- <p>A <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> supports the <code>#aspectRatio</code> feature if it implements presentation semantic support for
- values of the <a href="#ttp-aspectRatio"><code>ittp:aspectRatio</code></a> attribute.</p>
+ <p>A <a href="#dfn-transformation-processor" class="internalDFN">transformation processor</a> supports the <code>#aspectRatio</code> feature if it recognizes and is capable of
+ transforming values of the <a href="#ttp-aspectRatio"><code>ittp:aspectRatio</code></a>.</p>
+
+ <p>A <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> supports the <code>#aspectRatio</code> feature if it implements presentation semantic
+ support for values of the <a href="#ttp-aspectRatio"><code>ittp:aspectRatio</code></a> attribute.</p>
</section>
<section class="appendix" id="forceddisplay">
@@ -2809,18 +2810,18 @@
<p>A <a href="#dfn-transformation-processor" class="internalDFN">transformation processor</a> supports the <code>#forcedDisplay</code> feature if it recognizes and is capable of
transforming values of the <a href="#tts-forcedDisplay"><code>itts:forcedDisplay</code></a>.</p>
- <p>A <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> supports the <code>#forcedDisplay</code> feature if it implements presentation semantic support
- for values of the <a href="#tts-forcedDisplay"><code>itts:forcedDisplay</code></a> attribute.</p>
+ <p>A <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> supports the <code>#forcedDisplay</code> feature if it implements presentation semantic
+ support for values of the <a href="#tts-forcedDisplay"><code>itts:forcedDisplay</code></a> attribute.</p>
</section>
<section class="appendix" id="alttext">
<h3 aria-level="2" role="heading" id="h3_alttext"><span class="secno">D.5 </span>#altText</h3>
- <p>A <a href="#dfn-transformation-processor" class="internalDFN">transformation processor</a> supports the <code>#altText</code> feature if it recognizes and is capable of transforming
- values of the <a href="#ttm-altText"><code>ittm:altText</code></a> element.</p>
-
- <p>A <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> supports the <code>#altText</code> feature if it implements presentation semantic support for
- values of the <a href="#ttm-altText"><code>ittm:altText</code></a> element.</p>
+ <p>A <a href="#dfn-transformation-processor" class="internalDFN">transformation processor</a> supports the <code>#altText</code> feature if it recognizes and is capable of
+ transforming values of the <a href="#ttm-altText"><code>ittm:altText</code></a> element.</p>
+
+ <p>A <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> supports the <code>#altText</code> feature if it implements presentation semantic support
+ for values of the <a href="#ttm-altText"><code>ittm:altText</code></a> element.</p>
</section>
</section>
--- a/ttml-ww-profiles/ttml-ww-profiles.source.html Fri Aug 01 12:24:20 2014 +0200
+++ b/ttml-ww-profiles/ttml-ww-profiles.source.html Sat Aug 02 10:31:33 2014 +0200
@@ -70,19 +70,13 @@
<p>The text-only profile is a strict superset of [[SDPUS]] and the image-only profile uses extensions specified in
[[!ST2052-1]].</p>
</section>
-
- <section id='terms'>
+
+ <section id='terms'>
<h2>Terms and Definitions</h2>
- <p>
- <dfn>Presentation processor</dfn>. See Section 2.2 at [[!TTML1]].
- </p>
-
-
- <p>
- <dfn>Transformation processor</dfn>. See Section 2.2 at [[!TTML1]].
- </p>
-
+ <p><dfn>Presentation processor</dfn>. See Section 2.2 at [[!TTML1]].</p>
+
+ <p><dfn>Transformation processor</dfn>. See Section 2.2 at [[!TTML1]].</p>
</section>
<section id="conformance">
@@ -92,6 +86,8 @@
<p>A <a>presentation processor</a> that conforms to a profile defined in this specification SHALL:</p>
<ul>
+ <li>satisfy the Generic Processor Conformance requirements at Section 3.2.1 of [[!TTML1]];</li>
+
<li>satisfy all normative provisions specified by the profile; and</li>
<li>be capable of presenting any subtitle document that conforms to the profile, i.e. if it implements all features and
@@ -101,12 +97,18 @@
<p>A <a>transformation processor</a> that conforms to a profile defined in this specification SHALL:</p>
<ul>
+ <li>satisfy the Generic Processor Conformance requirements at Section 3.2.1 of [[!TTML1]];</li>
+
<li>satisfy all normative provisions specified by the profile; and</li>
<li>be capable of transforming any subtitle document that conforms to the profile, i.e. if it implements all features and
provisions of the profile.</li>
</ul>
-
+
+ <p class='note'>The use of the terms <a>presentation processor</a> (<a>transformation processor</a>) do not imply conformance
+ to the DFXP Transformation Profile (DFXP Transformation Profile) specified in [[!TTML1]]. In other words, it is not considered
+ an error for a presentation processor (transformation processor) to conform to a profile defined in this specification without
+ also conforming to the DFXP Transformation Profile (DFXP Transformation Profile).</p>
</section>
<section id='profiles'>
@@ -302,8 +304,8 @@
on a specific frame of the related video object.</p>
<p>When mapping a media time expression M to a frame F of a related video object, e.g. for the purpose of rendering a
- subtitle document onto the related video object, the <a>presentation processor</a> SHALL map M to the frame F with the presentation
- time that is the closest to, but not less, than M.</p>
+ subtitle document onto the related video object, the <a>presentation processor</a> SHALL map M to the frame F with the
+ presentation time that is the closest to, but not less, than M.</p>
<aside class="example">
A media time expression of 00:00:05.1 corresponds to frame ceiling(5.1 × ( 1000 / 1001 × 30) = 153 of a related video
@@ -383,7 +385,7 @@
<li>no element references another element (i) occurring later in the document or (ii) with a later begin time; and</li>
- <li>a <code>ittp:progressivelyDecodable</code> attribute with value "true" is present on the <code>tt</code>
+ <li>a <code>ittp:progressivelyDecodable</code> attribute with value "true" is present on the <code>tt</code>
element.</li>
</ol>
@@ -396,8 +398,8 @@
<div class="exampleInner">
<pre>
imsc:progressivelyDecodable
- : "true"
- | "false"
+ : "true"
+ | "false"
</pre>
</div>
</td>
@@ -405,17 +407,16 @@
</tbody>
</table>
- <p>The initial value of <code>ittp:progressivelyDecodable</code> shall be "false".</p>
-
- <p>A <code>ittp:progressivelyDecodable</code> attribute with value "false" may be present on the <code>tt</code>
- element if the subtitle document is not a progressively decodable subtitle document.</p>
+ <p>The initial value of <code>ittp:progressivelyDecodable</code> shall be "false".</p>
+
+ <p>A <code>ittp:progressivelyDecodable</code> attribute with value "false" may be present on the <code>tt</code> element if
+ the subtitle document is not a progressively decodable subtitle document.</p>
<p>A <code>ittp:progressivelyDecodable</code> attribute is considered to be significant only when specified on the
<code>tt</code> element.</p>
<p class='note'>The placement and use of <code>div</code>, <code>region</code> and <code>span</code> that contain time
- attributes, and the use of <code>set</code> are constrained when <code>ittp:progressivelyDecodable="true"</code>
- .</p>
+ attributes, and the use of <code>set</code> are constrained when <code>ittp:progressivelyDecodable="true"</code> .</p>
</section>
<section id='tts-forcedDisplay'>
@@ -424,10 +425,9 @@
<p><code>itts:forcedDisplay</code> allows the processor to override the computed value of <code>tts:visibility</code>
attribute in conjunction with an application parameter <code>displayForcedOnlyMode</code>.</p>
- <p>If the value of <code>displayForcedOnlyMode</code> is "true", a content element with a
- <code>itts:forcedDisplay</code> computed value of "false" shall be assumed to have a <code>tts:visibility</code>
- computed value equal to "hidden", even if <code>tts:visibility</code> would otherwise be computed to
- "true".</p>
+ <p>If the value of <code>displayForcedOnlyMode</code> is "true", a content element with a <code>itts:forcedDisplay</code>
+ computed value of "false" SHALL not produce any visible rendering, but still affect layout, regardless of the computed
+ value of <code>tts:visibility</code>.</p>
<table class="simple">
<colgroup>
@@ -479,13 +479,19 @@
<code>itts:forcedDisplay</code> to display translation subtitles always, independently of whether the hard of hearing
captions are displayed or hidden.</p>
- <p>The <a>presentation processor</a> SHALL accept an optional boolean parameter called <code>displayForcedOnlyMode</code>, whose
- value MAY be set by a context external to the <a>presentation processor</a>. If not set, the value of
- <code>displayForcedOnlyMode</code> SHALL be assumed to be equal to "false".</p>
+ <p>The <a>presentation processor</a> SHALL accept an optional boolean parameter called <code>displayForcedOnlyMode</code>,
+ whose value MAY be set by a context external to the <a>presentation processor</a>. If not set, the value of
+ <code>displayForcedOnlyMode</code> SHALL be assumed to be equal to "false".</p>
<p>The algorithm for setting the <code>displayForcedOnlyMode</code> parameter based on the circumstances under which the
subtitle document is presented is left to the application.</p>
+ <p class='note'>The background of a region is drawn even if the computed value of <code>tts:visibility</code> equals
+ "hidden" for all active content within. This can occur if <code>itts:forcedDisplay</code> equals "false" for all active
+ content elements within a region for which <code>itts:forcedDisplay</code> equals "true", and
+ <code>displayForcedOnlyMode</code> equals "true". Authors can avoid this situation, for instance, by ensuring that content
+ elements and the regions that they are flowed into always have the same value of <code>itts:forcedDisplay</code>.</p>
+
<p class='note'>Although <code>itts:forcedDisplay</code>, like all the TTML style attributes, has no defined semantics on a
<code>br</code> content element, <code>itts:forcedDisplay</code> will apply to a <code>br</code> content element if it is
either defined on an ancestor content element of the <code>br</code> content element or it is applied to a region element
@@ -542,22 +548,20 @@
<ol>
<li>
- <p><code>tts:opacity</code> is not equal to "0.0" for the region; and</p>
- </li>
-
- <li>
- <p><code>tts:display</code> is not "none"; and</p>
+ <p><code>tts:opacity</code> is not equal to "0.0" for the region; and</p>
</li>
<li>
- <p>content is selected into the region or <code>tts:showBackground</code> is equal to "always" for the
- region.</p>
+ <p><code>tts:display</code> is not "none"; and</p>
+ </li>
+
+ <li>
+ <p>content is selected into the region or <code>tts:showBackground</code> is equal to "always" for the region.</p>
</li>
</ol>
- <p class='note'>As specified in [[!TTML1]], the initial value of <code>tts:opacity</code> is "1.0", the initial
- value of <code>tts:showBackground</code> is "always", and the initial value of <code>tts:display</code> is
- "auto"</p>
+ <p class='note'>As specified in [[!TTML1]], the initial value of <code>tts:opacity</code> is "1.0", the initial value of
+ <code>tts:showBackground</code> is "always", and the initial value of <code>tts:display</code> is "auto"</p>
</section>
<section>
@@ -873,7 +877,7 @@
<td><code>#timeBase-media</code></td>
<td>SHALL be used. <code>ttp:timeBase</code> SHALL be present on the <code>tt</code> element and SHALL be equal to
- "media".</td>
+ "media".</td>
</tr>
<tr>
@@ -1117,7 +1121,7 @@
<tr>
<td><code>#color</code></td>
- <td>MAY be used. The initial value of <code>tts:color</code> SHALL be "white". NOTE: This is consistent with
+ <td>MAY be used. The initial value of <code>tts:color</code> SHALL be "white". NOTE: This is consistent with
[[ST2052-1]].</td>
</tr>
@@ -1130,23 +1134,22 @@
<tr>
<td><code>#displayAlign</code></td>
- <td>MAY be used. The initial value of <code>tts:displayAlign</code> SHALL be "after" for the default region.
- NOTE: This is consistent with [[ST2052-1]].</td>
+ <td>MAY be used. The initial value of <code>tts:displayAlign</code> SHALL be "after" for the default region. NOTE: This
+ is consistent with [[ST2052-1]].</td>
</tr>
<tr>
<td><code>#extent-region</code></td>
<td>The <code>tts:extent</code> attribute when applied to a region element SHALL use <code>px</code> units or
- "percentage" representation, and SHALL NOT use <code>em</code> units.<br></td>
+ "percentage" representation, and SHALL NOT use <code>em</code> units.<br></td>
</tr>
<tr>
<td><code>#fontFamily-generic</code></td>
- <td>MAY be used. A <code>tts:fontFamily</code> of either "monospaceSerif" or
- "proportionalSansSerif" SHOULD be specified for all presented text content. A tts:fontFamily of
- "default" SHALL be equivalent to "monospaceSerif".</td>
+ <td>MAY be used. A <code>tts:fontFamily</code> of either "monospaceSerif" or "proportionalSansSerif" SHOULD be
+ specified for all presented text content. A tts:fontFamily of "default" SHALL be equivalent to "monospaceSerif".</td>
</tr>
<tr>
@@ -1225,8 +1228,8 @@
<td><code>#lineHeight</code></td>
<td>MAY be used.<br>
- An explicit <code><length></code> SHOULD be specified as there is no uniform implementation of the
- "normal" value at the time of this writing.</td>
+ An explicit <code><length></code> SHOULD be specified as there is no uniform implementation of the "normal" value
+ at the time of this writing.</td>
</tr>
<tr>
@@ -1244,8 +1247,8 @@
<tr>
<td><code>#origin</code></td>
- <td>The <code>tts:origin</code> attribute SHALL use <code>px</code> units or "percentage" representation, and
- SHALL NOT use <code>em</code> units.</td>
+ <td>The <code>tts:origin</code> attribute SHALL use <code>px</code> units or "percentage" representation, and SHALL NOT
+ use <code>em</code> units.</td>
</tr>
<tr>
@@ -1293,8 +1296,8 @@
<tr>
<td><code>#textAlign</code></td>
- <td>MAY be used. The initial value of <code>tts:textAlign</code> SHALL be "center" for the default region.
- NOTE: This is consistent with [[ST2052-1]].</td>
+ <td>MAY be used. The initial value of <code>tts:textAlign</code> SHALL be "center" for the default region. NOTE: This
+ is consistent with [[ST2052-1]].</td>
</tr>
<tr>
@@ -1620,9 +1623,8 @@
<p>The model operates on successive intermediate synchronic documents obtained from an input subtitle document, and uses a
simple double buffering model: while an intermediate synchronic document E<sub>n</sub> is being painted into Presentation
- Buffer P<sub>n</sub> (the "front buffer" of the model), the previous intermediate synchronic document
- E<sub>n-1</sub> is available for display in Presentation Buffer P<sub>n-1</sub> (the "back buffer" of the
- model).</p>
+ Buffer P<sub>n</sub> (the "front buffer" of the model), the previous intermediate synchronic document E<sub>n-1</sub> is
+ available for display in Presentation Buffer P<sub>n-1</sub> (the "back buffer" of the model).</p>
<p>The model specifies an (hypothetical) time required for completely painting an intermediate synchronic document as a
proxy for complexity. Painting includes drawing region backgrounds, rendering and copying glyphs, and decoding and copying
@@ -1759,8 +1761,8 @@
container width)</p>
<aside class='example'>
- For a region R<sub>i</sub> in with <code>tts:extent="250px 50px"</code> within a root container with
- <code>tts:extent="1920px 1080px"</code>, NSIZE(R<sub>i</sub>) = 0.603.
+ For a region R<sub>i</sub> in with <code>tts:extent="250px 50px"</code> within a root container with
+ <code>tts:extent="1920px 1080px"</code>, NSIZE(R<sub>i</sub>) = 0.603.
</aside>
<p>NBG(R<sub>i</sub>) SHALL be the total number of <code>tts:backgroundColor</code> attributes associated with the given
@@ -2001,8 +2003,8 @@
<aside class='example'>
Setting a Glyph Buffer Normalized Size effectively sets a limit on the total number of distinct glyphs present in any
given intermediate synchronic document E<sub>n</sub>. For example, assuming a maximum Normalized Glyph Buffer Size of 1
- and the default tts:fontSize of 1c are used, the glyph's height as percentage of root container height is 1/15 , and
- the maximum number of distinct glyphs that can be buffered is 1÷(1÷15)^2=225 glyphs. In this example, an implementation
+ and the default tts:fontSize of 1c are used, the glyph's height as percentage of root container height is 1/15 , and the
+ maximum number of distinct glyphs that can be buffered is 1÷(1÷15)^2=225 glyphs. In this example, an implementation
rendering at 1920x1080 would need to allocate a glyph buffer no smaller than (1920÷32)×(1080÷15)×225=~1 Mpixels.
</aside>
@@ -2427,9 +2429,8 @@
<h2>Forced content (non-normative)</h2>
<p><a href='#fig-forced-content'></a> below illustrates the use of forced content, i.e. <code>itts:forcedDisplay</code> and
- <code>displayForcedOnlyMode</code>. The content with <code>itts:forcedDisplay</code>="true" is the French translation
- of the "High School" sign. The content with <code>itts:forcedDisplay</code>="false" are French subtitles
- capturing a voiceover.</p>
+ <code>displayForcedOnlyMode</code>. The content with <code>itts:forcedDisplay</code>="true" is the French translation of the
+ "High School" sign. The content with <code>itts:forcedDisplay</code>="false" are French subtitles capturing a voiceover.</p>
<figure id='fig-forced-content'>
<img src="forced-example-figure-1.png" alt="Illustration of the use of itts:forcedDisplay">
@@ -2440,12 +2441,12 @@
</figure>
<p>When the user selects French as the playback language but does not select French subtitles,
- <code>displayForcedOnlyMode</code> is set to "true", causing the display of the sign translation, which is useful to
- any French speaker, but hiding the voiceover subtitles as the voiceover is heard in French.</p>
+ <code>displayForcedOnlyMode</code> is set to "true", causing the display of the sign translation, which is useful to any French
+ speaker, but hiding the voiceover subtitles as the voiceover is heard in French.</p>
<p>If the user selects French as the playback language and also selects French subtitles, e.g. if the user is hard-of-hearing,
- <code>displayForcedOnlyMode</code> is set to "false", causing the display of both the sign translation and the
- voiceover subtitles.</p>
+ <code>displayForcedOnlyMode</code> is set to "false", causing the display of both the sign translation and the voiceover
+ subtitles.</p>
<p>The algorithm for setting the <code>displayForcedOnlyMode</code> parameter and selecting the appropriate combination of
subtitle and audio tracks depends on the application.</p>
@@ -2470,15 +2471,14 @@
<p>For instance, in subtitling and captioning, italics can be used to indicate an off screen speaker context (for example a
voice from a radio). An author can choose to include this functional information in the text equivalent; for example, by
- including the word "Radio: " before the image equivalent text. It should also be noted that images in an Image
- Profile subtitle document that are intended for use as <em>captions</em>, i.e. intended for a hard of hearing audience, might
- already include this functional information in the rendered text.</p>
-
- <p>Guideline 1.1 of [[!WCAG20]] also recommends that accessible text alternatives must be "programmatically
- determinable." This means that the text must be able to be read and used by the assistive technologies (and the
- accessibility features in browsers) that people with disabilities use. It also means that the user must be able to use their
- assistive technology to find the alternative text (that they can use) when they land on the non-text content (that they
- can't use).</p>
+ including the word "Radio: " before the image equivalent text. It should also be noted that images in an Image Profile subtitle
+ document that are intended for use as <em>captions</em>, i.e. intended for a hard of hearing audience, might already include
+ this functional information in the rendered text.</p>
+
+ <p>Guideline 1.1 of [[!WCAG20]] also recommends that accessible text alternatives must be "programmatically determinable." This
+ means that the text must be able to be read and used by the assistive technologies (and the accessibility features in browsers)
+ that people with disabilities use. It also means that the user must be able to use their assistive technology to find the
+ alternative text (that they can use) when they land on the non-text content (that they can't use).</p>
</section>
<section class='appendix' id='features-and-extensions'>
@@ -2494,21 +2494,22 @@
<section class='appendix'>
<h3>#progressivelyDecodable</h3>
- <p>A <a>transformation processor</a> supports the <code>#progressivelyDecodable</code> feature if it recognizes and is capable of
- transforming values of the <a href="#ttp-progressivelyDecodable"><code>ittp:progressivelyDecodable</code></a>.</p>
-
- <p>A <a>presentation processor</a> supports the <code>#progressivelyDecodable</code> feature if it implements presentation semantic
- support for values of the <a href="#ttp-progressivelyDecodable"><code>ittp:progressivelyDecodable</code></a> attribute.</p>
+ <p>A <a>transformation processor</a> supports the <code>#progressivelyDecodable</code> feature if it recognizes and is
+ capable of transforming values of the <a href="#ttp-progressivelyDecodable"><code>ittp:progressivelyDecodable</code></a>.</p>
+
+ <p>A <a>presentation processor</a> supports the <code>#progressivelyDecodable</code> feature if it implements presentation
+ semantic support for values of the <a href="#ttp-progressivelyDecodable"><code>ittp:progressivelyDecodable</code></a>
+ attribute.</p>
</section>
<section class='appendix'>
<h3>#aspectRatio</h3>
- <p>A <a>transformation processor</a> supports the <code>#aspectRatio</code> feature if it recognizes and is capable of transforming
- values of the <a href="#ttp-aspectRatio"><code>ittp:aspectRatio</code></a>.</p>
-
- <p>A <a>presentation processor</a> supports the <code>#aspectRatio</code> feature if it implements presentation semantic support for
- values of the <a href="#ttp-aspectRatio"><code>ittp:aspectRatio</code></a> attribute.</p>
+ <p>A <a>transformation processor</a> supports the <code>#aspectRatio</code> feature if it recognizes and is capable of
+ transforming values of the <a href="#ttp-aspectRatio"><code>ittp:aspectRatio</code></a>.</p>
+
+ <p>A <a>presentation processor</a> supports the <code>#aspectRatio</code> feature if it implements presentation semantic
+ support for values of the <a href="#ttp-aspectRatio"><code>ittp:aspectRatio</code></a> attribute.</p>
</section>
<section class='appendix'>
@@ -2517,18 +2518,18 @@
<p>A <a>transformation processor</a> supports the <code>#forcedDisplay</code> feature if it recognizes and is capable of
transforming values of the <a href="#tts-forcedDisplay"><code>itts:forcedDisplay</code></a>.</p>
- <p>A <a>presentation processor</a> supports the <code>#forcedDisplay</code> feature if it implements presentation semantic support
- for values of the <a href="#tts-forcedDisplay"><code>itts:forcedDisplay</code></a> attribute.</p>
+ <p>A <a>presentation processor</a> supports the <code>#forcedDisplay</code> feature if it implements presentation semantic
+ support for values of the <a href="#tts-forcedDisplay"><code>itts:forcedDisplay</code></a> attribute.</p>
</section>
<section class='appendix'>
<h3>#altText</h3>
- <p>A <a>transformation processor</a> supports the <code>#altText</code> feature if it recognizes and is capable of transforming
- values of the <a href="#ttm-altText"><code>ittm:altText</code></a> element.</p>
-
- <p>A <a>presentation processor</a> supports the <code>#altText</code> feature if it implements presentation semantic support for
- values of the <a href="#ttm-altText"><code>ittm:altText</code></a> element.</p>
+ <p>A <a>transformation processor</a> supports the <code>#altText</code> feature if it recognizes and is capable of
+ transforming values of the <a href="#ttm-altText"><code>ittm:altText</code></a> element.</p>
+
+ <p>A <a>presentation processor</a> supports the <code>#altText</code> feature if it implements presentation semantic support
+ for values of the <a href="#ttm-altText"><code>ittm:altText</code></a> element.</p>
</section>
</section>
</body>