From: "GEERT@telefonica.net" <GEERT@telefonica.net>
Subject: Re : My ConTeXt cannot use Type1 fonts...
Date: Thu, 31 Mar 2005 22:37:08 +0200 [thread overview]
Message-ID: <37a543bbb2.3bbb237a54@teleline.es> (raw)
I had exactly the same problem today after updating from an older
tetex/context to the latest version of tetex.
Problem seems to be some modifications in pdftex.
After moving my type1 fonts (that previously worked fine) with their
tfm, afm and type1 files to the new $HOME/.texmf-var/fonts folder,
putting the map files in $HOME/.texmf-var/fonts/map folder and including
those mapfiles with updmap, texexec generated the pdf file with pk
bitmap fonts.
Although I believed that tex could find all necessary font files and
mapfiles, it was only after explicitly adding
\loadmapfile[myownfonts.map]
in the tex file, that everything suddenly worked fine (this was not
necessary in my old tetex/context setup).
Don't know if this will work with your chinese fonts, but you could give
it a try....
geert
reply other threads:[~2005-03-31 20:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=37a543bbb2.3bbb237a54@teleline.es \
--to=geert@telefonica.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).