ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Fw: Re: Update ConTeXt 2004-12-06 for teTeX 2.99.4-beta: map files
Date: Wed, 08 Dec 2004 14:47:03 +0100	[thread overview]
Message-ID: <41B705D7.6090605@wxs.nl> (raw)
In-Reply-To: <20041208133506.3eeebc9f.taco@elvenkind.com>

Taco Hoekwater wrote:
> Toch maar eerst even alleen naar jou ipv naar ntg-pdftex ...
> 
> On the ConTeXT list, Thomas Esser stated:
> 
> 
>>>1. In ConTeXt all map files are in fonts/map/pdftex/context/*.map
>>
>>That's the wrong location. There is nothing pdftex specific in these
>>files, so the "syntax" is dvips, not pdftex. I have told Hans about it.
> 
> 
> Is this really true these days? I remember that in the past pdftex and 
> dvips mapfiles have had a number of different options, and I thought that
> was still the case. Is mapfile.c from dvips and pdftex really the same file 
> these days?

discussion on the tex live list about files being generic ended up nowhere since 
there is nothing generic defined;

i put the files under pdftex because i want the freedom to adapt them to changes 
/ bugs / whatever when needed; for instance i (and users) can manipulate these 
files by removing font names, which will make them non-dvips;

anyhow, when the new pdftex is distributed and available widely i will probably 
no longer use map files but do run-time definitions (using \pdfmapline); 
dvipdfmx will provide similar features


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
-----------------------------------------------------------------

           reply	other threads:[~2004-12-08 13:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20041208133506.3eeebc9f.taco@elvenkind.com>]

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=41B705D7.6090605@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).