W3C home > Mailing lists > Public > www-style@w3.org > May 2012

Re: [css3-text] feedback on 'word-break: keep-all;'

From: Ambrose LI <ambrose.li@gmail.com>
Date: Thu, 3 May 2012 10:30:43 -0400
Message-ID: <CADJvFOVu0=R30Q-QN8BCN2AoJKp8UbUJ-DABDr-fNSVq877e3g@mail.gmail.com>
To: "Kang-Hao (Kenny) Lu" <kennyluck@csail.mit.edu>
Cc: WWW Style <www-style@w3.org>
2012/5/3 Kang-Hao (Kenny) Lu <kennyluck@csail.mit.edu>:
> The current prose for this is
>  # ‘keep-all’
>  #
>  #   Lines may break only at word separators and other explicit break
>  #   opportunities. Otherwise this option is equivalent to ‘normal’.
>  #   This option is mostly used where word separator characters are
>  #   present to create line-breaking opportunities, as in Korean.
> . This is certainly less vague than what was previous written (CJK text
> and non-CJK text, IIRC), but I have a question and a feedback:
> 1. What does "other explicit break opportunities" mean? forced breaks? I
> should note that IE9 breaks after hyphen even if "keep-all" is
> specified, is it following the spec? In any case, I think this should be
> the specced behavior as I think it's weird if 'word-break: keep-all' has
> side effect like this for Korean authors.
> 2. Word separators include nbsp but IE9 doesn't break at nbsp when
> "keep-all" is specified and I think nbsp should be excluded here.

Personally opinions here only, but breaking at hyphens
indiscriminately cannot be right. Even in English there are many
scenarios where indiscriminate breaking at hyphens is intuitively
wrong (short prefixes like e- or co-, phone numbers, unit or street
numbers in addresses, and so on), so I don’t know why IE does that.

On the other hand, nbsp is the “non-breaking space”, so by
construction nbsp must not a valid break point unless the user
overrides that assumption.

My two cents.
-ambrose <http://gniw.ca>
Received on Thursday, 3 May 2012 14:31:16 UTC

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