Re: [css3-text] Appendix F not needed

Koji Ishii wrote:

> > Koji, I'm not saying line breaking behavior should be defined only in
> > UAX14 or that you shouldn't include exceptions for specific codepoints in a property
> > definition, I'm simply saying the need to list a set of codepoints is unnecessary since
> > they are already defined in UAX14.
> 
> Thanks for the clarification, that is helpful. Am I right to
> understand that you're asking to remove code points that are
> defined in both specs?

No, I'm saying remove Appendix F in the Text spec and refer to
LineBreak = CJ in Unicode instead.  As my daughter would say,
easy peasy, lemon squeezy.

> I'm not strongly oppose to the idea, but also I do not see
> values of doing so either. There's some risk that, since
> UAX14 may change over time, we may have to tweak the list
> as UAX14 changes if we try to do so. Having a list of what
> we want to make sure in our spec doesn't seem to harm
> anyone.

CSS specs should avoid being the repositories of character-level
property information like Appendix F.  That's fundamentally the role
of Unicode specs.  If we need to explicitly list exceptions/deltas on
top of categories defined in Unicode, we can, but it's best for
everyone if those changes are pushed to Unicode instead.

1. Edit:

  Following breaks be forbidden in ‘strict’ line breaking and allowed in ‘normal’ and ‘loose’:
  * breaks before Japanese small kana
  * breaks before the Katakana-Hiragana prolonged sound mark: ー U+30FC, ｰ U+FF70

  Change to:

  Following breaks be forbidden in ‘strict’ line breaking and allowed in ‘normal’ and ‘loose’:
  * breaks before Japanese small kana and sound marks (Unicode Line Break property == 'CJ' as 
    defined within LineBreak.txt in the Unicode Character Database).

2. Remove Appendix F

Regards,

John Daggett

Received on Monday, 10 December 2012 04:46:10 UTC