From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: texinfo markup fixes (was: server parameter vs. server variable)
Date: Mon, 21 Apr 2003 22:23:13 +0200 [thread overview]
Message-ID: <v9y9237g7i.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3d6jhi4pu.fsf@defun.localdomain>
On Sun, Apr 20 2003, Jesper Harder wrote:
> But I think @dfn is the right mark up in this case, i.e.
>
> Server variables are often called @dfn{server parameters}.
Committed. Shouldn't we have a @dfn{Server variables} in (info
"(gnus)Server Variables") too? Where?
BTW: I think @sc{...} should be replaced with @acronym or @var in most
places. Opinions?
@sc{gnus 4.1} @sc{gnus} @sc{html} @sc{imapd} @sc{imap} @sc{mime}
@sc{nntp} @sc{oed} @sc{pem} @sc{pgp/mime} @sc{rmail}
@sc{s/mime} @sc{semi} @sc{smtp} @sc{soup} @sc{ssl} @sc{url} @sc{vm}
... should all be changed to @acronym, I think.
@sc{your@@email.address} should be @var{your@@email.address}.
I'm unsure about the following:
@sc{Cc:} @sc{Note:} @sc{To:} ?
@sc{create} @sc{append} @sc{nov} @sc{xover} @sc{head} @sc{mode reader}
Should we use @command{CREATE} or @code?
@sc{marks} ("any @sc{marks} files") ?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2003-04-21 20:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 16:59 mail splitting to another backend Ted Zlatanov
2003-04-17 18:56 ` Paul Jarc
2003-04-17 19:09 ` Ted Zlatanov
2003-04-17 19:53 ` Paul Jarc
2003-04-17 19:41 ` Simon Josefsson
2003-04-17 20:22 ` Ted Zlatanov
2003-04-17 20:31 ` Paul Jarc
2003-04-18 8:56 ` Simon Josefsson
2003-04-18 10:06 ` Kai Großjohann
2003-04-18 21:33 ` server parameter vs. server variable (was: mail splitting to another backend) Reiner Steib
2003-04-18 23:03 ` server parameter vs. server variable Paul Jarc
2003-04-20 14:35 ` Kai Großjohann
2003-04-20 15:11 ` Jesper Harder
2003-04-21 20:23 ` Reiner Steib [this message]
2003-04-21 22:05 ` texinfo markup fixes Jesper Harder
2003-04-22 0:31 ` François Pinard
2003-04-22 0:36 ` Jesper Harder
2003-04-22 0:53 ` François Pinard
2003-04-18 17:12 ` mail splitting to another backend Ted Zlatanov
2003-04-18 22:48 ` Paul Jarc
2003-04-18 23:00 ` Ted Zlatanov
2003-04-27 3:09 ` Lars Magne Ingebrigtsen
2003-04-29 18:42 ` Ted Zlatanov
2003-05-01 6:55 ` Lars Magne Ingebrigtsen
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=v9y9237g7i.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).