Comment 10 for bug 135985

I agree with adding a option to convert the encodings, but I don't think it can solve the problem completely. Some users who are just turning from MS Windows, will have lots of media files with those legacy encodings, and most of them need to have them on Windows as well in a not-too-short time during there switch. Because media players on Windows always don't support UTF-8 very well, people don't like to convert the tags at once, and they will be *very* happy to see everything work without doing any extra things or even looks (just looks) to break things. Thus, adding legacy encodings support is the best way for those users, and I think it won't cost too much to check and really worth it.