Re: [MiKTeX] epstopdf error: /undefined in .notdef
MiKTeX source code moved to GitHub
Brought to you by:
csc
From: George N. W. I. <gn...@gm...> - 2011-01-03 13:36:51
|
On Mon, Jan 3, 2011 at 8:52 AM, Ulrike Fischer <li...@ni...> wrote: > Am Mon, 3 Jan 2011 04:27:01 -0800 (PST) schrieb Peter Grabs: > >>> I tried with miktex 2.7.: >>> I:\Z-Test>set path=J:\MiKTeX2.7\miktex\bin > >> i see you removed the default space in "MiKTeX 2.7". is that on >> purpose? i seem to remember that some older versions only liked >> 8.3 paths. are there maybe still some remnants of that? > > I don't use spaces in folder and file names if I can. This avoids to > having to think about proper quoting and other problems. > > >>> Did you check your environment variables if something >>> points to another ghostscript? > >> i have no other ghostscript installed and if i remove that >> gs_fntem.ps at the expected location i get an error message. so >> that cannot be the problem. It can hard to determine if ghostscript is installed because it is often included with 3rd party applications (e.g, matlab). > Well you wrote that you did install another ghostscript: "(normally > i am quite computer savvy, but this just doesnt give me a clue, > except i installed ghostscript, but to no avail):" > > Also it never hurts to check the environment variables. I remember a > discussion where a problem was solved after an old environment > variable from a previous miktex version has been removed. You can also search your disk for ghostscript components, e.g., gswin32c.exe and other filenames you find in miktex's ghostscript. -- George N. White III <aa...@ch...> Head of St. Margarets Bay, Nova Scotia |