discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: "Anthony J. Bentley" <anthony@anjbe.name>
To: discuss@mdocml.bsd.lv
Subject: Re: Dashes and strange markup
Date: Mon, 06 Mar 2017 07:55:25 -0700	[thread overview]
Message-ID: <22192.1488812125@cathet.us> (raw)
In-Reply-To: <86wpc2ac39.fsf@desk.des.no>

Dag-Erling Smørgrav writes:
> | .Sh NAME
> | .Nm beastie.4th
> | .Nd FreeBSD ASCII art boot module
> | .Sh DESCRIPTION
> | The file that goes by the name of
> | .Nm
> | is a set of commands designed to draw the ASCII art FreeBSD mascot
> | .Nd known simply as
> | .Ic beastie
> | .Nd to the right of the boot loader menu.

Mandoc's behavior aside, this manual should be using \(em or \(en instead
of .Nd here.

> The next issue is that I tried to replace .Nd with either \(en and \(em,
> but the former is rendered as a single hyphen and the latter as two
> hyphens, instead of actual en- or em-dashes.  Is that intentional?

\(en and \(em become en and em dashes in a Unicode locale. In an ASCII
locale, they become one and two hyphens, respectively.

> The third issue is that according to conventional English typography[*],
> the correct usage is an em-dash with no surrounding spaces, and I can't
> figure out how to suppress the spaces, short of gluing everything
> together (like\(em\&this).

I don't really understand the question here. If you put spaces in,
there will be spaces. If you don't, there won't be. It's common usage
to just leave out the spaces. For example, with double quotes:

  \(lqquotation here\(rq

-- 
Anthony J. Bentley
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2017-03-06 14:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 11:17 Dag-Erling Smørgrav
2017-03-06 14:55 ` Anthony J. Bentley [this message]
2017-03-06 16:52   ` Dag-Erling Smørgrav
2017-03-06 15:57 ` Ingo Schwarze
2017-03-06 16:39   ` Dag-Erling Smørgrav
2017-03-06 17:34     ` Ingo Schwarze

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=22192.1488812125@cathet.us \
    --to=anthony@anjbe.name \
    --cc=discuss@mdocml.bsd.lv \
    --subject='Re: Dashes and strange markup' \
    /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

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 NNTP newsgroup(s).