From: Thomas A.Schmitz <thomas.schmitz@uni-bonn.de>
Subject: Re: Times New Roman
Date: Wed, 16 Mar 2005 19:25:54 +0100 [thread overview]
Message-ID: <351bdef55377a3266998cc691aa0e15a@uni-bonn.de> (raw)
In-Reply-To: <424C517B@webmail.colostate.edu>
hmm, I have zero experience with Windows and wouldn't get near a
computer running Windows if you payed me for it, but I guess there must
be a central configuration file somewhere. On linux and unix systems,
it's called texmf.cnf. That's where you define which tex-trees you have
and in what order they should be searched. So if you want to have your
new C/Context searched first, your C/Texlive second, one of them should
be set as TEXMFLOCAL, the other as TEXMFMAIN. What does
kpsewhich -var-value TEXMFLOCAL
produce?
On Mar 16, 2005, at 7:08 PM, ishamid wrote:
>> ===== Original Message From "Thomas A.Schmitz"
>> <thomas.schmitz@uni-bonn.de>
> ====
>
>> Moreover, are you sure that your system is finding texnansi.enc?
>> What does
>> kpsewhich texnansi.enc
>> produce?
>
> Ok I realize that my texfont problems are almost certainly related to
> my
> upgrade problems:
>
> a. From C:\TeXLive (old system)
>
> \system_fonts\timesnewroman>kpsewhich texnansi.enc
> c:/TeXLive/texmf/dvips/ly1/texnansi.enc
>
> so far so good
>
> b. From C\:ConTeXt (latest system)
>
> \system_fonts\timesnewroman>C:\ConTeXt\texmf-mswin\bin\kpsewhich
> texnansi.enc
> \system_fonts\timesnewroman>
>
> nothing found
>
> So I think my problems in part go back to something I asked before:
> how do I
> get my C\:ConTeXt tree to secondarily search the TeXLive tree?
>
> Thnx for all your help!
> Idris
>
> Professor Idris Samawi Hamid
> Department of Philosophy
> Colorado State University
> Fort Collins, CO 80523
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
next prev parent reply other threads:[~2005-03-16 18:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 18:08 ishamid
2005-03-16 18:25 ` Thomas A.Schmitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-01 13:46 Alan Bowen
2008-12-01 14:04 ` Mojca Miklavec
2008-12-01 14:19 ` Alan Bowen
2008-12-01 14:28 ` Yue Wang
2008-12-01 14:51 ` Alan Bowen
2008-12-01 16:23 ` Steve Peter
2008-12-01 15:13 ` Mojca Miklavec
2008-12-01 17:38 ` Wolfgang Schuster
2008-12-01 21:12 ` Alan Bowen
2005-03-16 19:00 ishamid
2005-03-16 17:56 ishamid
2005-03-17 9:20 ` Hans Hagen
2005-03-16 16:05 ishamid
2005-03-16 15:42 ishamid
2005-03-16 15:41 ishamid
2005-03-16 17:21 ` Thomas A.Schmitz
2005-03-16 14:40 ishamid
2005-03-16 14:48 ` Taco Hoekwater
2005-03-16 14:56 ` Adam Lindsay
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=351bdef55377a3266998cc691aa0e15a@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).