From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: Re: [kbd] Problems in codepage.1, loadkeys.1
Date: Tue, 2 Oct 2018 22:36:45 +0200 [thread overview]
Message-ID: <20181002203645.GH3219@comp-core-i7-2640m-0182e6> (raw)
In-Reply-To: <20180612191613.AD9F13A4F12@snark.thyrsus.com>
On Tue, Jun 12, 2018 at 03:16:13PM -0400, esr@thyrsus.com wrote:
> This is automatically generated email about markup problems in a man
> page for which you appear to be responsible. If you are not the right
> person or list, please tell me so I can correct my database.
>
> See http://catb.org/~esr/doclifter/bugs.html for details on how and
> why these patches were generated. Feel free to email me with any
> questions. Note: These patches do not change the modification date of
> any manual page. You may wish to do that by hand.
>
> I apologize if this message seems spammy or impersonal. The volume of
> markup bugs I am tracking is over five hundred - there is no real
> alternative to generating bugmail from a database and template.
>
> --
> Eric S. Raymond
Applied. Thanks!
> Problems with codepage.1:
>
> Broken command synopsis syntax. This may mean you're using a
> construction in the command synopsis other than the standard
> [ ] | { }, or it may mean you have running text in the command synopsis
> section (the latter is not technically an error, but most cases of it
> are impossible to translate into DocBook markup), or it may mean the
> command syntax fails to match the description.
>
> The incorrect sytntax used to express option alternation cannot be lifted
> to XML. In addition, use of <> around the filename argument violates
> the normal convention and is unparseable.
>
> --- codepage.1-unpatched 2010-07-24 20:52:28.000000000 -0400
> +++ codepage.1 2010-07-24 20:53:50.000000000 -0400
> @@ -7,16 +7,16 @@
> .B codepage
> [
> .I \-c
> -] | [
> +|
> .I \-l
> -] |
> +|
> .I \-L
> -] | [
> +|
> .I \-a
> |
> .I nnn
> ]
> -.I <file.cpi>
> +.I file.cpi
>
> .SH DESCRIPTION
> The
> Problems with loadkeys.1:
>
> Unbalanced group in command synopsis. You probably forgot
> to open or close a [ ] or { } group properly.
>
> --- loadkeys.1-unpatched 2018-05-16 19:54:23.148111507 -0400
> +++ loadkeys.1 2018-05-16 19:57:02.391029285 -0400
> @@ -7,7 +7,6 @@
> [
> .I -a --ascii
> ] [
> -[
> .I -b --bkeymap
> ] [
> .I -c --clearcompose
> _______________________________________________
> kbd mailing list
> kbd@lists.altlinux.org
> https://lists.altlinux.org/mailman/listinfo/kbd
--
Rgrds, legion
prev parent reply other threads:[~2018-10-02 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 19:16 [kbd] Problems in codepage.1, loadkeys.1 esr
2018-10-02 20:36 ` Alexey Gladkov [this message]
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=20181002203645.GH3219@comp-core-i7-2640m-0182e6 \
--to=gladkov.alexey@gmail.com \
--cc=kbd@lists.altlinux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).