Re: [css-text] I18N-ISSUE-316: Line breaking defaults

On 10/22/2014 12:51 PM, Richard Ishida wrote:
> The i18n WG discussed this at and concluded that there should be
> normative wording to say that UAX14 SHOULD be followed except in those specific cases where issues arise (we don't think there
> are many besides the  kana characters, and mostly it's a question of encouraging those who haven't implemented UAX14 for a
> given set of characters to catch up those browsers that do).  See the test results below for details.

It's not an issue of kana characters, those are actually
normatively covered in the section on 'line-break'.

It's also not an issue of the non-tailorable sets you are
citing, since those are already normatively required also.

If you're asking about the BA category, in order to safely
make a normative requirement, I need it split into two sets:
   - characters after which a break is always permissible
     and recommended, such as the visible word separators
   - characters after which a break is sometimes a good
     idea but not always, such as hyphens and slashes

I will not issue a normative recommendation to honor BA
behavior of the second category. This will result in bad
line-breaking when implementations try to comply without
performing a thoughtful survey of each individual case
and what contextual information the line break may need
to consider. Please note that this is not a theoretical
concern: we have already run into this exact problem.


Received on Wednesday, 22 October 2014 22:13:34 UTC