On 2 May 2014, at 5:36 pm, 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).
Will this affect backwards compatibility? What
See hbo and heb at Ethnologue.com.
Aloha,
Michael
http://mpj.us
> On May 1, 2014, at 23:32, David Haslam wrote:
>
> Shouldn't we distinguish modern Hebrew and ancient Hebrew for our Bible
> modules by using a different language code, just as we do for the modern and
> Koine (ancient) Greek mod
The book list was implemented at same time as scope in jsword.
On 2 May 2014 15:18, "DM Smith" wrote:
>
> On May 2, 2014, at 3:36 AM, John Austin
> wrote:
>
> - There will be a Scope parameter in the .conf file, formatted as an
> osisID of the specified v11n, which details the books, chapters, a
On May 2, 2014, at 3:36 AM, John Austin wrote:
> - There will be a Scope parameter in the .conf file, formatted as an osisID
> of the specified v11n, which details the books, chapters, and verses that are
> included in the entire module. The Scope param is the only way to detect
> which books
Hi John
On the Scope parameter, I believe this was discussed and rejected.
(although JSword will have support for this, and will write a separate conf
file, should the scope be absent from the .conf file).
Chris
On 2 May 2014 08:36, John Austin wrote:
> IBT's repository has dozens of SWORD B
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In case it is relevant, you can find the ISO 639-3 language codes at
https://en.wikipedia.org/wiki/Hebrew_language
Blessings,
Jaak
On 02.05.2014 12:32, David Haslam wrote:
> Shouldn't we distinguish modern Hebrew and ancient Hebrew for our
> Bible
On Fri, May 2, 2014 at 5:17 AM, Greg Hellings wrote:
> A few more fixes and patches - sword 1.7.3 alpha 3 is now out alongside the
> alpha1 tarball.
>
> If I hear nothing more bad in the next few days I'll cut it over as the
> official release.
It still builds on our buildsystem.
> --Greg
>
> __
Shouldn't we distinguish modern Hebrew and ancient Hebrew for our Bible
modules by using a different language code, just as we do for the modern and
Koine (ancient) Greek modules?
They are not the same language! In fact, I know someone in Israel who is
translating the Bible into modern Hebrew.
B
IBT's repository has dozens of SWORD Bible modules, and they all need to
be rebuilt for SWORD 1.7+ using OSIS module best practices (as outlined
in the extremely useful CrossWire wiki). Below are some conceivably
controversial issues. We hope to achieve excellent module functionality
with the v
