All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: problems in one or more man pages you maintain
Date: Thu, 19 May 2005 06:25:05 +0000	[thread overview]
Message-ID: <20040712185807.5ae81670.khali@linux-fr.org> (raw)
In-Reply-To: <200407121514.i6CFEqXm017215@snark.thyrsus.com>

Hi Eric,

> See http://catb.org/~esr/doclifter/problems.html for details on how
> and why these patches were generated.  Feel free to email me with any
> questions.

FYI: Link to http://catb.org/~esr/doclifter/prepatch/isadump.8.patch is broken.

> Problems with isadump.8:
> 
> 1. Parenthesized comments in command synopsis.  This is impossible
> to translate to DocBook.
> 
> --- isadump.8-orig	2004-07-10 06:49:29.502190656 -0400
> +++ isadump.8	2004-07-10 06:50:39.737513264 -0400
> @@ -7,11 +7,9 @@
>  .I addrreg
>  .I datareg
>  .RI [ "bank " [ bankreg ]]
> -(for I\u2\dC-like access)
>  .br
>  .B isadump
>  .BI "-f " address
> -(for flat address space)
>  
>  .SH DESCRIPTION
>  isadump is a small helper program to examine registers visible
>  through the ISA

This change, as is, is certainly not acceptable as it discards an
information I consider important for the reader.

BTW, why doesn't DocBook accept parenthesized comments in synopsis?
DocBook is mostly XML if I'm not mistaking, I don't see how parentheses
cause any problem. What are you going to do for C manual pages, which
all have parentheses in their synopsis?

Anyway, if there is a solid reason why DocBook cannot cope with that,
and if it is not going to be improved, I cannot see why manual pages
would need to be changed for that. The syntax used in this manual page
doesn't break any standard as far as I know. If DocBook cannot accept
it, then your "doclifter" converter simply has to learn how to handle
that case. Either drop the parenthesized comment, or (better) find an
alternate syntax to replace the parentheses. Doesn't sound that complex,
does it?

-- 
Jean "Khali" Delvare
http://khali.linux-fr.org/

  reply	other threads:[~2005-05-19  6:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:25 problems in one or more man pages you maintain esr
2005-05-19  6:25 ` Jean Delvare [this message]
2005-05-19  6:25 ` Eric S. Raymond
2005-05-19  6:25 ` esr
  -- strict thread matches above, loose matches on Subject: below --
2004-02-17 13:22 E. Gryaznova
2004-02-17  5:56 esr
2003-12-09 19:29 esr

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=20040712185807.5ae81670.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@vger.kernel.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.