From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Mike Frysinger <vapier@gentoo.org>, linux-man@vger.kernel.org
Subject: Re: [PATCH] [rfc] drop "coding: UTF-8" header
Date: Thu, 13 Aug 2020 21:07:31 +1000 [thread overview]
Message-ID: <20200813110726.thqinrnat2zy3dik@localhost.localdomain> (raw)
In-Reply-To: <c2d1c695-d6fe-465c-5c4f-a76df9754feb@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
Hi Michael and Mike,
Just an FYI here.
At 2020-08-13T09:38:06+0200, Michael Kerrisk (man-pages) wrote:
> Hi Mike,
>
> On 7/26/20 8:23 AM, Mike Frysinger wrote:
> > From: Mike Frysinger <vapier@chromium.org>
> >
> > This header is used inconsistently -- man pages are UTF-8 encoded
> > but not setting this marker. It's only respected by the man-db
> > package, and seems a bit anachronistic at this point when UTF-8
> > is the standard default nowadays.
>
> Thanks. Patch applied.
Sorry I missed Mike's original mail, but there is _something_ else
besides man-db that respects this "coding: utf-8" thing.
It's the editor that some people might use to maintain the man pages:
GNU Emacs[1].
That said, UTF-8 is an easy encoding to detect, the Unix standard of
many years now as you note, and for about that long Emacs has also
scanned the ends of files for file variables as well (in a more
expressive and powerful format), so they don't need to be packed in at
the beginning.
Also, it's no skin off me personally because I use Vim. :P
Regards,
Branden
[1] https://www.gnu.org/software/emacs/manual/html_node/emacs/Specifying-File-Variables.html#Specifying-File-Variables
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-13 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 6:23 [PATCH] [rfc] drop "coding: UTF-8" header Mike Frysinger
2020-08-13 7:38 ` Michael Kerrisk (man-pages)
2020-08-13 11:07 ` G. Branden Robinson [this message]
2020-08-13 11:27 ` Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200813110726.thqinrnat2zy3dik@localhost.localdomain \
--to=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox