---- Original Message ----- *From:* DM Smith <[EMAIL PROTECTED]> *To:* "SWORD Developers' Collaboration Forum" <sword-devel@crosswire.org> *Sent:* 12/02/2008 7:46:28 PM +0700 *Subject:* [sword-devel] osis2mod warnings
> > 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. > > I think that I'm more interested in the BCV version. I don't have control of the texts and the copyright holders want to maintain them in USFM format. So the OSIS conversion is just to get it into a better format to import to a Sword module. And I prefer to keep the BCV formatting since that is strong in the original format and what is eventually used by the Sword engine. > > 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. > > I may take you up on that offer but I'll muddle along on my own for a little first. ak _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
