Add EOF and BOM sections

Author: ehmicky

README.md

@@ -32,6 +32,7 @@ information.
 - [System configuration](#system-configuration)
 - [Character encoding](#character-encoding)
 - [Newlines](#newlines)
+- [EOF and BOM](#eof-and-bom)
 - [File paths](#file-paths)
 - [Filenames](#filenames)
 - [Shell](#shell)
@@ -247,6 +248,36 @@ don't, which is why when reading from or writing to a file the OS-specific
 newline [`os.EOL`](https://nodejs.org/api/os.html#os_os_eol) should be used
 instead of `\n`.
 
+# EOF and BOM
+
+The [substitute character](https://en.wikipedia.org/wiki/Substitute_character)
+(`CTRL-Z`)
+[stops file streams](https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/read?view=vs-2017#remarks)
+on some Windows commands when in text mode. This includes the
+[`type` command](https://ss64.com/nt/type.html) in `cmd.exe`. As a consequence
+that character should be avoided in non-binary files.
+
+As opposed to Windows, Unix does not implicitely add a newline at the end of
+files. Thus it is recommended to end files with a
+[newline character](#newlines). However please remember that Windows will print
+these as if two newlines were present instead.
+
+The [BOM](https://en.wikipedia.org/wiki/Byte_order_mark) is a special character
+at the beginning of a file indicating its
+[endianness](https://en.wikipedia.org/wiki/Endianness) and
+[character encoding](https://en.wikipedia.org/wiki/Character_encoding). Since
+it creates issues with
+[shebangs](<https://en.wikipedia.org/wiki/Shebang_(Unix)>) and adds little
+value to [UTF-8](https://en.wikipedia.org/wiki/UTF-8), it is better not to add
+it to new files. However if a BOM is present in input, it should be properly
+handled. Fortunately this is the default behavior of Node.js core methods, so
+this should usually not create any issues.
+
+Character encoding, newlines and EOF behavior should be specified with
+[editorconfig](https://editorconfig.org/). They can also be enforced with tools
+like [ESLint](https://eslint.org/docs/rules/eol-last) and
+[Prettier](https://github.com/prettier/prettier).
+
 # File paths
 
 While `/` is used as a file path delimiter on Unix (`/file/to/path`), `\` is
@@ -805,6 +836,11 @@ retrying few milliseconds later.
   [log-symbols](https://github.com/sindresorhus/log-symbols).
 - use [`os.EOL`](https://nodejs.org/api/os.html#os_os_eol) when reading from or
   writing to a file, `\n` otherwise.
+- end files with a newline.
+- use [editorconfig](https://editorconfig.org/).
+- avoid the
+  [substitute character](https://en.wikipedia.org/wiki/Substitute_character)
+  (`CTRL-Z`) in non-binary files.
 - use
   [`path.normalize()`](https://nodejs.org/api/path.html#path_path_normalize_path)
   when writing a file path to a terminal or file. Otherwise use Unix paths