ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: peter.rolf@arcor.de
Subject: Re: Emdedding Acrobat Reader
Date: Fri, 20 Sep 2002 15:15:16 +0200 (MEST)	[thread overview]
Message-ID: <6441526.1032527716817.JavaMail.ngmail@mx11.arcor-online.net> (raw)

Thanks Bill for the fast and detailed help!

I fixed the different naming in /definefontsynonym[] and the linked
map file. Still no errors, still no embedding...

My \autoloadmapfilestrue was also disabled. I tried this out earlier,
but due to the fact that I copied all map-files into /pdftex/config
I got tons of warnings (fonts already defined). MiKTeX isn't the easiest
base to install and learn ConTeXt...
All ConTeXt related map files are now in the /pdftex/config/context path
but I still get some warnings after the first page:

...
pdftex         : using map file: ec-bh-lucida.map
pdftex...
...
[1.1{psfonts.map}
Warning: PDFETEX (file ec-bh-lucida.map): cannot open font map file
Warning: PDFETEX...
...

This is much better than getting over 1000 lines per texexec pass, but not as
it should be.

Also thanks for your hint to the file name database. I will use mktexlsr
in the future (instead of pushing the "refresh now" button in mo).

I will follow your suggestion, to install the desired fonts with texfont.pl.
Let's see what happens. But for now I will take a long break, `cause

"Browsing the font sub-tree of the texmf directory can drive you crazy."
[from mtexfont.pdf]

Peter
-----------------------------------------------------------------------
Kaufen Sie sich Ihren Kandidaten! Nur 49 Cent!
Vom 20. bis 22. September:
http://www.arcor.de/home/redir.php/email.kandidat
-----------------------------------------------------------------------


                 reply	other threads:[~2002-09-20 13:15 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=6441526.1032527716817.JavaMail.ngmail@mx11.arcor-online.net \
    --to=peter.rolf@arcor.de \
    /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).