Bush hid the facts
||It has been suggested that this article be merged into Unicode in Microsoft Windows. (Discuss) Proposed since November 2013.|
|Some or all of this article's listed sources may not be reliable. (April 2010)|
Bush hid the facts is a common name for a bug present in some Microsoft Windows applications, which causes a file of text encoded in ASCII or its superset (such as in a Windows code page) to be interpreted as if it were UTF-16LE, resulting in mojibake. When "Bush hid the facts" (without newline or quotes) is put in a new (pre-Vista) Notepad document and saved, closed, and reopened, the nonsensical words "畂桳栠摩琠敨映捡獴" (Liu Benrenmotian Touyingjianmeng) appear instead.
While "Bush hid the facts" is the sentence most commonly presented on the Internet to induce the error, the bug can be triggered by many sentences with characters and spaces in a particular order so that the bytes match the UTF-16LE encoding of valid (if nonsensical) Chinese Unicode characters. Other popular strings are "this app can break", "acre vai pra globo" (Portuguese for "acre goes to Globe"), and "aaaa aaa aaa aaaaa". The bug is triggered even by the text "a ".
The bug occurs when the string is passed to the Win32 charset detection function
IsTextUnicode with no other characters.
IsTextUnicode sees what it thinks is valid UTF-16LE Chinese and returns true, and the application then incorrectly interprets the text as UTF-16LE.
Many text editors and tools exhibit this behavior because they use
IsTextUnicode as well.
The bug appeared for the first time in Windows NT 3.5 but was not discovered until early 2004. Older versions of Notepad such as those that came with Windows 95, 98, ME, and NT 3.1 do not include Unicode support so the bug does not occur.
Editing the text to not be a pattern that triggers this bug will fix it. For instance, adding a new line in the first 20 characters will work.
If the file is saved as "UTF-8" rather than "ANSI" (which in reality means Windows-1252 on systems using western European languages) the text displays correctly, because Notepad prepends a byte order mark as a non-standard UTF-8 flag, which is a different pattern that does not trigger this bug. UTF-8 without the byte order mark would still trigger the bug, as this sequence is represented identically in UTF-8 as in ASCII.
The bug is also avoided by saving as "Unicode", which in Microsoft Windows usually means UTF-16LE.
To retrieve the original text using Notepad, bring up the "Open a file" dialog box, select the file, select "ANSI" or "UTF-8" in the "Encoding" list box, and click Open. (Under Windows 2000, Notepad lacks the "Encoding" list box. Notepad2 makes the same error (by trusting IsTextUnicode), and also lacks an option to override encoding when opening a file. However, WordPad opens the text file correctly by default.)