Bruce Pourciau wrote:
Thanks for any help the list can provide.
Bruce
Did I miss you making a minimal example file available?
Usually a .lyx file and the suspected .eps images linked
to a webpage to make a download from. Maybe you can send
the files one at a time to the list and not exceed the
limit the user list imposes on file attachments.
I was testing the Win32 Latex version from TexLive2005
and encountered your problem. In my case it was due to
a problem with the Latex installation. I will try to
find the solution in order to point to the problem area
on your installation. Sometimes making a minimal file
will discover the problem for you. If your example file
works on (our)other systems then you will know it is
your environment. This may be a wrong path to the folder
containing your eps files in your environment, or, they
don't get copied. So make a simple file with just one
or a few of the eps images and see if it works. Perhaps
you don't have all the helper apps for LyX installed or
one is working right. Maybe you could convert the eps
image to .png and use the .png filename in your doc
and try pdflatex and see if it views (or eps2pdf).
Here is an example that caused me a similar problem and
the fix. I'm not suggesting this is your particular
problem, just an example of possible causes. Your earlier
version, 1.3.4, maybe used some files that are obsolete
on your newer installation, perhaps Latex, not LyX.
I really think it is a good idea to try converting your
eps file(s) to another image format and including that
in your doc and see if it now displays. There may be
a simpler solution depending on the problem, or, the
solution may have a learning curve, so trying to change
the image format may be the quickest. I think there is
a method to use pdf and maintain (needed?) scalability.
Finally, an advantage of a minimal file displaying the
problem is you may be fortunate enough to have Paul Rubin
scutinize it.
--------------------------------------------------------
Dan Luecking wrote:
"The eps to pdf conversion does fail out of the box, but
that seems tobe because dvipdfm can't take PDF higher than
version 1.3. One needs to change the config file so that
the eps to pdf conversion process
(the line beginning with D) produces version 1.3 or lower.
I use D "epstopdf --outfile=%o --nocompress %i"
in config and edit epstopdf.pl (which produces 1.4 by
default on my system). Instead of editing epstopdf.pl,
one could set GS_OPTIONS=-dCompatibilityLevel=1.2
on the command line or use a gs command in config that sets
the level:
D "gswin32c.exe -q -sPAPERSIZE=letter -sDEVICE=pdfwrite
-dCompatibilityLevel=1.2 -dUseFlateCompression=true -dNOPAUSE
-sOutputFile=%o %i -c quit"
(all on one line). Problems can occur "out of the box"
because theout-of-the-box config file has incorrect quoting
for windows. The config-win provided (copy it to config)
uses epstopdf. Using dvipdfm's -vv option quickly showed me
where the problem lied (in the pdf version produced by epstopdf).
I remove quoting around the file names (%o and %i) in config's D
option, and never use filenames or paths with spaces in them."
-----------------------------------------------------------------
Regards,
Stephen
Topic ontology recapitulates entropic phylogeny.
