W3C home > Mailing lists > Public > www-international@w3.org > October to December 2013

[Bug 24129] [WebVTT] Support for bidi

From: <bugzilla@jessica.w3.org>
Date: Mon, 23 Dec 2013 08:36:41 +0000
To: www-international@w3.org
Message-ID: <bug-24129-4285-zPz2FhNqfa@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24129

--- Comment #3 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> ---
Richard, thanks for the history. I will have to read up on RFC 2070.

One big difference between HTML and WebVTT is that WebVTT is fundamentally a
line-based file format, while HTML is fundamentally a markup-based format. Fir
example, in WebVTT newlines are actually meaningful. We only introduce markup
into WebVTT when there is no other remedy. In all other situations, UTF8
characters are what counts. WebVTT is more like a txt file than a html file in
that respect.

Another big difference is that WebVTT has a very small and limited means of
manipulating text - there are no tables, no canvas, not even image tags etc.
WebVTT in particular doesn't have an extensive document structure like HTML.

That unicode control characters are hard to read (where? in a typical text
editor? on the command line?) isn't a sufficient requirement to introduce a
duplicate solution - an authoring tool for WebVTT could simply expose those
characters better, thus providing a remedy for this problem.

We should only introduce new markup in cases where the unicode characters are
not sufficient to provide the correct rendering.

So, I think we will have to re-do the analysis that you have made for HTML and
apply it specifically to WebVTT. I'll need to take some time to read up on it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 23 December 2013 08:36:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:35 UTC