Re: problem with metapost files

[Oscar López]

Matej Cepl wrote:

Well, \lambda is OK on my computer, because I have configured
properly GhostScript (see pdf file on
http://www.volny.cz/cepls/ps-pdf/foo.pdf). Unpack the attached
tarball (of course, I assume that you are with real operating
system which supports links not M$ crap), and then set up an
environment variable GS_LIB to point to that directory (in
~/.profile, ~/.bash_profile, ~/.zshenv, /etc/profile, etc. --
check with set | less, that it is really set). Then open your
file with

   gs foo.ps 2>&1 | tee foo.log

in xterm and you should see messages of ghostscript loading
appropriate fonts. If there is anything wrong, send me foo.log.

Now it seems to work properly!!! Several questions, though:

1. The definition of GS_LIB does not conflict with the default GS_LIB just in the case that it existe before?

2. The links are pointing to files that actually exists in my distribution why they weren't found by latex/dvips? I suppose that the point is in the definition of $GS_LIB

3 Several messages complaingin of dvips are:

This is dvips(k) 5.86e Copyright 2001 Radical Eye Software (www.radicaleye.com)
' TeX output 2003.01.21:1843' -> foo.ps
dvips: Font cmr10 used in file /home/oscar/tmp/mp/fnflm_p.0 is not in the mapping file.
dvips: Font cmmi10 used in file /home/oscar/tmp/mp/fnflm_p.0 is not in the mapping file.
dvips: Font cmmi7 used in file /home/oscar/tmp/mp/fnflm_p.0 is not in the mapping file.
dvips: Font cmsy10 used in file /home/oscar/tmp/mp/fnflm_p.0 is not in the mapping file.
<texc.pro><special.pro>. [1</home/oscar/tmp/mp/fnflm_p.0>]

Are they important?

4. This means that I must generate every metapost file to be included in lyx by menas of:

mpost '\prologues :=1; input file.mp' in order to ensure that they have a prologues :=1; line mustn't I?

Finally I would like to thank you all your help.

   Have a nice day,

      Matej Cepl

--
http://www.iit.upco.es/~oscar
It's NO USE ... I've gone to "CLUB MED"!!