Re: Bug#865713: Declaring a charset of UTF-8 for policy files

On Sun, Jun 25, 2017 at 8:54 AM, Simon McVittie wrote:

> For what it's worth, I agree that declaring the correct charset in HTTP
> metadata is a better solution than prepending U+FEFF ZERO WIDTH NO-BREAK SPACE
> (aka the "byte-order mark") in the file content.

Forcing every text file to UTF-8 isn't the correct solution either,
since it breaks text files that are not encoded in UTF-8 (such as old
dedication texts) and does not work on Debian mirrors that are not
controlled by us.