From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Making context produce dvi file.
Date: Tue, 12 Sep 2006 19:27:02 +0200 [thread overview]
Message-ID: <4506EDE6.5010306@wxs.nl> (raw)
In-Reply-To: <E1GMtSn-0006It-00@skye.ra.phy.cam.ac.uk>
Sanjoy Mahajan wrote:
>>>> texexec --dvips yourfile
>>>>
>>> That works after excising some grqphics. Just as a matter of
>>> curiosity, why is the parameter --dvips and not dvi?
>>>
>> because one can also say -dvipdfmx
>>
>
> Trying a few tests here (TeXExec 6.2.0): 'texexec --dvi' seems
> equivalent to running 'texexec --dvips'.
>
> 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
untested
> -Sanjoy
>
> `Never underestimate the evil of which men of power are capable.'
> --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2006-09-12 17:27 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 [this message]
2006-09-14 13:28 ` Sanjoy Mahajan
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=4506EDE6.5010306@wxs.nl \
--to=pragma@wxs.nl \
--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).