- From: ±è¿µº¸ <tonextday@gmail.com>
- Date: Sun, 6 May 2012 04:18:05 +0900
- To: Wonsuk Lee <wonsuk73@gmail.com>
- Cc: Koji Ishii <kojiishi@gluesoft.co.jp>, "HTML Korean Interest Group (public-html-ig-ko@w3.org)" <public-html-ig-ko@w3.org>, "CJK discussion (public-i18n-cjk@w3.org)" <public-i18n-cjk@w3.org>
- Message-ID: <CAD3J0QwZ0jKuiBKvL02Tdv++aK=UZ+mK-w_woZ6GzyjOvT7b5g@mail.gmail.com>
I am sorry. A whole sentence was not read, written different conclusion. Generally, the balance of a line is important. therefore, a default value - word-break:keep-all; - it is not suit. /* Korean prefers to break only at spaces */ :root:lang(ko) { word-break: keep-all; } word-break:break-all is more suit. :root:lang(ko) { word-break: break-all; } 2012/5/5 ±è¿µº¸ <tonextday@gmail.com> > Hello. > My name is YoungBo Kim. > I agree your opinion bellow. > "Years ago I was told from my Korean colleague that Korean line breaking > rules should be the same as English and CJ rules should not apply" > > Korean language - Hanguel, space is not used line breaking. Space is > inserted in order to classify the meaning of a character. It is clear that > the purpose and a function differ from space used by CJ. > It differs from using space, in order to change into Kanji. > > I don't test bellow style rules. > /* Korean prefers to break only at spaces */ > :root:lang(ko) { > word-break: keep-all; > } > > Thanks. > > 2012/5/5 Wonsuk Lee <wonsuk73@gmail.com> > >> Hi. Koji. >> Thanks for email. >> >> 2012/5/5 Koji Ishii <kojiishi@gluesoft.co.jp>: >> > Hello, >> > >> > Can someone please help me to figure out an issue in CSS Text Level 3? >> > >> > The current CSS Text Level 3 has informative appendix for the default >> UA stylesheet[1], which contains: >> > >> > /* Korean prefers to break only at spaces */ >> > :root:lang(ko) { >> > word-break: keep-all; >> > } >> > >> > The "word-break: keep-all"[2] disallows breaking between CJK characters >> and make line breaking rules just like English. Years ago I was told from >> my Korean colleague that Korean line breaking rules should be the same as >> English and CJ rules should not apply, so we put this. But Example 3 of >> UAX#14, 8.2 Examples of Customization[3] says: >> > >> >> Depending on the nature of the document, Korean either uses implicit >> >> breaking around characters Space-based layout is common in magazines >> >> and other informal documents with ragged margins, while books, with >> >> both margins justified, use the other type, as it affords more line >> break >> >> opportunities and therefore leads to better justification. >> > >> > If this behavior depends on documents, and most sites do not use >> "word-break: keep-all" today (as far as I observed quickly,) I guess it's >> probably wrong to put "word-break: keep-all" into the UA default stylesheet. >> > >> > I proposed removal of this to the www-style[4], but could someone >> please confirm if my understanding is correct? >> >> Frankly I am not expert in this domain. So after got your email, I >> closely looked at physical things like a Korean book, newspaper and >> magazine. But all of these I checked doesn't seems to use word >> separators and other explicit break opportunities. >> >> Therefore I would like to see other opinions from experts of Korean >> Interest Group. >> >> best regards, >> Wonsuk. >> >> >> > Thank you for your support in advance. >> > >> > [1] http://dev.w3.org/csswg/css3-text/#default-stylesheet >> > [2] http://dev.w3.org/csswg/css3-text/#word-break >> > [3] http://unicode.org/reports/tr14/#Examples >> > [4] http://lists.w3.org/Archives/Public/www-style/2012May/0132.html >> > >> > Regards, >> > Koji >> > >> >> >> >> -- >> >> ========================================= >> ÀÌ ¿ø ¼® (Wonsuk, Lee) / Principal Engineer, Ph.D >> SAMSUNG ELECTRONICS Co., LTD. (ß²àøï³í) >> Mobile: +82-10-5800-3997 >> E-mail: wonsuk11.lee@samsung.com, wonsuk73@gmail.com >> http://www.wonsuk73.com/, twitter: @wonsuk73 >> ----------------------------------------- >> Inspire the World, Create the Future !!! >> ========================================= >> >> >
Received on Saturday, 5 May 2012 19:18:35 UTC