From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Capitalization in man pages.
Date: Tue, 6 Dec 2005 04:22:28 -0800 [thread overview]
Message-ID: <B78101C3-D90B-4E30-9D5C-699FA0FA5032@orthanc.ca> (raw)
In-Reply-To: <7359f0490512052301j592031dft96b46e860da7198d@mail.gmail.com>
On Dec 5, 2005, at 11:01 PM, Rob Pike wrote:
> If you see many instances that sow such confusion, either
> I missed them the first time or, more likely, they've been
> edited since by someone less focused.
Or perhaps the underlying conflict is that between the grammars of C
and English. C's grammar is concise, and does not suffer ambiguity
(ANSI notwithstanding), whereas English thrives on ambiguity. For man
(6) authors this is the pit of dispair.
I confess to being a fan of the BSD mdoc macros. They recommend a
writing style that strikes a reasonable balance between the goals of
prose vs. precise. But most importantly, they try to ensure
consistency throughout the documentation set. When it comes to
laying out documentation -- especially reference documentation --
consistency of style is critical to making it easy for the reader to
find what they need. The correct use of layout and typefaces will
quickly draw the reader to the information they are scanning for.
Using an offsetting typeface to highlight (only) function names will
immediately draw the eye to that information; mixing case just stalls
the rapid scanning process, as the brain has to pause to assimilate
the "almost" pattern match in the context of the search. And it's
this visual scanning process that concerns me. Mixed case for grep
is easily solved with -i.
--lyndon
next prev parent reply other threads:[~2005-12-06 12:22 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 12:07 [9fans] irc answers - man and memmove Russ Cox
2005-12-05 19:07 ` Sascha Retzki
2005-12-06 1:09 ` Paul Lalonde
2005-12-06 1:14 ` Rob Pike
2005-12-06 1:17 ` Paul Lalonde
2005-12-06 1:48 ` Russ Cox
2005-12-07 9:57 ` Gorka guardiola
2005-12-07 10:41 ` Lucio De Re
2005-12-06 1:22 ` erik quanstrom
2005-12-06 6:31 ` [9fans] Capitalization in man pages Lyndon Nerenberg
2005-12-06 7:01 ` Rob Pike
2005-12-06 9:44 ` Charles Forsyth
2005-12-06 11:01 ` Lyndon Nerenberg
2005-12-06 11:17 ` Charles Forsyth
2005-12-06 11:27 ` Lyndon Nerenberg
2005-12-06 11:12 ` Lyndon Nerenberg
2005-12-06 11:18 ` Lucio De Re
2005-12-06 12:22 ` Lyndon Nerenberg [this message]
2005-12-06 12:32 ` Charles Forsyth
2005-12-06 12:40 ` Lyndon Nerenberg
2005-12-06 13:02 ` Lyndon Nerenberg
2005-12-06 13:41 ` Charles Forsyth
2005-12-06 13:54 ` Lyndon Nerenberg
2005-12-06 14:30 ` John Stalker
2005-12-06 18:11 ` Charles Forsyth
2005-12-06 18:31 ` Rob Pike
2005-12-08 3:58 ` Lyndon Nerenberg
2005-12-08 4:10 ` Russ Cox
2005-12-08 4:55 ` Uriel
2005-12-07 3:56 ` Jeff Sickel
2005-12-06 15:57 ` jmk
2005-12-07 0:11 ` geoff
2005-12-07 0:17 ` Francisco J Ballesteros
2005-12-07 0:22 ` Steve Simon
2005-12-08 3:55 ` Lyndon Nerenberg
2005-12-06 12:46 ` erik quanstrom
2005-12-06 15:02 ` Brantley Coile
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=B78101C3-D90B-4E30-9D5C-699FA0FA5032@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9fans@cse.psu.edu \
/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).