ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Nigel King <king@dircon.co.uk>
Cc: Gerben Wierda <Sherlock@rna.nl>
Subject: Re: texfont and type-tmf.dat
Date: Wed, 08 Oct 2003 18:14:30 +0100	[thread overview]
Message-ID: <BBAA0486.16A39%king@dircon.co.uk> (raw)
In-Reply-To: <5.2.0.9.1.20030811144332.022c1f50@server-1>

Dear Gerben or Hans,
I have been away on holiday. So I have lost the result of this thread. Have
you or Hans solved this problem. If so, do I need to upgrade i-tetex or
ConTeXt or both. I would really like to solve this problem and get back to
standard ConTeXt fonts.

TIA

> From: Hans Hagen <pragma@wxs.nl>
> At 00:05 07/08/2003 +0200, Gerben Wierda wrote:
> 
>> Yes, this could be. If texexec or any ConTeXt tool does not use texmf.cnf
>> values but has hardcoded ideas about where to find stuff (texmf), then the
>> rearranging of the texmf directories could have an influence. Hans can
>> probably say if this is possibly the case. After all, the rearranging had
>> no ill effects whatsoever on TeX or LaTeX, because where files are is
>> governed by texmf.cnf and that was adapted as well to reflect the changed
>> situation. If there is hardcoded stuff in texexec that is playing a role
>> (I am guessing here), making it dynamic by calls to kpsewhich is a good
>> solution.
>> 
>> For the rest, the content of texmf.tetex is created by Thomas Esser, not
>> me. And there you will find not a complete set of URW but an Adobe set and
>> thatis what the discussion is also about. hans is right in stating that.
> 
> context can happily work in the texmf tree and does depemnd on its own
> trees; with regards to texfont:
> 
> - it will install in either texmf-fonts or texmf-local, depending on what
> is present; the reason for having texmf-fonts is that we need a place for
> commercial fonts (and texmf-local is for my updates, local stuff etc)
> 
> - texfonts uses prefixed names (texnansi-* and alike) for several reasons:
> (1) when i buy a font, i wan tto copy the fonts to some temp path, call
> texfont, and have the job done; i don't want to mess around with 8 char
> names that may conflict is i do something wrong;
> 
> - another reason for texfonts naming sheme of 'third party fonts' is that
> when one starts slanting fonts (and alike) the kb naming sheme does not
> keep track of what slant is used, which in principle will lead to conflicts
> if one has multiple instances (wherever they may come from)
> 
> - for the same reason i keep separate map files for those third part
> collections
> 
> - with regards to the fonts on tex live the confusion comes from the mix of
> adobe names and urw type ones. So far whatever i made default, failed on
> someones system, which is why we have now type-akb for the mixed users
> 
> - also: context font mechanism is set up in a way that makes it possible to
> combine fonts with minimal calls (once understood -), supporting relative
> scaling and alike; i don't want user sto be dependent on one (few) persons
> to define / install / use fonts.
> 
>> If that is the case, texfont is a problem because it hard codes locations
>> where texmf.cnf is the source for locations and kpsewhich is the way to
>> find out about them.
> 
> afaik it uses kpsewhich an-r env vars and one can set things on the command
> line as well; there is not so much hard coded in there -)
> 
> Hans

-- 
Nigel

  reply	other threads:[~2003-10-08 17:14 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BAA1DC4D.ECA9%king@dircon.co.uk>
2003-08-06 20:21 ` Nigel King
2003-08-06 22:05   ` Gerben Wierda
2003-08-07  6:42     ` Nigel King
2003-08-08  0:31       ` darnold
2003-08-08  1:14         ` Trouble with updated Context darnold
     [not found]       ` <1591.209.209.17.128.1060305294.squirrel@webmail.inreach.co m>
2003-08-08  7:47         ` Hans Hagen
     [not found]     ` <1516.209.209.15.183.1060302710.squirrel@webmail.inreach.co m>
2003-08-08  7:48       ` texfont and type-tmf.dat Hans Hagen
2003-08-11 13:00     ` Hans Hagen
2003-10-08 17:14       ` Nigel King [this message]
2003-10-08 17:32         ` Patrick Gundlach
2003-10-08 17:59           ` Nigel King
2003-10-08 18:13             ` Patrick Gundlach
2003-10-08 22:04               ` Hans Hagen
2003-10-09  9:00                 ` Patrick Gundlach
2003-10-09  9:23                   ` Hans Hagen
2003-10-09 10:15                     ` Patrick Gundlach
2003-10-09 17:31                       ` Nigel King
2003-10-09 18:52                         ` Patrick Gundlach
2003-10-14 21:48                           ` Nigel King
2003-10-14 22:14                             ` Patrick Gundlach
2003-10-14 22:58                               ` Nigel King
2003-10-14 23:04                                 ` Patrick Gundlach
2003-10-14 23:27 George N. White III
2003-10-14 23:46 ` Patrick Gundlach
  -- strict thread matches above, loose matches on Subject: below --
2003-10-10 17:38 George White
2003-10-10 20:21 ` Patrick Gundlach
2003-08-03  5:37 Matthew Huggett
2003-08-03  5:57 ` David Arnold
2003-08-04  8:14 ` 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=BBAA0486.16A39%king@dircon.co.uk \
    --to=king@dircon.co.uk \
    --cc=Sherlock@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).