Re: agenda+ css-writing-modes-3 review

Hi,

I've completed my review of the spec for issues 47 and 53 and have some
conclusions:

Issue 47:

Over all the text looks fine.

The 'note' in 3.1.1 I think should be removed. In SVG 1.1, the inline
-progression-direction only seems to play a role in the absence of
Unicode direction information so I don't think one needs to mention
that here. The second paragraph is clearly wrong based on SVG 1.1. It
is the 'direction' property that can cause text to shift (when coupled
with the 'text-anchor' property) and reverse the order of glyphs (with
'unicode-bidi' value 'bidi-override').

In 3.1.1.2, there seems to be an error in the UA stylesheet: it should
be 'horizontal-tb' not 'horizontal-tbl'.

The discussion of 'glyph-orientation' appears to match what we decided
at the Paris 2015 FXTF meeting.


Issue 53:

I think the answer is yes. In SVG 1.0 there were two places where the
values 'lr' and 'rl' could produce different results. The first is in
the actual layout of text. This can only effect non-Unicode text. As
Unicode is now ubiquitous, the need to specify an 'inline-progression
-direction' in not needed. For the one place it could have an effect,
determining the placement of Unicode ambiguous characters like '!', I
see no evidence that any renderer changed behavior based on these
values.
    
The second place in SVG 1.0 where the values could produce different
results is when coupled with the 'text-anchor' property. Here, SVG 1.1
(and SVG 1.2 Tiny) are very explicit that alignment is to be done
considering the 'direction' property. Whether or not this was a change
from SVG 1.0 is moot.


A more detail analysis can be found at:

 http://tavmjong.free.fr/SVG/WRITING_MODES/

Tav


On Thu, 2015-10-01 at 19:08 -0400, Doug Schepers wrote:
> Hi, Dirk, Amelia, Cameron–
> 
> We decided that we need (at least some of) you on the telcon to
> really 
> deal with this issue and help move the CSS Writing Modes 3 spec to
> CR.
> 
> Are you available to be on the telcon next week?
> 
> Tav is going to be reviewing the spec in depth, and you can
> coordinate 
> with him to provide feedback, if you can't be on the telcon.
> 
> Thanks–
> –Doug
> 
> On 9/30/15 9:58 PM, Doug Schepers wrote:
> > Hi, Erik–
> > 
> > Can we please add the CSS Writing Modes 3 spec review to the
> > agenda?
> > Fantasai says she needs our feedback on 2 issues (listed below),
> > and
> > she's available to attend the telcon tomorrow to explain the issue.
> > 
> > (Fantasai, telcon details below in Erik's original agenda email.)
> > 
> > [[
> > I'm blocked on the SVGWG here:
> > https://drafts.csswg.org/css-writing-modes-3/issues-cr-2014
> > 
> > Two issues require SVGWG review
> > 
> > first one is 
> > https://lists.w3.org/Archives/Public/www-svg/2015Sep/0016.html
> > 
> > That's the one that needs review of spec wording
> > 
> > second issue is this
> > https://lists.w3.org/Archives/Public/www-svg/2015Sep/0017.html
> > 
> > The question on hand is whether we can fold 'writing-mode: rl' and
> > 'writing-mode: lr' together
> > 
> >  From a CSS perspective, they're the same
> > 
> > The different values don't affect anything in the CSS model
> > 
> > They're both horizontal writing modes, and the rl vs. lr doesn't
> > affect
> > bidi
> > 
> > But the SVG spec says they affect the "inline progression
> > direction"
> > and I can't figure out what that means or should have an effect on
> > 
> > But it's quite clear that it doesn't affect reordering!
> > 
> > There's a test file here
> > https://lists.w3.org/Archives/Public/www-svg/2015Sep/att-0027/test.
> > svg
> > 
> > which does very interesting things in Presto
> > 
> > but otherwise renders the two values identically in Blink and
> > InkScape
> > 
> > So, yeah, have fun with that?
> > 
> > maybe someone in the group knows what the SVG spec was trying to
> > say,
> > and whether or not it was important
> > ]]
> > 
> > Regards–
> > –Doug
> > 
> > On 9/30/15 4:46 PM, Erik Dahlström wrote:
> > > Please find the agenda for this week’s telcon below.
> > > 
> > > Time:
> > > http://www.timeanddate.com/worldclock/fixedtime.html?month=10&day
> > > =1&year=2015&hour=20&min=30&sec=0&p1=0
> > > 
> > > 
> > > Phone: +1-617-324-0000 (access code: 649 040 824)
> > > IRC for minutes/discussion: #svg on irc.w3.org, port 6665
> > > Agenda requests: http://www.w3.org/Graphics/SVG/WG/wiki/Agenda
> > > WebEx logistics: https://www.w3.org/Graphics/SVG/WG/wiki/WebEx
> > > 
> > > Agenda:
> > > 
> > > * Path stroking for paths that end with tight curves (Tav)
> > >    http://tavmjong.free.fr/blog/?p=1257
> > > 
> > > * Declarative animation and conformance
> > >    https://github.com/w3c/svgwg/issues/23
> > > 
> > > * SVG 2 chapter progress
> > > 
> > 
>

Received on Monday, 5 October 2015 14:37:52 UTC