ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: font mapfiles
Date: Tue, 17 May 2005 23:42:47 +0200	[thread overview]
Message-ID: <B95387F0-1725-4A3E-93C7-70FF51F02A00@uni-bonn.de> (raw)
In-Reply-To: <428A31E3.1000402@wxs.nl>

Hans, Adam,

thanks for your replies! I just tried with Adam's version and my old  
version of cont-sys.tex, but it made no difference - do I have to  
rebuild the formats every time I change this file? I'll do more  
experiments this weekend, but will be away from my computer from  
tomorrow till Friday. Thanks for your help, I'll report back!

Best

Thomas

On May 17, 2005, at 8:03 PM, Hans Hagen wrote:

> Thomas A. Schmitz wrote:
>
>> Sorry for reposting, but I'm really curious about this issue!
>> I just had to reinstall my TeX installation (upgrade to OS X  
>> 10.4).  After mucking around with my old TeX, I decided to  
>> reinstall, and I  hit a problem: even though I ran updmap, ConTeXt  
>> doesn't seem to work  with the fonts I installed myself unless I  
>> include the \loadmapfile [foo] either in the typescript or in the  
>> source file. This wasn't the  case before. I also tried moving the  
>> mapfiles to texmf/fonts/map/ pdftex/context insteadt of just fonts/ 
>> map/, but that didn't change  anything. Am I missing something  
>> obvious, or is this the expected  behavior? I much prefer to have  
>> system-wide mapfiles since I use  LaTeX from time to time and want  
>> the same fonts available there. They  work with plain pdfetex as  
>> well, it's just ConTeXt that gives  trouble. So my question is: is  
>> this the new setup, are we supposed to  load mapfiles this way,  
>> and what is the advantage over the old method?
>>
>
> my guess is that you lost your local cont-sys.tex and that cont- 
> sys.rme is used now; in there you will find
>
> \resetmapfiles
>
> so, in your case, you need a special version of cont-sys.tex  
> (preferable in context/user so that it is not lost when you wipe  
> out context/base)
>
> btw, in some future release i will drop context map files and stick  
> to inline map entries,
>
> 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
> -----------------------------------------------------------------
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>

  reply	other threads:[~2005-05-17 21:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17 15:14 Thomas A. Schmitz
2005-05-17 18:03 ` Hans Hagen
2005-05-17 21:42   ` Thomas A. Schmitz [this message]
2005-05-17 21:49     ` Adam Lindsay
2005-05-17 22:00     ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2005-05-12 13:00 Thomas A. Schmitz

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=B95387F0-1725-4A3E-93C7-70FF51F02A00@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.de \
    --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).