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

Paul Hardy <[email protected]> writes:

> If using the UTF-8 signature in a document is too aesthetically
> distateful (and I don't disagree), and if setting the HTTP header to
> denote a UTF-8 charset is not a universal solution because it will only
> have effect on Debian's servers, would a tool that converted such text
> files to an HTML document be desirable?  Such a hypothetical tool would
> insert a meta tag in the header saying <meta charset="UTF-8">.

That's one of the things that confuses me a bit -- why not just use the
existing HTML files?  All the text files in Debian Policy (except for
virtual-package-names-list.txt, which doesn't have any UTF-8) are
generated by rendering the HTML to text.  The HTML is there alongside, and
if you're looking at things in a web browser, I'd think they'd be
preferrable.

I assume you're looking at:

    https://www.debian.org/doc/devel-manuals#policy

All of the primary links are to HTML.

I'm certainly happy to try to get the text versions correct, but I would
expect most people would prefer to use the HTML versions.