Return-Path: owner-linux-activists@Niksula.hut.fi
Return-Path: <owner-linux-activists@Niksula.hut.fi>
Received: from joker.cs.hut.fi by hydra.Helsinki.FI (4.1/SMI-4.1/36)
	id AA22653; Mon, 23 Nov 92 04:11:27 +0200
Received: from joker.cs.hut.fi by niksula.hut.fi id <61656-2>; Mon, 23 Nov 1992 04:11:04 +0200
Received: from mail1.its.rpi.edu ([128.113.100.7]) by niksula.hut.fi with SMTP id <61504-2>; Mon, 23 Nov 1992 04:09:38 +0200
Received: from sub.aix.rpi.edu (aix.rpi.edu) by mail1.its.rpi.edu (4.1/SMHUB40);
	id AA18331; Sun, 22 Nov 92 21:09:45 EST for linux-activists@niksula.hut.fi
From: Daniel Russell <russed@rpi.edu>
Received: by sub.aix.rpi.edu (5.61-AIX-1.2/RPI-ITS-SUB10-AIX);
	id AA101871; Sun, 22 Nov 92 21:09:42 -0500 for linux-activists@niksula.hut.fi
Message-Id: <9211230209.AA101871@sub.aix.rpi.edu>
Sender: owner-linux-activists@Niksula.hut.fi
To: linux-activists@Niksula.hut.fi
X-Note1: Remember to put 'X-Mn-Key: normal' to your mail body or header
X-Mn-Key: DOC
Subject: revision control between ASCII and typeset versions
Date: Mon, 23 Nov 1992 04:09:14 +0200
Status: RO
X-Status: 

	Hello.  Awfully quiet lately.
	Does anyone have any ideas about how to control revisions/updates
when the _working_ copy (i.e. the one that the author has) is in ASCII
and the _distribution_ copy is in LaTeX?  Some ideas I have:
	1) Re- LaTeX the document from the ASCII each time a new revision
is due out to the masses
	   Problem: too much redundant work

   	2) keep an ASCII copy of the current LaTeX copy do diffs between
the old and new ASCII copies, and put the changes into the LaTeX
copy by hand.
	   Problem: it's possible the editor will miss out on information,
   	   or that diff will choke if the differences are big (I'm not
   	   that experienced with diff, does it work equally well with 
   	   flowing paragraphs as it does with code?)

   	Any improvements will be readily flamed, shot down and otherwise
degraded (postfix-negate factorial)

 dan
=====
Dan Russell			russed@rpi.edu			Linux Forever!
  	       I need a new .sig  Send me ideas, please



