(1) add note under first usage of 'character edge attributes';
authorGlenn Adams <glenn@skynav.com>
Sat, 01 Sep 2012 06:44:47 +0800
changeset 269 99f4dd11e93d
parent 268 dd58d5018c99
child 270 6ea28aad9d37
(1) add note under first usage of 'character edge attributes';
(2) remove incorrect usage of fontStyle(s);
(3) minor editorial change on textOutline regarding character edge types; more changes needed...
ttml10-sdp-us/Overview.html
--- a/ttml10-sdp-us/Overview.html	Thu Aug 30 17:12:56 2012 +0800
+++ b/ttml10-sdp-us/Overview.html	Sat Sep 01 06:44:47 2012 +0800
@@ -901,6 +901,7 @@
 <p data-transform='constraint'>The player MUST allow the user to specify a generic fontFamily for the document using the values shown in the preceding table.</p>
 <p data-transform='constraint'>The player MUST allow the user to specify character edge attributes and types for the generic fontFamily names for the values shown in the preceding table.</p>
 <p>Note: Player and Unicode code point support is defined in <a href="#code_points">Code Point support</a></p>
+<p>Note: Text outline can be specified using a style property to apply to characters selected for specific areas for content flowed into a region. Text outline applies a specific character edge to content. For example, when the textOutline style property is used, a type of shadow or thickness can be applied to content.</p>
 </section>
 </section>
 <section id='Constrained_TTML_Feature_display_display_fontSize'>
@@ -964,10 +965,7 @@
 <section class='Core_Constraints'>
 <h4>Constraints</h4>
 <p>Processors MUST support the capability to present documents where the following constraints apply:</p>
-<p data-transform='constraint'>Processors MUST support the capability to provide presentation semantic support for values of the tts:fontStyle attribute as defined for the fontFamily-generic feature.</p>
-<p>Note: Various fontStyle(s) unspecified in TTML 1.0, such as casual, cursive and smallcap styles, may be used. Players that recognize the string as a particular font style could use a comparable style.</p>
-<p>Note: A default fontStyle - white, mid-weight san serif with an initial font height of 5% of the video height and with a black outline using textOutline-unblurred of 10% of the fontSize - is suggested.</p>
-<p data-transform='constraint'>The capability MUST exist for the user to specify the italic style for the fontStyle(s) identified in this profile.</p>
+<p data-transform='constraint'>The capability MUST exist for the user to specify the italic style for the font families identified in this profile.</p>
 </section>
 </section>
 <section id='Constrained_TTML_Feature_length_percentage'>
@@ -1175,9 +1173,8 @@
 <section class='Core_Constraints'>
 <h4>Constraints</h4>
 <p>Processors MUST support the capability to present documents where the following constraints apply:</p>
-<p data-transform='constraint'>The tts:textDecoration-under attribute MUST support the fontStyle constraints identified in this profile.</p>
-<p data-transform='constraint'>The capability MUST exist for the user to specify the underline style for the fontStyle(s) identified in this profile.</p>
-<p>Note: See also <a href="#Constrained_TTML_Feature_fontStyle">tts:fontStyle attribute</a>.</p>
+<p data-transform='constraint'>The tts:textDecoration-under attribute MUST support the constraints identified in this profile.</p>
+<p data-transform='constraint'>The capability MUST exist for the user to specify the underline decoration for the font families identified in this profile.</p>
 </section>
 </section>
 <section id='Constrained_TTML_Feature_textOutline_unblurred'>
@@ -1208,7 +1205,7 @@
 <p data-transform='constraint'>Character edge attributes MUST be expressed using textOutline-unblurred based on the settings identified in CEA-708-D, Section 8.5.8.</p>
 <p data-transform='constraint'>A text outline MUST be expressed using textOutline-unblurred of up to 10%.</p>
 <p data-transform='constraint'>The user MUST be able to specify character edge and type attributes using tts:textOutline attribute.</p>
-<p data-transform='constraint'>The user MUST be able to specify the rendering of character edge types of: None, raised, depressed, uniform or drop shadowed edges.</p>
+<p data-transform='constraint'>The user MUST be able to specify the rendering of character edge types of: none, raised, depressed, uniform or drop shadowed edges.</p>
 <p></p>
 </section>
 </section>
@@ -1300,7 +1297,7 @@
 <p>Processors MUST support the capability to present documents where the following constraints apply:</p>
 <p data-transform='constraint'>At most 32 characters MUST be present in any displayed text line.</p>
 <p data-transform='constraint'>At most one p element MUST be selected into a region at a time.</p>
-<p>NOTE: The fontStyle, fontSize and the characteristics of region impact how selected text flows into a region (i.e. selected text may flow outside of the region such as on a mobile device).</p>
+<p>NOTE: The style properites of region and the content selected for the region impact how selected text flows into a region (i.e. selected text may flow outside of the region such as on a mobile device).</p>
 <p>NOTE: Constraining one p element to a region logically places content from two different speakers to different region(s).</p>
 <p>NOTE: When a document author wants to construct a single phrase from a speaker with more than one line in a region, the br within a p element can be used. This construction adheres to the constraints in this section. For example for one speaker with more than one line:</p>
 <pre class="example" style="font-family: Segoe UI; font-size: 13; color: black; background: white;">