ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Bill McClain <wmcclain@salamander.com>
Cc: NTG-ConTeXt mailing list <ntg-context@ntg.nl>
Subject: Re: font question
Date: Tue, 19 Feb 2002 12:31:06 -0600	[thread overview]
Message-ID: <3C7299EA.91B069DA@salamander.com> (raw)
In-Reply-To: <014d01c1b96a$1941d020$0400a8c0@arnhem.chello.nl>

Frans Goddijn wrote:
> 
> Thanks Bill for your message. My current problem is that I can't figure out
> why TeX says "Warning: pdfetex.exe (file tir): Font tir at 480 not found --
> Warning: pdfetex.exe (file tii): Font tii at 600 not found" -- I never
> willingly told TeX to look for these "tir" and "tii" files...

You get that sort of message when pdftex cannot find the type1 files and
it tries to fall back and generate bitmap fonts (which don't exist
either).

I haven't been through your setup, but try this just as an experiment.
It will determine if the map file is correct. Create a job with nothing
but these lines:

%****
\font\testRoman=tnr2
\font\testItalic=tnri2
\font\testItalicUpright=tnru2
\font\testRomanSlant=tnro2

\testRoman This is roman.
\testItalic This is italic.
\testItalicUpright This is italic upright.
\testRomanSlant This is roman slant.
%****

Does it run and produce the output you would expect?

-Bill

PS - I'm curious about lines such as these:

> \definefontsynonym [SerifCapsI]                       [tnrexpi]
> \definefontsynonym [OldStyleIt] [Times-RomanSCItalic]

These indicate that ConTeXt would know how to do variants such as
small-caps-italic and old-stype-italic, which I did not think was
possible. I do not see any references in the source. Did it ever work?

-Bill


  reply	other threads:[~2002-02-19 18:31 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-19 15:04 Frans Goddijn
2002-02-19 16:32 ` Bill McClain
2002-02-19 17:22   ` Frans Goddijn
2002-02-19 18:31     ` Bill McClain [this message]
     [not found]     ` <003701c1b976$6ab1c800$0100a8c0@digitpaint.nl>
2002-02-19 21:27       ` Frans Goddijn
2002-02-20 12:39         ` Bill McClain
2002-02-20 18:47         ` W. Egger
  -- strict thread matches above, loose matches on Subject: below --
2008-02-29 19:42 Font question Marcin Borkowski
2008-02-29 20:54 ` Hans Hagen
2008-02-29 22:31   ` Marcin Borkowski
2008-02-29 22:57     ` Hans Hagen
2008-03-01  0:17       ` Marcin Borkowski
2008-03-01  0:22         ` Idris Samawi Hamid
2008-03-02  8:48           ` Marcin Borkowski
2008-03-02 13:08             ` Mojca Miklavec
2008-03-02 13:20               ` Wolfgang Schuster
2008-03-04 20:58               ` Marcin Borkowski
2008-03-04 21:09                 ` Wolfgang Schuster
2008-03-04 21:49                   ` Marcin Borkowski
2008-03-05  8:40                 ` Hans Hagen
2008-03-04 22:55     ` Marcin Borkowski
2008-03-05  6:55       ` Thomas A. Schmitz
2008-03-05 14:23         ` Marcin Borkowski
2008-03-05  9:17       ` Taco Hoekwater
2008-03-05 14:29         ` Marcin Borkowski
2008-03-11 14:07         ` Marcin Borkowski
2005-12-12 15:32 Font Question Henry Blodgiitt
2005-12-07 22:46 Aditya Mahajan
2005-12-07 23:45 ` Adam Lindsay
2005-12-08  0:05   ` Aditya Mahajan
2005-12-07 23:55 ` Hans Hagen
2001-08-02 17:01 Marco Kuhlmann
2001-08-03 14:01 ` Hans Hagen
2001-08-05 21:02   ` Marco Kuhlmann
2001-08-06  7:42     ` 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=3C7299EA.91B069DA@salamander.com \
    --to=wmcclain@salamander.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).