The specification for the manifest file for web applications was
recently updated¹ and it changed one of the recommended file extensions
from `.manifest` to the unique `.webmanifest`².
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
¹ 0eecadd090
² https://github.com/w3c/manifest/issues/346
* Reorganized media types and order them alphabetically
* Include some new media types in order to align with what is provided
by the Apache configurations.
c805353c41/src/media_types/media_types.conf
Four years ago the recommended file extension for AppCache manifest
files was changed¹ from `.manifest` to `.appcache`. So, even adding
into consideration the transitional period, it no longer makes sense
to keep the configurations that ensure that `.manifest` files are
served with the AppCache required `text/cache-manifest` media type.
Also, recently, `.manifest` became one of the recommended file
extensions for web application manifest² files.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
¹ https://html5.org/r/5812
² http://w3c.github.io/manifest/
Apply all the configs used for `.ico` files to `.cur` files as the two
image formats are almost identical.
The MIME type for the `.cur` file doesn't matter as browsers seem to
sniff the content. However, `image/x-icon` is specified because it's
the one usually used for `.ico` file and because it's shorther then the
other frequentlly used one (`image/vnd.microsoft.icon`), making the
header size smaller.
See also:
* http://en.wikipedia.org/wiki/ICO_%28file_format%29
* http://msdn.microsoft.com/en-us/library/windows/desktop/ms648007%28v=vs.85%29.aspxClose: #5.
Use a `CHANGELOG.md` file to keep the project history available within
the repository, therefore, making it easier to track what has changed
since the last tagged release.
Léo Colombaro