W3C home > Mailing lists > Public > www-style@w3.org > November 2013

Re: [CSSWG][css-text-3] CSS3 Text Last Call Working Draft

From: Koji Ishii <kojiishi@gluesoft.co.jp>
Date: Wed, 13 Nov 2013 23:17:32 -0500
To: CE Whitehead <cewcathar@hotmail.com>, "fantasai.lists@inkedblade.net" <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <CEAA6F96.4D33E%kojiishi@gluesoft.co.jp>
These are beyond my English capability, I'll consult with someone to get back to you.

From: CE Whitehead <cewcathar@hotmail.com<mailto:cewcathar@hotmail.com>>
Date: Friday, November 8, 2013 12:21 PM
To: fantasai <fantasai.lists@inkedblade.net<mailto:fantasai.lists@inkedblade.net>>, "www-style@w3.org<mailto:www-style@w3.org>" <www-style@w3.org<mailto:www-style@w3.org>>
Subject: RE: [CSSWG][css-text-3] CSS3 Text Last Call Working Draft
Resent-From: <www-style@w3.org<mailto:www-style@w3.org>>
Resent-Date: Friday, November 8, 2013 12:21 PM

5.1, par 1, 3rd bullet

"As long as care is taken to avoid such awkward breaks, allowing breaks at appropriate punctuation other than spaces is recommended, as it results in more even-looking margins, particularly in narrow measures. "
{ COMMENT on Content:  "recommended"? I am not sure that this practice is always "recommended" in languages such as English and French,  when the column width/text box width is not narrow; however breaking longer urls at slashes might be recommended in most every language (you do not mention urls; but that's a common instance where text  is broken where there are no spaces). But I am not sure that you should use the word "recommended" when talking about breaking of standard written prose. Also I am confused about the word "such." What "such awkward breaks" are you referring to?

=>
"As long as care is taken to avoid awkward breaks (such as ?), allowing breaks at appropriate punctuation other than spaces is acceptable in some cases, particularly when the text must fit into a narrow width, as it results in more even-looking margins."


5.2 2nd or 3rd par? 1rst bulleted item
 "Following breaks be forbidden in ‘strict’ line breaking and allowed in ‘normal’ and ‘loose’:

    breaks before Japanese small kana or the Katakana-Hiragana prolonged sound mark: i.e. characters with the Unicode Line Break property CJ. (See LineBreak.txt in [UNICODE].) "

{ COMMENT/QUESTION: Don't you mean, "The following breaks . . . ??" I think you have omitted the definite article here.    I have the same comment on the second bulleted item, "Following breaks be forbidden in ‘normal’ and ‘strict’ line breaking and allowed in ‘loose’" => "The following breaks be forbidden in . . . "; in any case, I think this whole set of bulleted items might benefit from rewording; I particularly did not like breaking up "that" and "be forbidden"; in my rewrite, I've used * to indicate the outer bullet and + to indicate the inner one }

"However, this specification does require that:

  *  Following breaks be forbidden in ‘strict’ line breaking and allowed in ‘normal’ and ‘loose’:
      +  breaks before Japanese small kana or the Katakana-Hiragana prolonged sound mark: i.e. characters with the Unicode Line Break property CJ. (See LineBreak.txt in [UNICODE].)
     If the content language is Chinese or Japanese, then additionally allow (but otherwise forbid) for ‘normal’ and ‘loose’:
      +  breaks before hyphens:
        ‐ U+2010, – U+2013, 〜 U+301C, ゠ U+30A0
  *  Following breaks be forbidden in ‘normal’ and ‘strict’ line breaking and allowed in ‘loose’:
      +   breaks before iteration marks:
        々 U+3005, 〻 U+303B, ゝ U+309D, ゞ U+309E, ヽ U+30FD, ヾ U+30FE
      +  breaks between inseparable characters such as ‥ U+2025, … U+2026 i.e. characters with the Unicode Line Break property IN. (See LineBreak.txt in [UNICODE].)
     If the content language is Chinese or Japanese, then additionally allow (but otherwise forbid) for ‘loose’:
       +  breaks before certain centered punctuation marks:
          : U+003A, ; U+003B, ・ U+30FB, : U+FF1A, ; U+FF1B, ・ U+FF65, ! U+0021, ? U+003F, ‼ U+203C, ⁇ U+2047, ⁈ U+2048, ⁉ U+2049, ! U+FF01, ? U+FF1F
      +  breaks before suffixes:
        % U+0025, ¢ U+00A2, ° U+00B0, ‰ U+2030, ′ U+2032, ″ U+2033, ℃ U+2103, % U+FF05, ¢ U+FFE0
      +  breaks after prefixes:
        № U+2116 and all currency symbols (Unicode general category Sc) other than ¢ U+00A2 and ¢ U+FFE0 "

=>

"However, this specification requires the  following:

  *  The following breaks are/must be forbidden in ‘strict’ line breaking and allowed in ‘normal’ and ‘loose’:
       + breaks before Japanese small kana or the Katakana-Hiragana prolonged sound mark: i.e. characters with the Unicode Line Break property CJ. (See LineBreak.txt in [UNICODE].)
    If the content language is Chinese or Japanese, then additionally allow (but otherwise forbid) for ‘normal’ and ‘loose’:
       + breaks before hyphens:
        ‐ U+2010, – U+2013, 〜 U+301C, ゠ U+30A0
 * The following breaks are/must be forbidden in ‘normal’ and ‘strict’ line breaking and allowed in ‘loose’:
       + breaks before iteration marks:
        々 U+3005, 〻 U+303B, ゝ U+309D, ゞ U+309E, ヽ U+30FD, ヾ U+30FE
       + breaks between inseparable characters such as ‥ U+2025, … U+2026 i.e. characters with the Unicode Line Break property IN. (See LineBreak.txt in [UNICODE].)
    If the content language is Chinese or Japanese, then additionally allow (but otherwise forbid) for ‘loose’:
       + breaks before certain centered punctuation marks:
        : U+003A, ; U+003B, ・ U+30FB, : U+FF1A, ; U+FF1B, ・ U+FF65, ! U+0021, ? U+003F, ‼ U+203C, ⁇ U+2047, ⁈ U+2048, ⁉ U+2049, ! U+FF01, ? U+FF1F
       + breaks before suffixes:
        % U+0025, ¢ U+00A2, ° U+00B0, ‰ U+2030, ′ U+2032, ″ U+2033, ℃ U+2103, % U+FF05, ¢ U+FFE0
       + breaks after prefixes:
        № U+2116 and all currency symbols (Unicode general category Sc) other than ¢ U+00A2 and ¢ U+FFE0 "

7.3.1 par 2

"Similarly, when space is distributed an expansion opportunity between two characters, it is applied under the same rules as for ‘letter-spacing’. "

{ COMMENT: I think you have omitted a preposition here? Do you mean, "distributed TO an expansion opportunity"?}

=>
"Similarly, when space is distributed to an expansion opportunity between two characters, it is applied under the same rules as for ‘letter-spacing’. "

Received on Thursday, 14 November 2013 04:17:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:36 UTC