Hi Jonas, Last week I looked at the python-id3lib code a bit (for the purpose of adding UTF8 support to Jack) and came to the conclusion that IMHO it would be better to drop python-id3lib in favor of python-eyed3.
The upstream python-id3lib package seems to be unmaintained and the underlying libid3 library itself also seems to have a plethora of open bugs, several of which related to UTF8. The python-eyed3 library on the other hand seems to be well maintained and UTF8-aware. Porting an application from python-id3lib to python-eyed3 is quite easy. So, in this respect I prefer to spend my time porting Jack (and if requested also other rdepends on python-id3lib) to python-eyed3 than fixing python-id3lib itself. Hope you understand... Best regards, Chris. --- > Hi Chris, > > If you get around to hacking UTF-8 support into the python library > please post the patch here, so I can include it with the official Debian > package. > > You say you'd preserve current behaviour of the library by default - but > does that make sense at all? I don't know the details of ID3v2 if it is > defined as UTF-8 then current behaviour is broken IMHO (even if it > happens to work in the western world). > > As you can probably read between the lines of the above, I do packaging, > but is not capable of hacking the code itself, so can't be of assistence > in fixing this. > > > Regards, > > - Jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
