On 02/10/2012 02:00 AM, Jonathan Morgan wrote:
Hi all,
This proposal of Peter's received a lot of discussion back in
January. However, when I look at the Wiki I see that Scope is
listed in the conf file specification as a proposed conf file
element which may change. A few questions:
1.
Let's not forget that some modules are for a work in progress by the
translators.
e.g. A New Testament only module may have plenty of cross-references to OT
passages, in anticipation that the translation would one day eventually be
completed.
And - yes - as DM noted, xrefs for modules that are
Someone has enquired through the Go Bible Forum about the availability of the
OSIS XML source text for the Arabic SVD module.
If someone could provide a link, I'll be able to help them further.
As the original translation was published in 1865, in what sense is this now
a copyrighted work?
Hey guys. I'm remember this thread from a while back am to lazy to go
back and look.
Please remind me why we want a .conf entry and not a call like:
SWMgr library;
SWModule *kjv = kjv = library.getModule(KJV);
VerseKey testKey = jn.3.16;
//
ListKey range =
The motivation that Peter mentioned was to use a versification (Synodal) that
contained deuterocanonical material for a module that excluded such content.
I have no big opinion as to whether to have it in the conf or to compute it.
Other than performance. I think having the cached value in the
On 10/02/12 22:11, DM Smith wrote:
The motivation that Peter mentioned was to use a versification (Synodal) that
contained deuterocanonical material for a module that excluded such content.
Yes, this was the main initial reason to get this info.
We do have a whole bunch of texts in the
