[sword-devel] Beginning help question - Calvin's Commentaries

[Troy A. Griffitts]

Dave,

if you have the test programs, parsetest should show you if you have a 
valid range.  Something like:

parsetest "mat 1:1-17;lk 3:23-38"

should show that this is valid, and you can assume that anything 
parsetest recognizes will be treated the same way in a $$$ imp key, so:

$$$mat 1:1-17;lk 3:23-38
<text>

SHOULD work, but I can't guarantee it.  If it doesn't, we should fix it. 
  If you try it and it does, let us know so we can tell others with 
confidence :)

	-Troy.



Dave Hall wrote:
> OK.
> 
> I could possibly generate an import file from the source instead of rawcom.
> 
> Is the structure of the import file defined somewhere?
> The
> 	$$$<passage>
> 	<text>
> is clear but Calvin does a harmony of the Gospels and the Law so I would
> like to link 2 or more gospel(or law) passages to the same text.
> 
> Would something like these work:
> 	$$$MATTHEW 1:1-17
> 	$$$LUKE 3:23-38
> 	<text>
> or
> 	$$$MATTHEW 1:1-17; LUKE 3:23-38
> 	<text>
> 
> 
> Chris, I could upload the zcom (20MB) or rawcom files somewhere. Or, if I
> get the import file correct, I could up load that but its 60MB.
> 
> - Dave
> 
> 
> -----Original Message-----
> From: Troy A. Griffitts [mailto:scribe@crosswire.org]
> Sent: Friday, December 06, 2002 1:15 PM
> To: sword-devel@crosswire.org
> Subject: Re: [sword-devel] Beginning help question - Calvin's
> Commentaries
> 
> 
> Dave,
> 	Yeah, I also had troubles with sf today.  I think they're just
> having 
> server problems (or else they changed their wiki url structure).
> 
> 	It could just be that mod2imp doesn't yet correctly handle exporting
> of 
> linked verses.  That's a very probable conclusion, so I wouldn't worry 
> about it, if I were you.  Now _I_ have to worry about it. :)
> 
> 	Thanks for taking all this time to work on such a large piece of
> work! 
>   I'm sure Chris can let you know where he'd like the module (emailed, 
> or a link to it posted somewhere).  He can place it in the beta site for 
> you.
> 
> 	-Troy.
> 
>