[Bug 28257] [webvtt] start/end linked to left/right [I18N-ISSUE-422]


--- Comment #26 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> ---
(In reply to Simon Pieters from comment #23)
> (In reply to Richard Ishida from comment #22)
> > [2] The alignment of the lines of text within the cue box also has no effect
> > on the position of the frame of the cue box (other than that you need to
> > take into account the width of the box if you have some rtl and some ltr
> > lines).
> No, currently align:left and align:start will position the box on the left
> (unless it is explicitly positioned somewhere).

The reason for this is that it feels much more natural when you author a cue
text and you say "align:start" and you've made your cue box smaller (e.g. 50%
size) that this box sits at the beginning of the screen and not in the middle.
Everything else is confusing.

> My proposal
> https://github.com/w3c/webvtt/pull/273 is to let align:start/end be
> positioned the same as align:center.

That has been found to be counter-intuitive by many captioners.

> > [3] On the other hand, the *writing-mode* of the text will indeed affect the
> > placement of the box.  (NB: writing-mode has *nothing* to do with base
> > direction, it only refers to the direction in which the lines progress, one
> > after the other.) The positioning of the cue box varies between vertical and
> > horizontal coordinates, depending on the writing-mode direction. 
> > 
> > As i understand it, the spec currently uses `start` to abstract away from
> > whether a position relates to left (for horizontal writing-mode) or top (for
> > vertical writing-mode), and end to mean either right or bottom.  I'm not
> > sure the terms start and end are apposite here, but that's a terminology
> > issue – start in this case does not always mean 'left', it may also mean
> > 'top'.
> Yeah, but this is pretty inconsistent with CSS, as is pointed out in comment
> 9.

I could live with replacing 'start' and 'end' with 'left', 'top', 'right' and

You are receiving this mail because:
You are on the CC list for the bug.

Received on Thursday, 11 February 2016 16:24:10 UTC