First of all, thank you for responding. The bug I mentioned does not seem to be due to cdda2wav directly, but to something in my network. But as only cdda2wav (and Icedax, I just tried) was affected and not other programs (in various versions on various OS's) it looked like a cdda2wav bug ...
Anyway, what I wanted to say is, as already was proposed by someone else, it would be nice to consider support for FreeDB protocol 6. From your description I can see however this would involve some important changes. As you say, cdda2wav outputs as ISO-8859-1. If FreeDB protocol 6 would be added this would mean changing the output encoding to unicode (it would not make sense to read information as unicode from FreeDB for loosing the information afterwards). But this in turn would mean quite some charset recoding (especially for CD text). Also, as I understand you, this would also mean serious problems for cdrecord as the input files could be either ISO-8859-1 or unicode (well, the use of unicode should probably be specified in the files, but this would still represent some important changes). The main gain would by the way not be for writting CD text which has limited charset support, but when encoding to other formats using cdda2wav information for writting the tags (flac, mp4, mp3, ... ). -- cdda2wav - cannot cope with accents in CDDB data https://bugs.launchpad.net/bugs/6493 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
