[sword-devel] 1 bug left for 1.5.8
Troy A. Griffitts
scribe at crosswire.org
Sun Apr 3 23:43:41 MST 2005
I've had a quick look at your test file, and although it validates
against the schema, this does not mean that it is valid OSIS (including
invalid osisID elements), it also doesn't seem to comply with the best
practices OSIS user guide.
Thank you for spending the time to come up with this document. It will
be great to use when we try to make our import tools handle most any
case that might come up.
I have fixed the Windows UI for </p> not being imported correctly.
This is indeed a bug in the osis2mod importer.
I'm sure osis2mod has many things that it cannot do right now which you
would like and which it should do.
Having said this, we have encoded very complex Bibles including the
NASB and ESV into OSIS and successfully imported them with the osis2mod
It is important for us to progress this tool to support more types of
OSIS markup which are valid, but advancing this tool does not have any
bearing on the engine and it is my opinion that it shouldn't hold up its
I would like to help you get your Bible encoded into best practice OSIS
encoding, and even stricter encoding which our tool will support. Might
I send you an excerpt from our NASB module that you can mimic, so you
can get your Bible working with SWORD?
Please don't take this wrong. I really want to help you, but don't
have the time myself to make this tool work for all of these variant
encodings right now, and no one else seems willing to step up and do it
either. And we really need to get a labeled version out the door so
frontend developers can have something they might release against.
I hope this is understandable and that you know I don't want to imply
that your contributions and Bible are not important.
-Troy A. Griffitts.
Krzysztof Bialas wrote:
> From: "Daniel Glassey" <danglassey at ntlworld.com>
> To: "SWORD Developers' Collaboration Forum" <sword-devel at crosswire.org>
> Sent: Friday, April 01, 2005 12:28 AM
> Subject: [sword-devel] 1 bug left for 1.5.8
>> This is the details of the only bug left in the library for 1.5.8. If
>> this bug isn't important enough please move it to a future release. If
>> anyone can fix it please do. If there are any library bugs that aren't
>> in the tracker please put them there or 1.5.8 will be released without
>> a fix.
> Hi Daniel,
> So the Osis2Mod problems I've reported are NOT scheduled for 1.5.8?
> (API-22 & API-14)? API-14 was written by Troy. The included osis test
> file shows something like 10 serious errors in import tool. Is fixing
> osis2mod postponed? I'm very dissapointed as the statement on the Sword
> Developement pages note that module developers should move to OSIS
> modules, and the module I'm working on would be quite crippled without
> those 'features' solved...
> A bit frustrated,
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel