Closed GoogleCodeExporter closed 9 years ago
Well, saved cue sheet is always encoded with UTF-8.
I don't know what you did in XLD before saving .cue, but if you couldn't see
correct characters in the track list view in XLD, of course saved .cue should
contain incorrect characters.
And please do not ignore a template of the bug tracker. Steps to reproduce is
the most important information for a developer.
Original comment by tmkkmac
on 22 May 2012 at 5:50
Saved the new edit tags as a .cue sheet. Reopening it in XLD produces errors:
Artist: Arild Andersen (Acoustic and Electric Bass), Nils Petter Molvær
(Trumpet),
Album: Bande À Part [Vinyl 24/96] [Side 1]
Comments: ECM 1319 Masqualero - Bande À Part [Vinyl 24/96] [ECM 1319]
(1986) Recorded August and December 1985 at Rainbow Studio, Oslo Engineer: Jan
Erik Kongshaug Produced by Manfred Eicher and Masqualero
The .cue files looks like this, if opened in Apples Textedit :
TITLE "3 For 5"
PERFORMER "Arild Andersen (Acoustic and Electric Bass), Nils Petter Molvær (Trumpet), Tore Brunborg (Tenor and Soprano Saxophones), Jon Balke (Acoustic and Electric Piano, DX7 Synthesizer), Jon Christensen (Drums, Percussion)"
SONGWRITER "Arild Andersen"
REM COMMENT "ECM 1319 Masqualero - Bande À Part [Vinyl 24/96] [ECM 1319] (1986) Recorded August and December 1985 at Rainbow Studio, Oslo Engineer: Jan Erik Kongshaug Produced by Manfred Eicher and Masqualero"
INDEX 01 00:00:00
I hope this give a better idea of the problem...
It is easy to reproduce. Open some separate track files in for example .flac
format, Edit them using XLD and use foreign characters and save a new .cue
sheet.
Reopening the saved .cue sheet shows the above problem
Original comment by bilog...@gmail.com
on 22 May 2012 at 6:26
So, do you mean the cue sheet itself has correct characters (TextEdit.app shows
them correctly), but opening it with XLD doesn't work, right?
Then I guess you give wrong character encoding for cue sheet (available in XLD
Preferences).
Original comment by tmkkmac
on 22 May 2012 at 6:47
You are absolutely right. I'm used that Macs do things automatically. Never
looked closely at the character code option in the preferences menu. That is
kind of silly from me oops!!! Thx for your help, you have saving me a lot of
time...
Original comment by bilog...@gmail.com
on 22 May 2012 at 7:07
Original comment by tmkkmac
on 22 May 2012 at 7:11
Original issue reported on code.google.com by
bilog...@gmail.com
on 22 May 2012 at 5:37Attachments: