ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Gerben Wierda" <Gerben.Wierda@rna.nl>
Subject: Re: Getting texfont to do batch installs on gwTeX (was  Re:	Palatino)
Date: Wed, 23 Nov 2005 18:46:24 +0100 (CET)	[thread overview]
Message-ID: <20969.159.46.248.233.1132767984.squirrel@mail.rna.nl> (raw)
In-Reply-To: <43849D11.7000400@wxs.nl>

> Gerben Wierda wrote:
>
>>texfont and/or ConTeXt seems to be keyed to a certain distribution setup.
>>I would say that for ConTeXt that is ok (though as far as I know Hans
>>himself keeps the fonts in TEXMFFONTS or so, so he needs a specialized
>>type-tmf.dat as well). That the default is TeX Live also seems to be fine
>>to me.
>>
>>
> the reason for a separate three texmffonts is that it permits me to
> update the main tree (wipe out, copy new) and still have my installed
> extra fonts
>
> (i tried to get a texmffonts var in the regular texmf.cnf but that was
> rejected: objection "too many trees" while in the meantime we have more
> trees in tl as well -)
>
>>The easiest way would be if you can give this as an argument to texfonts.
>>
>>Another issue is that fonts can be in multiple trees. Some i-Packages may
>>install in texmf.local (so it can be easily uninstalled), or fonts can be
>>in texmf.tetex or texmf.gwtex). I do not know enough about texfont, but
>> if
>>Hans wants to work with me we can sort that out. After all, I probably
>>have a good example of a non-TL multi-tree setup. BTW, there are support
>>reasons why I do not use the TEXMFMAIN name or the standard texmf-dist
>>directory name.
>>
>>
>
> ah, i see, so the problem is TEXMFMAIN in the dat file
>
> before we start hacking ... this --ro stands for --rootlist so it may be
> a list; so
>
> ..... --ro=TEXMFMAIN,TEXMF.TETEX,TEXMF.GWTEX

--ro=TEXMFMAIN,TEXMFTE,TEXMFGW

> should work; can someone test that?

Are these "write" or "read" trees? If it is write, then my guess is the
default shoul dbe TEXMFLOCAL because officially that is the place where
local site modifications should go. That would also survive an upgrade or
install of TeX itself.

G

  reply	other threads:[~2005-11-23 17:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22  1:27 Palatino David Arnold
2005-11-22  9:29 ` Palatino Taco Hoekwater
2005-11-22 15:02   ` Palatino David Arnold
2005-11-22 15:32     ` Palatino Hans Hagen
2005-11-22 17:08       ` Palatino David Arnold
2005-11-23 14:16         ` Getting texfont to do batch installs on gwTeX (was Re: Palatino) Adam Lindsay
2005-11-23 16:07           ` Gerben Wierda
2005-11-23 16:47             ` Hans Hagen
2005-11-23 17:46               ` Gerben Wierda [this message]
2005-11-23 18:19                 ` Hans Hagen
2005-11-23 21:07               ` David Arnold
2005-11-26 10:39                 ` Taco Hoekwater
2005-12-01 19:04                 ` Hans Hagen
2005-11-23 16:10           ` Hans Hagen
2005-11-23 20:51           ` David Arnold
2005-11-23 21:39             ` Hans Hagen
2005-11-23 23:04 Adam Lindsay
2005-11-24 23:13 ` 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=20969.159.46.248.233.1132767984.squirrel@mail.rna.nl \
    --to=gerben.wierda@rna.nl \
    --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).