All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Watson <cjwatson-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Bruno Haible <bruno-nWNVUoHt2MvYtjvyW6yDsg@public.gmane.org>,
	Werner Lemberg <wl-mXXj517/zsQ@public.gmane.org>,
	Peter Schiffer <pschiffe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: Converting man-pages to UTF-8
Date: Fri, 14 Feb 2014 16:30:35 +0000	[thread overview]
Message-ID: <20140214163035.GF6397@riva.ucam.org> (raw)
In-Reply-To: <52FE360B.9050302-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On Fri, Feb 14, 2014 at 04:28:11PM +0100, Michael Kerrisk (man-pages) wrote:
> Thanks for the extensive reply! One final point. For the pages that
> have non-ASCII characters only in source comments, not in rendered
> input source, does it matter whether or not the "coding:" tag is added?
> I ask because, simply for documentary purposes, I'm wondering whether
> we should add that tag only in the pages that have UTF-8 in the rendered
> input.

I don't *believe* it will make a difference to groff's preconv, since
all the other encodings people might be using will at worst only mangle
UTF-8 characters in comments in ways that preserve their comment status.
It might allow man-db to be marginally more efficient, but I think any
difference would be negligible.

Regards,

-- 
Colin Watson                                       [cjwatson-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org]
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-02-14 16:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 10:43 Converting man-pages to UTF-8 Michael Kerrisk (man-pages)
     [not found] ` <CAKgNAkh5tHmJc2DrcoAJsDWWFao6bPckd2sN1dw-CZDSFNi5kQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-14 11:42   ` Colin Watson
     [not found]     ` <20140214114216.GE6397-K2jUmMR1UYV4cg9Nei1l7Q@public.gmane.org>
2014-02-14 15:28       ` Michael Kerrisk (man-pages)
     [not found]         ` <52FE360B.9050302-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-02-14 16:30           ` Colin Watson [this message]
     [not found]             ` <20140214163035.GF6397-K2jUmMR1UYV4cg9Nei1l7Q@public.gmane.org>
2014-02-16  7:41               ` 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=20140214163035.GF6397@riva.ucam.org \
    --to=cjwatson-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
    --cc=bruno-nWNVUoHt2MvYtjvyW6yDsg@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=pschiffe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=wl-mXXj517/zsQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.