deestan/srt2vtt

Encoding-aware .srt (SubRip Text) to .vtt (WebVTT) converter.

srt2vtt

Encoding-aware .srt (SubRip Text) to .vtt (WebVTT) converter.

Handles CP1252 and UTF8/16/16LE/32/32LE.

Quick Example

var fs = require('fs');
var srt2vtt = require('srt2vtt');

var srtData = fs.readFileSync('captions.srt');
srt2vtt(srtData, function(err, vttData) {
  if (err) throw new Error(err);
  fs.writeFileSync('captions.vtt', vttData);
});

## Download

For Node.js, use npm:

npm install srt2vtt

Documentation

### srt2vtt (srtBuffer, callback) ### srt2vtt (srtBuffer, defaultCodepageOverride, callback)

It assumes input srtBuffer has the default CP1252 encoding, unless a UTF8, UTF16, UTF16LE, UTF32, or UTF32LE BOM is found at the start.

If the defaultCodepageOverride is given, that codepage is used instead of CP1252.

Callback is assumed to be a function(error, vttBuffer).

Arguments

• srtBuffer - Buffer containing the .srt file.
• defaultCodepageOverride (optional) - int number of codepage to use instead of CP1252 when no UTF BOM is found. This must be a numeric value, so e.g. give 1256 for codepage CP1256 (Arabic).
• callback - function(error, vttBuffer), in which error will be null if the conversion were successful, or an error message if not successful. vttBuffer is a UTF8-encoded buffer containing the converted WEBVTT file data.

### bin/convert.js

A command-line utility that expects a .srt file in stdin, will transform it to .vtt, and send it to stdout.

Example

$ node bin/convert.js < mighty_jack.srt > mighty_jack.vtt

srt2vtt's Issues

RFE: Allow changing output font size and bg color

Use less node dependencies if possible

eg: use Arraybuffer instead of buffer. That makes it more browser friendlier since it works in both environments

Codepage error

Im getting this error when trying to execute your example script.
`C:\Users\user\Desktop\subs\node_modules\srt2vtt\node_modules\codepage\cputils.js:109
mdb.length = 2 * len;
^

TypeError: Cannot set property length of [object Object] which has only a getter
at sbcs_d (C:\Users\user\Desktop\subs\node_modules\srt2vtt\node_modules\codepage\cputils.js:109:20)
at Object.decode (C:\Users\user\Desktop\subs\node_modules\srt2vtt\node_modules\codepage\cputils.js:397:40)
at Object.convertToUTF8 (C:\Users\user\Desktop\subs\node_modules\srt2vtt\encoding.js:93:46)
at srt2vtt (C:\Users\user\Desktop\subs\node_modules\srt2vtt\index.js:45:12)
at Object. (C:\Users\user\Desktop\subs\test.js:5:1)
at Module._compile (module.js:435:26)
at Object.Module._extensions..js (module.js:442:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:311:12)
at Function.Module.runMain (module.js:467:10)`

NOTE breaks subtitles in IE11/10

NOTE
Converted from .srt via srt2vtt: https://github.com/deestan/srt2vtt

Causes video.textTracks[0].cues to be empty on IE11; probably IE10 too.

Note that VTT files need also be served as Content-Type: text/vtt for subtitles to work on IE11.

UTF-8 encoding without BOM

When passing a UTF-8 encoded Buffer without a BOM it falls into the last conditional check // No BOM means CP1252 - convert but it seems to be working anyway.
Should I worry about it?

Allow other code-pages while reading SRT files

Many srt files are not cp1252 or utf8 encoded. I think it would be pretty helpful to enable reading those using their native encodings