Angus Leeming <[EMAIL PROTECTED]> writes: > > Enrico Forestieri wrote: > > > I tried dvipng 1.7 on linux and its output is exactly equal to what that > > RE matches. So it is not a problem with dvipng itself but seemingly with > > the dvipng shipped with MikTeX. > > Then I guess you know who to complain to. > > I wonder if the MikTeX version is piping its stderr stream to stdout? (For > reasons unknown.)
No, it is not like that. I can separately capture stderr and stdout. I tried compiling dvipng 1.7 under cygwin, which should be more reliable, and I am seeing a similar problem: $ dvipng ... This is dvipng 1.7 Copyright 2002-2005 Jan-Ake Larsson dvipng warning: cannot find ps2pk.map, nor psfonts.map [1 (preview-latex version 11.81) depth=6 height=16] The warning should not matter. It is due to the fact that I used the cygwin tetex-devel package (for libkpathsea) and simply did: $ ln -s /c/texmf /usr/share/texmf for using the MikTeX texmf tree, but unfortunately ps2pk.map and psfonts.map are not in /c/texmf: $ kpsewhich ps2pk.map C:/localtexmf/dvips/config/ps2pk.map $ kpsewhich psfonts.map C:/localtexmf/dvips/config/psfonts.map So, I am going to read the libkpathsea documentation for setting some environment variable... I'll see what it turns out to be. Having the sources, I can use ddd for debugging dvipng. -- Enrico
