2.0.0 • Published 11 months ago
@ltftf/srt-parser-2 v2.0.0
srt-parser-2
An SRT parser for Javascript.
It reads an .srt file into an array.
This is a fork of srt-parser-2.
What's changed
- Removed the unnecessary class instantiation
- Text is parsed as an array of strings (by line) instead of a single string with
\ncharacters
Install
npm
npm install @ltftf/srt-parser-2or yarn
yarn add @ltftf/srt-parser-2Example
This is an SRT format file:
1
00:00:11,544 --> 00:00:12,682
Hello
Worldit would become:
[{
id: "1",
startTime: "00:00:11,544",
startSeconds: 11.544,
endTime: "00:00:12,682",
endSeconds: 12.682,
text: [ "Hello", "World" ]
}]Environment support
Since it only process text,
it should work in both Browser and Node.js environment
Usage
let srt = `
1
00:00:11,544 --> 00:00:12,682
Hello
`;
import { fromSrt, toSrt } from "@ltftf/srt-parser-2";
var srtArray = fromSrt(srt);
console.log(srtArray);
// turn array back to SRT string.
var srtString = toSrt(srtArray);
console.log(srtString);You can run this example using node example/1.Comma.js
CLI
npx srt-parser-2 -i input.srt -o output.json --minifyOptions:
| Option | Required | Default |
|---|---|---|
| --input or -i | Yes | |
| --output or -o | No | output.json |
| --minify | No | false |
License
MIT
Why?
Why this one special? There are plenty of SRT parsers on npm:
What's wrong with them?
Nothing wrong.
All of them can handle this format:
1
00:00:11,544 --> 00:00:12,682
HelloBut I want to handle format like these:
00:00:11.544This is wrong format, it use period as separator
Or this:
00:00:11,5440This is also wrong format, millisecond has 4 digit (should be 3)
Or this:
1:00:11,5Similar, hour & millisecond is only 1 digit (wrong)
Or this
00:00:00.05etc
Format Support
| Format | Other parser | srt-parser-2 | srt-parser-2 would turn this into |
|---|---|---|---|
| 00:00:01,544 | Yes :white_check_mark: | Yes :white_check_mark: | 00:00:01,544 |
| 00:00:01.544 | :question: Yes for some of them | Yes :white_check_mark: | 00:00:01,544 |
| 00:00:01.54 | :question: Yes for some of them | Yes :white_check_mark: | 00:00:01,544 |
| 00:00:00.3333 | No :x: | Yes :white_check_mark: | 00:00:00,333 |
| 00:00:00.3 | No :x: | Yes :white_check_mark: | 00:00:00,300 |
| 1:2:3.4 | No :x: | Yes :white_check_mark: | 01:02:03,400 |
Basic principle:
- If hour,minute,second is shorter than 2 digit, pad start with "0", if longer than 2 digit, only save first 2 digit.
- Millisecond is the same, but it's 3 digit.
- Separator can be
.(periods) or,(comma), periods(incorrect) will be replace with comma(correct)
Conclusion
- Support more time format (even wrong format)
- Have extensive test
2.0.0
11 months ago