Colin Watson <cjwat...@debian.org> writes: > On Fri, Jun 23, 2017 at 11:49:20PM -0700, Russ Allbery wrote:
>> I'm still a bit dubious about this, since I don't believe editors and >> generators normally add it, but given how we generate the text versions >> of the documents, it's relatively easy to add a leading BOM and seems >> harmless. I'll take a look. > I share the discomfort in your previous message with using the UTF-8 > BOM. I'd have thought that a better approach here would be to fix this > at the HTTP layer: > https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt > (and other text files here) should return "Content-Type: text/plain; > charset=UTF-8", not just "Content-Type: text/plain". debian-web folks, is there a way to declare UTF-8 as the charset for all the *.txt files that originate from the debian-policy package and are served by www.debian.org? I can guarantee that all the text files shipped as part of the Policy package will be valid UTF-8. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
