From: Hans Hagen <pragma@wxs.nl>
Cc: ConTeXt Mailing List <ntg-context@ntg.nl>
Subject: Re: newbi: config
Date: Wed, 05 Jun 2002 23:52:05 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20020605234620.02bae450@server-1> (raw)
In-Reply-To: <3CFDEF9B.65DE52A2@lamel.bo.cnr.it>
At 01:01 PM 6/5/2002 +0200, Eros Albertazzi wrote:
>Let me take again your time, sorry but being alone w/o teachers in my
well, you live in italy so you can be teached even in italian by GB (aka
Oblomov, on this list)
>istitution and moving to ConText is not that easy. Running the example
esp not easy since you start with the tricky things: graphictext uses
tex/mp/gs etc ... -)
>\starttext
>\startMPcode
> graphictext "MP" scaled 8 reversefill
> withdrawcolor .7blue withfillcolor .7white
> dashed evenly withpen pencircle scaled 1pt ;
>\stopMPcode
>\stoptext
>
>I obtain an almost empty page with just page number 1 at top and
>several warning (maybe unrelated to the result)
>
>pdftex : needs map file: original-context-symbol.map
>pdftex : needs map file: pl0-ams-cmr.map
>pdftex : needs map file: original-vogel-symbol.map
no problem, just a warning
>Warning: pdfetex (file /usr/share/texmf/dvips/config/pdftex.map):
>invalid entry
> for `rtxphvbo': SlantFont/ExtendFont can be used only with embedded T1
>fonts
>Warning: pdfetex (file /usr/share/texmf/dvips/config/pdftex.map):
>invalid entry
> for `rtxphvro': SlantFont/ExtendFont can be used only with embedded T1
>fonts
>Warning: pdfetex (file /usr/share/texmf/dvips/config/pdftex.map):
>invalid entry
> for `rtxptmbo': SlantFont/ExtendFont can be used only with embedded T1
>fonts
>Warning: pdfetex (file /usr/share/texmf/dvips/config/pdftex.map):
>invalid entry
> for `rtxptmro': SlantFont/ExtendFont can be used only with embedded T1
>fonts
>}]
these are warnings: looks like some of you rmap files define slanted
versions of embedded fonts, you may want force embedding (good idea anyway
even for times etc)
in order to get graphictext working, are you sure that makempy runs ok,
i.e. that pstoedit is installed and in your path?
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-06-05 21:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 19:02 Eros Albertazzi
2002-06-05 7:59 ` Tobias Burnus
2002-06-05 11:01 ` Eros Albertazzi
2002-06-05 21:52 ` Hans Hagen [this message]
[not found] ` <Pine.LNX.4.44.0206050954160.22693-100000@hils.physik.fu-be rlin.de>
2002-06-05 20:05 ` Hans Hagen
2002-06-06 7:55 ` Tobias Burnus
2002-06-06 8:24 ` Taco Hoekwater
2002-06-06 8:48 ` Hans Hagen
2002-06-06 8:54 ` Tobias Burnus
2002-06-05 21:54 ` Hans Hagen
2002-06-07 9:09 ` Eros Albertazzi
[not found] <5.1.0.14.1.20020606111535.0346cd20@server-1>
2002-06-06 10:06 ` Tobias Burnus
2002-06-06 11:40 ` Taco Hoekwater
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=5.1.0.14.1.20020605234620.02bae450@server-1 \
--to=pragma@wxs.nl \
--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).