[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#489849: context: texexec --listing --dvipdfmx uses pdftex instead of dvipdfmx



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 example where the option works:
Test file test.tex:

\starttext
test
\stoptext

Command line:

texexec --dvipdfmx test

The last lines of the output, some of which is from dvipdfmx:

** WARNING ** Could not open config file "fontmapsx".
test.dvi -> test.pdf
[1]
1901 bytes written
TeXExec | runtime: 4.855625

Moreover, pdfinfo reports dvipdfmx as producer of test.pdf,
so I conclude that it was generated by dvipdfmx.

Best wishes,

     Gábor Braun

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.




Reply to: