Main.WebVTTSpec History

Hide minor edits - Show changes to output

Changed line 3 from:
Silvia gave an update on what was discussed at the =W3C= TPAC (technical plenary meeting) about how to move =WebVTT= onto a standards track through the =W3C= Timed Text WG.
to:
Silvia gave an update on what was discussed at the [=W3C=] TPAC (technical plenary meeting) about how to move [=WebVTT=] onto a standards track through the [=W3C=] Timed Text WG.
Changed lines 3-4 from:
Silvia gave an update on what was discussed at the W3C TPAC (technical plenary meeting) about how to move WebVTT onto a standards track through the W3C Timed Text WG.
to:
Silvia gave an update on what was discussed at the =W3C= TPAC (technical plenary meeting) about how to move =WebVTT= onto a standards track through the =W3C= Timed Text WG.
Added lines 14-16:
* discussion about whether it would make sense to stop having 2 different ways of doing captions: normal captions and regions
* discussion whether to just unify the rendering or also the syntax
* can't change the syntax of the normal captions (already in HLS), but might be able to introduce region features into normal cues (Silvia is sceptical)
Changed lines 5-7 from:
[[Attach:WebVTT_status.pdf]]
to:
[[Attach:WebVTT_status.pdf | WebVTT status report]]

[[Attach:WebVTT_Bugs.pdf | WebVTT bug classifying
]]
Added lines 10-11:
* discussed the [[https://dvcs.w3.org/hg/text-tracks/raw-file/default/608toVTT/608toVTT.html | CEA608/708 to WebVTT conversion spec]]
* registered a bug on the region spec that the region box needs to grow to contain the cue text for larger font etc
Added lines 1-9:
!! WebVTT Spec

Silvia gave an update on what was discussed at the W3C TPAC (technical plenary meeting) about how to move WebVTT onto a standards track through the W3C Timed Text WG.

[[Attach:WebVTT_status.pdf]]

* Discussion of Bug 19836 - cue settings need to use float for percentages - identified as a blocker bug because it stops us from implementing CEA608 completely accurately - will do
* discussed regions and why they are required
* Ken explained why the FCC requires CEA708 support, see [[http://www.w3.org/community/texttracks/wiki/708Features | 708 Features list]]