search

yusiwen / xld

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

not correct recognition Russian language in the .cue #334

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
Transcode any .cue files containing Russian language

How about the reproducibility (always, sometimes, rarely, ...)?
any cue files containing Russian language

What is the expected output? What do you see instead?
symbols instead of letters

What version of the product are you using? On what operating system?
20141129 (148.1) / Mac OS X 10.10.3 (in previous versions it was similar)

Please provide any additional information below.

Original issue reported on code.google.com by APEXXX...@gmail.com on 18 May 2015 at 7:33

Attachments:

GoogleCodeExporter commented 9 years ago 
How about changing the encoding in Preferences pane?

Original comment by tmkkmac on 18 May 2015 at 7:36

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Please upload .cue here

Original comment by tmkkmac on 18 May 2015 at 7:46

GoogleCodeExporter commented 9 years ago 
in settings was Cyrillic (Mac OS) - I believe it should be
Try changing to Unicode(UTF-8) see what happens

Original comment by APEXXX...@gmail.com on 18 May 2015 at 7:47

GoogleCodeExporter commented 9 years ago 
change the encoding did not help - the same result

Original comment by APEXXX...@gmail.com on 18 May 2015 at 7:53

Attachments:

GoogleCodeExporter commented 9 years ago 
I guess it should be Cyrillic (Windows).

Original comment by tmkkmac on 18 May 2015 at 8:02

GoogleCodeExporter commented 9 years ago 
Yes, you're right, I have found the problem! but a new question - how will be 
the case with "normal" CUE or other languages?

Original comment by APEXXX...@gmail.com on 18 May 2015 at 8:05

GoogleCodeExporter commented 9 years ago 
It depends on the file. Choose the correct one every time.

Note that .cue created with XLD is always encoded with UTF-8.

Original comment by tmkkmac on 18 May 2015 at 8:12