[sword-devel] compiling modules

[Beth Bryson]

Chris Little wrote:
> Hi Beth,
> 
> I don't know if I've mentioned or promised this to you before, but we 
> have a decent USFM to OSIS converter at 
> http://crosswire.org/ftpmirror/pub/sword/utils/perl/usfm2osis.pl

Thanks.  What I'm using is a modified version of a very old sfm2osis.pl,
but I should definitely try this newer one.  (I wasn't sure if you would
remember me...)

> We have some module import documentation in progress on our Wiki at 
> http://www.crosswire.org/wiki/index.php/DevTools:Modules

Okay, I hadn't poked around the wiki enough--this helps.  But if I want
to, can I edit it to add a little more info about the tools?  For
instance, it would be helpful if somewhere what you explained about the
arguments was available.  Or could I submit suggested edits for someone
to approve?

> It may be worth your trouble to export a module using mod2vpl to see an 
> example vpl file, as expected by vpl2mod. E.g. 'mod2vpl ASV 1 > asv.txt' 
> will export the module ASV to asv.txt, which can then be re-imported 
> with 'vpl2mod asv ./ 1'.

I wanted to try this, but I didn't know if it would work with compressed
modules.  I think I tried it on one and didn't get anywhere.  This is
nice and specific--thanks!

> I can't see how this is possible. imp2vs doesn't retain the state of
> verse references from one entry to another and has no notion of verse
> ordering, so I don't think it's possible to have verse offset errors. It
> also cannot function at all unless it parses the verse references after
> $$$, so I would guess that you were actually seeing results from one of
> your vpl2mod builds that wasn't overwritten.

I hadn't thought of that, but that actually sounds quite likely!  I will
experiment more, and see if I can figure out just which parts do or
don't work....

Thanks for helping me understand how it *should* work.  These
suggestions along with Greg's will help me go in the right direction.
Thanks to both of you!

-Beth