From: Ed L Cashin <ecashin@uga.edu>
Cc: ntg-context@ntg.nl
Subject: Re: Examples for letters, articles, books?
Date: Thu, 20 Nov 2003 13:42:02 -0500 [thread overview]
Message-ID: <87smki991h.fsf@uga.edu> (raw)
In-Reply-To: <185B77C2-1B7A-11D8-8EFB-000393C787B2@poellath.org> (Ralph =?iso-8859-1?q?P=F6llath's?= message of "Thu, 20 Nov 2003 17:53:41 +0100")
Ralph Pöllath <lists@poellath.org> writes:
...
> 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 :-)
A lot of TeX-philes still use 8-character name + 3-character extension
filenames. I think it's for compatibility with DOS.
--
--Ed L Cashin | PGP public key:
ecashin@uga.edu | http://noserose.net/e/pgp/
prev parent reply other threads:[~2003-11-20 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 15:10 Ralph Pöllath
2003-11-20 16:33 ` Willi Egger
2003-11-20 16:53 ` Ralph Pöllath
2003-11-20 18:28 ` docs naming scheme (was: Examples...) Henning Hraban Ramm
2003-11-20 18:42 ` Ed L Cashin [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=87smki991h.fsf@uga.edu \
--to=ecashin@uga.edu \
--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).