Date: Mon, 9 May 2005 23:58:14 +0200 From: Joerg Wunsch <j@uriah.heep.sax.de> To: ports@freebsd.org Cc: bsd@freebsd.org Subject: teTeX 3.0 woes Message-ID: <20050509215814.GM60161@uriah.heep.sax.de>
next in thread | raw e-mail | index | archive | help
I've come across a number of occasions where the new pdflatex-based LaTeX produces PDF files where it's normally supposed to generate a DVI file instead. My devel/simulavr port is currently broken for that; while one could blame doxygen (which produces the LaTeX source in question) for that, I haven't even found a way at all to tweak the LaTeX file so it would cause a PDF file to be generated. (I could find a fix for devel/avr-libc's documentation that is also doxygen- generated. The very same fix doesn't work for simulavr though.) Now, with running texi2dvi (which comes from teTeX itself) on devel/avrdude's texinfo documentation, I run into the same issue. There appears to be no chance to convince the new LaTeX command to actually generate DVI in some situations. Does anyone know of a remedy for this? [Please keep me Cc'ed, I'm not subscribed on ports@freebsd.org] -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050509215814.GM60161>