ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: debian-tex-maint@lists.debian.org,
	Danai SAE-HAN <danai.sae-han@edpnet.be>
Subject: Re: New Debian context package based on context	release 061207
Date: Mon, 11 Dec 2006 11:02:18 +0100	[thread overview]
Message-ID: <457D2CAA.80902@wxs.nl> (raw)
In-Reply-To: <20061210201832.GC24149@gamma.logic.tuwien.ac.at>

Norbert Preining wrote:
> Hi Danai!
>
> On Son, 10 Dez 2006, Danai SAE-HAN wrote:
>   
>>> So here is -0.2, which does the following:
>>> - install doc files
>>> - do NOT install any map activation files in /etc/texmf/updmap.d
>>>       
>> So if I understand correctly, ConTeXt (which I haven't used yet)
>> doesn't use the .map files anymore with pdfTeX?  This might be
>> interesting for the CJK packages.  Or is the change only relevant for
>> ConTeXt-specific fonts?
>>     
>
> No, but the map files are installed into
> 	..../texmf/fonts/map/pdftex/context/...
> so that context/pdftex finds them. But there is no need for activation
> via updmap as *only* pdftex is used. Or at least this is how I
> understand it.
>
>   

the problem with a big map file is that it is potentially problematic 
(it definitely was in the past) because there is some fuzzy logic 
involved when embedded files are handled in pdftex;

so, in context, i don't preload all map files, but use \pdfmapfile{...} 
to explicitly load a map file so that we can be sure we have the right 
one -- keep in mind that we can have files on the system with similar 
internal names (the one between " in the map file) but different metric 
(slant, ext, cap,...) ; so, when you have a problem with a missing file 
(reported by pdftex), you can use \loadmapfile[somename.map] in context

Hans

      reply	other threads:[~2006-12-11 10:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-09 21:14 Norbert Preining
2006-12-09 23:28 ` Taco Hoekwater
2006-12-10  9:51   ` [NTG-context] " Norbert Preining
2006-12-10 10:53     ` Norbert Preining
2006-12-10 21:52     ` Aditya Mahajan
2006-12-11  7:48       ` Norbert Preining
2006-12-11  9:03         ` Taco Hoekwater
2006-12-11  9:27           ` [NTG-context] " Norbert Preining
2006-12-11  9:31             ` Taco Hoekwater
2006-12-11  9:34               ` Norbert Preining
2006-12-11  9:39                 ` [NTG-context] " Taco Hoekwater
2006-12-11  9:48                   ` Norbert Preining
2006-12-11  9:54                     ` Hans Hagen
2006-12-11  9:47                 ` Hans Hagen
2006-12-11 10:23                   ` Norbert Preining
2006-12-11  9:45           ` [NTG-context] " Norbert Preining
2006-12-11 22:52           ` Sanjoy Mahajan
2006-12-12  6:18             ` [NTG-context] " Norbert Preining
2006-12-12 14:41               ` Sanjoy Mahajan
2006-12-10 11:00 ` Norbert Preining
2006-12-10 18:48   ` Danai SAE-HAN
2006-12-10 20:18     ` Norbert Preining
2006-12-11 10:02       ` 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=457D2CAA.80902@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=danai.sae-han@edpnet.be \
    --cc=debian-tex-maint@lists.debian.org \
    --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).