[sword-devel] OSIS 2.0.1 modules available

[Michael Paul Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


American Standard Version http://eBible.org/asv/asvosis.zip
God's Living Word http://eBible.org/glw/glwosis.zip
Hebrew Names Version http://eBible.org/hnv/hnvosis.zip
King James Version http://eBible.org/kjv/kjvosis.zip
Melanesian Pidgin http://eBible.org/pdg/TokPisinOSIS.zip
World English Bible http://eBible.org/web/webosis.zip

Text status:
ASV - contains fewer typos than in most commercial ASV texts. OT + NT. 
This text will be updated in place if any more typos/scan errors are 
found. Words of Jesus are not marked. "Minimal" level OSIS 2 
compliance. Public Domain.

GLW - John & John's Letters only. Words of Jesus marked in a 
nonstandard way (see header of OSIS file.) Copyrighted freeware text. 
Further translation has been halted for this edition in favor of the 
Public Domain WEB. Words of Jesus marked in a nonstandard way.

HNV (AKA World English Bible: Messianic Edition or WEBME) - Draft OT + 
NT. Old Testament revision status is given at http://eBible.org/web/ 
(same as WEB because it is generated from the WEB with a phrase 
substitution list and program, but does not include the Apocrypha.) 
Words of the Messiah marked in a nonstandard way (see header of OSIS 
file.) This file will be updated frequently as progress on this work 
continues. Public Domain, but names trademarked to prevent use for 
anything but the genuine text.

KJV - at least as good as most commercial KJV texts. May be updated in 
place if any typos are found. Words of Jesus marked. "Minimal" level 
OSIS 2.0 compliance. Perpetual Crown Patent valid in Great Britain and 
possibly in all British Commonwealth countries, but not copyrighted 
under international treaty.

Melanesian Pidgin - proofreading in progress. This copy probably has 
some more errors of text omissions and missing paragraph marks, based 
on the proofreading done so far. Flunks the paragraph & quote 
consistency check in gbf2osis.exe (which actually works better in 
Melanesian Pidgin than in English) for most books of the Bible, but I 
put it up here at least temporarily, so that software writers can test 
with it. I plan to update this text from time to time as proofreading 
continues. It contains verse bridges, which the other versions above 
do not use. Based on and improved over the Sword copy found at 
crosswire.org web site. Words of Jesus not marked, except with 
quotation marks. Copyrighted in PNG. "Minimal" level OSIS 2 
compliance.

WEB - Draft OT + partial draft Apocrypha (one book) + NT. See 
completion status at http://eBible.org/web/. This file will be updated 
regularly until it is completed. (Update schedule varies, but expect 
at least once a month. Subscribe to the webnews mailing list at 
http://eBible.org/subscribe.htm if you want notifications of updates.) 
Words of the Messiah marked in a nonstandard way (see header of OSIS 
file.) Public Domain, but names trademarked to prevent use for 
anything but the genuine text.

The above comprise a good test suite for software that uses or 
converts OSIS 2 texts, at least with a simple Latin alphabet. They 
vary in ranges of books presented, handling of quotation marks, and 
use of verse bridges or not.

If you care to alter the <q> marker and quote marks to strictly comply 
with the OSIS 2 documentation, then you face the following 
difficulties:

1. You MUST provide additional information outside of the OSIS 
standard to the users of OSIS text that allows the punctuation to be 
EXACTLY recreated as in the original text. The rules of this 
recreation and the exact markers used are different for different 
languages, different dialects, and even for different translations 
within the same dialect. They aren't even the same for all of the 
texts above. If you use the <q> marks in the KJV to generate red text, 
that is OK, but if you generate quotation marks, you are changing the 
text. The KJV has no quotation marks, nor does the ASV.

2. If you scan a new Bible text that has correct quotation marks, you 
probably won't be able to fully automate conversion from those marks 
to <q> markup.

3. If you fail in doing 1 or 2, above, you may be in violation of 
copyright, trademark, and/or common law. Worse yet, you shift 
responsibility before God from the translators to yourself for the 
accurate transmission of His Word.

The OSIS spec should be changed to allow separation of quotation mark 
generation markers from words of Jesus markers.

The program and C# source code used to generate the above OSIS 
documents from GBF documents may be found at 
http://ebt.cx/translation/gbf.htm, if you are interested.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
Comment: http://eBible.org/mpj/gpg.htm

iD8DBQFAFbhoRI/gxxfXR7sRArdKAKChUZzetAKnzp8Ml333PuaNlpsqQwCeMKaL
n0ZFP6+0I67hisUNuSNbXWI=
=ArJV
-----END PGP SIGNATURE-----