> Given the longevity of this bug, I don't think upstream is handling this, so > it seems like the solution is to either > change the library id3v2 uses (libid3 to libid3tag)
I actually ported parts of id3v2 to libid3tag a while back (just out of personal curiosity) and while libid3tag can't fully replace libid3 (IIRC it won't let you figure out whether you're dealing with a v1 or a v2 tag - some features of the id3v2 tool need that, though) I should be able to somehow hack basic, read-only v2.4 support into id3v2... cheers -- Stefan Ott http://www.ott.net/ "You are not Grey Squirrel?" -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
