-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enabling conversion options breaks encoding (Linux, 0.1.9, x64) #37
Comments
Please check version 0.2.0. There were improvements applied in file encoding detection. |
I've problem checking it - see #41 |
Still a lot of problems with conversion options on 0.2.0 and master from git. The only one which works all the time is "Nie dodawaj informacji o QNAPI". Charset conversion works only if i select manually input and output charset. Auto-detection doesn't work. The same with file type conversion. |
Reproduced encoding problem on Windows too. EDIT: I'm used charset auto-detection. |
@Tapcio Thank you for the files. Auto-detection of file encoding was broken for non-polish subtitles. Bugfix will be available in 0.2.1 version. |
Mostly i download subtitles in win1250. But sometimes files are in UTF-8 so i want to be sure that i've final subtitles in win1250. So i enable after enabling conversion options and selecting converting to win1250. But every subtitle after such conversion is gibberish. enca (Linux tool to check file charset) says final file is in UTF-8 but it isn't. It's some strange encoding.
The text was updated successfully, but these errors were encountered: