[Pkg-crosswire-devel] Thoughts on sword-frontend and packaging sword modules

DM Smith dmsmith555 at yahoo.com
Mon Aug 17 19:15:25 BST 2009

On 08/17/2009 01:54 PM, Dmitrijs Ledkovs wrote:
> * About packaging crosswire texts
> I've played around with Jonathan's scripts. Scripts are nice =) But
> this scripts are packaging binary files from a raw zip file into a
> deb.
> Something that would be great is to actually get hold of source (eg
> OSIS formatted texts) and then use $format2mod utilities to build
> these modules and recreate from scratch files that are packaged in
> rawzip's.
> First of all this will stress-test $format2mod utils for generating
> modules and will be able to notice regressions in the sword utils.
CrossWire does not maintain original source, except for the KJV. The 
reason is fairly straightforward: we rely on primary sources and once 
converted into a module the desired information has been captured.

While I have argued that we should maintain copies of these originals 
and the scripts that converted them, it is not going to happen. AFAICT, 
the reason is that CrossWire does not want to become a secondary source 
of primary material. Each module's conf should give the location of the 
primary source. (I say should because it is not very accurate, 
especially when the holder of the primary keeps moving it around w/o 
maintaining permanent links.)

You are welcomed to the KJV text that I maintain.

In Him,

More information about the Pkg-crosswire-devel mailing list