Nickname:
Title:
State: OPEN CLOSED
Product: None activity appmanifest browser implementations charmod-norm chrome/blink clreq contacts-api css-background css-counter-styles css-flexbox css-fonts css-garc css-inline css-lists css-ruby css-shapes css-syntax css-text css-text-decoration css-ui css-variables css-writing-modes data-on-web-best-practices dpub-annotation-uc dpub-aria dpub-latinreq encoding file-uri find-text hdtime2 html html-longdesc html5-markup ilreq its klreq linked-data-patch-format media-capture-and-streams none notifications polyglot precis presentation-api qt31 rdf service-workers tabular-data-json tabular-data-model tabular-data-rdf tabular-metadata tracking-compliance tracking-dnt turtle unicode-xml url utr51 vehicle-information-access wcag web-packaging web-payments-use-cases webstorage webvtt1 woff xslt-30
Raised By: Matitiahu Allouche Eemeli Aro Fátima Baña Bert Bos David Clarke Andrew Cunningham Martin Dürst Elika Etemad Richard Ishida Koji Ishii John Klensin Tatsuo KOBAYASHI Toshi Kobayashi Aharon Lanin Jason Linehan Yoichiro Nagao Erik Nordin Yuki Okushi Addison Phillips Oliver Renwick Florian Rivoal Felix Sasaki Atsushi Shimono Santhosh Thottingal Najib Tounsi Bobby Tung Fuqiao Xue François Yergeau Junichi Yoshii Richard Ishida
Description: THREAD: http://www.w3.org/Mail/flatten/index?subject=I18N-ISSUE-316&list=www-style 5. Line Breaking and Word Boundaries http://www.w3.org/TR/2013/WD-css-text-3-20131010/#line-breaking "CSS does not fully define where soft wrap opportunities occur, however some controls are provided to distinguish common variations" I think that, for the sake of interoperability, the CSS spec should require the use of UAX14 as a default for line breaking behaviour. It should also state that the rules in UAX14 may need tailoring for certain scripts, and that the properties specified in this section assist the user in controlling line breaking behaviour. Text in the spec such as the definition of word-break: normal, which says "Words break according to their usual rules", would then provide a little more guidance to the implementor.
Add notes (no markup allowed, URIs get automatically hyperlinked):
WG comment.
[aphillip]: want to ask CSS to make normative, possibly as SHOULD
https://github.com/w3c/i18n-activity/issues/91