[gstreamer-bugs] [Bug 629764] [subparse] Add WebSRT support

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=629764
  GStreamer | gst-plugins-base | git

--- Comment #6 from Philippe Normand <phil at base-art.net> 2010-12-27 13:16:20 UTC ---
(In reply to comment #4)
> Note that the voices ("narrator", "music", "lyric", "sound", "comment",
> "credit") are likely going to be removed.
> 

Ok I'll remove support for parsing those then.

> Also, since there's nothing to differentiate WebSRT and normal SRT,

WebSRT was renamed to WebVTT 3 days ago :)
It seems the file first line has to be WEBVTT FILE or the parser should fail.
A text/vtt mimetype is also introduced.

http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#webvtt-0


> if you
> actually follow the WebSRT, any unescaped occurence of < in the cue text that
> isn't intended to start a new tag will be treated differently.
> 

Well in my current branch "foo < bar" would be parsed to "foo &lt; bar". Isn't
that right?

> subrip_unescape_formatting looks a bit weird in how it uses tags_whitelist,
> maybe it would fit better in the tokenizer (which is what the spec says).

That's because the srt parser currently allows a fixed set of tags, so it
escapes all the cue text and unescape it then based on that white list. I
didn't change this from the original parser, I only refactored it to allow tags
with more than one letter.

(In reply to comment #5)
> For now it would also be great to have something that works with GStreamer 0.10

Hum ok, so where/how do I store the cue settings?

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.