- From: Aharon (Vladimir) Lanin <aharon@google.com>
- Date: Wed, 29 Sep 2010 12:26:11 +0200
- To: public-i18n-bidi@w3.org
- Message-ID: <AANLkTi=x04xBdiGLYfZN2yaF92o2=1m=57VsRr3ToidB@mail.gmail.com>
I have sent to Richard Ishida of the i18n WG the bugs to be filed on HTML5, so the i18n WG can track them. Sometime today, they will become visible on http://www.w3.org/International/reviews/0802-html5/ (it's numbers 9 through 30), and Richard will mass-upload them to the HTML WG database. (Wipe tears of happiness and exhaustion ...) At about the same time, Richard will also make available another editor's draft of the proposal ( http://www.w3.org/International/docs/html-bidi-requirements/), where I've updated sections 2.2 (first-strong now exactly aqs in UBA), 3.4, 3.6, 3.10 (does not yet include the proposed new CSS property, though), and 3.12. I will be offline until Monday. Regards to all! Aharon On Mon, Sep 27, 2010 at 10:19 PM, Aharon (Vladimir) Lanin <aharon@google.com > wrote: > I have checked in an intermediate draft of the proposal and Richard has > made it available at > http://www.w3.org/International/docs/html-bidi-requirements/. > > This draft is only meant to be suitable as a reference for the HTML5 bugs, > which I am about to start filing. I still have not updated a number of > sections of this draft, mostly ones without HTML implications (e.g. limited > to CSS), and have not made any of the stylistic changes that have been > recommended over the past year. I intend to do that after the HTML5 deadline > rush. > > Section 2.2 (Support auto-direction) is not in its final state either. It > still has first-strong defined as returning LTR for numbers, which was > challenged today, and does not include autodirmethod=plaintext. There are > two reasons for the latter: the open issues in the plaintext spec, and lack > of time. I will be happy to put it in if and when we get it ironed out. > > Here are the bugs that I see being filed on the basis of each section. *** > Important ***: please make sure that I have addressed (HTML vs CSS vs > Ecmascript) things correctly. > > 2.1: > - (HTML) ubi=ubi|""|off attribute. Asking WG to decide whether ubi value > should be "on" instead. > > 2.2 (update not complete): > - (HTML) dir=auto value, autodirmethod=first-strong|any-rtl|plaintext. The > last value may or may not make it in, depending on how ready it is. > > 2.3: > - (HTML) submitdir attribute (pure boolean) > > 2.4: > - (CSS) rtlflip keyword in background-image, list-style-image etc. Asking > WG to decide whether instead of rtlflip, ltr and rtl keywords. > > 3.1: > - (HTML) bidibreak=soft|hard attribute. > > 3.2: > - (HTML) LINE SEPARATOR (U+2028) and PARAGRAPH SEPARATOR (U+2029) in <textarea> > and in elements with white-space:pre|pre-line|pre-wrap should break lines > - (HTML) line breaks and PARAGRAPH SEPARATOR (U+2029) in <textarea> and in > elements with white-space:pre|pre-line|pre-wrap should act as UBA paragraph > breaks > - (Ecmascript?) line breaks and LINE SEPARATOR (U+2028) and PARAGRAPH > SEPARATOR (U+2029) in dialog text. > > 3.3: > - (HTML) block-display elements should act as UBA paragraph breaks > - (HTML) block element with display-inline to have ubi=ubi by default > instead of embedding > > 3.4 (not yet updated): > - (Ecmascript?) script dialog text direction > - (Ecmascript?) Unicode spec re Default Ignorable Code Points applies to > directional formatting characters in dialog text > - (Ecmascript) support optional direction parameter in alert(), confirm(), > and prompt() > > 3.5 (not yet updated): > - (HTML) <title> supports and inherits dir attribute > - (HTML) Unicode spec re Default Ignorable Code Points applies > to directional formatting characters in <title> > > 3.6 (not yet updated): > - (HTML) titledir attribute and title attribute value direction > - (HTML) alt attribute value direction > - (HTML) Unicode spec re Default Ignorable Code Points applies > to directional formatting characters in title attribute > - (HTML) Unicode spec re Default Ignorable Code Points applies > to directional formatting characters in alt attribute > > 3.7: > - (HTML) <option> supports dir attribute, even after it has been selected. > - (HTML) <option> supports align attribute, even after it has been > selected. > > 3.8 > - (HTML) setting <input> and <textdir> direction through browser UI should > set the dir attribute and trigger oninput event > - (HTML) on an OS that has a widespread convention for setting direction, user > agent should support it > > 3.9 > - (HTML) when an input value is remembered, its direction should be > remembered too > > 3.10 (not updated) > - (CSS) list-style-direction property > > 3.11 > - (CSS) location of user agent window's overall vertical scrollbar > > 3.12 (not updated) > - (CSS) location of vertical scrollbar of an element when it is not the user > agent window's overall vertical scrollbar > > 3.13 (not written) > - (CSS) "match-parent" value for text-align property >
Received on Wednesday, 29 September 2010 10:27:29 UTC