Not sure if this is the right place to post it, but i’ll give it a try. Changing the encoding to UTF-8 BOM would securely prevent that.

These are two reasons why I think it is dangerous to use merely UTF-8 - accidentally the files could be commited with a wrong encoding.

If the characters which require UTF-8 encoding are too far away from the start of the file (the files will grow over times due to newly added plugins) the correct encoding detection may fail. é) if Npp’s automatic encoding detection will set the encoding of the opened file to UTF-8.Īdditionally I guess that the automatic encoding detection doesn’t inspect a whole file but only some bytes from the beginning. If the encoding of the plugin list files is UTF-8 it depends on the presence of characters which require UTF-8 encoding (e.g. When other plugin authors edit the file(s) they will presumably do it with Notepad++ and it is not sure that all plugin devs have set their standard document encoding to UTF-8, it also may be ANSI (like in my case). I’ve already elaborated about this in this comment. OK for UTF-8 encoded, but with BOM is not necessary.

Notepad++ plugins download