search

MarrySunshine / xld

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

Definition of the .cue sheet text encoding #17

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
If you exchange .cue sheets with EAC it is fine for english Names, but German 
or French umlauts are not carried over. So I have to use a text editor like 
BBEdit to change the UTF8 Unix LF format to the Windows Latin-1 Windows CRLF 
encoding.

I had cases where the other way round worked right from EAC but not from XLDs 
own files generated. I have to look up this for the current build as you 
changed the UTF8 handling.

But a switch for interpreting for read and write to the different formats would 
be great to omit the text editor step.

If you need Example files, I can deliver some.

Original issue reported on code.google.com by stargato...@gmail.com on 7 Jul 2011 at 11:39

GoogleCodeExporter commented 9 years ago 
UTF-8 cuesheets are still not supported in EAC?

Original comment by tmkkmac on 7 Jul 2011 at 11:50

GoogleCodeExporter commented 9 years ago 
It reads the cue sheet with UTF8 from XLD and every Umlaut is wrong. So I 
consider it is not supporting it. (current edition of EAC Exact Audio Copy V1.0 
beta 2 ). It accepts it now everywhere but in the .cue sheet, as the burner 
seems not to be changed and it uses a old tool .cue to .toc to generate a 
CDRDAO compatible burn list.

Original comment by stargato...@gmail.com on 7 Jul 2011 at 11:56

GoogleCodeExporter commented 9 years ago 
I love XLD so much that it's much better than any iTunes flac player that after 
conversion it's natively supported by iTunes but those players have to maintain 
a separated playlist for iTunes unsupported files.

However, almost all my collections are under flac/ape/dts + cue (which is in 
Chinese). I can almost use none of them in my iTunes with my new DAC.

Is there a plan to fix this any sooner??

Original comment by chunwei....@gmail.com on 4 Dec 2012 at 2:59

GoogleCodeExporter commented 9 years ago 
Well, this topic is for writing cue sheets. For reading, you can always change 
the encoding in Preferences pane.

Original comment by tmkkmac on 4 Dec 2012 at 3:07

GoogleCodeExporter commented 9 years ago 
Thanks a lot! it works pretty well for reading.

Is there a way to specify reading cue file encoding in the command line tool? i 
didn't find any options there.

Original comment by chunwei....@gmail.com on 19 Dec 2012 at 2:25

GoogleCodeExporter commented 9 years ago 
The setting in the GUI is automatically applied to the CLI tool.

Original comment by tmkkmac on 19 Dec 2012 at 2:31

GoogleCodeExporter commented 9 years ago 
I have strange behaviour with Russian CP1251 .cue. Оn opening, I can read 
correct Names within 1-2 sec. In this time, XLD still loading, and after all 
names (Title, Artist) in XLD windows converted to unreadable format (latin1?). 
I tried convert CUE to UTF8 with LF from CP1251 with CRLD, and defined correct 
encoding in XLD prefs instead of Automatic, but always tags visible only on 
load. Album Artist name always encoded correctrly in main window and Tags 
Editor interface.

Original comment by tsy...@gmail.com on 30 Dec 2012 at 4:51

Attachments:

GoogleCodeExporter commented 9 years ago 
Well, that is because of the automatic CDDB connection feature, isn't it? If 
you have turned it on try disabling it.

PS: off-topic. please create a new topic for the different issue.

Original comment by tmkkmac on 30 Dec 2012 at 4:58