-
seconv info reports some ANSI subs as beeing UTF8 without BOM. This is also the case with SE5 GUI, while SE4 opens these as windows-1252, even if they are windows-1250(wrong, but not unexpected). While some errors in ANSI detection are to be expected, it was my understanding that UTF8 is not easily "confused". I'm attaching an example sub.
-
--input-encoding-fallback:windows-1250 works
-
Default --FixCommonErrors applies Spanish inverted question/exclamation marks. Using --fix-common-errors-rules:all,-FixSpanishInvertedQuestionAndExclamationMarks works, but, I'm not seeing the FixSpanishInvertedQuestionAndExclamationMarks equivalent listed in the SE5 GUI in it's respective place, nor does the GUI app apply that fix, even if selecting spanish as the language. Not sure what exactly is going on here, but, beeing familiar with the settings in the GUI, I suspect many users will be scratching their heads after runnign the default config.
-
--encoding:NONSENSE does not generate an error, which it should
-
--encoding:source does not work as it did with old SE, and probably falls within 4. Even with --input-encoding-fallback beeing available, this is still a useful option to have, just in case.
-
How do these differ and which is recommended? --fix-common-errors-rules:FixOverlappingDisplayTimes vs --apply-min-gap:0
-
Is seconv supposed to be able to ingest the Settings.json file that SE5 generates? That doesn't seem to be the case. For example, your documentation specifies "removeTextForHearingImpaired", while SE5 uses "RemoveTextForHi" in it's settings file. Seeing as SE4 CLI actually used (some of) the settings set in the batch convert section of the GUI, it would probably make sense for seconv to be able so use it's GUI counterpart's settings file.
-
After trying 7., I followed the documentation, and tried and failed to remove an all uppercase line with --settings:Settings.json --RemoveTextForHI, with the following contents of said setting file:
{
"removeTextForHearingImpaired": {
"IsRemoveTextUppercaseLineOn": true
}
}
Used the same example sub I've attached in 1.
seconv inforeports some ANSI subs as beeing UTF8 without BOM. This is also the case with SE5 GUI, while SE4 opens these as windows-1252, even if they are windows-1250(wrong, but not unexpected). While some errors in ANSI detection are to be expected, it was my understanding that UTF8 is not easily "confused". I'm attaching an example sub.--input-encoding-fallback:windows-1250worksDefault
--FixCommonErrorsapplies Spanish inverted question/exclamation marks. Using--fix-common-errors-rules:all,-FixSpanishInvertedQuestionAndExclamationMarksworks, but, I'm not seeing theFixSpanishInvertedQuestionAndExclamationMarksequivalent listed in the SE5 GUI in it's respective place, nor does the GUI app apply that fix, even if selecting spanish as the language. Not sure what exactly is going on here, but, beeing familiar with the settings in the GUI, I suspect many users will be scratching their heads after runnign the default config.--encoding:NONSENSEdoes not generate an error, which it should--encoding:sourcedoes not work as it did with old SE, and probably falls within 4. Even with--input-encoding-fallbackbeeing available, this is still a useful option to have, just in case.How do these differ and which is recommended?
--fix-common-errors-rules:FixOverlappingDisplayTimesvs--apply-min-gap:0Is seconv supposed to be able to ingest the
Settings.jsonfile that SE5 generates? That doesn't seem to be the case. For example, your documentation specifies "removeTextForHearingImpaired", while SE5 uses "RemoveTextForHi" in it's settings file. Seeing as SE4 CLI actually used (some of) the settings set in the batch convert section of the GUI, it would probably make sense for seconv to be able so use it's GUI counterpart's settings file.After trying 7., I followed the documentation, and tried and failed to remove an all uppercase line with
--settings:Settings.json --RemoveTextForHI, with the following contents of said setting file:Used the same example sub I've attached in 1.