ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: fonts / proposal
Date: Mon, 06 Aug 2001 14:13:37 +0200	[thread overview]
Message-ID: <5.1.0.14.1.20010806140354.027c1330@server-1> (raw)
In-Reply-To: <200108061017.MAA29360@plane.elvenkind.com>

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
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


  reply	other threads:[~2001-08-06 12:13 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 [this message]
2001-08-06 13:14         ` siep
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=5.1.0.14.1.20010806140354.027c1330@server-1 \
    --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).