From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: svn manuals
Date: Sun, 27 Nov 2005 10:29:28 +0100 [thread overview]
Message-ID: <43897C78.9010504@elvenkind.com> (raw)
In-Reply-To: <5F2B2835-2140-48DF-9217-9E7854A51DD2@northcoast.com>
David Arnold wrote:
> 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:
Good idea.
> 1. Which is the main file to compile.
or just display the (series of) command(s) required to run
> 2. Some font handling instructions.
> 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.
That is the idea behind the \startnotmode[atpragma], but those
definitions are a bit buggy. Of course Hans is never *not*
'atpragma', and up 'til now, he was the only person compiling
the manuals.
> 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.
Two more items are handy if the files get moved around between people:
4. Original (source) location of the manuals
5. Copyright & Contact info
Taco
prev parent reply other threads:[~2005-11-27 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 18:32 David Arnold
2005-11-27 9:29 ` Taco Hoekwater [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=43897C78.9010504@elvenkind.com \
--to=taco@elvenkind.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).