From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: more font packages
Date: Tue, 27 Dec 2005 22:41:07 +0100 [thread overview]
Message-ID: <43B1B4F3.70602@elvenkind.com> (raw)
In-Reply-To: <43B1B145.2090604@wxs.nl>
Hans Hagen wrote:
>>
>> Wow! I am going to create a texmf-hraban tree. :-)
>
> nice indeed!
I settled for texmf-fonts, actually. I have a bunch of other
(commercial) fonts as well, so it made sense to group those
together, apart from my private macro files.
> suggestion:
>
> put the typescripts under
>
> tex/context/third/
>
> (taco, do we need a subdir there ... maybe just third/typescripts ?)
How about tex/context/third/hraban ? :-)
I believe an extra level is a good idea, but I have no strong
feelings about naming conventions below third/. The chance of
collisions is (very) small as it stands, so I believe there is no
need to be prescriptive beyond that extra level.
Cheers,
Taco
next prev parent reply other threads:[~2005-12-27 21:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-24 0:54 Henning Hraban Ramm
2005-12-24 9:18 ` Taco Hoekwater
2005-12-24 15:00 ` Henning Hraban Ramm
2005-12-27 21:25 ` Hans Hagen
2005-12-27 21:41 ` Taco Hoekwater [this message]
2005-12-27 21:29 ` 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=43B1B4F3.70602@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).