Edit ISSUE-332: Lack of complete kashida description ⓒ

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 Addison Phillips

Description:
http://www.w3.org/2013/12/05-i18n-minutes.html Section 7.3. The I18N WG is aware that there is not a complete description of how kashida should be implemented--no "Arabic LREQ" similar to the "JLREQ" document--and that this makes interoperable styling that includes kashida difficult for implementers to contemplate and difficult for CSS to describe.

Add notes (no markup allowed, URIs get automatically hyperlinked):