ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: Making context produce dvi file.
Date: Mon, 11 Sep 2006 12:32:23 -0400 (EDT)	[thread overview]
Message-ID: <Pine.GSO.4.63.0609111216090.13800@rrpf4327h10.ratva.hzvpu.rqh> (raw)
In-Reply-To: <200609110805.47267.john@wexfordpress.com>

John,

On Mon, 11 Sep 2006, John R. Culleton wrote:

> For one recurring task I first produce a booklet version 5.5. x
> 8.5in, then a straight pdf 8.5 x 11in, all controlled by modes. The
> third format is plain text. Others recommend dvi2tty for this
> conversion. But how do I get Context to produce a dvi file? The
> Context manual does not make this clear.

Not that you asked, but dvitty does not seem to be the best way to get a 
plain text output. I am assuming that you do not have maths, otherwise 
text output will not make much sense.

Assuming that you have a document with simple structure (title, section, 
header, etc), and not too complicated floats (figures and tables), and you 
want pdf and plain text, I think that starting from xml is better. For 
simple tasks, html is sufficient. For more complicated tasks, you will 
need to define your own xml schema. In either case, you can get a pdf with 
all the bells and whistles by compiling the xml (or html) file using 
context. To get a plain text output, open your file in a browser and save 
as text  (lynx --dump or links -dump will work if the file is html) to 
get a text output.

IMHO, this is much easier than trying to coax tex to output something that 
resemples a typewritter output (fixed width fonts, no hyphenation, etc)

Aditya

  parent reply	other threads:[~2006-09-11 16:32 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
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 [this message]
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=Pine.GSO.4.63.0609111216090.13800@rrpf4327h10.ratva.hzvpu.rqh \
    --to=adityam@umich.edu \
    --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).