IlgnerBri / subtitleedit

Automatically exported from code.google.com/p/subtitleedit
0 stars 0 forks source link

in addition from fix 64 #68

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Translated with google to russian.
2. output in translated window is fine now.
3. I save the file with one of the available encoding formats (no other choice).

What is the expected output? What do you see instead?
The saved .srt file become unreadable!

What version of the product are you using? On what operating system?
I use the fixed program in the zip file you send me after the fix.

Please provide any additional information below.

When you save the translated file, it will take the shown encoding "ANSI-1252" 
to save the file to.

After using this file in several (srt or video) programs it becomes unreadable 
(saved in the wrong encoding).

Even after saving the file with the other 4 encoding's of choice the result is 
an unreadable file.

I think when there is an option to save the file with the proper encoding 
(Cyrylic, ANSI-1251, KOI8-R, ...) for this case Russian, the problem will be 
fixed.

Original issue reported on code.google.com by patbe...@gmail.com on 3 Jan 2012 at 9:09

GoogleCodeExporter commented 8 years ago
I would recommend utf-8 (ANSI is really one big hack...)

Original comment by nikse.dk@gmail.com on 3 Jan 2012 at 10:22

GoogleCodeExporter commented 8 years ago
SE 3.2.4 automatically shifts to UTF-8 after Google translate - also, encoding 
combo-box now display more encodings

Original comment by nikse.dk@gmail.com on 16 Mar 2012 at 9:14