From: David Wooten <dw@trichotomic.net>
Subject: OpenType installation basics for ConTeXt
Date: Wed, 20 Apr 2005 16:01:31 -0700 [thread overview]
Message-ID: <ac06a09db75c2e8d44f2a8e2f58733e5@trichotomic.net> (raw)
Greetings all, and esp. Adam :)
Been toying with Adam Lindsay's recent PracTeX Journal guide for
installing OpenType. The sample with torunska works (though the noted
GPOS errors are there) up to the point where I issue the command:
texexec --pdf --mode=compact --once
texnansi-LIGA-KERN-public-torunska.tex
Whereupon I receive the following (I've cut it perhaps too severely,
let me know what more would be helpful to see):
[ v. much cut out ]
systems : end file texnansi-LIGA-KERN-public-torunska at line 63
kpathsea: Running mktexpk --mfmode / --bdpi 72 --mag 1+0/72 --dpi 72
texnansi-LIGA-KERN-AntykwaTorunskaMe
d-Regular
mktexpk: don't know how to create bitmap font for
texnansi-LIGA-KERN-AntykwaTorunskaMed-Regular.
kpathsea: Appending font creation commands to missfont.log.
)
Warning: pdfetex (file texnansi-LIGA-KERN-AntykwaTorunskaMed-Regular):
Font tex
nansi-LIGA-KERN-AntykwaTorunskaMed-Regular at 72 not found
kpathsea: Running mktexpk --mfmode / --bdpi 72 --mag 1+0/72 --dpi 72
texnansi-LIGA-KERN-AntykwaTorunskaMe
d-Italic
mktexpk: don't know how to create bitmap font for
texnansi-LIGA-KERN-AntykwaTorunskaMed-Italic.
[ cut: same for each font variant ]
Output written on texnansi-LIGA-KERN-public-torunska.pdf (17 pages,
364611 byte
s).
Transcript written on texnansi-LIGA-KERN-public-torunska.log.
return code : 0
run time : 51 seconds
total run time : 52 seconds
---
Each of the named variants seems to have been installed correctly in
tetex.local, and I did texhash, etc.
Thanks very much,
David Wooten
next reply other threads:[~2005-04-20 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 23:01 David Wooten [this message]
2005-04-20 23:21 ` Adam Lindsay
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=ac06a09db75c2e8d44f2a8e2f58733e5@trichotomic.net \
--to=dw@trichotomic.net \
--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).