June 21, 200620 yr Only happens on Vista. I know, their notepad is broken.Happens on all unicode versions of notepad And in Notepad2 too. Which is pretty easy to understand since I think it uses the same APIs as windows's notepad to display text.
June 28, 200620 yr Oh, this doesn't happens anymore in Notepad2!Hum, what is XVI32 doing in my taskbar ?Also, And this never happens in Notepad++ which can also be used to restore your text. PS: notepad2 doesn't use the same API than windows's notepad. That was a Big mistake. Edited June 28, 200620 yr by Camarade_Tux
June 29, 200620 yr This specific sequence should be a header. Right ?Yes, Unicode text files should have FFFE as the first word. The programmer forgot to add a check for that, and instead assumed Unicode.
July 6, 200620 yr heh, that's strange.it's not a problem with the API itself though, because i use that same API in another app and it handles the file like normal.
July 6, 200620 yr Thanks to a problem with an AutoHotKey script I think I found some explanations.The FF FE sequence is used to determine the endianness of the file. It is a BOM.If you read wikipedia's articles you know endianness is hardware-dependent.Now, do you think Notepad, Notepad2... could run on something else than little-endian machines such as Intel's processors ?So there is no need to bother with "FF FE", it will always be little-endian.Then, Notepad++ is based on ScinTilla, and ScinTilla can run on win32 and machines that support GTK+. So it can include big-endian machines. Thus, it needs this FF FE string.If you try to open a unicode text file created on a machine with a SPARC processor (SunOS) with Notepad/Notepad2, you will probably have troubles reading it.
Create an account or sign in to comment