All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marko Myllynen <myllynen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: charmap.5: clarify keyword syntax
Date: Wed, 15 Jun 2016 10:58:05 +0300	[thread overview]
Message-ID: <57610A8D.6080105@redhat.com> (raw)
In-Reply-To: <20160614165643.GF4053-UgUKS2FnFs9+urZeOPWqwQ@public.gmane.org>

Hi,

On 2016-06-14 19:56, Mike Frysinger wrote:
> On 13 Jun 2016 10:20, Marko Myllynen wrote:
>> The patch below updates charmap.5 to match the syntax all the glibc
>> charmap files are using currently.
> 
> hmm, i guess this is confusing.  when i read the man page, i see it as
> the normal syntax of "<required value>" rather than the <> being literal
> characers that you need to type out.  although in that regard, i would
> expect it to look something like:
> 	<character> <byte-sequence> [comment]
> 
> although in the locale(5) page, we rarely use the <foo> syntax.

Yes, in the locale(5) page <foo> is now used only in cases like:

  The characters <space> and <tab> are automatically included.

In the glibc charmap files the <> notation is used with keywords, the
man pages states that comment is optional but would it make thing
clearer if we would use something like:

.TP
<
.I code_set_name
> is followed by the name of the character map.

(Ok, that renders badly but you get the idea.)

Thanks,

-- 
Marko Myllynen
--
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:[~2016-06-15  7:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13  7:20 charmap.5: clarify keyword syntax Marko Myllynen
     [not found] ` <575E5EA5.6050707-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-06-14 16:31   ` Michael Kerrisk (man-pages)
2016-06-14 16:56   ` Mike Frysinger
     [not found]     ` <20160614165643.GF4053-UgUKS2FnFs9+urZeOPWqwQ@public.gmane.org>
2016-06-15  7:58       ` Marko Myllynen [this message]
     [not found]         ` <57610A8D.6080105-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-06-20 20:34           ` Michael Kerrisk (man-pages)
     [not found]             ` <60df9e3e-8ea2-0c70-c00e-af07f36b0019-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-06-21  7:07               ` Marko Myllynen
     [not found]                 ` <5768E7BE.6020002-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-06-23 10:55                   ` 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=57610A8D.6080105@redhat.com \
    --to=myllynen-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=vapier-aBrp7R+bbdUdnm+yROfE0A@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.