[CSSWG][css-writing-modes] Last Call for Comments on CSS3 Writing Modes

[fantasai]

The CSS WG has published a Last Call Working Draft of CSS Writing Modes
Level 3:

http://www.w3.org/TR/css-writing-modes-3/

CSS Writing Modes Level 3 defines CSS handling of various international
writing modes, such as left-to-right (e.g. Latin or Indic), right-to-left
(e.g. Hebrew or Arabic), bidirectional (e.g. mixed Latin and Arabic) and
vertical (e.g. Asian scripts).

Recent changes are listed at:
http://www.w3.org/TR/2013/WD-css-writing-modes-3-20131126/#changes

Please send any comments to the www-style mailing list, <www-***@w3.org>,
and please, prefix the subject line with

[css-writing-modes]

(as I did on this message). The deadline for comments is

** 24 December 2013 **

Please let us know if you need an extension, so that we know
to wait for your comments.

For the CSS WG,
~fantasai

[Asmus Freytag]

The very first "note" in the draft overlays and obscures part of the
illustration in the sidebar.
Observed in Firefox.

The note is also not as helpful as perhaps imagined and rather
distracting from the task of understanding the concepts that are
actually used. Esp. for someone reading this for the first time.

[Tab Atkins Jr.]

Post by Asmus Freytag
The very first "note" in the draft overlays and obscures part of the
illustration in the sidebar.
Observed in Firefox.

I can't do any editing at the moment, but some notes for fantasai:

The fix is just making the note a BFC. Do you think we should fix it
in this one spot with a targeted overflow:hidden, or should we add it
to all notes/issues?

~TJ

[Alan Gresley]

Post by Tab Atkins Jr.

Post by Asmus Freytag
The very first "note" in the draft overlays and obscures part of the
illustration in the sidebar.
Observed in Firefox.

The fix is just making the note a BFC. Do you think we should fix it
in this one spot with a targeted overflow:hidden, or should we add it
to all notes/issues?
~TJ

Possibly all notes and issues and use overflow:auto since any widths
also applied to the notes and issues may end up having things hidden.

Alan

[Koji Ishii]

Post by Alan Gresley
Possibly all notes and issues and use overflow:auto since any widths
also applied to the notes and issues may end up having things hidden.

Thank you Alan for the suggestion, fixed in the editor's draft[1].

[1] http://dev.w3.org/csswg/css-writing-modes/

[Aharon (Vladimir) Lanin]

Hixie filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=24006 on Writing
Modes in the beginning of December, and I added some comments there. It
does not seem to have been addressed yet.

Post by fantasai
The CSS WG has published a Last Call Working Draft of CSS Writing Modes
http://www.w3.org/TR/css-writing-modes-3/
CSS Writing Modes Level 3 defines CSS handling of various international
writing modes, such as left-to-right (e.g. Latin or Indic), right-to-left
(e.g. Hebrew or Arabic), bidirectional (e.g. mixed Latin and Arabic) and
vertical (e.g. Asian scripts).
http://www.w3.org/TR/2013/WD-css-writing-modes-3-20131126/#changes

,

and please, prefix the subject line with
[css-writing-modes]
(as I did on this message). The deadline for comments is
** 24 December 2013 **
Please let us know if you need an extension, so that we know
to wait for your comments.
For the CSS WG,
~fantasai

[fantasai]

Post by Aharon (Vladimir) Lanin
Hixie filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=24006 on
Writing Modes in the beginning of December, and I added some comments
there. It does not seem to have been addressed yet.

Thanks for punting that to the ML.

Wrt the paragraph beginning "In general...", it has been revised:

# In CSS, the paragraph embedding level must be set (following rule HL1)
# according to the direction property of the paragraph’s containing
# block rather than by the heuristic given in steps P2 and P3 of the
# Unicode algorithm. There is, however, one exception: when the
# computed unicode-bidi of the paragraph’s containing block is
# 'plaintext', the Unicode heuristics in P2 and P3 are used as
# described in [UAX9], without the HL1 override.

Wrt referring to the HL* rules, the bidi spec does not appear to require
such references, only that modifications to the algorithm conform to
those rules. However I have added the references as you request to help
clarify the intent.

Wrt using "must" everywhere, whether one agrees or disagrees with the style,
it is not a habit of the CSS specs to do so, and statements without the
modifier are nonetheless normative per
http://www.w3.org/TR/css3-writing-modes/#conventions

Post by Aharon (Vladimir) Lanin

is "the bidi control codes assigned to the end" defined anywhere?

Yes, the control codes are defined under the various unicode-bidi
values [..] But I agree that some sort of reference is needed.

Since this sentence is only a few paragraphs below the section that
defines them, I haven't added a link. But all of them are now talking
about rule HL3, so this will help create that correspondance.

Post by Aharon (Vladimir) Lanin
I now realize, however, that the spec does not make it 100% clear for
isolate-override whether it "combines" the isolate on the outside of
the override or vice-versa.

This is now specified explicitly.

Comment #2 is handled separately, see thread at
http://lists.w3.org/Archives/Public/www-style/2014Feb/0267.htm

Updated ED: http://dev.w3.org/csswg/css-writing-modes/

Please let me know if this sufficiently addresses the comment.

~fantasai

[Aharon (Vladimir) Lanin]

Thanks, looks great!

Just one nit: HL1 etc. are not rules. UAX9 referes to the HLs as "clauses".
So, the references to them should be something like "clause HLx of [UAX9]".

Post by fantasai

Post by Aharon (Vladimir) Lanin
Hixie filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=24006 on
Writing Modes in the beginning of December, and I added some comments
there. It does not seem to have been addressed yet.

Thanks for punting that to the ML.
# In CSS, the paragraph embedding level must be set (following rule HL1)
# according to the direction property of the paragraph’s containing
# block rather than by the heuristic given in steps P2 and P3 of the
# Unicode algorithm. There is, however, one exception: when the
# computed unicode-bidi of the paragraph’s containing block is
# 'plaintext', the Unicode heuristics in P2 and P3 are used as
# described in [UAX9], without the HL1 override.
Wrt referring to the HL* rules, the bidi spec does not appear to require
such references, only that modifications to the algorithm conform to
those rules. However I have added the references as you request to help
clarify the intent.
Wrt using "must" everywhere, whether one agrees or disagrees with the style,
it is not a habit of the CSS specs to do so, and statements without the
modifier are nonetheless normative per
http://www.w3.org/TR/css3-writing-modes/#conventions

Post by Aharon (Vladimir) Lanin
is "the bidi control codes assigned to the end" defined anywhere?
Yes, the control codes are defined under the various unicode-bidi
values [..] But I agree that some sort of reference is needed.

Since this sentence is only a few paragraphs below the section that
defines them, I haven't added a link. But all of them are now talking
about rule HL3, so this will help create that correspondance.
I now realize, however, that the spec does not make it 100% clear for

Post by Aharon (Vladimir) Lanin
isolate-override whether it "combines" the isolate on the outside of
the override or vice-versa.

This is now specified explicitly.
Comment #2 is handled separately, see thread at
http://lists.w3.org/Archives/Public/www-style/2014Feb/0267.htm
Updated ED: http://dev.w3.org/csswg/css-writing-modes/
Please let me know if this sufficiently addresses the comment.
~fantasai

[fantasai]

Post by Aharon (Vladimir) Lanin
Thanks, looks great!
Just one nit: HL1 etc. are not rules. UAX9 referes to the HLs as
"clauses". So, the references to them should be something
like "clause HLx of [UAX9]".

Fixed!

~fantasai