[foms] WebVTT implementation in browsers
silviapfeiffer1 at gmail.com
Sat Feb 23 11:45:54 UTC 2019
Nice work! Look forward to getting that data set made available - there's
not enough standardised test material available for WebVTT.
A could of notes of feedback:
The srclang attribute is supposed to specify one and only one language,
encoded as an IETF language code. This does not match how my videos work.
As mentioned previously, it is possible that the track with srclang="cs"
(Czech) will be exactly the same as the one with srclang="sk" (Slovak)."
That's not a Problem, because you can specify the same caption fund in
multiple <track> tags.
You further wrote: Audio-without-video subtitles as a problem to render.
That's rest: just put the audio file in a video element and it will work.
Hot this helps.
On Tue., 19 Feb. 2019, 9:13 am Thomas Levine, <_ at thomaslevine.com> wrote:
> Silvia Pfeiffer writes:
> > On Sat, Apr 7, 2018 at 2:10 PM, Thomas Levine <_ at thomaslevine.com>
> > > I have found the discrepancy between the draft specification and the
> > > actual implementation to lead to ample disappointment, so I appreciate
> > > any reconciliation. The main feature that I really wish would be
> > > implemented is karaoke display. I don't use polyfills, but I am
> > > rendering my WebVTT files differently to cope with the lack of karaoke
> > > display. I would render them with ordinary karaoke timings if that
> > > worked in browsers.
> > >
> > > You remind me, I still haven't gotten around to writing up the opinions
> > > I developed over the past year about the language settings in the
> > > specification and in the HTML track tags. I have been working on a
> > > project with subtitles in many different languages, and the modeling of
> > > languages is inappropriate for my use. Once I write up these opinions,
> > > do you want me to post it on this issue tracker?
> > > https://github.com/w3c/webvtt/issues
> > Yes please! That's where all work for WebVTT happens now.
> > Thanks,
> > Silvia.
> Almost one year later, I have finally composed my comments. I personally
> try to limit my use of proprietary software, but you may copy the
> comments to the issue tracker.
> I have also added it to the FOMS 2019 position statement page.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the foms