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: Thu, 14 Aug 2014 17:13:10 +0200	[thread overview]
Message-ID: <20140814151310.GC29858@iris.usta.de> (raw)
In-Reply-To: <20140814065720.GB7407@harkle.home.gateway>

Hi Jason,

> i'm not sure what difference there is between "stress emphasis"
> and "importance". to my mind, they are the same.

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

  Stress emphasis
  ---------------
  The placement of stress emphasis changes the meaning of the
  sentence.  The element thus forms an integral part of the content.
  The precise way in which stress is used in this way depends on
  the language.

  These examples show how changing the stress emphasis changes the
  meaning.  First, a general statement of fact, with no stress:

  <p>Cats are cute animals.</p>

  By emphasizing the first word, the statement implies that the kind
  of animal under discussion is in question (maybe someone is asserting
  that dogs are cute):

  <p><em>Cats</em> are cute animals.</p>

  Moving the stress to the verb, one highlights that the truth of the
  entire sentence is in question (maybe someone is saying cats are not
  cute):

  <p>Cats <em>are</em> cute animals.</p>
  [...]


  Importance
  ----------
  The "strong" element represents strong importance, seriousness,
  or urgency for its contents.

  Importance: The strong element can be used in a heading, caption,
  or paragraph to distinguish the part that really matters from
  other parts of it that might be more detailed, more jovial, or
  merely boilerplate.
  [...]

  Seriousness: The strong element can be used to mark up a warning
  or caution notice.

  Urgency: The strong element can be used to denote contents that
  the user needs to see sooner than other parts of the document.
  [...]

  Changing the importance of a piece of text with the strong element
  does not change the meaning of the sentence.

I think this distinction has usually been made in typography.  In
a professionally typeset technical manual, you might find "grep -v
selects the lines that are <em>not</em> matched by the pattern" or
"<strong>Warning:</strong> sed -i can destroy your file", but hardly
the other way round.  Even if people couldn't explain the rules, a
conforming text subconsciously helps understanding, just like good
orthography helps understanding even for people who make many
spelling errors when writing themselves.

That's not the main point of my patch, though.  Sure, I'm also
trying to make the description of .Sy (right now: "Format enclosed
arguments in symbolic" - ?!?) a bit clearer, but the main point is
to clearly mark .Em and .Sy as physical markup.

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

  parent reply	other threads:[~2014-08-14 15:14 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 [this message]
     [not found]     ` <20140814201627.GD7407@harkle.home.gateway>
2014-08-14 22:05       ` 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=20140814151310.GC29858@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).