You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the tool will fail when trying to parse files with this character encoding. For a viable solution the tool should be able to detect the character encoding and convert to UTF-8 when required.
The converted data should be written even if nodes were not modified, this will remove the need to convert a file multiple times when running subclean on an entire library as a scheduled task.
See this #7 (comment) for information on a temporary solution for the current problem.
Unfortunately this will require a dependency like utf8.
If you're using Bazarr, you can avoid this issue with the setting:
Settings → Subtitles → Post-Processing → Encode Subtitles To UTF8
DrKain
changed the title
[Feature Request] Support for UCS-2 BE BOM character encoding
[Feature Request] Support for other character encodings
May 4, 2023
Right now the tool will fail when trying to parse files with this character encoding. For a viable solution the tool should be able to detect the character encoding and convert to UTF-8 when required.
The converted data should be written even if nodes were not modified, this will remove the need to convert a file multiple times when running subclean on an entire library as a scheduled task.
See this #7 (comment) for information on a temporary solution for the current problem.
Unfortunately this will require a dependency like utf8.
Test files:
The text was updated successfully, but these errors were encountered: