[css-text-3] Move section for better readability between Phase 1 and Phase 2 sections.

fantasai · fantasai · commit b0fd8a461d35 · 2020-01-21T18:43:37.000+01:00
diff --git a/css-text-3/Overview.bs b/css-text-3/Overview.bs
@@ -1402,198 +1402,6 @@ Text Processing</h3>
       white-space-bidirectionality-001.xht
     </wpt>
 
-    <h4 id="line-break-transform">
-      Segment Break Transformation Rules</h4>
-
-      <p>When 'white-space' is ''pre'', ''pre-wrap'', ''break-spaces'', or ''pre-line'',
-      <a>segment breaks</a> are not <a>collapsible</a>
-      and are instead transformed into a preserved line feed (U+000A).
-
-      <wpt pathprefix="/css/CSS2/text/">
-        white-space-008.xht
-        white-space-processing-016.xht
-        white-space-processing-017.xht
-        white-space-processing-018.xht
-      </wpt>
-
-      <p>For other values of 'white-space', <a>segment breaks</a> are <a>collapsible</a>.
-        Any collapsible <a>segment break</a> immediately following another collapsible <a>segment break</a>
-        is removed.
-        Then any remaining <a>segment break</a> is
-        either transformed into a space (U+0020) or removed
-        depending on the context before and after the break:
-
-        <wpt pathprefix="/css/vendor-imports/mozilla/mozilla-central-reftests/text3/">
-          segment-break-transformation-removable-2.html
-          segment-break-transformation-removable-4.html
-        </wpt>
-
-      <ul>
-        <li>If the character immediately before or immediately after the [=segment break=]
-          is the zero-width space character (U+200B), then the break
-          is removed, leaving behind the zero-width space.
-
-          <wpt>
-            white-space/seg-break-transformation-016.html
-            white-space/seg-break-transformation-017.html
-            white-space/seg-break-transformation-018.html
-            white-space/seg-break-transformation-019.html
-          </wpt>
-          <wpt pathprefix="/css/vendor-imports/mozilla/mozilla-central-reftests/text3/">
-            segment-break-transformation-removable-1.html
-            segment-break-transformation-removable-3.html
-          </wpt>
-        <li>Otherwise, if the <a>East Asian Width property</a> [[!UAX11]] of both
-          the character before and after the [=segment break=] is
-          <code>Fullwidth</code>, <code>Wide</code>, or <code>Halfwidth</code>
-          (not <code>Ambiguous</code>),
-          and neither side is Hangul,
-          then the [=segment break=] is removed.
-
-          <wpt>
-            white-space/seg-break-transformation-001.html
-            white-space/seg-break-transformation-002.html
-            white-space/seg-break-transformation-003.html
-            white-space/seg-break-transformation-004.html
-            white-space/seg-break-transformation-005.html
-            white-space/seg-break-transformation-006.html
-            white-space/seg-break-transformation-007.html
-            white-space/seg-break-transformation-008.html
-            white-space/seg-break-transformation-009.html
-            white-space/seg-break-transformation-010.html
-            white-space/seg-break-transformation-011.html
-            white-space/seg-break-transformation-012.html
-            white-space/seg-break-transformation-014.html
-            white-space/seg-break-transformation-015.html
-          </wpt>
-          <wpt pathprefix="/css/vendor-imports/mozilla/mozilla-central-reftests/text3/">
-            segment-break-transformation-rules-001.html
-            segment-break-transformation-rules-002.html
-            segment-break-transformation-rules-003.html
-            segment-break-transformation-rules-004.html
-            segment-break-transformation-rules-005.html
-            segment-break-transformation-rules-006.html
-            segment-break-transformation-rules-007.html
-            segment-break-transformation-rules-008.html
-            segment-break-transformation-rules-009.html
-            segment-break-transformation-rules-010.html
-            segment-break-transformation-rules-011.html
-            segment-break-transformation-rules-012.html
-            segment-break-transformation-rules-013.html
-            segment-break-transformation-rules-014.html
-            segment-break-transformation-rules-015.html
-            segment-break-transformation-rules-016.html
-            segment-break-transformation-rules-017.html
-            segment-break-transformation-rules-018.html
-            segment-break-transformation-rules-019.html
-            segment-break-transformation-rules-020.html
-            segment-break-transformation-rules-021.html
-            segment-break-transformation-rules-022.html
-            segment-break-transformation-rules-023.html
-            segment-break-transformation-rules-024.html
-            segment-break-transformation-rules-025.html
-            segment-break-transformation-rules-026.html
-            segment-break-transformation-rules-027.html
-            segment-break-transformation-rules-028.html
-            segment-break-transformation-rules-029.html
-            segment-break-transformation-rules-030.html
-            segment-break-transformation-rules-031.html
-            segment-break-transformation-rules-032.html
-            segment-break-transformation-rules-033.html
-            segment-break-transformation-rules-034.html
-            segment-break-transformation-rules-035.html
-            segment-break-transformation-rules-036.html
-            segment-break-transformation-rules-037.html
-            segment-break-transformation-rules-038.html
-            segment-break-transformation-rules-039.html
-            segment-break-transformation-rules-040.html
-            segment-break-transformation-rules-041.html
-            segment-break-transformation-rules-042.html
-            segment-break-transformation-rules-043.html
-            segment-break-transformation-rules-044.html
-            segment-break-transformation-rules-045.html
-            segment-break-transformation-rules-046.html
-            segment-break-transformation-rules-047.html
-            segment-break-transformation-rules-048.html
-            segment-break-transformation-rules-049.html
-          </wpt>
-        <li>Otherwise, if the <a>writing system</a> of the <a>segment break</a>
-          is <a for=writing-system>Chinese</a>, <a for=writing-system>Japanese</a>, or Yi,
-          and the character before or after the [=segment break=]
-          is punctuation or a symbol (Unicode <a>general category</a> P* or S*)
-          and has an <a>East Asian Width property</a> of <code>Ambiguous</code>,
-          and the character on the other side of the [=segment break=] is
-          <code>Fullwidth</code>, <code>Wide</code>, or <code>Halfwidth</code>,
-          and not Hangul,
-          then the [=segment break=] is removed.
-
-          <wpt>
-            writing-system/writing-system-segment-break-001.html
-          </wpt>
-        <li>Otherwise, the [=segment break=] is converted to a space (U+0020).
-      </ul>
-
-      <p>
-        For this purpose,
-        Emoji (Unicode property <code>Emoji</code>)
-        with an <a>East Asian Width property</a> of
-        <code>Wide</code> or <code>Neutral</code>
-        are treated as having an <a>East Asian Width property</a> of
-        <code>Ambiguous</code>.
-
-      <p class="note">Note: The white space processing rules have already
-        removed any [=tabs=] and [=spaces=] after the [=segment break=] before these checks
-        take place.</p>
-
-      <div class="example">
-        The purpose of the segment break transformation rules
-        (and white space collapsing in general)
-        is to “unbreak” text that has been
-        <a href="#white-space-processing">broken into segments</a>
-        to make the document source code easier to work with.
-        In languages that use word separators, such as English and Korean,
-        “unbreaking” a line requires joining the two lines with a [=space=].
-
-        <figure>
-          <pre>
-            Here is an English paragraph
-            that is broken into multiple lines
-            in the source code so that it can
-            more easily read in a text editor.
-          </pre>
-          <p>Here is an English paragraph that is broken into multiple lines in the source code so that it can be more easily read in a text editor.</p>
-          <figcaption>
-            Eliminating a line break in English requires maintaining a [=space=] in its place.
-          </figcaption>
-        </figure>
-
-        In languages that have no word separators, such as Chinese,
-        “unbreaking” a line requires joining the two lines with no intervening space.
-
-        <figure>
-          <pre>
-            这个段落是呢么长，
-            在一行写不行。最好
-            用三行写。
-          </pre>
-          <p>这个段落是呢么长，在一行不行。最好用三行写。</p>
-          <figcaption>
-            Eliminating a line break in Chinese requires eliminating any intervening [=white space=].
-          </figcaption>
-        </figure>
-
-        The segment break transformation rules thus use adjacent context
-        to either transform the segment break into a space
-        or eliminate it entirely.
-      </div>
-
-      <p class="feedback issue">Comments on how well these rules would work in practice would
-        be very much appreciated, particularly from people who work with
-        Thai and similar scripts.
-        Note that browser implementations do not currently follow these rules consistently
-        (although IE does in some cases transform the break,
-        and Firefox follows the first two bullet points).</p>
-
     <h4 id="white-space-phase-2">Phase II: Trimming and Positioning</h4>
 
     <p>Then, the entire block is rendered.
