From: Henning Hraban Ramm <hraban@fiee.net>
Subject: Re: naming and distribution of typescripts
Date: Wed, 27 Aug 2003 21:12:09 +0200 [thread overview]
Message-ID: <5B3BD0CC-D8C2-11D7-AB8B-0030659899AA@fiee.net> (raw)
In-Reply-To: <20030826221329.6e31cb87.morawski@gmx.net>
Am Dienstag, 26.08.03, um 22:13 Uhr (Europe/Zurich) schrieb Jens-Uwe
Morawski:
> Is there some standard how to name typescripts and locate them in
> a texmf-tree, so that distribution of typescripts is possible in a
> controled way?
I always name them "type-vendor-collection.tex" (e.g.
"type-adobe-palatino.tex")
and put them into mytexmf/tex/context/user
Typescripts are simply TeX files -- you could put the commands
even in your environment file or like that -- so they should
stay with "tex" instead of inventing something new that
nobody (and noproggy) understands.
BTW: My typescripts files are updated, and my site finally shows file
dates.
Grüßlis vom Hraban!
--
http://www.fiee.net/texnique/ (material/typescripts.zip)
next prev parent reply other threads:[~2003-08-27 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 20:13 Jens-Uwe Morawski
2003-08-27 19:12 ` Henning Hraban Ramm [this message]
2003-08-28 6:55 ` Jens-Uwe Morawski
2003-09-04 19:59 ` Hans Hagen
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=5B3BD0CC-D8C2-11D7-AB8B-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).