[sword-devel] 1.5.8 bugs
krzbia at ctm.gdynia.pl
Tue Mar 22 23:12:20 MST 2005
Well, that reminds me of one feature I really miss in Sword project (that is
already present in BibleDesktop) - the nightly builds (for Sword AND sword
In my personal opinion that will help those people developing modules to
test the newest corrections and provide proper feedback on found errors
providing a bit tighter developement cycle.
----- Original Message -----
From: "Chris Little" <chrislit w crosswire.org>
To: "SWORD Developers' Collaboration Forum" <sword-devel w crosswire.org>
Sent: Tuesday, March 22, 2005 10:58 PM
Subject: Re: [sword-devel] 1.5.8 bugs
>I should point out that the mod2osis in SVN may or may not work correctly
>at the moment. Last time I tried it, it was broken, but some commits have
>occurred since then.
> Chris Little wrote:
>> You're using the wrong tool. You need to use osis2mod. osis2mod is for
>> Bibles and expects Bible structures. xml2gbs is for free form books that
>> will go to our GenBook driver and it expects different types of
>> structures. You can force a Bible through xml2gbs and it will work
>> correctly, but only if you encode it like a free form book (which would
>> violate best practices).
>> I don't plan to rewrite xml2gbs and I doubt Troy plans to rewrite
>> osis2mod to use a full DOM parser. In the end, data have to be imported
>> to Sword format, which means we have to handle them ourselves eventually.
>> Without any specific examples, the best I can say is simply that I think
>> we can manage without the added trouble of an external parser.
>> Justus Piater wrote:
>>> "Krzysztof Bialas" <krzbia w ctm.gdynia.pl> wrote on Sun, 20 Mar 2005
>>> 15:01:02 +0100:
>>>> I've invested quite some time into developing an example osis file
>>>> showing off the problems with osis2mod/Sword for windows 1.5.8pre3
>>>> that are (in my opinion) 1.5.8 blockers. These are stated in the
>>>> forum message
>>> I have converted another Bible to OSIS 2.0.1 format, and xml2gbs
>>> (1.5.7 Linux) crashes half-way through. If I take only parts of the
>>> Bible, it completes, but all verses are empty.
>>> After running it in the debugger and looking at the source, it seems
>>> that the problem is due to unhandled elements or unanticipated ways of
>>> nesting elements.
>>> At this point I stopped investigating because I don't think there's
>>> any hope of ever parsing OSIS XML correctly using an ad-hoc parser;
>>> OSIS is way too complex and very flexible. A clean solution would
>>> require that xml2gbs be rewritten to employ an external XML library
>>> (e.g., libxml2 from http://xmlsoft.org/).
>>> It is not up to me to judge whether this blocks 1.5.8.
>> sword-devel mailing list: sword-devel w crosswire.org
>> Instructions to unsubscribe/change your settings at above page
> sword-devel mailing list: sword-devel w crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel