[css-text] Require CJK to be treated equally, SE Asian to be treated equally. Might rephrase this later.

Author: fantasai

css-text/Overview.bs

@@ -1778,18 +1778,30 @@ Cursive Scripts</h4>
 Possible Algorithms</h4>
 
   <p>For <a value for=text-justify>auto</a> justification, this specification does not define
-	what all of the <i>justification opportunities</i> are,
-	how they are prioritized, or
-	when and how multiple levels of <i>justification opportunities</i> interact.
-	However, it does require that if a <i>justification opportunity</i> exists within a line,
-	it must be justified,
-	and that, unless contraindicated by the typographic traditions of the <i>content language</i> or adjacent symbols/punctuation,
-	each of the following provides a <i>justification opportunity</i>:
-	<ul>
-	<li><i>Word separators</i>
-	<li>The boundary between a <i>visually-perceived character</i> of any <i>block scripts</i> and any other <i>visually-perceived character</i>
-	<li>The boundary between a <i>visually-perceived character</i> of any <i>clustered scripts</i> and any other <i>visually-perceived character</i>
-	</ul>
+  what all of the <i>justification opportunities</i> are,
+  how they are prioritized, or
+  when and how multiple levels of <i>justification opportunities</i> interact.
+  However, it does require that
+  
+  <ul>
+    <li>
+      If a <i>justification opportunity</i> exists within a line,
+      it must be justified.
+    <li>
+      Unless contraindicated by the typographic traditions of the <i>content language</i> or adjacent symbols/punctuation,
+      each of the following provides a <i>justification opportunity</i>:
+      <ul>
+        <li><i>Word separators</i>
+        <li>The boundary between a <i>visually-perceived character</i> of any <i>block scripts</i> and any other <i>visually-perceived character</i>
+        <li>The boundary between a <i>visually-perceived character</i> of any <i>clustered scripts</i> and any other <i>visually-perceived character</i>
+      </ul>
+    <li>
+      All <i>letters</i> belonging to all <i>block scripts</i> are treated the same,
+      and all <i>letters</i> belonging to all <i>clustered scripts</i> are treated the same.
+      For example, no distiction is made between
+      the justification opportunity between a Han letter followed by another Han letter,
+      vs. the justification opportunity between a Han letter followed by a Hangul letter.
+  </ul>
 
   <p>The guidelines in this level of CSS do not describe a complete
   justification algorithm. They are merely a minimum set of requirements
@@ -2576,13 +2588,22 @@ Appendix C: Scripts and Spacing</h2>
   	  The following scripts are included: Bopomofo, Han, Hangul, Hiragana, Katakana, and Yi.
   	  Characters of the East Asian Width property [[!UAX11]] W and F are also included.
   	<dt><dfn>clustered scripts</dfn></dt>
-  	<dd>Scripts that have discrete units but do not use spaces between words, such as many Southeast Asian systems.
-  	  The following scripts are included: Javanese, Khmer, Lao, Myanmar, Thai,
-  	  <span class=issue>This list is likely incomplete. What else fits here?</span>
+  	<dd>Scripts that have discrete units,
+      break only at word boundaries,
+      but do not use visible word separators.
+      They comfortably admit inter-character spacing for justification.
+  	  The following scripts are included:
+      Khmer,
+      Lao,
+      Myanmar,
+      New Tai Lue,
+      Tai Le,
+      Tai Tham,
+      Tai Viet,
+      Thai
   	<dt><dfn title="cursive script">cursive scripts</dfn>
-  	<dd>
-  <p>The following scripts in Unicode 6 are considered to be cursive scripts,
-    and do not admit gaps between their letters for either justification or 'letter-spacing':
+  	<dd>The following scripts in Unicode 6 are considered to be cursive scripts,
+      and do not admit gaps between their letters for either justification or 'letter-spacing':
       Arabic,
       Mandaic,
       Mongolian,
@@ -2594,6 +2615,10 @@ Appendix C: Scripts and Spacing</h2>
     to handle as-yet-unencoded cursive scripts in future versions of Unicode,
     and are encouraged to ask the CSSWG to update this spec accordingly.
 
+  <p class="issue">Should block and cluster scripts be merged?
+  They have different tolerances for space-justification vs inter-character justification,
+  but both admit both.
+
 <h2 id="character-properties" class="no-num">Appendix D.
 Characters and Properties</h2>
 

css-text/Overview.html

@@ -104,7 +104,7 @@
 </p>
   <h1 class="p-name no-ref" id=title>CSS Text Module Level 3</h1>
   <h2 class="no-num no-toc no-ref heading settled heading" id=subtitle><span class=content>Editor’s Draft,
-    <span class=dt-updated><span class=value-title title=20140722>22 July 2014</span></span></span></h2>
+    <span class=dt-updated><span class=value-title title=20140723>23 July 2014</span></span></span></h2>
   <div data-fill-with=spec-metadata><dl>
 	<dt>This version:
 	<dd><a class=u-url href=http://dev.w3.org/csswg/css-text-3/>http://dev.w3.org/csswg/css-text-3/</a>
@@ -1920,18 +1920,30 @@ <h4 class="heading settled heading" data-level=7.4.5 id=justify-algos><span clas
 Possible Algorithms</span><a class=self-link href=#justify-algos></a></h4>
 
   <p>For <a class=css-code data-link-for=text-justify data-link-type=value href=#valdef-text-justify.auto title=auto>auto</a> justification, this specification does not define
-	what all of the <a data-link-type=dfn href=#justification-opportunity title="justification opportunities">justification opportunities</a> are,
-	how they are prioritized, or
-	when and how multiple levels of <a data-link-type=dfn href=#justification-opportunity title="justification opportunities">justification opportunities</a> interact.
-	However, it does require that if a <a data-link-type=dfn href=#justification-opportunity title="justification opportunity">justification opportunity</a> exists within a line,
-	it must be justified,
-	and that, unless contraindicated by the typographic traditions of the <a data-link-type=dfn href=#content-language title="content language">content language</a> or adjacent symbols/punctuation,
-	each of the following provides a <a data-link-type=dfn href=#justification-opportunity title="justification opportunity">justification opportunity</a>:
-	<ul>
-	<li><a data-link-type=dfn href=#word-separator title="word separators">Word separators</a>
-	<li>The boundary between a <a data-link-type=dfn href=#visually-perceived-character title="visually-perceived character">visually-perceived character</a> of any <a data-link-type=dfn href=#block-scripts title="block scripts">block scripts</a> and any other <a data-link-type=dfn href=#visually-perceived-character title="visually-perceived character">visually-perceived character</a>
-	<li>The boundary between a <a data-link-type=dfn href=#visually-perceived-character title="visually-perceived character">visually-perceived character</a> of any <a data-link-type=dfn href=#clustered-scripts title="clustered scripts">clustered scripts</a> and any other <a data-link-type=dfn href=#visually-perceived-character title="visually-perceived character">visually-perceived character</a>
-	</ul>
+  what all of the <a data-link-type=dfn href=#justification-opportunity title="justification opportunities">justification opportunities</a> are,
+  how they are prioritized, or
+  when and how multiple levels of <a data-link-type=dfn href=#justification-opportunity title="justification opportunities">justification opportunities</a> interact.
+  However, it does require that
+
+  <ul>
+    <li>
+      If a <a data-link-type=dfn href=#justification-opportunity title="justification opportunity">justification opportunity</a> exists within a line,
+      it must be justified.
+    <li>
+      Unless contraindicated by the typographic traditions of the <a data-link-type=dfn href=#content-language title="content language">content language</a> or adjacent symbols/punctuation,
+      each of the following provides a <a data-link-type=dfn href=#justification-opportunity title="justification opportunity">justification opportunity</a>:
+      <ul>
+        <li><a data-link-type=dfn href=#word-separator title="word separators">Word separators</a>
+        <li>The boundary between a <a data-link-type=dfn href=#visually-perceived-character title="visually-perceived character">visually-perceived character</a> of any <a data-link-type=dfn href=#block-scripts title="block scripts">block scripts</a> and any other <a data-link-type=dfn href=#visually-perceived-character title="visually-perceived character">visually-perceived character</a>
+        <li>The boundary between a <a data-link-type=dfn href=#visually-perceived-character title="visually-perceived character">visually-perceived character</a> of any <a data-link-type=dfn href=#clustered-scripts title="clustered scripts">clustered scripts</a> and any other <a data-link-type=dfn href=#visually-perceived-character title="visually-perceived character">visually-perceived character</a>
+      </ul>
+    <li>
+      All <a data-link-type=dfn href=#letter title=letters>letters</a> belonging to all <a data-link-type=dfn href=#block-scripts title="block scripts">block scripts</a> are treated the same,
+      and all <a data-link-type=dfn href=#letter title=letters>letters</a> belonging to all <a data-link-type=dfn href=#clustered-scripts title="clustered scripts">clustered scripts</a> are treated the same.
+      For example, no distiction is made between
+      the justification opportunity between a Han letter followed by another Han letter,
+      vs. the justification opportunity between a Han letter followed by a Hangul letter.
+  </ul>
 
   <p>The guidelines in this level of CSS do not describe a complete
   justification algorithm. They are merely a minimum set of requirements
@@ -2699,13 +2711,22 @@ <h2 class="no-num heading settled heading" id=script-groups><span class=content>
   	  The following scripts are included: Bopomofo, Han, Hangul, Hiragana, Katakana, and Yi.
   	  Characters of the East Asian Width property <a data-biblio-type=normative data-link-type=biblio href=#biblio-uax11 title=biblio-uax11>[UAX11]</a> W and F are also included.
   	<dt><dfn data-dfn-type=dfn data-noexport="" id=clustered-scripts>clustered scripts<a class=self-link href=#clustered-scripts></a></dfn></dt>
-  	<dd>Scripts that have discrete units but do not use spaces between words, such as many Southeast Asian systems.
-  	  The following scripts are included: Javanese, Khmer, Lao, Myanmar, Thai,
-  	  <span class=issue id=issue-d3e18b12><a class=self-link href=#issue-d3e18b12></a>This list is likely incomplete. What else fits here?</span>
+  	<dd>Scripts that have discrete units,
+      break only at word boundaries,
+      but do not use visible word separators.
+      They comfortably admit inter-character spacing for justification.
+  	  The following scripts are included:
+      Khmer,
+      Lao,
+      Myanmar,
+      New Tai Lue,
+      Tai Le,
+      Tai Tham,
+      Tai Viet,
+      Thai
   	<dt><dfn data-dfn-type=dfn data-noexport="" id=cursive-script title="cursive script">cursive scripts<a class=self-link href=#cursive-script></a></dfn>
-  	<dd>
-  <p>The following scripts in Unicode 6 are considered to be cursive scripts,
-    and do not admit gaps between their letters for either justification or <a class=property data-link-type=propdesc href=#propdef-letter-spacing title=letter-spacing>letter-spacing</a>:
+  	<dd>The following scripts in Unicode 6 are considered to be cursive scripts,
+      and do not admit gaps between their letters for either justification or <a class=property data-link-type=propdesc href=#propdef-letter-spacing title=letter-spacing>letter-spacing</a>:
       Arabic,
       Mandaic,
       Mongolian,
@@ -2717,6 +2738,10 @@ <h2 class="no-num heading settled heading" id=script-groups><span class=content>
     to handle as-yet-unencoded cursive scripts in future versions of Unicode,
     and are encouraged to ask the CSSWG to update this spec accordingly.
 
+  <p class=issue id=issue-929bca17><a class=self-link href=#issue-929bca17></a>Should block and cluster scripts be merged?
+  They have different tolerances for space-justification vs inter-character justification,
+  but both admit both.
+
 <h2 class="no-num heading settled heading" id=character-properties><span class=content>Appendix D.
 Characters and Properties</span><a class=self-link href=#character-properties></a></h2>
 
@@ -3114,5 +3139,8 @@ <h2 class="no-num heading settled" id=issues-index><span class=content>Issues In
     please send the information to <a href=mailto:www-style@w3.org>www-style@w3.org</a>
     with <kbd>[css-text]</kbd> in the subject line.<a href=#issue-37a23328> ↵ </a></div>
 
-<div class=issue>This list is likely incomplete. What else fits here?<a href=#issue-d3e18b12> ↵ </a></div>
-  	</div>
+<div class=issue>Should block and cluster scripts be merged?
+  They have different tolerances for space-justification vs inter-character justification,
+  but both admit both.
+
+<a href=#issue-929bca17> ↵ </a></div></div>