• Clément Bœsch's avatar
    lavf/srtdec: rewrite parsing logic · 77eeaa2c
    Clément Bœsch authored
    Fixes Ticket #5032
    
    The samples in Ticket #5032 is using \r\r\n as line breaks.  Since we
    already are handling \r, or \n, or \r\n as line breaks, \r\n\n will be
    considered as a double line breaks. This is an issue because
    ff_subtitles_read_text_chunk() will as a result stop extracting a chunk
    after just one line.
    
    So instead of parsing the SRT by "chunks" (which means splitting every
    double LB), this new parser is detecting timing lines, and split the
    events on this basis. While this sounds safe and simple, it needs to
    take into account the event number preceding the timing line while
    handling situations such as:
    
     - event number starting at 0 or actually any number instead of 1
     - event numbers not being ordered at all
     - event number being followed by text garbage (this really happened,
       see Ticket #4898)
     - event payload containing one or multiple number (a protagonist saying
       a count-down, a date or whatever) which could be confused with a
       chapter number
     - event number being empty (see Ticket #2167)
     - all kind of weird line breaks can appear randomly like wild pokémons
     - untrustable line breaks (Ticket #5032)
    
    The sample madness.srt tries to sum up most of this into one sample,
    ticket5032-rrn.srt is the file containing \r\r\n line breaks. and
    empty-events-2167.srt contains empty events.
    77eeaa2c
Name
Last commit
Last update
..
acodec Loading commit data...
fate Loading commit data...
lavf Loading commit data...
lavf-fate Loading commit data...
seek Loading commit data...
vsynth Loading commit data...
vsynth1 Loading commit data...
vsynth_lena Loading commit data...