ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: modules maps fails
Date: Sat, 07 Jun 2008 11:33:35 +0200	[thread overview]
Message-ID: <484A55EF.1020408@elvenkind.com> (raw)
In-Reply-To: <6faad9f00806070211h2a9ad2dek1630befa12234e2e@mail.gmail.com>

Mojca Miklavec wrote:
> On Sat, Jun 7, 2008 at 9:28 AM, Diego Depaoli wrote:
>>> I have added map files, but I doubt that that is enough. Please try
>>> and report whether it works.
>> now, with --xtx switch, I get this error
>>
>> (/home/diego/tex/texmf-context/tex/context/base/type-xtx.tex)
>> ! Font \*map7ptrmscss*:=CharterBT-SmallCap at 6.64998pt not loadable:
>> Metric (TFM) file or installed font not found.

This is a dud/bug: there really is no font named "CharterBT-SmallCap".

The name was accidentally created when converting from tfm to actual
font names (fontinst and texfont both have a virtual small caps and
an oblique charter font, but is totally artificial).

\definefontsynonym [Charter-Roman-Caps]  [file:bchrc8a]

hopefully fixes that. The rest of the typescript should be fine.

> Proper fix - Hans, Taco,
> should I filter the useful files out of that zip and add them to the
> minimals? Which ones?

Yes, but proposing a truly minimal set is beyond me. Charter, Utopia and
Verdana are useful for sure. I am not so sure about antp and lbr, but
perhaps it is easiest to simply include all fonts that are not
superseded by tex-gyre.

Best wishes,
Taco
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-06-07  9:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 23:40 Diego Depaoli
2008-06-07  0:02 ` Mojca Miklavec
     [not found] ` <6faad9f00806061703x252df153r3e6fec92c128cb5f@mail.gmail.com>
     [not found]   ` <6faad9f00806062011i44e967d9heb837551c15d3fd8@mail.gmail.com>
     [not found]     ` <83e5fb980806070028u4eef32aat4381bb54f655c05d@mail.gmail.com>
2008-06-07  9:11       ` Mojca Miklavec
2008-06-07  9:33         ` Taco Hoekwater [this message]
2008-06-07 11:16           ` Diego Depaoli

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=484A55EF.1020408@elvenkind.com \
    --to=taco@elvenkind.com \
    --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).