What's more likely is that the original web page which MPFreaker retrieved the lyrics from has mangled formatting exactly as shown. Most lyrics retrieved by MPFreaker which include apostrophes come out fine here. There are loads of cases of bad formatting which MPFreaker fixes as it inserts them into a song file.

For us to see an example of exactly what you're talking about, it would be helpful if you could point out the artist name and song title in this case. There may be something we can do about this for future MPFreakers.

I'm afraid there are too many badly-decoded-then-reencoded examples out there like this for MPFreaker to have any hope of fixing. The best we can probably hope for is for MPFreaker to recognize such garbage and to refuse it, and for it to then look elsewhere for properly encoded text.

For instance, instead of just a dot in the column, put a green check mark if it's 100% good, a red check mark if it's complete, but with horked characters, and a question mark if there are less than, say, 10 characters in there?

I suggest that last one because I've noticed that sometimes there are just one or two characters in the lyrics field, but MPFreaker considers that song to have the lyrics just because *something* is there.