Description of Problem: I am experiencing several problems with index entries. In particular, some as described in this message: http://sources.redhat.com/ml/docbook-tools-discuss/2000/msg00262.html The most annoying part is that, as the message above says, running jadetex/pdfjadetex an even number of times still makes lots of entries be printed as "-999", but TeX does NOT report any unresolved references. That's IMHO unacceptable, as it gives a false sense of "safety": the problem is still there (just check the PDF output), but you're not told about it. Consequences should also be obvious in an automated environment. Unfortunately I can't provide a testcase, as my problems are occurring with a very large document, which I can't redistribute anyway. I have noticed, though, that version 3.11 solves some of the problems and, more importantly, never omits to mention that there are unresolved references. This might be of enough help to others. I am taking a closer look at the tens of unresolved references still left and they all seem to be variants of two or three basic problems (e.g. <indexterm>s in <entry>s); those, which are not solved in 3.11 yet, will be filed in a separate report (with simple testcases). Version-Release number of selected component (if applicable): jadetex-3.6-4 Additional Information: Newer releases of JadeTeX are hosted by SourceForge. You can check e.g. the ChangeLog here: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jadetex/jadetex/ChangeLog The layout of the distribution archive has changed a bit; I have a SRPM which I'll happily email, upload or attach if you are interested.
Fixed in jadetex-3.11-1.