RE: [Dvipng] Windows MiKTex/TexLive2007 dvipng problems with fonts

[Mark Hammond]

Jan-Ake Larsson wrote:

> This is happening because kpathsea (the TeX path-searching library)
> cannot find the appropriate fonts, usually the hang is because it cannot
> find _any_ fonts at all. The call to makepk is internal to kpathsea and
> not anything that dvipng can influence, which is why the -q flag to
> dvipng cannot do anything about the --verbose flag used by kpathsea.

MiKTeX seems to be using its own kpathsea emulation wherein directories are set 
via the MiKTeX Options utility (in the Roots tab).  These settings all appear 
correct, however.  The truly odd thing is that if I run dvipdfmx a PDF is 
generated without error with properly embedded Type 1 font subsets.  However 
yap also generates PK fonts.

> This kind of report has popped up before (when using MIKTeX) and my
> suggestion has been to reinstall. My guess is that the affected systems
> have everything installed, but the font-searching paths are wrongly set.
> I have not before seen the combination of MIKTeX and TeXlive, though.

I tested this on two systems, one running Windows Server 2003 and one running 
Windows XP, both reproduced the issue with complete MiKTeX installations and 
removal/reinstallation of the complete MiKTeX package.

In my particular case, the issue isn't with TeXlive (that isn't present on 
either system).

> (In any case, for further hints it would help to know what version of
> dvipng you are using, whether it came with MIKTeX or TeXlive, and
> whether it is linked to FreeType (best output) or libt1 (fallback) or if
> it only has the built-in PK-font support.)
>
> /JÅ

This occurs using dvipng 1.12 included with MiKTeX 2.8.  I analyzed the 
executable using dependency walker, and it has a dependency on 
MIKTEX208-FREETYPE2.DLL.

-Mark