This change establishes the Google Developer Documentation Style Guide as the official style guide for the ReadMe. This will provide a starting point for editors or writers looking to work on documentation. This edit also does an initial patch on the readme based on that style guide
* Appveyor updates
Remove unused stuff (mysql, choco)
Use MSVC 2015
Upgrade Qt to 5.9, protobuf to 3.4.1
* stick qith qt 5.6 for winxp 32bit compatibility; zlib test
* Appveyor is using a randmon clone path for pulls, get it from an env variable
Remove support for Fedora 22 (been EOL for a while)
Add support for Ubuntu 17.04 and 17.10
Note that debug builds for 17.04 and 17.10 are still affected by issue #2343, and so always fail.
* Portable mode for windows
* fix start menu in portable mode
* Make gcc an happy puppy
* Clean old installation if we are installing over an old portable mode installation
* Default to Desktop\CockatricePortable
* Settings dialog fixes
* wording
* enable cache
* caching on mac
* fix ci caching on mac
* fix
* add mac cache
* added homebrew cache and pretty print yaml (+ structural ordering)
* cleanup
* fix ccache on mac
* testing workaround
https://github.com/travis-ci/travis-ci/issues/7456#issuecomment-296505058
* try xcode7.3 instead of workaround
* cache timout value
more time for cache to upload
When checking unknown sets, consider sets with an empty long name,
set type and release date as 'incomplete'/'partial' sets.
Do not mark partial sets as known, or ask the user to enable them.
Instead, silently enable partial sets.
When a partial set becomes complete, the user is prompted to enable the
set as before. If they choose not to enable, those partial sets are
disabled, as we can no longer assume they are disabled by default.
* More descriptive reason for "to many requests" when registering
Currently the only way for a user to get a response of "to many registration attempts" is by the servers configuration to restrict the number of registration attempts but the error message presented to the user is very vague as to why they have been denied. This PR updates the reasoning. I'm open for suggestions on any clarity recommendations.
* Added more clarity
Updated error message to include email address information for even greater clarity.