@@ -1870,6 +1678,199 @@ Text Processing</h3>
       when measuring the line’s contents for fit.
     </div>
 
+
+    <h4 id="line-break-transform">
+      Segment Break Transformation Rules</h4>
+
+      <p>When 'white-space' is ''pre'', ''pre-wrap'', ''break-spaces'', or ''pre-line'',
+      <a>segment breaks</a> are not <a>collapsible</a>
+      and are instead transformed into a preserved line feed (U+000A).
+
+      <wpt pathprefix="/css/CSS2/text/">
+        white-space-008.xht
+        white-space-processing-016.xht
+        white-space-processing-017.xht
+        white-space-processing-018.xht
+      </wpt>
+
+      <p>For other values of 'white-space', <a>segment breaks</a> are <a>collapsible</a>.
+        Any collapsible <a>segment break</a> immediately following another collapsible <a>segment break</a>
+        is removed.
+        Then any remaining <a>segment break</a> is
+        either transformed into a space (U+0020) or removed
+        depending on the context before and after the break:
+
+        <wpt pathprefix="/css/vendor-imports/mozilla/mozilla-central-reftests/text3/">
+          segment-break-transformation-removable-2.html
+          segment-break-transformation-removable-4.html
+        </wpt>
+
+      <ul>
+        <li>If the character immediately before or immediately after the [=segment break=]
+          is the zero-width space character (U+200B), then the break
+          is removed, leaving behind the zero-width space.
+
+          <wpt>
+            white-space/seg-break-transformation-016.html
+            white-space/seg-break-transformation-017.html
+            white-space/seg-break-transformation-018.html
+            white-space/seg-break-transformation-019.html
+          </wpt>
+          <wpt pathprefix="/css/vendor-imports/mozilla/mozilla-central-reftests/text3/">
+            segment-break-transformation-removable-1.html
+            segment-break-transformation-removable-3.html
+          </wpt>
+        <li>Otherwise, if the <a>East Asian Width property</a> [[!UAX11]] of both
+          the character before and after the [=segment break=] is
+          <code>Fullwidth</code>, <code>Wide</code>, or <code>Halfwidth</code>
+          (not <code>Ambiguous</code>),
+          and neither side is Hangul,
+          then the [=segment break=] is removed.
+
+          <wpt>
+            white-space/seg-break-transformation-001.html
+            white-space/seg-break-transformation-002.html
+            white-space/seg-break-transformation-003.html
+            white-space/seg-break-transformation-004.html
+            white-space/seg-break-transformation-005.html
+            white-space/seg-break-transformation-006.html
+            white-space/seg-break-transformation-007.html
+            white-space/seg-break-transformation-008.html
+            white-space/seg-break-transformation-009.html
+            white-space/seg-break-transformation-010.html
+            white-space/seg-break-transformation-011.html
+            white-space/seg-break-transformation-012.html
+            white-space/seg-break-transformation-014.html
+            white-space/seg-break-transformation-015.html
+          </wpt>
+          <wpt pathprefix="/css/vendor-imports/mozilla/mozilla-central-reftests/text3/">
+            segment-break-transformation-rules-001.html
+            segment-break-transformation-rules-002.html
+            segment-break-transformation-rules-003.html
+            segment-break-transformation-rules-004.html
+            segment-break-transformation-rules-005.html
+            segment-break-transformation-rules-006.html
+            segment-break-transformation-rules-007.html
+            segment-break-transformation-rules-008.html
+            segment-break-transformation-rules-009.html
+            segment-break-transformation-rules-010.html
+            segment-break-transformation-rules-011.html
+            segment-break-transformation-rules-012.html
+            segment-break-transformation-rules-013.html
+            segment-break-transformation-rules-014.html
+            segment-break-transformation-rules-015.html
+            segment-break-transformation-rules-016.html
+            segment-break-transformation-rules-017.html
+            segment-break-transformation-rules-018.html
+            segment-break-transformation-rules-019.html
+            segment-break-transformation-rules-020.html
+            segment-break-transformation-rules-021.html
+            segment-break-transformation-rules-022.html
+            segment-break-transformation-rules-023.html
+            segment-break-transformation-rules-024.html
+            segment-break-transformation-rules-025.html
+            segment-break-transformation-rules-026.html
+            segment-break-transformation-rules-027.html
+            segment-break-transformation-rules-028.html
+            segment-break-transformation-rules-029.html
+            segment-break-transformation-rules-030.html
+            segment-break-transformation-rules-031.html
+            segment-break-transformation-rules-032.html
+            segment-break-transformation-rules-033.html
+            segment-break-transformation-rules-034.html
+            segment-break-transformation-rules-035.html
+            segment-break-transformation-rules-036.html
+            segment-break-transformation-rules-037.html
+            segment-break-transformation-rules-038.html
+            segment-break-transformation-rules-039.html
+            segment-break-transformation-rules-040.html
+            segment-break-transformation-rules-041.html
+            segment-break-transformation-rules-042.html
+            segment-break-transformation-rules-043.html
+            segment-break-transformation-rules-044.html
+            segment-break-transformation-rules-045.html
+            segment-break-transformation-rules-046.html
+            segment-break-transformation-rules-047.html
+            segment-break-transformation-rules-048.html
+            segment-break-transformation-rules-049.html
+          </wpt>
+        <li>Otherwise, if the <a>writing system</a> of the <a>segment break</a>
+          is <a for=writing-system>Chinese</a>, <a for=writing-system>Japanese</a>, or Yi,
+          and the character before or after the [=segment break=]
+          is punctuation or a symbol (Unicode <a>general category</a> P* or S*)
+          and has an <a>East Asian Width property</a> of <code>Ambiguous</code>,
+          and the character on the other side of the [=segment break=] is
+          <code>Fullwidth</code>, <code>Wide</code>, or <code>Halfwidth</code>,
+          and not Hangul,
+          then the [=segment break=] is removed.
+
+          <wpt>
+            writing-system/writing-system-segment-break-001.html
+          </wpt>
+        <li>Otherwise, the [=segment break=] is converted to a space (U+0020).
+      </ul>
+
+      <p>
+        For this purpose,
+        Emoji (Unicode property <code>Emoji</code>)
+        with an <a>East Asian Width property</a> of
+        <code>Wide</code> or <code>Neutral</code>
+        are treated as having an <a>East Asian Width property</a> of
+        <code>Ambiguous</code>.
+
+      <p class="note">Note: The white space processing rules have already
+        removed any [=tabs=] and [=spaces=] after the [=segment break=] before these checks
+        take place.</p>
+
+      <div class="example">
+        The purpose of the segment break transformation rules
+        (and white space collapsing in general)
+        is to “unbreak” text that has been
+        <a href="#white-space-processing">broken into segments</a>
+        to make the document source code easier to work with.
+        In languages that use word separators, such as English and Korean,
+        “unbreaking” a line requires joining the two lines with a [=space=].
+
+        <figure>
+          <pre>
+            Here is an English paragraph
+            that is broken into multiple lines
+            in the source code so that it can
+            more easily read in a text editor.
+          </pre>
+          <p>Here is an English paragraph that is broken into multiple lines in the source code so that it can be more easily read in a text editor.</p>
+          <figcaption>
+            Eliminating a line break in English requires maintaining a [=space=] in its place.
+          </figcaption>
+        </figure>
+
+        In languages that have no word separators, such as Chinese,
+        “unbreaking” a line requires joining the two lines with no intervening space.
+
+        <figure>
+          <pre>
+            这个段落是呢么长，
+            在一行写不行。最好
+            用三行写。
+          </pre>
+          <p>这个段落是呢么长，在一行不行。最好用三行写。</p>
+          <figcaption>
+            Eliminating a line break in Chinese requires eliminating any intervening [=white space=].
+          </figcaption>
+        </figure>
+
+        The segment break transformation rules thus use adjacent context
+        to either transform the segment break into a space
+        or eliminate it entirely.
+      </div>
+
+      <p class="feedback issue">Comments on how well these rules would work in practice would
+        be very much appreciated, particularly from people who work with
+        Thai and similar scripts.
+        Note that browser implementations do not currently follow these rules consistently
+        (although IE does in some cases transform the break,
+        and Firefox follows the first two bullet points).</p>
+
   <h3 id="tab-size-property" caniuse="css3-tabsize" oldids="tab-size">
     Tab Character Size: the 'tab-size' property</h3>
 
