Michael H wrote:
> Hi John,
>
> If you're planning to submit to crosswire for hosting, All of these questions are handled by the
> module maintainer at crosswire (currently Peter.) You don't really need to worry about them,
> other than to confirm your source does compile. You need to confirm it's clean source (the OSIS,
> ThML etc. has no technical flaws), and that it compiles cleanly, but the module you build is only
> for testing, local use. Peter (or the current maintainer) builds the module to be hosted on the
> server. Once you've completed the module and it works, you submit the source material to
> compile a module, not a complete/compiled module.
>
> If you're planning to host a repository, then these are important concerns. Using the 4 bit flag is fine for everything, but note
> that if you're actually displaying 64kb of text at one time, response time on some devices gets nearly unmanageable. More text
> in one chunk = more lag.
I am working on a project that is a collaboration of two small publishing houses, one in Quebec and one in France. We are
preparing a set of Bible study materials for French-speaking African pastors, to be used in AndBible.
I have set up a repository that will be used in the confines of the project. So I am learning how to build modules, hopefully
reasonably optimized for this project. I say resonably, because it is hard to predict the hardware environment over time going
forward.
As to whether we submit any of our modules to Crosswire, that remains to be determined by the boards of the publishing houses.
Some materials are copyrighted with specific rights negotiated for this project. Others are public domain or otherwise
non-restricted by the copyright owners.
> If you're building for personal use, plain text generally runs a bit faster and less cpu intensive
> (not that any computer/phone/device is going to have any visible difference these days) and the
> memory cost is minimal. So.. you're phone battery lasts a bit longer if you leave the module
> uncompressed, but you'll run out of memory more quickly. Crosswire compresses everything,
> mostly to keep internet bandwidth down, but there are minor copyright concerns as well.
It's hard to know which constraint will be the critical one. In Africa, internet connectivity is not a given, and bandwidth is pretty
much guaranteed to be an issue. But the primary distribution method will be side-loading from MicroSD cards. We will be
targeting a specific Chinese tablet, but since AndBible runs well on phones also, and since hardware changes every few months,
there is no way to know what devices people may want to use it on and how much storage they have. It is pretty much a given
that many phones will be low-end. As to battery life, many pastors will be charging their devices with solar panels. So battery life
is also an issue, but sunshine is plentiful. Since some constraints are at odds with other constraints (ie. cpu/battery life vs
storage/bandwidth), we will see how things go.
> Related to "installing" the module before compressing it with mod2zmod... You need to be able
> to access the plain text module with diatheke (is diatheke still supported?) from the same
> command line you will run mod2zmod. That is, the command line needs to be able to access the
> module: the command line program diatheke is your testing tool to determine it does.
Ok I've got to figure out what this means. DM also gave me some pointers.
Are there any cases where mod2zmod must be used, or does mod2zmod only apply to commentaries and bibles that I can do
with osis2mod anyway? It looks like tei2mod can do compression, too.
> Regarding mod2zmod - I never made it work.. I was only successful using the compression
> within osis2mod.
My other question was about compressed GenBooks. I notice that all the GenBooks I have downloaded from Crosswire are
rawgenbooks. Also I don't see reference to compression of GenBooks in the wiki. So is there such a thing, or are GenBooks
always Raw?
Thanks!
John
> On Fri, Jan 26, 2018 at 4:49 PM, John Dudeck <john.dud...@sim.org> wrote:
> In the Wiki, on the http://wiki.crosswire.org/DevTools:Modules page it gives directions for
> using mod2zmod for compressing modules.
>
> However osis2mod.exe has command-line switches for creating compressed modules.
>
> My question is: do these produce equivalent results? Which is preferred?
>
> For GenBooks, is mod2zmod the only way to compress them?
>
> Related question re mod2zmod. When it says "First you will need to install the module so
> that it can be accessed using the SWORD engine", exactly what does this mean? I am
> building each module in its own branch of an svn repository, and would like to create the
> compressed module in that tree. This is working fine using osis2mod. Is there a way to do
> the same with mod2zmod?
>
> Thanks and sorry for the newby questions.
John Dudeck
Programmer at Editions Cle Lyon, France
john.dud...@sim.org j...@editionscle.com
--
Sign in Swiss restaurant:
"Our wines leave you nothing to hope for."
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
