From: Hans Hagen <pragma@wxs.nl>
Subject: Re: texexec.rb + pdfetex ignoring map files in $TEXMFPROJECT
Date: Fri, 18 Aug 2006 22:09:31 +0200 [thread overview]
Message-ID: <44E61E7B.8090603@wxs.nl> (raw)
In-Reply-To: <1155930463.2640.12.camel@vision.buscaluz.org>
Stuart Jansen wrote:
> Using older ConTeXt minimals based on texexec.pl, I was able to
> export TEXMFPROJECT=${PWD}/texmf
> in each projects directory and use fonts local to just that project.
>
> Switching to the latest minimal with texexec.rb, pdfetex can't find my
> custom *.map files. Interestingly, it does find my custom type-*.tex
> files.
>
strange since i use minimals here; are you sure that the cnf file has;
TEXFONTMAPS.dvipdfm = .;$TEXMF/fonts/map/{dvipdfm,dvips,}//;./fonts//
TEXFONTMAPS.dvipdfmx = .;$TEXMF/fonts/map/{dvipdfm,dvips,}//;./fonts//
TEXFONTMAPS.pdftex = .;$TEXMF/fonts/map/{pdftex,dvips,}//;./fonts//
TEXFONTMAPS.pdfetex = .;$TEXMF/fonts/map/{pdftex,dvips,}//;./fonts//
TEXFONTMAPS.luatex = .;$TEXMF/fonts/map/{pdftex,dvips,}//;./fonts//
TEXFONTMAPS.xetex = .;$TEXMF/fonts/map/{xetex,pdftex,dvips,}//;./fonts//
TEXFONTMAPS.dvips = .;$TEXMF/fonts/map/{dvips,pdftex,}//;./fonts//
TEXFONTMAPS =
.;$TEXMF/fonts/map/{$progname,pdftex,dvips,}//;$TEXMF/{$progname,pdftex,dvips}/{config,}//;./fonts//
kind of emtries?
> What is the correct way to include fonts on a project by project basis
> instead of installing them into the global ConTeXt tree?
>
as you do, use project trees (makes me think if i should add a switch --project to texexec)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
prev parent reply other threads:[~2006-08-18 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 19:47 Stuart Jansen
2006-08-18 20:09 ` Hans Hagen [this message]
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=44E61E7B.8090603@wxs.nl \
--to=pragma@wxs.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).