From: Tobias Wolf <towolf@gmail.com>
Subject: Re: cont 2005.10.27 & t5-lmtt10 font problem
Date: Fri, 4 Nov 2005 19:34:45 +0100 [thread overview]
Message-ID: <e06bd0fe0511041034r772df474j8471930003826e05@mail.gmail.com> (raw)
In-Reply-To: <436B7BA2.6080308@wxs.nl>
On 11/4/05, Hans Hagen <pragma@wxs.nl> wrote:
> Tobias Wolf wrote:
>
> >My system, as I mentioned, is teTex 3 from Debian unstable, which has
> >a weird new map system that is working through .cfg files in
> >/etc/texmf/updmap.d . I kept it there, so it mounts lm.map itself (is
> >it used anyway in ConText?).
> >
> >
> i don't use updmap at all
>
> context loads map files on demand (when configured in cont-sys.tex)
>
> when no cont-sys.tex is present, then cont-sys.rme is used
>
> the presense of those files in /etc is disturbing (and strange since tex
> has pretty well layed out tree with defined configuration places)
>
> i have no idea how tex + friends can/will locate those files
I think they want to make people use /etc for configuration, which
could make sense if you want to make backups of the system config.
The updmap.d directory is supposed to make mounting maps easier, I
guess. You just drop a file there containing the Map/MixedMap
assignments and that is merged into updmap.cfg on issuing updmap-sys.
Pretty confusing all that.
But on the other hand, Hans, why can't I compile the PDFTex docs
because I don't have this (
http://www.ntg.nl/pipermail/ntg-context/2004/006705.html )
And secondly, why is the file system searched case sensitive, so that
the fonts are called in lowercase through the ConText maps
(ec-raw-lte5002), so that I have to rename all files, but then
mktextfm fails because it looks for ec-raw-LTe50021?
For me the disturbing things are starting to prevail in my ConText
experience. Is it supposed to be like that?
-- Tobias
> Hans
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
next prev parent reply other threads:[~2005-11-04 18:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 21:45 VnPenguin
2005-11-01 22:17 ` Thomas A. Schmitz
2005-11-01 23:01 ` VnPenguin
2005-11-02 21:23 ` Tobias Wolf
2005-11-02 22:25 ` VnPenguin
2005-11-04 9:57 ` Tobias Wolf
2005-11-04 10:21 ` VnPenguin
2005-11-04 10:43 ` Taco Hoekwater
2005-11-04 12:44 ` Tobias Wolf
2005-11-04 13:38 ` Taco Hoekwater
2005-11-04 14:48 ` Tobias Wolf
2005-11-09 10:40 ` Hans Hagen
2005-11-04 15:17 ` Hans Hagen
2005-11-04 18:34 ` Tobias Wolf [this message]
2005-11-04 19:10 ` Taco Hoekwater
2005-11-04 21:30 ` Tobias Wolf
2005-11-09 8:30 ` Hans Hagen
2005-11-04 19:40 ` compiling pdftex docs (was: cont 2005.10.27 & t5-lmtt10 font problem) Taco Hoekwater
2005-11-04 21:15 ` Tobias Wolf
2005-11-04 22:15 ` compiling pdftex docs Taco Hoekwater
2005-11-05 10:59 ` compiling pdftex docs => BUG Taco Hoekwater
2005-11-09 8:34 ` compiling pdftex docs Hans Hagen
2005-11-09 8:28 ` cont 2005.10.27 & t5-lmtt10 font problem Hans Hagen
2005-11-07 10:16 ` Debian Installation (was: cont 2005.10.27 & t5-lmtt10 font problem) Taco Hoekwater
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=e06bd0fe0511041034r772df474j8471930003826e05@mail.gmail.com \
--to=towolf@gmail.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).