ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "George N. White III" <whiteg@dfo-mpo.gc.ca>
Cc: Wouter Verheijen <wouter.verheijen@worldmail.nl>,
	conTeXt <ntg-context@ntg.nl>
Subject: Re: Tables and graphs
Date: Wed, 27 Dec 2000 16:20:17 -0400	[thread overview]
Message-ID: <Pine.SGI.4.31.0012271605380.153867-100000@wendigo.bio.dfo.ca> (raw)
In-Reply-To: <3.0.6.32.20001227093332.013aa750@pop.wxs.nl>

On Wed, 27 Dec 2000, Hans Hagen wrote:

> Hi George,
>
> >there may be ways in texexec to specify some programs that should be
> >run before the context processing.  If the programs are simple, it
>
> Texexec has a --convert but currently that is limited to some local xml
> filter. We can generalize that but it can be dangerous so we need to
> discuss it first. Say that there is
>
> --convert=myscript
>
> that takes whatever.abc and converts it into whatever.tex, is it accepted
> that teh old file is overwritten, or should I save it first and restore it
> later?

maybe the input format for the problem at hand (a hook to automate
conversion of some external format into .tex that will be included in a
document)  _should_ be xml.

In any case, "whatever.tex" should only be overwritten if "whatever.abc"
is newer.  This way you have the "whatever.tex" in case you need to study
the contents, and if you edit it and save a new version it won't be
overwritten unless there is a good reason (e.g., the input "abc" file is
changed).

-- 
George N. White III <WhiteG@dfo-mpo.gc.ca>  tel: 902.426.8509
  Bedford Institute of Oceanography, Nova Scotia, Canada (TZ=AST4ADT)


      reply	other threads:[~2000-12-27 20:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-22 17:26 Wouter Verheijen
2000-12-23  6:52 ` Johannes H?sing
2000-12-27  8:33   ` Hans Hagen
2000-12-23 14:02 ` George N. White III
     [not found] ` <Pine.SGI.4.31.0012230948570.141578-100000@wendigo.bio.dfo. ca>
2000-12-27  8:33   ` Hans Hagen
2000-12-27 20:20     ` George N. White III [this message]

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.SGI.4.31.0012271605380.153867-100000@wendigo.bio.dfo.ca \
    --to=whiteg@dfo-mpo.gc.ca \
    --cc=ntg-context@ntg.nl \
    --cc=wouter.verheijen@worldmail.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).