Hi,
thank you very much for your suggestion for fixing this!
Michael Urman wrote:
> It is completely out of spec to store non-UTF8 in a vorbiscomment. That
Indeed, and Joe already convinced me that working around the brokeness
in QL might not be a good idea. It might be cool to be able to retag
those file in EF or tell the user about why he cannot, but that's really
up to you.
> vorbiscomment -l "$f" | iconv -f latin1 -t utf8 | vorbiscomment -w "$f"
Thanks for the hint, it was most helpful. In case anyone reads this for
his own problems, you probably want to use "-R":
vorbiscomment -lR "$f" | iconv -f latin1 -t utf8 |
vorbiscomment -wR "$f"
Without the "-R" option, vorbiscomment will replace illegal UTF8 chars
with "#", even when the locale uses uf8.
> tags as best as you can. As for whether QL/EF should notify the user of
> files which have invalid tags, it's up for debate. Sometimes I think a
Well, QL currently dumps a traceback and continues. That works well
enough for me. Doing as vorbiscomment does would have been more
comfortable in the short term, but I can see why you don't want that.
Kind regards
T.
BTW: I have filed Debian bug #349707 for abcde to not produce broken oggs.
--
Thomas Viehmann, http://thomas.viehmann.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
