Without re-reading all the messages that took place in this thread, something
else today prompted me to look up the following in the OSIS reference
manual.
*7.5.1. Scope*
The *div* element has a *scope* attribute that should be used when it
contains less than a complete work. For example, some
Hi Troy,
On Sat, Feb 11, 2012 at 7:39 AM, Troy A. Griffitts scr...@crosswire.orgwrote:
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 =
By having things in the .conf file, frontends can potentially show those
details in install manager. That's about the only advantage I can see in
having it in the .conf file (excluding any speed issues, which you say are
negligible).
I'd say that any precomputed module scope would have to be to
On 12/02/12 20:47, Ben Morgan wrote:
I'd say that any precomputed module scope would have to be to chapter
granularity at its finest, and possibly only book granularity.
Chapters would sort all doctrinal issues, I would think, with shared
versifications.
Verses would easily become messy for
In the case of synodal it has 100 verses in Daniel 3. Protestant synodal would
be 33 (IIRC). It might need to be at the verse level.
In Him,
DM
Short reply from my phone.
On Feb 12, 2012, at 3:53 PM, Peter von Kaehne ref...@gmx.net wrote:
On 12/02/12 20:47, Ben Morgan wrote:
I'd say
Hi DM,
Your assertion about the Protestant version of the Russian Synodal is noted
- but please be aware that the RSP module v3.2 now being officially
distributed by IBT with their xulsword based MK Holy Bible software does
actually have 100 verses in Daniel 3, and MK displays all of them, albeit
Corrigendum:
The italics in Daniel 3 stop at verse 90. Verses 91-100 are back in normal
style.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Av11n-and-coverage-tp4265350p4382235.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
On Mon, Feb 13, 2012 at 8:58 AM, DM Smith dmsm...@crosswire.org wrote:
In the case of synodal it has 100 verses in Daniel 3. Protestant synodal
would be 33 (IIRC). It might need to be at the verse level.
I think frontends should handle missing verses properly themselves,
regardless of the
On Feb 12, 2012, at 6:16 PM, Ben Morgan wrote:
On Mon, Feb 13, 2012 at 8:58 AM, DM Smith dmsm...@crosswire.org wrote:
In the case of synodal it has 100 verses in Daniel 3. Protestant synodal
would be 33 (IIRC). It might need to be at the verse level.
I think frontends should handle missing
I've seen something similar with the end of Mark.
In Him,
DM
On Feb 12, 2012, at 5:27 PM, David Haslam wrote:
Hi DM,
Your assertion about the Protestant version of the Russian Synodal is noted
- but please be aware that the RSP module v3.2 now being officially
distributed by IBT
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
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
Versification mapping sounds very useful. Is there any
agreement/design/plan for what it would actually entail?
From my uninformed perspective, it seems like there could be lots of
ambiguity or disagreement about the use cases and priorities
especially if there needed to be a staged
Hi,
I'm not a coder, just an interested theological student. I am excited about
this debate. Logos does this and it would add a lot to SWORD-based programs if
versifications were mapped like that. So, this is great from an academical
point of view
I clearly cannot answer from a coder's
For the new config property, would Scope be a better word than Coverage?
http://www.merriam-webster.com/dictionary/coverage
http://www.merriam-webster.com/dictionary/scope
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Av11n-and-coverage-tp4265350p4268743.html
Extending Peter's concept, might we also make the book order something that
can be worked with by front-end developers?
e.g. For the NT in Eastern Canonical order we might have:
Scope=Matt-Acts James-Jude Rom-Heb Rev
i.e. with the General Epistles ordered prior to the Pauline Epistles.
This
While there is no support for module-supplied v11n in engine, no sense to
making and testing modules. Test module for this task could be any
incomplete module (without NT or OT).
As for me this task is not very difficult and well discussed to start
working over implementation. But two
On Fri, Jan 6, 2012 at 3:29 AM, David Haslam dfh...@googlemail.com wrote:
Extending Peter's concept, might we also make the book order something that
can be worked with by front-end developers?
e.g. For the NT in Eastern Canonical order we might have:
Scope=Matt-Acts James-Jude Rom-Heb Rev
2012/1/6 Костя и Алёна Маслюк kale...@mail.ru:
While there is no support for module-supplied v11n in engine, no sense to
making and testing modules. Test module for this task could be any
incomplete module (without NT or OT).
And there you have the problem.
- The engine has no reason to
On 1/6/2012 1:21 AM, David Haslam wrote:
For the new config property, would Scope be a better word than Coverage?
http://www.merriam-webster.com/dictionary/coverage
http://www.merriam-webster.com/dictionary/scope
David
I'm somewhat more in favor of Scope, since it is the term used in OSIS
On 1/6/2012 1:29 AM, David Haslam wrote:
Extending Peter's concept, might we also make the book order something that
can be worked with by front-end developers?
e.g. For the NT in Eastern Canonical order we might have:
Scope=Matt-Acts James-Jude Rom-Heb Rev
i.e. with the General Epistles
I prefer Scope too. It is a term we already use in JSword to express what the
module includes.
In Him,
DM
On Jan 6, 2012, at 6:12 PM, Chris Little wrote:
On 1/6/2012 1:21 AM, David Haslam wrote:
For the new config property, would Scope be a better word than Coverage?
I agree with Chris.
It will take a lot of work in the SWORD and JSword engine to implement it.
If anything we should develop a v11n that can be read in from a resource file.
But before that I'd like to see support for mapping from one v11n to another.
In Him,
DM
On Jan 6, 2012, at
Yes, mapping! I don't have strong opinion about how this works out on
the engine side of things, but proper mapping between versifications for
front-ends that support parallel display is essential for doing work
with Old Testament Hebrew and Greek texts and with modern translations.
I have
Some of our modules need a certain versification, but do not use all the
books available in the versification. Sometimes this is the result of
the translation being incomplete, but sometimes this is the result of a
theological stance:
Many translations in the former USSR area will use the synodal
Excellent ideas.
Minor point. DMSmith writes, Chapter 1, Verse 1 is present in all books
that exist.
Er, actually, no!
DC books in which the Greek Additions to Esther begin at chapter 10:4
springs to mind as a counter-example.
David
--
View this message in context:
On Thu, Jan 5, 2012 at 9:56 AM, David Haslam dfh...@googlemail.com wrote:
Excellent ideas.
Minor point. DMSmith writes, Chapter 1, Verse 1 is present in all books
that exist.
Minor, minor point: DMSmith writes, But they rely on unreliable assumptions:
He was pointing out that the assumption
Nice idea, we can document this and use to fix existing display problems
with incomplete modules (on level of conf files and frontends, not
engine). But its more like on crutches for me and really universal
solution is module-supplied v11ns.
Peter von Kaehne ref...@gmx.net писал(а) в
2012/1/5 Костя и Алёна Маслюк kale...@mail.ru:
Nice idea, we can document this and use to fix existing display problems
with incomplete modules (on level of conf files and frontends, not engine).
But its more like on crutches for me and really universal solution is
module-supplied v11ns.
32 matches
Mail list logo
