![](https://secure.gravatar.com/avatar/b16ca16bcbc474a1ba15813999e212da.jpg?s=120&d=mm&r=g)
Hans Hagen wrote:
And, a small point of disagreement with the old man entry for texexec: 'texexec --output=dvi' produces pdf.
line 116 in tex.rb in the ruby base path can be adapted:
['dvips','ps','dvi'] .each do |b| @@backends[b] = 'dvips' end
That didn't change it, perhaps because of some clever code looking for prefix matches when processing options? (I need to study the code a bit more but that was one guess.) I tried the following file for fun: \setupcolors[state=start] \starttext \showcolor \stoptext 'texexec --dvi 1.tex' produces ps, via dvips, with or without the change to tex.rb. 'texexec --output=dvi 1.tex' produces pdf, with or without the change. The texexec.pl script produced dvi when given the --dvi option, but maybe it's a bad idea to allow generic dvi output (without going to postscript or pdf), for the reason you say: that the included specials depend on the backend, whether dvips or dvipsone etc. By the way I was pleasantly surprised that xdvi could display the colors in 1.dvi, I guess because ConTeXt generated direct postscript specials (like "ps: 0 0 1 setrgbcolor") rather than dvips's color specials. -Sanjoy `Never underestimate the evil of which men of power are capable.' --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.