tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Jason McIntyre <jmc@kerhand.co.uk>
Cc: tech@mdocml.bsd.lv
Subject: Re: mdoc(7): improve description of .Em and .Sy
Date: Fri, 15 Aug 2014 00:05:14 +0200	[thread overview]
Message-ID: <20140814220514.GK29858@iris.usta.de> (raw)
In-Reply-To: <20140814201627.GD7407@harkle.home.gateway>

Hi Jason,

Jason McIntyre wrote on Thu, Aug 14, 2014 at 09:16:02PM +0100:
> On Thu, Aug 14, 2014 at 05:13:10PM +0200, Ingo Schwarze wrote:

>> Citing from 
>> http://www.w3.org/html/wg/drafts/html/CR/text-level-semantics.html
[...]

> these are nice tidy rules, though i note no example is given for
> importance.

Oh, they do have an example for importance, i just cut it for brevity.

> anyway, i'm just trying to say it's blurry.

That is certainly true.  All the more reason for trying to at least
make the idea as clear als possible, even though cases where the
application is ambiguous will no doubt occur in practice.

> emphasis is not
> just about "stress" (more a spoken thing anyway). yes, in that case you
> can change the meaning of a sentence. what about:
> 
> 	The shell is a
> 	.Em command line interpreter .
> 
> 	The shell is a
> 	.Sy command line interpreter .

Actually, it depends on the context.  I would consider the following
good usage:

  When espie@ complained what a
  .Em horribly
  designed programming language the shell is,
  halex@ tried to argue that it's not actually
  .Em that
  bad, and jmc@ remarked that it's just a
  .Em command line interpreter .

  Some commonly installed programs:
  .Bl -bullet
  .It
  scp is a
  .Em remote copy program.
  If is part of the OpenSSH suite...
  .It
  The shell is a
  .Sy command line interpreter .
  Many flavours are available: ksh, csh, zsh, bash, ...
  .It
  sed is a non-interactive
  .Em stream editor
  ...

> this is not stress emphasis, but i'd pick Em.
> maybe i'd be wrong (along with 1000 other man pages).

Hm, i'm not quite sure which context you are thinking of.

> yes, i can see the mess you're trying to clean up.
> i'm fine with your diffs, and haven;t a better solution to hand.

Good, so it's in.

Yours,
  Ingo
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

      parent reply	other threads:[~2014-08-14 22:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-13 21:22 Ingo Schwarze
2014-08-13 22:54 ` Guy Harris
2014-08-14 16:07   ` Ingo Schwarze
     [not found] ` <20140814065720.GB7407@harkle.home.gateway>
2014-08-14 15:13   ` Ingo Schwarze
     [not found]     ` <20140814201627.GD7407@harkle.home.gateway>
2014-08-14 22:05       ` Ingo Schwarze [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=20140814220514.GK29858@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=jmc@kerhand.co.uk \
    --cc=tech@mdocml.bsd.lv \
    /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 NNTP newsgroup(s).