Bugzilla – Bug 2750
MMM importing fails to decode unicode
Last modified: 2008-09-15 14:39:24 UTC
using the new 1.5beta/rc in headless mode, the imported metadata is coming in encoded as ascii or cp1252. When extended characters appear (see test files from other unicode bugs, which is all that I have no hand), then the characters are incorrect. Raw file scan without musicmagic enabled works fine. utf8_decode_guess returns: No appropriate encodings found! System is based on debian unstable, locale en_CA.UTF-8 slimserver reports utf8 in version line
I believe this is actually a bug in MMM
Have an email sent off to sergey and wendell about this.
seems fixed with release candidate, release of 1.5 immiment.