[ttml10se, ttml11] fix typo - change initial to computed
authorGlenn Adams <glenn@skynav.com>
Fri, 12 Jul 2013 05:53:41 -0600
changeset 451 00a9b799895d
parent 450 5ef8c270b890
child 452 abff58e26f97
[ttml10se, ttml11] fix typo - change initial to computed
ttml10/spec/ttaf1-dfxp.xml
ttml10/spec/ttml-changes.html
ttml11/spec/ttml-changes.html
ttml11/spec/ttml11.xml
--- a/ttml10/spec/ttaf1-dfxp.xml	Thu Jul 11 10:30:09 2013 -0600
+++ b/ttml10/spec/ttaf1-dfxp.xml	Fri Jul 12 05:53:41 2013 -0600
@@ -4059,7 +4059,7 @@
 and <emph>height</emph>, where the first specification is the
 <emph>width</emph>, and the second specification is the <emph>height</emph>.</p>
 <p>The <loc href="#style-value-length">&lt;length&gt;</loc> value(s) used to express extent must be non-negative.</p>
-<p>If the value of this attribute is <code>auto</code>, then the initial value
+<p>If the value of this attribute is <code>auto</code>, then the computed value
 of the style property must be considered to be the same as the extent of the <emph>Root Container Region</emph>.</p>
 <p>The extent of the <emph>Root Container Region</emph> is determined either by a
 <att>tts:extent</att> specified on the <el>tt</el> element, if
@@ -4576,7 +4576,7 @@
 </tbody>
 </table>
 <p>If the value of this attribute is <code>normal</code>, then the
-initial value of the style property must be considered to be the same
+computed value of the style property must be considered to be the same
 as the largest font size that applies to any
 descendant element.</p>
 <p>If specified as a <loc
@@ -4795,7 +4795,7 @@
 <p>If the value of this attribute consists of two <loc href="#style-value-length">&lt;length&gt;</loc> specifications,
 then they must be interpreted as <emph>x</emph> and <emph>y</emph> coordinates, where the first specification
 is the <emph>x</emph> coordinate, and the second specification is the <emph>y</emph> coordinate.</p>
-<p>If the value of this attribute is <code>auto</code>, then the initial value
+<p>If the value of this attribute is <code>auto</code>, then the computed value
 of the style property must be considered to be the same as the origin of the <emph>Root Container Region</emph>.</p>
 <p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
--- a/ttml10/spec/ttml-changes.html	Thu Jul 11 10:30:09 2013 -0600
+++ b/ttml10/spec/ttml-changes.html	Fri Jul 12 05:53:41 2013 -0600
@@ -50,6 +50,12 @@
 * In 8.1.2, remove erroneous sentence stating that style element takes metadata children (this
   support was removed in the sytnax definition and schema before REC was published, but this
   sentence was inadvertently left in the text).
+* In 8.2.7, correct typo where "initial" value was written, but "computed" value
+  intended.
+* In 8.2.12, correct typo where "initial" value was written, but "computed" value
+  intended.
+* In 8.2.13, correct typo where "initial" value was written, but "computed" value
+  intended.
 * In 9.1.2, add note elaborating that a region's area need not be contained in the root container
   region and that clipping behavior on the root container region is not specified.
 * In 12.1.7, clarify that agent attribute on ttm:actor must reference a "significant" ttm:agent
--- a/ttml11/spec/ttml-changes.html	Thu Jul 11 10:30:09 2013 -0600
+++ b/ttml11/spec/ttml-changes.html	Fri Jul 12 05:53:41 2013 -0600
@@ -55,6 +55,14 @@
 * In Appendix N, change appendix designation to normative, effectively making
   the time expression semantics normatively applicable.
 
+<span class="strong">Editorial Changes</span>
+
+* In 8.2.7, correct typo where "initial" value was written, but "computed" value
+  intended.
+* In 8.2.12, correct typo where "initial" value was written, but "computed" value
+  intended.
+* In 8.2.13, correct typo where "initial" value was written, but "computed" value
+  intended.
 </pre>
 </div>
 </div>
--- a/ttml11/spec/ttml11.xml	Thu Jul 11 10:30:09 2013 -0600
+++ b/ttml11/spec/ttml11.xml	Fri Jul 12 05:53:41 2013 -0600
@@ -4105,7 +4105,7 @@
 and <emph>height</emph>, where the first specification is the
 <emph>width</emph>, and the second specification is the <emph>height</emph>.</p>
 <p>The <loc href="#style-value-length">&lt;length&gt;</loc> value(s) used to express extent must be non-negative.</p>
-<p>If the value of this attribute is <code>auto</code>, then the initial value
+<p>If the value of this attribute is <code>auto</code>, then the computed value
 of the style property must be considered to be the same as the extent of the <emph>Root Container Region</emph>.</p>
 <p>The extent of the <emph>Root Container Region</emph> is determined either by a
 <att>tts:extent</att> specified on the <el>tt</el> element, if
@@ -4622,7 +4622,7 @@
 </tbody>
 </table>
 <p>If the value of this attribute is <code>normal</code>, then the
-initial value of the style property must be considered to be the same
+computed value of the style property must be considered to be the same
 as the largest font size that applies to any
 descendant element.</p>
 <p>If specified as a <loc
@@ -4841,7 +4841,7 @@
 <p>If the value of this attribute consists of two <loc href="#style-value-length">&lt;length&gt;</loc> specifications,
 then they must be interpreted as <emph>x</emph> and <emph>y</emph> coordinates, where the first specification
 is the <emph>x</emph> coordinate, and the second specification is the <emph>y</emph> coordinate.</p>
-<p>If the value of this attribute is <code>auto</code>, then the initial value
+<p>If the value of this attribute is <code>auto</code>, then the computed value
 of the style property must be considered to be the same as the origin of the <emph>Root Container Region</emph>.</p>
 <p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the