bug encoding multibyte?
lalinsky at gmail.com
Tue Feb 6 00:15:20 CET 2007
On Po, 2007-02-05 at 22:11 +0100, Xavier Duret wrote:
> > As I said, I'd like to turn it just to a collection of plugins, once the
> > important bugs (e.g. File::insert) are fixed in TagLib.
> I must confess that I am a bit worried about how this plugin system is
> going to work with the C bindings. Would you mind explaining it to me?
There isn't a way to load "plugins" automatically, you need to
explicitly register new file type resolvers for FileRef. I the C API, I
can think of calling a function on startup (e.g. `void
taglib_ext_register()`), that would add support for the new file
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://mail.kde.org/pipermail/taglib-devel/attachments/20070205/bb0dc2a3/attachment.pgp
More information about the taglib-devel