From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: Re: Making context produce dvi file.
Date: Thu, 14 Sep 2006 14:28:53 +0100 [thread overview]
Message-ID: <E1GNrGv-0007SX-00@skye.ra.phy.cam.ac.uk> (raw)
In-Reply-To: Your message of "Tue, 12 Sep 2006 19:27:02 +0200." <4506EDE6.5010306@wxs.nl>
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.
next prev parent reply other threads:[~2006-09-14 13:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 12:05 John R. Culleton
2006-09-11 13:14 ` luigi scarso
2006-09-11 14:58 ` Willi Egger
2006-09-11 14:11 ` Mari Voipio
2006-09-11 15:21 ` Hans Hagen
2006-09-11 18:06 ` John R. Culleton
2006-09-11 19:08 ` Hans Hagen
2006-09-11 21:37 ` Sanjoy Mahajan
2006-09-12 17:27 ` Hans Hagen
2006-09-14 13:28 ` Sanjoy Mahajan [this message]
2006-09-14 18:55 ` Hans Hagen
2006-09-14 22:03 ` Sanjoy Mahajan
2006-09-11 19:14 ` Mojca Miklavec
2006-09-12 7:18 ` Hans Hagen
2006-09-11 16:32 ` Aditya Mahajan
2006-09-11 19:34 ` Sanjoy Mahajan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1GNrGv-0007SX-00@skye.ra.phy.cam.ac.uk \
--to=sanjoy@mrao.cam.ac.uk \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).