Six edge cases in SubRip (SRT) parsing, and a tolerant Python parser: a technical note

SRT2Word

doi:10.5281/zenodo.23106266

RResearcharAcademic radar for researchers

Feed Venues Groups Network Inbox Profile

Your academic radar

One personalized feed of papers, calls for papers, collaborators and datasets — plus research groups and paid-in-points study recruitment.

Create account Log in

Top venues

Browse all

Loading…

Six edge cases in SubRip (SRT) parsing, and a tolerant Python parser: a technical note · Researchar

Back to feed

Paperopenalex

ZCE

Six edge cases in SubRip (SRT) parsing, and a tolerant Python parser: a technical note

SRT2Word · Zenodo (CERN European Organization for Nuclear Research) 2026 · 2026

DOI: 10.5281/zenodo.23106266

0citations

Natural Language Processing TechniquesSyntax, Semantics, Linguistic VariationMathematics, Computing, and Information ProcessingPython (programming language)ByteComputer science+2

ZCEZenodo (CERN European Organization for Nuclear Research)Repository

Download PDF Publisher

Citations by source

Synced 2026-10-04T02:30:24.144801Z

0OpenAlex · primary0Semantic Scholar0Crossref

Counts differ because each database indexes a different set of publications. We treat OpenAlex as the canonical count; Google Scholar is not shown (no API, and crawling it violates its ToS).

Abstract

A short technical note on six cases that break a quick SubRip (.srt) parser: byte order marks and CRLF line endings, a period instead of a comma in timestamps, missing cue indexes, dialogue that is only a number, inline markup, and extra blank lines. Includes a tested Python function that reads cue start times and text, and lists what it still assumes. Author's tool: https://srt2word.com

Discussion (0)

No comments yet — start the discussion below.