Aaron Isotton <[EMAIL PROTECTED]> writes: > That's not the problem, it won't build anyway. There are still quite a > lot of serious problems with xmltex, passivetex and the related tools on > Debian. There are quite some bugs filed against the relevant packages, > some of which got "closed" recently but which aren't fixed at all. I'd > report them again but I don't really know which are the faulty packages. > > BTW, the '—' error is probably outputted by xmllint, not by > xsltproc because it is called with the wrong options. (Yes, I filed a > bug report against that and it got closed without fixing).
What I'm hearing you say is that the XSL toolchain in Debian is pretty highly broken still, right? Personally I would suggest moving away from xmlto and instead calling xsltproc and other processors directly. I find the "helper" scripts like xmlto do nothing to really help, especially in the case of errors. In fact, I find they make it very much harder to diagnose problems. And when you have makefiles, you can put the exact set of rules in the Makefile. This is more robust. And it's codified in the makefile, so having a long series of complex commands is no big problem, since the user still just does 'make whatever'. If something is closed but you upgrade to that version and the problem is not fixed, then please reopen the bug. If you get into problems with the maintainer, please let me know about it, e.g., the bug number, and I can take it up with the maintainer for you. Before you do that, really do do me a favor and give me exact commands being run (pointing me to DDP Makefile targets is fine) -- I am not able to trace down ownership if xmlto or any other xml "helper" script is involved. -- ...Adam Di Carlo...<[EMAIL PROTECTED]>.......<URL:http://www.onshored.com/>
