nik8;431140 Wrote: > I had exactly the same problem and traced it down to bad chars in the > comment field of some of my tracks: > > <comment>The celebrated <snip> COMM > > ÿà > %&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz Â¢£¤¥¦§¨©ª²³´µ¶·¸¹ºÃÃÃà ÃÃÃÃÃÃÃÃÃÃÃÃÃÃáâãäåæçèéêñòóôõö÷øùúÿà > > ÿà > $4á%ñ&'()*56789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz Â¢£¤¥¦§¨©ª²³´µ¶·¸¹ºÃÃÃà ÃÃÃÃÃÃÃÃÃÃÃÃÃÃâãäåæçèéêòóôõö÷øùúÿÃ</comment> > > If I removed these values it works fine. > > Peter, is there any way of filtering this out during log writing? Am I > right to assume it's a UTF encoding issue? Or just plain bad chars in > the file tags? > > thanks > > N
Just chiming in here - I had the exact same problem and the source was some WGBH classical podcast tracks with characters in the comments that didn't pass valid-XML muster (xmllint sussed them out pretty easily). If I find time to noodle with an xmllint clean-up cron job or something, I'll post back. Peter - if you can put fixing this on your to-do list for a future version it would be nice. -Matt -- MJP ------------------------------------------------------------------------ MJP's Profile: http://forums.slimdevices.com/member.php?userid=30501 View this thread: http://forums.slimdevices.com/showthread.php?t=44582
_______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
