Closed GoogleCodeExporter closed 8 years ago
Do any of the scripts I've attached play back correctly?
Original comment by cyber.sp...@gmail.com
on 15 May 2012 at 12:31
Attachments:
For uft-8, it works good.
And still not work for the win936 version.
Original comment by cagen530...@gmail.com
on 15 May 2012 at 12:54
I'm not seeing any difference between xy-VSFilter, VSFilter 2.39, and VSFilter
2.40 on Windows 7 (English locale). All just show boxes on the win936 scripts
set to use default encoding.
If I set the encoding to Windows-936 in the script style (encoding 134) like
with the attached script, then xy-VSFilter, VSFilter 2.39, and VSFilter 2.40
all display the characters correctly as they should.
I've passed it on to our Chinese developer to see if he can reproduce your the
problem.
What do you have set for your non-Unicode System Locale under Regional and
Language settings?
Original comment by cyber.sp...@gmail.com
on 15 May 2012 at 2:46
Attachments:
For non-Unicode System Locale I use Chinese ( Simplified, PRC ).
I have changed the encoding to other options (Such as ANSI, default, encoding
134, encoding 136), but the outcome seems didn't change at all.
I do some tests by changed some subtitles which can be play back correctly to
windows-936 encoding. Then they fail to play back correctly as before.
I have tried to change the non-Unicode System Locale to English (United
States). When I use the default encoding, it is all boxes as you said. Then I
changed to encoding 134, it was the same problem as I described before.
Attachment:
1. When all subtitles which play back wrong open with Aegisub will come out
such dialogue. (those 'correct' subtitles will just directly open).
2. the difference between correct and wrong.
Sorry for my broken English.
Thanks for your answers.
Original comment by cagen530...@gmail.com
on 16 May 2012 at 7:00
Attachments:
Original comment by cyber.sp...@gmail.com
on 17 May 2012 at 1:28
Original comment by cyber.sp...@gmail.com
on 20 May 2012 at 8:00
Fixed in xy-VSFilter 3.0.0.40
Original comment by cyber.sp...@gmail.com
on 20 Jun 2012 at 5:53
Original issue reported on code.google.com by
cagen530...@gmail.com
on 15 May 2012 at 11:25Attachments: