--- Begin Message ---
- To: dvipdfmx@ktug.or.kr
- Cc: 627521-forwarded@bugs.debian.org, Henry House <hajhouse@houseag.com>
- Subject: Re: Bug#627521: texlive-binaries: dvipdfm requires DVI file to end in .dvi, breaking some usage
- From: Frank Küster <frank@debian.org>
- Date: Sat, 21 May 2011 21:30:53 +0200
- Message-id: <87hb8nzw9e.fsf@alhambra.kuesterei.ch>
- In-reply-to: <20110521125042.11722.32138.reportbug@wotan.internal> (Henry House's message of "Sat, 21 May 2011 05:50:42 -0700")
- References: <20110521125042.11722.32138.reportbug@wotan.internal>
Dear dvipdfmx developers,
is this the right contact for a bug report?
Henry House <hajhouse@houseag.com> wrote:
> The dvipdfm binary
Couldn't care less if it was only in dvipdfm. But actually it's a
symlink now, and dvipdfmx has the same bug:
> seems to require that the DVI file be named as
> *.dvi, as when passed a filename such as testdvi (an actually existing
> file in DVI format) or testdvi.tmp, it fails with the message
>
> ** ERROR ** Could not open specified DVI file: testdvi.dvi
> or
> ** ERROR ** Could not open specified DVI file: testdvi.tmp.dvi
I didn't test it with latest dvidfmx, texlive 2010 has dvipdfmx-20090708
> etc. I've rated this bug "important" because it may cause printing DVI files
> from Evince to fail with a cryptic error message in the GUI. While this clearly
> problem could be worked around within Evince by renaming temporary files to
> ensure a *.dvi extension, the real bug is in dvipdfm, which should accept the
> user's input as given, and not second-guess (at least not without checking for
> existance of the filename as literally given before altering it).
I agree with that. Do you see any chance altering that?
Regards, Frank
--
Frank Küster
Vorstand B90/Grüne OV Miltenberg und Umgebung
VCD Miltenberg, ADFC Aschaffenburg-Miltenberg
Debian Developer (TeXLive)
--- End Message ---