From: "Eli Zaretskii" <eliz@gnu.org>
To: "Benjamin Mann (Jr)" <ben.mann@hp.com>
Cc: gdb@sources.redhat.com
Subject: Re: FW: [Gdb-discuss] Style Conventions for Documentation?
Date: Wed, 09 Jun 2004 19:33:00 -0000 [thread overview]
Message-ID: <2719-Wed09Jun2004210324+0300-eliz@gnu.org> (raw)
In-Reply-To: <85896742E37AAA47AA56CB578CB4173B062EFB02@tayexc18.americas.cpqcorp.net> (ben.mann@hp.com)
> Date: Wed, 9 Jun 2004 12:27:29 -0400
> From: "Mann, Benjamin (Jr)" <ben.mann@hp.com>
>
> Can you help me out? I am looking for style convention information used
> in the GNU documentation, if such guidelines exist.
For general guidelines, see the Texinfo manual and the standards.texi
manual (be sure to find the latest version from the GNU FTP site).
> Because there have been many contributors to the documentation (from
> many companies and with different points of view), many styles are
> implemented for similar items. For example, sometimes command
> options are in single quotes, sometimes not.
Could you please give a concrete example or two? I'm not sure I
understand the context.
> Or lead-ins to lists or code examples sometimes end with a colon,
> sometimes with no punctuation, and sometimes with a period.
This depends on the specifics of the text, but again, please provide
an example.
> As an editor I value consistency (among other things like clear
> writing, conciseness, and so forth)
Same here.
prev parent reply other threads:[~2004-06-09 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 16:27 Mann, Benjamin (Jr)
2004-06-09 19:33 ` Eli Zaretskii [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=2719-Wed09Jun2004210324+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=ben.mann@hp.com \
--cc=gdb@sources.redhat.com \
/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