On 12/09/12 22:49, DM Smith wrote:
>
> BTW, GBF doesn't and ThML might not have OSISrefs. (ThML can, but there's no
> guarantee.)
FWIW, while we still have 37 GBF modules in the main repo, none of these
have cross references.
We do have 2 ThML Bibles with references - the ISV and the Swe1917. I
Hi Chris,
On Thu, Sep 13, 2012 at 4:53 PM, Chris Little wrote:
> On 09/12/2012 02:49 PM, DM Smith wrote:
>
>> When they differed, I took a look at the input to understand the
>> differences. IIRC, in every difference the input was ambiguous (e.g.
>> v10 for this chapter's 10-th verse or Jud found
On Sep 13, 2012, at 8:57 AM, Peter von Kaehne wrote:
> And then, we should at least for OSIS modules disable all parsing of
> unresolved free text references.
I'll put that on the JSword todo list.
___
sword-devel mailing list: sword-devel@crosswire
On Sep 13, 2012, at 12:59 AM, Peter von Kaehne wrote:
> On 12/09/12 22:49, DM Smith wrote:>
>> I few years ago I scraped all the modules (GBF, ThML and OSIS; Bibles
>> and Commentaries) for their references. I then ran them through SWORD
>> and through JSword and compared what they interpreted t
> Von: DM Smith
> So lets use a different hypothetical, a module has "Ma 1:1" as a cross
> reference in the book of Malachi. To what should it resolve?
>
> The point of the example is that a book reference in a module that is
> ambiguous is just plain bad.
As a module maker I treat this follow
On Sep 13, 2012, at 2:53 AM, Chris Little wrote:
> On 09/12/2012 02:49 PM, DM Smith wrote:
>> When they differed, I took a look at the input to understand the
>> differences. IIRC, in every difference the input was ambiguous (e.g.
>> v10 for this chapter's 10-th verse or Jud found in the book of
