There should be automatic type conversions for
ASCII/Unicode strings. I've had to do this before with
code I've written, especially when it needs a COM
interface (where all strings are Unicode even though your
data may not be).
I ran into another problem where Find does not check
the encoding and convert raw ASCII to Unicode but
decided that this was more a general problem and a
feature request than a bug. For now I'm changing
id3com to convert input strings to ASCII because all the
mp3 files I've looked at have ASCII tags and I don't feel
the need for Unicode right now.