From: David Arnold <darnold@northcoast.com>
Subject: svn manuals
Date: Sat, 26 Nov 2005 10:32:37 -0800 [thread overview]
Message-ID: <5F2B2835-2140-48DF-9217-9E7854A51DD2@northcoast.com> (raw)
Hans, Taco, et al,
I think it would be a good idea (possibly saving you a lot of list
answering time) if you put a README file in each manual directory.
This could contain instructions such as:
1. Which is the main file to compile.
2. Some font handling instructions. Maybe a reminder of what to do
with texfont and type-tfm.dat on different systems. User would be
handy in getting this right.
3. Or, as font setups head to an environment file, maybe alternate
environment files could be provided to get a plain vanilla no other
fonts other than what is supplied with cont-fnt.zip.
Hopefully, other on this list can come up with other suggestions for
the README. I've just named a few that I know will help me.
David
next reply other threads:[~2005-11-26 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 18:32 David Arnold [this message]
2005-11-27 9:29 ` Taco Hoekwater
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=5F2B2835-2140-48DF-9217-9E7854A51DD2@northcoast.com \
--to=darnold@northcoast.com \
--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).