[gstreamer-bugs] [Bug 502497] New: SubRip subtitles starting from 0 not recognised

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=502497

  GStreamer | gst-plugins-base | Ver: HEAD CVS
           Summary: SubRip subtitles starting from 0 not recognised
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: robin.stocker at gmx.ch
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: 2.19/2.20
   GNOME milestone: Unspecified


Subparse doesn't accept SubRip subtitles (.srt) where the index starts from 0
instead of 1. According to Wikipedia (http://en.wikipedia.org/wiki/SubRip),
they should start from 1, but I've seen subtitles where index 0 was used for
"credits".

To reproduce, put this into an srt file named the same as a movie:

0

00:00:00,000 --> 00:00:01,000

Test

Then try to play it with a player using GStreamer. Then change the 0 to 1 and
try it again.

A user who doesn't know the SubRip format and tries to play a movie will be
surprised that his subtitles aren't displayed, not knowing that he could edit
the file and delete the entry with index 0 to make it work.

One solution would be a prominent FAQ entry somewhere. Another would be to make
subparse recognise srt with index starting at 0. What do you think?


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=502497.