Has this ever happened to you<\/a>? You’re downloading your daughter’s Chinese homework assignment, but the file name gets all up in your mojibake<\/a>, and the results are nonsense. <\/p>\n Time to do some reverse-mojibake. <\/p>\n The first step in reversing mojibake is figuring out what wrong turn the encoding went through. I took an educated guess and assumed that the file name was encoded in UTF-8, which was then misinterpreted as ANSI. I suspect this type of error is pretty common, so it was my first stab. <\/p>\n To reverse it, therefore, we need to take the Unicode file name, convert it to ANSI bytes, then reinterpret those bytes as UTF-8. Let’s try it: <\/p>\n I’ll take the file name on the command line, convert it via the default system code page into bytes, then take those bytes and convert them back into a string by reinterpret them as UTF-8. I then rename the file with the “fixed” name. <\/p>\n Fortunately, this worked. The file name got unscrambled. <\/p>\n\nusing System.Text;\n\nclass Program\n{\n static public void Main(string[] args)\n {\n foreach (var file in args)\n {\n var bytes = Encoding.Default.GetBytes(file);\n var s = Encoding.UTF8.GetString(bytes);\n System.IO.File.Move(file, s);\n }\n }\n}\n<\/pre>\n
| U+00E5<\/td>\n | U+00AE<\/td>\n | U+00B6<\/td>\n | U+00E5<\/td>\n | U+00BA<\/td>\n | U+00AD<\/td>\n | U+00E8<\/td>\n | U+0081<\/td>\n | U+00AF<\/td>\n | U+00E7<\/td>\n | U+00B5<\/td>\n | U+00A1<\/td>\n | U+00E5<\/td>\n | U+2013<\/td>\n | U+00AE<\/td>\n | U+002E<\/td>\n | U+0070<\/td>\n | U+0064<\/td>\n | U+0066<\/td>\n<\/tr>\n | |||||||||||||||||||||||||||||||||||||
| å<\/td>\n | ®<\/td>\n | ¶<\/td>\n | å<\/td>\n | º<\/td>\n | <\/td>\n | è<\/td>\n | <\/td>\n | ¯<\/td>\n | ç<\/td>\n | µ<\/td>\n | ¡<\/td>\n | å<\/td>\n | –<\/td>\n | ®<\/td>\n | .<\/td>\n | p<\/td>\n | d<\/td>\n | f<\/td>\n<\/tr>\n<\/table>\n Converted to bytes via code page 1252 Windows Western European Latin 1 (which is the default code page for the United States): <\/p>\n
|