<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">OK, I hear two votes for me to continue
generating OSIS files, so I won't rip that part of the code out of
Haiola and reclaim the server space. Instead, I'll help put OSIS
on life support in light of the rather inconvenient disappearance
of <a class="moz-txt-link-freetext" href="http://www.bibletechnologies.net">http://www.bibletechnologies.net</a> by offering
<a class="moz-txt-link-freetext" href="http://eBible.org/osis/">http://eBible.org/osis/</a> as a stable point of documentation
distribution and <a class="moz-txt-link-freetext" href="http://ebible.org/osisCore.2.1.1.xsd">http://ebible.org/osisCore.2.1.1.xsd</a> as a stable
home for the OSIS schema.<br>
<br>
Contrary to the impression some have of me, I don't hate OSIS. I
do see better ways to encode Scripture for most uses, but unless
The Sword Project were to decide to move away from OSIS as a
supported import format and OSIS-like fragments as part of the
internal module structure, I don't want to see OSIS die. That is
because I like The Sword Project for all of its virtues. The Sword
Project is a useful set of free and open source Bible study
programs, some of which I use regularly. The World English Bible
and The Sword Project kind of grew up together. Obviously, The
Sword Project isn't the only similar project, but it is good, and
still improving.<br>
<br>
I have just modified Haiola to renumber Psalm 151 as chapter 1 of
AddPs when generating OSIS files. That chapter number remains the
same (151) in the USFM source. I have regenerated the WEB and
WEBBE OSIS files with that change, and another typo correction.<br>
<br>
The in the files I generate, the USFM and USFX files are
equivalent, and equally reliable, always generated from the same
source (which can be either USFM or USFX), and round-trip tested
in the conversion. They both contain all available text and
formatting for the Bible or Scripture portion they represent. The
OSIS file is always generated from the USFX file, but may omit
some noncanonical USFM/USFX features that The Sword Project does
not support. The only significant difference between my modified
OSIS and pure standard OSIS is that character styles and Word of
Jesus formatting stop and restart at all verse and paragraph
boundaries, like USFM and Paratext require. Since the internal
Sword format does the same thing, this is not an issue at all for
Sword use. This sort of modified OSIS still fully validates
against the OSIS schema. The USFX to OSIS conversion in Haiola has
been tested against 305 real world Scripture projects, and
generates valid OSIS from every one of them. It maps all USFM
2.4/USFX markers to appropriate OSIS markers that are used in
actual reader's edition Bibles and that have corresponding support
in the Sword Project. It also supports extensions to USFM (which
are part of standard USFX) to encode Strong's numbers and
morphological data. If Sword utilities can't handle these OSIS
files for input, then they can't handle OSIS. Period.<br>
<br>
When I wrote Haiola's OSIS conversion, no other acceptable
USFM/USFX to OSIS conversion existed. Currently, usfm2osis.pl is
close to acceptable. It worked on one of two test cases I gave it,
but failed miserably on one. I didn't try all 305 of my projects
on it. (I did alter the pointer to the schema to point to
ebible.org instead of <a class="moz-txt-link-abbreviated" href="http://www.bibletechnologies.net">www.bibletechnologies.net</a>, so that wasn't
the cause of the failure.)<br>
<br>
So... take your pick. You may choose to use the OSIS files I
generate with <a href="http://haiola.org">Haiola</a> (or generate
some yourself, since Haiola is free and open source). Or you may
improve usfm2osis.py and use it. Either way, I recommend that
proprietary extensions and tweaks to the modified OSIS format you
import as Sword modules be created in a separate step, just in
case others take advice given previously that OSIS be used to
author Sword Bible modules. (That might actually happen, although
the best and most-used Bible translation editing tools use USFM.)
Either way, it is no skin off of my nose.<br>
<br>
May God bless you.<br>
<br>
<div class="moz-signature">
<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:part2.09060502.08090906@ebible.org"></td>
<td><font color="#000000" size="4">Your partner in
electronic Bible publishing,<br>
<img src="cid:part3.08060707.09000700@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>
On 02/05/2014 03:21 AM, Chris Burrell wrote:<br>
</div>
<blockquote
cite="mid:CACQnaRWv15fGWkOTcu=sWysrEj_SdM_7pV3waT5+AmqOUpb_2g@mail.gmail.com"
type="cite">
<p dir="ltr">We do. Do please keep generating them. </p>
<div class="gmail_quote">On 5 Feb 2014 02:40, "Kahunapule Michael
Johnson" <<a moz-do-not-send="true"
href="mailto:Kahunapule@ebible.org">Kahunapule@ebible.org</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On 02/03/2014 12:04 PM, Chris Little wrote:<br>
><br>
> We build modules from your sites from USFM, so what you
do with OSIS doesn't affect us.<br>
<br>
In that case, it is entirely up to you to deal with chapter
number starting point translation, if necessary. I think I
have dealt with all chapter or verse out of order issues
before you get them.<br>
<br>
Perhaps I should stop generating OSIS files. Nobody else uses
them, as far as I know.<br>
<br>
<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a moz-do-not-send="true"
href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a moz-do-not-send="true"
href="http://www.crosswire.org/mailman/listinfo/sword-devel"
target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
</blockquote>
<br>
</body>
</html>