[sword-devel] osis2mod warnings

DM Smith dmsmith555 at yahoo.com
Tue Dec 2 05:46:28 MST 2008

On Dec 2, 2008, at 5:46 AM, Adrian Korten wrote:

> On Mon, 1 Dec 2008 09:13:36 -0500
> DM Smith <dmsmith555 at yahoo.com> wrote:
>> Adrian/David (and others):
>> Most of these warnings are gone with with the latest build of
>> osis2mod. When you run it, it will say:
>> You are running osis2mod: $Rev: 2197
> Good day,
> I'm not using the most recent but where can I download the  
> latest .exe or linux binary (I don't have experience compiling).
> I've used the sfm2osis set of python programs and a python program  
> provided by UBS (paratext developers) to generate the xml. Both come  
> up with errors although not consistently with the same verses  
> always. Notes and quotations seem to be problem areas. The UBS  
> version uses an older OSIS best practices version. Is that still a  
> good idea?

Chris has finally convinced me that the OSIS best practice is to  
structure the Bible as a document (aka BCP) and lay in versification  
using milestones.

But the SWORD engine works best with verses being the primary  
structure (aka BCV). The purpose of osis2mod has always been convert  
the input OSIS into something that works well with the SWORD engine.  
That said, as we get more and more OSIS texts we are finding  
shortcomings in osis2mod.

The latest change, though buggy wrt titles/headings, went a long way  
toward accepting more high quality BCP OSIS texts.

I hope to fix the bug in osis2mod today and apply Chris' latest  
request of putting the revision number into the module.

> I'm thinking of tweaking my own python scripts to move from gbf to  
> basic OSIS. But that could be almost as much work as correcting the  
> OSIS from the two previous programs. So I don't like the two  
> alternatives but don't see another option except perhaps perhaps ThML.

ThML modules have the same problems. The importer does not tell you  
about them. Since we are actively encouraging OSIS, I added warnings/ 
errors to osis2mod.

My best recommendation is to write best-practice OSIS. If osis2mod  
does not handle it well, then use xslt to adapt it to something that  
osis2mod likes and pump that through osis2mod. Using the 1.5.11  
version of osis2mod, this would be transforming BCP elements into  
their milestoned form.

There are several of us here that could whip out the xslt. So if you  
need help, ask.

My other recommendation is that we fix osis2mod in a timely fashion. I  
hope to fix reported bugs in osis2mod today.

In Him,

More information about the sword-devel mailing list