[jsword-devel] KJV sword module...
Joe Walker
jsword-devel@crosswire.org
Mon, 05 Apr 2004 23:29:08 +0100
I've told the Sword people about this (the resp element?) and put some
hacks into the parser, but I can't help thinking that part of the
problem is that JAXB is validating.
I makes is hard to upgrade to 2.0 for example.
We thought long and hard about going to JAXB, but I can't help thinking
it was a mistake.
Does anyone have any experience with JiBX, JaxMe, Castor (or a.n.other
binding tool) enough to be able to say if they suffer from the same
strictness problem?
Joe.
DM Smith wrote:
> I have noticed that most of the NT is broken. It has elements not in
> OSIS 1.1.
> I have also noticed that Gen 17 is broken too.
>
>> From: Mark Goodwin <mark@thorubio.org>
>> Reply-To: jsword-devel@crosswire.org
>> To: jsword-devel@crosswire.org
>> Subject: [jsword-devel] KJV sword module...
>> Date: Mon, 5 Apr 2004 23:01:00 +0100
>>
>> Has anyone else noticed...
>>
>> The new sword KJV module seems to be broken.
>>
>> Check out http://mrgoodwin.is-a-geek.org/jsword/
>>
>> good.tar is an old module that seems to work.
>> bad.tar is the latest from crosswire.org and doesn't seem to work.
>>
>> _______________________________________________
>> jsword-devel mailing list
>> jsword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/jsword-devel
>
>
> _________________________________________________________________
> Is your PC infected? Get a FREE online computer virus scan from McAfee.
> Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>
> _______________________________________________
> jsword-devel mailing list
> jsword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/jsword-devel