* re-enforce requested project file formats and basic character-level coding style
* emphasize the Win/DOS requirement that BAT/CMD files *must* have CRLF line endings
.# Discussion
Using [EditorConfig](http://editorconfig.org) style rules helps devs to
maintain the file formatting and style of the project, even while using different
editors. This minimizes the semi-invisible, but, paradoxically, visually noisy,
whitespace differences between commits. It can also help enforce file format
requirements (such as the Win/DOS CMD shell requiring CRLF line endings for
correct functioning of BAT/CMD files).
* change file encoding of the basic shim to be in a normal ASCII character set
.# DISCUSSION
Within PowerShell, `echo STRING > FILE` generates a file encoded in UCS-2-BOM format
(or "Unicode", in PowerShell terminology). UCS-2 later morphed into the similar
UTF-16 encoding format, and, within PowerShell, is treated as a "fuzzy equivalent"
encoding. Problematically, these UCS-2 files are misinterpreted by CMD, which expects
files using the ASCII (or "extended-ASCII") character encoding. And, in general, the
UCS-2 format has many drawbacks when interpreted outside of a narrow PowerShell
window. So, in general, it's best to stick to pure ASCII (or UTF-8, *without BOM*)
encoded files, if at all possible.
NOTE: ASCII (not "extended-ASCII") and UTF-8 (non-BOM) encoded files are exactly equivalent.
NOTE: "Extended-ASCII" is poorly defined, requiring an associated Windows Code Page designation to firmly establish the encoding.
ref: [Unicode UTF and BOM] http://www.unicode.org/faq/utf_bom.html @@ https://archive.is/TKnyk
ref: [Unicode and NET] http://csharpindepth.com/Articles/General/Unicode.aspx @@ https://archive.is/czs89
.# Discussion
Appveyor doesn't have partial `appveyor.yml` suppression. So, unless the
`appveyor.yml` configuration file is completely suppressed, non-primary devs
receive notification errors with every build/test of the application. By
removing the user-specific notifications, other devs can now build/test the
application code (via the recipe specified within `appveyor.yml`) without
receiving notification errors.
For any given developer, personalized notification settings can be added on
top of the repo `appveyor.yml` project settings via the "Settings / Notifications"
section.
Simon Hartcher