Re: [Gnomesword-developers] FYI, recent development activity

[Robert P. <rob...@gm...>]

Karl,
I plan to do the Calvin commentaries how did you merg files together.


Bob


On 7/3/07, Karl Kleinpaste <ka...@kl...> wrote:
>
> "Robert Peters" <rob...@gm...> writes:
> > How did you do the hodge theology text?
>
> Generally speaking, I include the scripts which build my modules as
> part of the module content itself, though not the source files,
> because that would double (or better) the size of the download.
>
> If you look in ~/.sword/modules/genbook/rawgenbook/hodgesystheo, you
> will find 2 scripts, BuildModule and BuildAll.  _Systematic Theology_
> comes from CCEL in 4 separate *.xml.  When building, I put each in its
> own subdir (systheo[1-4]/systheo?.xml), and BuildModule produces the
> ThML-in-import-format file for one of those *.xml.  BuildAll is the
> overarching control to run BuildModule 4 times, cat(1) the group of
> them into a single monolithic *.imp, and then invoke imp2gbs to create
> the final module files.  Effective, if contorted.
>
> If you'd like to get copies of the original systheo[1234].xml that I
> used to produce HodgeSysTheo, let me know.
>
> Comedy is not pretty -- the text needed a fair amount of help.  The
> <div3> sections were badly edited/mangled and at first I thought a
> large portion of the text was simply missing, until I looked more
> carefully and found that it was all there, just not properly
> identified.
>
> > also, How would i set up an ftp for people to view?
>
> An ftp repository compatible with a Sword module manager is very
> simple: It contains the subdir structure of a typical ~/.sword area,
> consisting of mods.d and modules, and also contains mods.d.tar.gz,
> which is a single-file copy of the contents of mods.d.
>
> Sword module managers are configured by telling them a remote source's
> host and the local root of the tree where Sword things can be found,
> e.g., "ftp.kleinpaste.org" and "/pub/sword", or "ftp.crosswire.org"
> and "/pub/sword/raw".  The mod.mgr connects with ftp and retrieves
> mods.d.tar.gz from that directory, the contents of which are what the
> mod.mgr then uses as the definition of what's available in that
> repository.  When the user selects modules to be installed, the
> mod.mgr expects to find the appropriate substructure under the modules
> directory, and of course it'll whine if any of the expected files
> cannot be retrieved.  The mod.mgr is bright enough to chase its way
> into subdirectories if needed, which is important for e.g. "images"
> subdirectories (see the GnomeSword manual and BAO modules).
>
> Feel free to poke at ftp.kleinpaste.org in /pub/sword by hand, to see
> what's there.  There is more there than just the mod.mgr-compatible
> stuff -- I have other directories, in particular a "zip" directory, in
> which I maintain yet another copy of everything I produce, for the
> benefit of those who are looking for these modules but who are using a
> UI which doesn't yet support a proper mod.mgr (e.g. MacSword).
>
> --karl
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Gnomesword-developers mailing list
> Gno...@li...
> https://lists.sourceforge.net/lists/listinfo/gnomesword-developers
>