Thread: NSIS 3.0b2
View Single Post
Old 26th October 2015, 15:24   #8
Anders
Moderator
 
Anders's Avatar
 
Join Date: Jun 2002
Location: ${NSISDIR}
Posts: 5,528
Quote:
Originally Posted by aerDNA View Post
...especially since it is not documented.
The documentation is technically correct, the function reads UTF-16LE characters until it finds \r, \n or \0 or maxlen is reached.

You need to keep in mind that the BOM is actually Unicode Character 'ZERO WIDTH NO-BREAK SPACE' (U+FEFF) and is a legal character. It is not the only zero-width/invisible character so once you join the Unicode party you need to be prepared for files with invisible characters etc.

When special BOM handling is added it will be called out in the documentation.

IntOp $PostCount $PostCount + 1
Anders is offline   Reply With Quote