<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
The World English Bible project just reached a major milestone. The
complete Old and New Testaments are essentially done. The
Apocrypha/Deuterocanon set is complete, containing all books that
the NRSV with Apocrypha has in its fuller ecumenical edition. The
Apocrypha/Deuterocanon books (except for one) have not undergone the
same manual edit pass that the OT and NT have, so they don't have
quotation marks and still have some grammar that seems a little
backward to modern English speakers, but they are more readable than
the source Public Domain English texts and just as accurate. It
seems to me that now might be a good time to update the Sword
modules.<br>
<br>
Files that validate against the OSIS schema are at:<br>
<a href="https://bible.cx/Scriptures/eng-web_osis.zip">https://bible.cx/Scriptures/eng-web_osis.zip</a><br>
<a href="https://bible.cx/Scriptures/eng-webbe_osis.zip">https://bible.cx/Scriptures/eng-webbe_osis.zip</a><br>
<a href="https://bible.cx/Scriptures/eng-webbme_osis.zip">https://bible.cx/Scriptures/eng-webbme_osis.zip</a><br>
<a href="https://bible.cx/Scriptures/eng-webme_osis.zip">https://bible.cx/Scriptures/eng-webme_osis.zip</a><br>
<br>
It would be best if the WEB and WEBBE modules included the
Apocrypha/Deuterocanon. The two Messianic Edition modules don't
include the Apocrypha, because, for the most part, Messianic Jews
aren't very interested in those books. (One exception comes to mind
as I write that, but he can read those books in one of the two other
editions.) The World English Bible isn't frozen, and typo reports
and translational issue reports will still be considered, but edits
will be much fewer and much slower from here on out, and all likely
to be very small.<br>
<br>
I would create those modules, myself, along with modules for the
rest of the Bibles and portions in <a
href="https://bible.cx/Scriptures/">https://bible.cx/Scriptures/</a>,
but I kind of got bogged down in versification and configuration
file generation issues, plus little showstoppers like lack of
support for midverse titles, etc., and (not least of all) overcome
with my other work. My other workload is not going to let up any
time soon with a major deadline looming and travel to 3 countries in
3 months coming up for me, so I'm hoping one or more of you will
take that on.<br>
<br>
Most of the versification issues in the grand collection at <a
href="https://bible.cx/Scriptures/">https://bible.cx/Scriptures/</a>
are small variations from one of the hard-coded versification
schemes, but a testament to the creativity and individuality of
Bible translators in many languages and cultures. You can blame me
for versification in the 4 editions of the World English Bible and
the LXX2012 and Brenton modules, but the versification variations in
the other translations are all someone else's decision and
responsibility. In either case, it is up to the Bible study software
to adapt to the translation, not vice versa. Verse bridges are made
for translational reasons, and versification varies by church
tradition and textual criticism reasons. In my experience processing
Bible texts, it is not reasonable to hard code a small set of
versifications and expect all translations to fit into it, but it is
possible to encode an exception file listing the differences much
more compactly than duplicating the whole versification.
Implementation either way is a developer decision.<br>
<br>
I was appalled this morning to discover that the <a
href="http://www.cis.upenn.edu/%7Ebcpierce/unison/">Unison
software</a> that I had been using to keep the files on the
Bible.cx server synchronized with my desktop and notebook computers
and vice versa wasn't working as expected, leaving most of the files
stuck back in their condition as of last August. I just updated that
directory with sftp, and I'm checking to see if I need to abandon
Unison or just turn off its fastcheck option. Much work has gone on
since August, both on the World English Bible and on some of the
minority languages, as well as improvements in the OSIS generation.
Everything in <a href="https://bible.cx/Scriptures/">https://bible.cx/Scriptures/</a>
should have a date this month. If not, please clear your browser's
cache and try again. The use of https should defeat ISP-level
caches, like you might see if you were to get them with http or ftp.
Sorry about that.<br>
<br>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8">
<title>signature</title>
<table border="0" cellpadding="7" cellspacing="3">
<tbody>
<tr>
</tr>
<tr>
<td><img src="cid:part9.05090505.09080208@eBible.org"></td>
<td><font color="#000000" size="4">Your partner in
electronic Bible publishing,<br>
<img src="cid:part10.09000703.00070308@eBible.org"><br>
</font></td>
</tr>
</tbody>
</table>
<table border="0" cellpadding="7" cellspacing="3">
<tbody>
<tr>
<td style="background: rgb(255, 255, 0)"><font
color="#000000"><a href="http://MLJohnson.org">MICHAEL
JOHNSON</a><br>
<b>1215 S KIHEI RD STE O # 728<br>
KIHEI HI 96753-5225</b><br>
USA<br>
<br>
Verizon Wireless Mobile: +1 <b>808-333-6921</b><br>
Skype: kahunapule or +1 719-387-7238</font>
</td>
<td style="background: rgb(0, 255, 255)"><font
color="#000000">
<a href="http://eBible.org">eBible.org</a><br>
<a href="http://MLJohnson.org">MLJohnson.org</a><br>
<a href="http://PacificBibles.org">PacificBibles.org</a><br>
<a href="http://PNGScriptures.org">PNGScriptures.org</a><br>
<a href="http://TokPlesBaibel.org">TokPlesBaibel.org</a><br>
<a href="http://VanuatuBibles.org">VanuatuBibles.org</a><br>
</font></td>
</tr>
</tbody>
</table>
</div>
</body>
</html>