All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Alexis (flexibeast) <flexibeast@gmail.com>
To: groff <groff@gnu.org>
Cc: linux-man@vger.kernel.org
Subject: man(7) <-> mdoc(7) (approximate) correspondence table?
Date: Sat, 27 Apr 2024 16:17:28 +1000	[thread overview]
Message-ID: <87h6fnwcqv.fsf@gmail.com> (raw)


[ Not subscribed to the linux-man list, so please cc me if 
replying there. ]

Hi all,

As someone who's much more familiar with mdoc(7) than man(7), is 
there an approximate 'correspondence table' somewhere that gives 
at least a rough sense of which man(7) macros to use when, in an 
mdoc(7) context, one would use a given mdoc(7) macro? Such a table 
might look something like (to use some obvious probable 
correspondences):

| mdoc(7) | man(7) | Notes
+---------+--------+-------
| Lk      | UR     |
| Op      | OP     |
| Sh      | SH     |
| Ss      | SS     |
| ⋮       | ⋮      | 

i recognise that there's no bijection in general, and that 
specific mappings might differ between projects (e.g. the Linux 
man-pages project might use a certain man(7) macro where a 
different project uses another), but even a project-specific table 
would be helpful to me.

i thought there might be such a table in either groff_man(7) or 
groff_man_style(7), but nothing leapt out ....


Alexis.

             reply	other threads:[~2024-04-27  6:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-27  6:17 Alexis [this message]
2024-04-27  8:41 ` man(7) <-> mdoc(7) (approximate) correspondence table? Alejandro Colomar
2024-04-27  9:41   ` Alexis
2024-04-27 18:52 ` Lennart Jablonka
2024-04-28  4:46   ` Alexis

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=87h6fnwcqv.fsf@gmail.com \
    --to=flexibeast@gmail.com \
    --cc=groff@gnu.org \
    --cc=linux-man@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.