> How to proceed from here. Do you still need this option and if yes why?
I never saw a need that this is fixed. --dvipdfmx works when translating
documents, that is what it is used for.
THe --listing is a different piece, a commodity. One can easily create
the respective .tex input file reading
found 489849 2018.04.04.20181118-1
stop
On 08.07.08 09:58, Gábor Braun wrote:
Hi Gábor,
> $ echo test >test
> $ texexec --listing --dvipdfmx test
> $ pdfinfo texexec.pdf
> Producer: pdfTeX-1.40.3
> So texexec.pdf was created by pdftex.
> However, the dvipdfmx backend was requested.
>
How do you come to the idea that
--dvipdfmx
does something useful?
I have read the man page of texexec, which mentions the option:
--dvipdfmx, --dvipdfm, --dpx, --dpm
Use the TeX engine (e.g. pdftex or pdfetex) to make a DVI file and
dvipdfmx(1) to turn it into PDF.
An
On Mi, 09 Jul 2008, Braun Gábor wrote:
How do you come to the idea that
--dvipdfmx
does something useful?
I have read the man page of texexec, which mentions the option:
--dvipdfmx, --dvipdfm, --dpx, --dpm
Use the TeX engine (e.g. pdftex or pdfetex) to make a DVI file and
Package: context
Version: 2008.05.21-1
Severity: minor
$ echo test test
$ texexec --listing --dvipdfmx test
$ pdfinfo texexec.pdf
Title: texexec
Subject:
Keywords:
Author:
Creator:ConTeXt - 2008.05.21 15:21
Producer: pdfTeX-1.40.3
CreationDate: Tue Jul 8 09:53:16 2008
On Di, 08 Jul 2008, Gábor Braun wrote:
$ texexec --listing --dvipdfmx test
How do you come to the idea that
--dvipdfmx
does something useful?
Ok, we could retitle the bug
texexec: please bail out with unknown arguments
Other then that I don't see a bug. You asked for compiling
6 matches
Mail list logo
