- From: <bugzilla@jessica.w3.org>
- Date: Sun, 14 Feb 2016 00:28:40 +0000
- To: www-international@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28257 --- Comment #30 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> --- (In reply to Simon Pieters from comment #28) > (In reply to Silvia Pfeiffer from comment #26) > > 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. > > So for RTL text, with your proposal, the text begins in the middle of the > screen and extends leftwards. Are you saying that that is not confusing? > > +---------------------------------------+ > | | > | txet cibarA | > +---------------------------------------+ > ^ 0% ^ 50% ^ 100% > When the text is "align:start" and the box is 50% size, and you have RTL text, the text box sits in the right half, not the left half like this: +---------------------------------------+ | | | txet cibarA | +---------------------------------------+ ^ 0% ^ 50% ^ 100% That's the intention of automating the box placement based on the alignment and directionality. If the algo doesn't describe it this way, then there's a bug for RTL. > > > 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. > > Do you have a citation? Was mostly oral feedback. Specifically, when people used less than 100% width and specified alignment to be left. Then it seemed that the text would appear at random positions somewhat off the center and that was extremely confusing. > > I could live with replacing 'start' and 'end' with 'left', 'top', 'right' > > and 'bottom'. > > (In the PR we agreed with 'line-left' and 'line-right'.) Yes, I think that works even better! -- You are receiving this mail because: You are on the CC list for the bug.
Received on Sunday, 14 February 2016 00:28:51 UTC