Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
Can we please get rid of this grotesque, nonsense and absolutely confusing "ANSI as UTF-8" in the status line?
I think "UTF-8 without BOM", which is used in the menu, is correct. After all, a file is a bytestream. Even if the first bytes are EF BB BF, you never can be sure it _is_ UTF-8 text. You can assume an encoding and use it and state - in the status line - which encoding NPP actually uses for reading and writing. This may be UTF-8 with or without BOM, or may be Windows codepage 1252 (which I would not "ease" to "ANSI", because this is the next source of confusion). It cannot be "ANSI as UTF-8".
Big thanks for this software!
Yes, Notepad++ should use the correct terms. See these two bug reports: https://sourceforge.net/p/notepad-plus/bugs/4095/ and https://sourceforge.net/p/notepad-plus/bugs/3263/
I think ANSI as UTF-8 is a good description, because Notepad++ only works in your local codepage ( char not widechar ), so what you see in the editor, is what commonly is named ANSI characters. These ANSI characters are then saved as UTF-8.
No, Notepad++ is Unicode internally. Some time ago you had the choice between ANSI and Unicode builds, but "ANSI was dropped starting with version 6.0 in april 1012."
For proof get the file http://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-demo.txt and open it in N++. Of course, what you see is dependent on the capabilities of the font you use. Chances are good you already use a font which contains a wide range of glyphs.