From aa1a383342f72fb0dfb1fb016535735bc0480e7e Mon Sep 17 00:00:00 2001 From: wm4 Date: Tue, 22 Jul 2014 23:40:48 +0200 Subject: sub: add detection via BOM Useful for Windows stuff. Actually, ENCA support should catch this, but, well, whatever, everyone seems to hate ENCA. Detection with BOM is trivial, although it needs some hackery to integrate it with the existing autodetection support. For one, change the default value of --sub-codepage to make this easier. Probably fixes issue #937 (the second part). --- DOCS/man/options.rst | 3 +++ 1 file changed, 3 insertions(+) (limited to 'DOCS/man') diff --git a/DOCS/man/options.rst b/DOCS/man/options.rst index 86cfa965c2..99ce772514 100644 --- a/DOCS/man/options.rst +++ b/DOCS/man/options.rst @@ -2260,6 +2260,9 @@ OPTIONS which means it will try to use UTF-8, otherwise the ``UTF-8-BROKEN`` pseudo codepage (see below). + The default value for this optino is ``auto``, whose actual effect depends + on whether ENCA is compiled. + .. admonition:: Warning If you force the charset, even subtitles that are known to be -- cgit v1.2.3