From: siep@elvenkind.com
Cc: pragma@wxs.nl
Subject: Re: fonts / proposal
Date: Mon, 6 Aug 2001 15:14:00 +0200 (CEST) [thread overview]
Message-ID: <200108061409.QAA29928@plane.elvenkind.com> (raw)
In-Reply-To: <5.1.0.14.1.20010806140354.027c1330@server-1>
On 6 Aug, Hans Hagen wrote:
> At 11:22 AM 8/6/2001 +0200, siep@elvenkind.com wrote:
>
>>For me, it is a frequent source of confusion when Context does things
>>its own way. Filesearching deviating from kpsewhich filesearch was one
>>example; mapfile loading different from what dvips and pdftex do on
>>their own would be another.
>
> actually, file searching is not that different, since the only filetype
> supported by kpsewhich in tex itself are "tex" and "tfm"; i only block
> system wide searches for certain cases by forcing local searches, an dmost
> can be configured; global searches screw up any project with similar file
> names; context is meant for usage is highly structered projects' if you
> refer to figure inclusion, well this is messy anyway between tex's and apps -)
>
> concerning map files: dvips and pdftex already live in a world on their
> own, also, mapfiles can be highly conflicting [try to include a pdf graphic
> while using the default pdfonts.map and there is a reasonable change that
> you run into troubles due to naming conflicts]; also, many fonts in the map
> files are either not on any system, or in different names, etc etc.
> Actually, pdftex should be capable of using a format specific cfg file.
>
> I try to adapt as much as possible to anything standard, but esp with
> regards to fonts, less is standardized that one wishes, and i want once and
> for all to get rid of missing glyphs depending on what cd i mounted.
>
> Actually, it would already help a lot if mapfiles would be structured,
> properly named, etc
>
> Hans
I am certainly not claiming that things are perfect the way they are,
but I have my own workarounds, and I get along ok with kpsewhich and
mapfiles as they are.
What about letting out-of-the-box pdftex and dvips read the same
mapfiles that they would read outside Context, and letting Context use
kpsewhich for all its file searching, and that any non-standard
behaviour would have to be explicitly turned on in a configuration file?
Siep
next prev parent reply other threads:[~2001-08-06 13:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-03 15:32 Hans Hagen
2001-08-03 20:06 ` Giuseppe Bilotta
2001-08-04 11:45 ` Taco Hoekwater
2001-08-06 8:29 ` Hans Hagen
2001-08-07 17:59 ` Re[2]: " Giuseppe Bilotta
2001-08-08 8:32 ` Hans Hagen
2001-08-04 12:30 ` siepo
2001-08-06 8:38 ` Hans Hagen
2001-08-06 9:22 ` siep
2001-08-06 12:13 ` Hans Hagen
2001-08-06 13:14 ` siep [this message]
2001-08-07 8:40 ` Taco Hoekwater
2001-08-08 9:13 ` Hans Hagen
2001-08-08 9:34 ` siep
2001-08-08 12: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=200108061409.QAA29928@plane.elvenkind.com \
--to=siep@elvenkind.com \
--cc=pragma@wxs.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).