Edit ISSUE-167: Example of Bidirectional Text ⓒ

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-167&list=www-style Example of Bidirectional Text http://dev.w3.org/csswg/css3-writing-modes/#bidi-example I've been meaning to say for some years now that this is a very bad example. It should use dedicated bidi specific markup (see http://www.w3.org/International/questions/qa-bidi-css-markup#markup "You should therefore use dedicated bidi markup whenever it is available. Do not simply attach CSS styling to a general element to achieve the effect."). Here is an proposal for an alternative version of parts of the example. <HEBREW dir="rtl"> <PAR>HEBREW1 HEBREW2 english3 HEBREW4 HEBREW5</PAR> <PAR>HEBREW6 <EMPH>HEBREW7</EMPH> HEBREW8</PAR> </HEBREW> <ENGLISH dir="ltr"> <PAR>english9 english10 english11 HEBREW12 HEBREW13</PAR> <PAR>english14 english15 english16</PAR> <PAR>english17 <HE-QUO dir="rtl">HEBREW18 english19 HEBREW20</HE-QUO></PAR> </ENGLISH> /* Rules for bidi */ *[dir=rtl] {direction: rtl; unicode-bidi: embed;} *[dir=ltr] {direction: ltr; unicode-bidi: embed;} These generic style rules should be what goes in the separate style sheet. Also, we recommend not using bidi markup unless you need to change the base direction, so if this document had an overall base direction of ltr (either by default, or via <ROOT dir="ltr">), you wouldn't need to have the dir="ltr" after ENGLISH. It may be worth adding a note to that effect. It's also confusing that the markup is in uppercase, since the uppercase is used to indicate Hebrew characters. Unless you are trying to make a point that the markup uses hebrew element names (which I don't think is necessary here), they should probably be in lowercase.

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