<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Your input, observations, and tests on the eBible.org repository are
welcome and encouraged.<br>
<a class="moz-txt-link-freetext" href="ftp://ftp.ebible.org/pub/sword">ftp://ftp.ebible.org/pub/sword</a> user: "anonymous" or "ftp"; password:
blank or any email address you would like logged with your
application's use of the repository<br>
or<br>
<a class="moz-txt-link-freetext" href="http://eBible.org/sword/">http://eBible.org/sword/</a><br>
Both protocols access identical files.<br>
<br>
Changes from last run:<br>
All .zip files were re-created with the -D parameter to inhibit
creating entries for directories, to work around a bug in JSword.<br>
Many module names were changed, usually to a shorter length. Instead
of "_" separators, creative use of mixed case was used to show a
separation between language code and dialect or translation
abbreviation. There should be an "Obsoletes=" entry in the .conf
file for any module whose name was changed, even if there was only a
change in casing. I plan to remove the entries that differ only in
case on the next run, because I have concerns about how that line
would be handled in a case-insensitive file system, but not
including them in this run would likely be a hassle for my fellow
Linux lovers who have been testing.<br>
<br>
For the World English Bible and Word Messianic Bible, I added
"Obsoletes=" lines for the old versions from Crosswire main, because
these definitely are more up to date with respect to language
updates, typo corrections, etc. The copy in the eBible.org
repository will now be maintained as up to date as the HTML at
<a class="moz-txt-link-freetext" href="http://eBible.org">http://eBible.org</a> and <a class="moz-txt-link-freetext" href="http://WorldEnglishBible.org">http://WorldEnglishBible.org</a>. How often a user
updates their World English Bible module is up to them. It is mostly
stable, now, but there is a proofreading effort under way to make
punctuation use more consistent, especially with respect to colon,
double dash, semicolon, and comma usage. This will result in many
updates, each of which triggers a major version number increment.<br>
<br>
Some modules are tied to shared Paratext projects, and may be
updated regularly, like the English T4T and some Micronesian Bible
projects.<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:part1.09080806.04040703@eBible.org"></td>
<td><font size="4" color="#000000">Your partner in
electronic Bible publishing,<br>
<img src="cid:part2.03070206.02010509@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"><b>MICHAEL JOHNSON<br>
PO BOX 881143<br>
PUKALANI HI 96788-1143</b><br>
USA</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>
Mobile: +1 <b>808-333-6921</b><br>
Skype: kahunapule</font></td>
</tr>
</tbody>
</table>
</div>
</body>
</html>