From: Henning Hraban Ramm <hraban@fiee.net>
Subject: Re: docs naming scheme (was: Examples...)
Date: Thu, 20 Nov 2003 19:28:33 +0100 [thread overview]
Message-ID: <59080DF0-1B87-11D8-B438-0030659899AA@fiee.net> (raw)
In-Reply-To: <185B77C2-1B7A-11D8-8EFB-000393C787B2@poellath.org>
Am Donnerstag, 20.11.03, um 17:53 Uhr (Europe/Zurich) schrieb Ralph
Pöllath:
> But that leads me to another question: What's with the naming scheme?
> It sure doesn't make it easier to memorize which of the many
> documentation PDFs covers what - unless there is in fact a reason
> behind it, in which case I'd like to know :-)
What starts with "m" ist mostly a manual (except e.g. magazines, that
start with "mag");
an "i" oder "s" means an interactive/screen version, if there's also an
"p" (paper or print) version; sometimes there are language versions, so
"eni" is english interactive, while "nlp" is nederlandse print.
What starts with "pre" has to do with presentations. What starts with
"x" is about XML.
Grüßlis vom Hraban!
--
http://www.fiee.net/texnique/
next prev parent reply other threads:[~2003-11-20 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 15:10 Examples for letters, articles, books? Ralph Pöllath
2003-11-20 16:33 ` Willi Egger
2003-11-20 16:53 ` Ralph Pöllath
2003-11-20 18:28 ` Henning Hraban Ramm [this message]
2003-11-20 18:42 ` Ed L Cashin
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=59080DF0-1B87-11D8-B438-0030659899AA@fiee.net \
--to=hraban@fiee.net \
--cc=ntg-context@ntg.nl \
/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).