Open GoogleCodeExporter opened 8 years ago
About the double quotation in the cuesheet, XLD should read it without problem.
About the encoding issue, XLD assumes that the server returns UTF-8 characters
(server always returns UTF-8 encoded texts, by its specification). So if you
have odd characters in the cuesheet, that means you get wrongly submitted data
from the server.
Original comment by tmkkmac
on 21 Aug 2011 at 6:24
any comments?
Original comment by tmkkmac
on 2 Sep 2011 at 2:49
Well, obviously I think you're mistaken on both counts. But that's fine; I can
hand-tweak the cue sheet later to make it valid.
Original comment by mattne...@gmail.com
on 2 Sep 2011 at 4:45
mistaken?
Original comment by tmkkmac
on 2 Sep 2011 at 6:50
Sorry if I wasn't clear. Your comment 1 is a push-back indicating that my
original report is flawed and that there is no defect to correct in XLD. I'm
responding that I regard this as incorrect.
The fact is that in my normal workflow (put in a CD, get the metadata from an
online database, rip to flac + cue) I am sometimes getting invalid cue sheets
because the metadata is faulty (quotation marks in a track's title or incorrect
encoding). Of course this is not the fault of XLD; it's the fault of the
metadata database. But I'm suggesting that, since this *does* happen, instead
of generating invalid cue sheets in this situation, XLD should provide the
means to fix the problem and generate valid cue sheets.
You're implying that I'm wrong, and I'm disagreeing with you. But it's your
software, so obviously you're perfectly free to ignore my suggestion and I can
go on fixing the cue sheet by hand after XLD generates it.
Original comment by mattne...@gmail.com
on 3 Sep 2011 at 1:18
Well, XLD can correctly handle nested quotation marks in the cue sheet. So I
cannot understand what is your problem with it. There is no specification that
double quoted text should not include double quotation marks (it can be easily
handled by longest match principle).
Original comment by tmkkmac
on 3 Sep 2011 at 4:48
I have observed that XLD has trouble with cuesheets and double-quotes (when
creating them). I have taken to using single quotes anywhere I would otherwise
have double-quotes, which can occasionally look ugly.
Original comment by wils...@gmail.com
on 4 Sep 2011 at 6:02
What trouble?
Original comment by tmkkmac
on 4 Sep 2011 at 6:24
For example, in foobar2000, a program that generally supports standards about
as well as anybody:
could not enumerate tracks (Error parsing cuesheet: invalid TITLE syntax (line
8)) on:
\\vmware-host\shared folders\XLD\FLAC\Tom Petty and the
Heartbreakers\Doublequote Test-MFSL UDCD 565\Doublequote Test-MFSL UDCD 565.cue
Attached is an example (added some quotes to an album I happened to have
sitting around).
Original comment by wils...@gmail.com
on 4 Sep 2011 at 6:40
Attachments:
I don't think that is an issue. See my opinion in the comment 6.
Original comment by tmkkmac
on 4 Sep 2011 at 6:45
Original issue reported on code.google.com by
mattne...@gmail.com
on 21 Aug 2011 at 6:00