W3C home > Mailing lists > Public > public-i18n-cjk@w3.org > July to September 2012

Re: [css3-text] Korean should be added to enable additional line breaking rule sets

From: Glenn Adams <glenn@skynav.com>
Date: Mon, 17 Sep 2012 11:44:07 +0800
Message-ID: <CACQ=j+dNf4sKBArO64j_O8aCxK5vpugGoQQFjQmU=J6DojAYOw@mail.gmail.com>
To: Sangwhan Moon <sangwhan.moon@hanmail.net>
Cc: Koji Ishii <kojiishi@gluesoft.co.jp>, "www-style@w3.org" <www-style@w3.org>, "CJK discussion (public-i18n-cjk@w3.org)" <public-i18n-cjk@w3.org>, "HTML Korean Interest Group (public-html-ig-ko@w3.org)" <public-html-ig-ko@w3.org>, Florian Rivoal <frivoal@gmail.com>
> -----Original Message-----
> From: Sangwhan Moon [mailto:sangwhan.moon@hanmail.net]
> Sent: Sunday, September 16, 2012 11:19 AM
> To: Koji Ishii
> Cc: www-style@w3.org; CJK discussion (public-i18n-cjk@w3.org); HTML
> Korean Interest Group (public-html-ig-ko@w3.org); Florian Rivoal
> Subject: Re: [css3-text] Korean should be added to enable additional line
> breaking rule sets
> A quick review lead to the impression that the complexity needed to
> implement this is overwhelming for
> the benefits it provides - unless there is a absolute need for some of the
> exceptions, I believe this should
> be handled in a more pragmatic approach to reduce overall overhead needed
> for rendering text.

I would not agree that this is too complex to implement, since I recently
implemented it for Webkit without much difficulty. [1]

> Especially, I find "normal" to be too strict, as this is something that
> will be executed for every single piece of
> CJK text that will be rendered from a implementation - I strongly believe
> that putting a potential performance
> degradation on the default property is overkill unless absolutely
> necessary.

As Koji noted, the default is 'auto', not 'normal', and it is up to the UA
implementer to determine what 'auto' means. I have chosen a particular
interpretation [2] for my implementation, which does not measurably degrade
performance. [3]

not all UA implementors are CJK speakers (there aren't many of us who are
> also UA developers) non-normative examples of the rationale is probably
> necessary

Although I am not a native CJK speaker, I had no problem implementing this
feature, so this is not a relevant comment I think.

> so I believe this case should also be covered in the same (C)JK scope if
> possible. (Note: Chinese probably doesn't apply, although I have seen
> usages of ¥ instead of 元, only in ROC and only in a handwritten context.

I'm not sure if you are suggesting that CJK languages should all be treated
the same here or not. I believe they should; that is, where the current
CSS3 Text draft says "Chinese or Japanese", it should instead say "CJK
languages" or "Chinese, Japanese, or Korean". This will improve
interoperability and consistency of behavior.

Glenn Adams

[1] https://bugs.webkit.org/attachment.cgi?id=164255&action=prettypatch
[2] https://trac.webkit.org/wiki/LineBreakingCSS3Mapping
[3] https://bugs.webkit.org/attachment.cgi?id=163844
Received on Monday, 17 September 2012 03:44:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:59:17 UTC