7. Diagnosing problems

You've gone through all the trouble of installing dvipng, carefully read all the instructions in this manual, and still can't get something to work. The following sections provide some helpful hints if you find yourself in such a situation.

7.1 Contact information

Bug reports should be sent to [email protected].

Questions, suggestions for new features, pleas for help, and/or praise should go to [email protected]. For more information on this mailing list, send a message with just the word `help' as subject or body to [email protected] or look at http://lists.nongnu.org/mailman/listinfo/dvipng.

Offers to support further development will be appreciated. For developer access, ask on [email protected].

For details on the TeX path-searching library, and mktexpk problems, see (kpathsea)Common problems section `Common problems' in Kpathsea.

7.2 Debug options

The `-d' flag to dvipng helps in tracking down certain errors. The parameter to this flag is an integer that tells what errors are currently being tracked. To track a certain class of debug messages, simply provide the appropriate number given below; if you wish to track multiple classes, sum the numbers of the classes you wish to track. To track all classes, you can use -1.

Some of these debugging options are actually provided by Kpathsea (see (kpathsea)Debugging section `Debugging' in Kpathsea).

The classes are:

1

Normal dvi op-codes

2

Virtual fonts

4

PK fonts

8

TFM files

16

Glyph rendering

32

FreeType calls

64

Encoding loads

128

Color specials

256

GhostScript specials

512

T1lib calls

1024

Kpathsea stat calls

2048

Kpathsea hash table lookups

4096

Kpathsea path element expansion

8192

Kpathsea path searches

This document was generated on November, 11 2006 using texi2html 1.76.