Re: [sword-devel] OSIS markup best practice: sanity check

2015-09-30 Thread Matěj Cepl
On 02/05/14 09:36, John Austin wrote: > - Scripture reference tags will all specify target modules using > osisRefs like this: "ESV:Matt.1.1" (and it may be that the specified > module is not always installed, thus its av11n unknowable). After a long time I found this old email, and given I am jus

Re: [sword-devel] OSIS markup best practice: sanity check

2015-09-30 Thread Peter Von Kaehne
Hi Matej, Couple of points: 1) The idea to have specific modules or av11ns in the reference is not new and is IIRC part of the OSIS specification as an option. As an option it makes sense in following circumstances: a) commentaries, general books and devotionals which try to link to a specific

Re: [sword-devel] OSIS markup best practice: sanity check

2015-09-30 Thread DM Smith
According to the OSIS manual, the work prefix (module name in front of the reference) is an optional element. When it is absent, it defaults to the current module. JSword ignores the work prefix at this time. Not sure what SWORD does if the ESV module has KJV: as a prefix. — DM > On Sep 30,

Re: [sword-devel] Lamsa Bible

2015-09-30 Thread David Haslam
I just found this information about the copyright. "Scripture quotations marked Lamsa are from the Holy Bible From Ancient Eastern Manuscripts, George M. Lamsa, Copyright © 1933, 1939, 1940, 1957 A. J. Holman Company." See http://www.topical-bible-studies.org/other.htm This page may be of interest

Re: [sword-devel] OSIS markup best practice: sanity check

2015-09-30 Thread Matěj Cepl
On 2015-09-30, 11:12 GMT, Peter Von Kaehne wrote: > Couple of points: > > 1) The idea to have specific modules or av11ns in the > reference is not new and is IIRC part of the OSIS > specification as an option. As an option it makes sense in > following circumstances: I haven’t said (and I reall

Re: [sword-devel] OSIS markup best practice: sanity check

2015-09-30 Thread Peter Von Kaehne
Yes, we do have a tool. What it requires is a locale for Czech and the text of the reference. It is a method in the engine. You can play with it by looking a the utilities within the library's source. i am not at home, but I think it is called vs2osiref. You can access the method directly f

Re: [sword-devel] OSIS markup best practice: sanity check

2015-09-30 Thread DM Smith
I think Troy has a binding to the SWORD library in Java. If it exposes the same as Peter mentions, you can call out from xslt to Java. We do something similar for JSword. JSword can do some level of parsing of the references, but your example is not in a form that JSword can parse. — DM > On

Re: [sword-devel] OSIS markup best practice: sanity check

2015-09-30 Thread Greg Hellings
Troy's JNI bindings are specific to Android currently. --Greg On Wed, Sep 30, 2015 at 11:10 AM, DM Smith wrote: > I think Troy has a binding to the SWORD library in Java. If it exposes the > same as Peter mentions, you can call out from xslt to Java. We do something > similar for JSword. > > J

Re: [sword-devel] OSIS markup best practice: sanity check

2015-09-30 Thread Matěj Cepl
On 2015-09-30, 16:10 GMT, DM Smith wrote: > I think Troy has a binding to the SWORD library in Java. If it > exposes the same as Peter mentions, you can call out from xslt > to Java. We do something similar for JSword. > > JSword can do some level of parsing of the references, but > your example

Re: [sword-devel] OSIS markup best practice: sanity check

2015-09-30 Thread Matěj Cepl
On 2015-09-30, 16:04 GMT, Peter Von Kaehne wrote: > You can play with it by looking a the utilities within the > library's source. i am not at home, but I think it is called > vs2osiref $ vs2osisref 'Př 8,22-24' cs Př 8,22-24 $ What am I missing ('Př' is 'Přísloví' in Czech, that is

Re: [sword-devel] OSIS markup best practice: sanity check

2015-09-30 Thread Peter von Kaehne
The locale needs to be in same directory Sent from my phone. Apologies for brevity and typos.On 30 Sep 2015 10:27 pm, Matěj Cepl wrote: > > On 2015-09-30, 16:04 GMT, Peter Von Kaehne wrote: > > You can play with it by looking a the utilities within the > > library's source. i am not at home, bu