<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head>
<title></title>
<meta http-equiv="content-type" content="text/html;charset=utf-8"/>
<meta http-equiv="Content-Style-Type" content="text/css"/>
</head>
<body>
<div align="left"><font face="Arial" size="2"><span style=" font-size:10pt">Being somewhat new to the Sword project, and a module developer, not in Sword development per se, I don't have any particular
interest in GenBook bibles. It sound's like a kludgy way to avoid having to make the base engine powerful enough to handle
flexible versification.</span></font></div>
<div align="left"><font face="Arial" size="2"><span style=" font-size:10pt"><br />
</span></font></div>
<div align="left"><font face="Arial" size="2"><span style=" font-size:10pt">I have been a Logos content developer for several years, and what they call Bible Data Types that are defined in Verse Maps are
hard-coded into the Logos engine. This has always been a source of consternation for me. At least Logos has been willing to add
verse maps for new bibles without complaining. But it is a several-month process from the time the map is submitted until it
becomes active by a new release of Logos and the Logos Book Design Tools. I gather that the Sword project is similar, except
that it doesn't really have verse-by-verse maps that show how every given verse in one bible version maps to the equivalent
verse in every other version. Being limited to the current twenty v11n's, for which several French bibles do not match any of
them, is problematic, and requires some kind of work-around to get bibles and commentaries to work in a usable way.</span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt"><br />
</span></font></div>
<div align="left"><font face="Arial" size="2"><span style=" font-size:10pt">It seems to me that it should be possible to devise a pluggable v11n system where the verse mapping is embedded in the
module. Or at least where verse mapping is loaded from a file at run time, and does not need to be hard-coded and compiled into
the engine. I gather that this also the dream of the Sword development team. </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt"><br />
</span></font></div>
<div align="left"><font face="Arial" size="2"><span style=" font-size:10pt">I don't have time and energy to offer to the project at this time. I'm just trying to get my own modules to work. But the Sword
project is something that is worthwhile and needed from a strategic perspective in the global church. The modules that we are
preparing are destined for French-speaking African and Haitian pastors, and the open-source Sword project is perfectly suited to
the needs of the developing world.</span></font></div>
<div align="left"><font face="Arial" size="2"><span style=" font-size:10pt"><br />
</span></font></div>
<div align="left"><font face="Arial" size="2"><span style=" font-size:10pt">And yes, my smartphone that I just bought for US$70 is considerably more powerful than the IBM 3090-400 quad-core
supercomputer that cost US$12,000,000 and ran my entire university when I got my Master's in 1991.</span></font></div>
<div align="left"><font face="Arial" size="2"><span style=" font-size:10pt"><br />
</span></font></div>
<div align="left"><font face="Arial" size="2"><span style=" font-size:10pt">John</span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt"><br />
</span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> On Thu, May 31, 2018 at 4:56 AM, refdoc@gmx.net <refdoc@gmx.net> wrote:</span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> In respect of John's recent threads on correct encoding of various apocryphal texts, I had a </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> look again at our support for GenBook bibles. The wiki lists this as in development, but </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> whatever development has happened in last few years, it has not impacted onto GenBook </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> bibles.</span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> So my questions are:</span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> Do we still intend to support these in the library? </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> Last time I asked Troy the answer was no. This was an initial proposal before av11n was </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> conceived and implemented.</span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">>  </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> If so, which bits are missing in terms of support?</span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> Lots of them, but not all.</span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">>  </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> If so, what specific place do you see for GenBook bibles within our ecology?</span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> GenBook bibles do not support reference translation and this is a known serious drawback, </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> unlikely to be overcome. But I think this is not enough a reason to totally abandon them:</span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> My proposal is that we use GenBook bibles as stepping stone for texts which do not fit well, </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> but are either unlikely  to ever support an independent v11n or are in an area of much flux. </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> This would allow us to bypass the in the past not infrequent impasse where we have new </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> important texts but still argue about a new scheme. Download statistics will then also go </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> into our decision 're viability and need for a new v11n.</span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> My proposal is to make this an active project again and iron out any bugs and missing </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> pieces in order to aim for use of the facility within the next release iteration.</span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> Any thoughts?</span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> I'm a big advocate for giving the most flexibility to the content creators rather than to the </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> software. Modern devices, including smartphones, tend to have plenty of oomph to get through </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> the little bit of extra computation necessary that av11n instead allows us to optimize away. But </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> it's also a sight bit more difficult to implement and maintain. So, unless there is developer </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> dedication to it, it's unlikely to see the light of day. As with most software, that's one of the </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> biggest trade offs: ease of correct implementation vs developer time.</span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> --Greg</span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">>  </span></font></div>
<div align="left"><font face="Arial" color="#7f0000" size="2"><span style=" font-size:10pt">> Peter </span></font></div>
<div align="left"><font face="Arial" size="2"><span style=" font-size:10pt"><br />
</span></font></div>
<div align="left"><font face="Arial" size="2"><span style=" font-size:10pt">John Dudeck</span></font></div>
<div align="left"><font face="Arial" size="2"><span style=" font-size:10pt">Programmer at Editions Cle                             Lyon, France</span></font></div>
<div align="left"><font face="Arial" size="2"><span style=" font-size:10pt">john.dudeck@sim.org                            john@editionscle.com</span></font></div>
<div align="left"><font face="Arial" size="2"><span style=" font-size:10pt">--</span></font></div>
<div align="left"><font face="Arial" size="2"><span style=" font-size:10pt">The tree dies, but the word never dies. -- African proverb</span></font></div>
<div align="left"> </div>
</body>
</html>