[jsword-devel] Best way of keying verses in a separate database
Peter von Kaehne
refdoc at gmx.net
Mon Jul 2 06:52:30 MST 2012
Av11n does not make the mapping problem more acute. It exists just as much in the pre-av11n world:
A psalm with a (in KJV versification) canonical title and n verses would in the Synodal versification have n+1 verses, the canonical title being counted as verse 1.
But this same psalm in a KJV-ified module of a text in originally Synodal versification would while having only n (and not n+1) verses still show as v1 the canonical title and have its (n+1)th verse added to the nth verse.
So when looking for the commentary of verse x of that bible one would end up in the commentary of x-1 in the MHC.
Same, when verses are on the wrong side of the boundaries of chapters (as in German Pentateuch.
This happens now and has nothing to do with av11n.
When we pushed Synodal or Lutheran texts into a KJV mould we did not adjust and "rectify" versifications but simply did the equivalent of a bowl cut - all offending bits were cut off and squeezed into shape - with often horrendous results.
Mapping is a interesting computing problem, but not a huge one in the real world - the Kazakh mentioned is more likely reading a Russian commentary (also in Synodal) or will be well used to the oddities of Anglosaxon versifications.
E.g. for me as a German who grew up with 3 different versifications being absolutely mainstream at the same time - RC, Lutheran and KJV (via Elberfelder) we simply got on with it and asked when someone referred to a verse "Do mean such and such".
So, in summary, av11n does nothing to make the mapping problem worse. It prexists our release of av11n modules.
Wrt solution to mapping - there has been some discussion on sword-devel on it and some preliminary code has been checked in. Any mapping solution in jsword should probably take that into account.
-------- Original-Nachricht --------
> Datum: Mon, 2 Jul 2012 14:15:12 +0100
> Von: Martin Denham <mjdenham at gmail.com>
> An: JSword Developers Mailing List <jsword-devel at crosswire.org>
> Betreff: Re: [jsword-devel] Best way of keying verses in a separate database
> Hi Chris,
> I have no answers. I am still using pre-av11n code in AB but the second
> question you raised in your initial e-mail is troubling me: "is there a
> to translate from one versification to another".
> A simple example scenario is a user reading a bible with one versification
> wishing to view associated commentary having a different versification.
> for example a Kazakh user reading Psalm 50 in a SynodalP bible wishing to
> view MHC would be shown the wrong chapter if there is no mapping between
> versifications because (I am told) most Psalms in SynodalP are offset by
> Sorry, I have no answers but hopefully somebody does.
> btw I understand from DM that JSword av11n implementation was delayed a
> weeks by other unrelated issues, so DM is still working on it.
> On 1 July 2012 16:15, Chris Burrell <chris at burrell.me.uk> wrote:
> > Hi
> > Any ideas on this? The only way I can think of is to lookup the OSIS ID
> > one version and hope it's present in a different version. Will this work
> > for Books of different languages?
> > Chris
> > On 8 June 2012 17:25, Chris Burrell <chris at burrell.me.uk> wrote:
> >> Hi all
> >> I used to be using the getOrdinal() on the verse range to key a set of
> >> references in my database against particular resources. Now that it's
> >> deprecated, what's the best way. I'm happy to assume that my database
> >> be keyed in a particular known version (e.g. KJV). I need a way to key
> >> in numerical form to allow me to do intersection of ranges, etc.
> >> Should getOrdinal be re-instated? Also, is there a way to translate
> >> one versification to another? So if the user is looking at version x,
> >> like to translate what he's looking at to the version stored in the
> >> database.
> >> Any ideas?
> >> Chris
> > _______________________________________________
> > jsword-devel mailing list
> > jsword-devel at crosswire.org
> > http://www.crosswire.org/mailman/listinfo/jsword-devel
More information about the jsword-devel