From: "Helin Gai" <helin.gai@gmail.com>
Subject: Strange ConTeXt - XeTeX problem
Date: Mon, 8 Jan 2007 16:04:10 +0800 [thread overview]
Message-ID: <8570be060701080004n24748833g3553761541a3648b@mail.gmail.com> (raw)
Hi,
I'm trying to learn about using XeTeX in ConTeXt. The problem is that
when I compile a file using texexec --xtx filename.tex, I get the
following error message
*** fontmap psfonts.map not found; texmf.cnf may be broken
*** font ec-lmtt10 not found in psfonts.map or host system; will
substitute Helvetica glyphs
But if I just use xdv2pdf filename.tex, everything turns out perfectly.
I'm wondering what the problem could be.
Thanks!
Sincerely,
Helin
--
Helin (Colin) Gai
Class of 2009, Duke University
Box 96332
Durham, NC 27708
Phone: 919-943-6302
helin.gai at gmail.com
hg9 at duke.edu
next reply other threads:[~2007-01-08 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 8:04 Helin Gai [this message]
2007-01-08 9:25 ` Hans Hagen
2007-01-08 12:49 ` Helin Gai
2007-01-08 15:46 ` Aditya Mahajan
2007-01-08 16:00 ` Helin Gai
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=8570be060701080004n24748833g3553761541a3648b@mail.gmail.com \
--to=helin.gai@gmail.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).