Troy, integrating this in BibleTime Mini, i found that it is hard task to
make parallel Bible display to work correctly (in he light of av11n
support). And in my opinion it does not worth to force each frontend to
implement this.
I have two ideas for now:
1. provide Chapter and Entry renderer,
On 07/11/2013 06:46 PM, Chris Burrell wrote:
> How do you know that verse 0 maps to verse 1 in the first instance, and 2 in
> the next? What if in the target versification, verse 0 is made of 1&2&3.
This is why the various v11n schemes have to be clearly defined either
within the Sword engine, or
In the Psalm KJV contracting example, I'm not sure how you "choose your
expansion". How do you know that verse 0 maps to verse 1 in the first
instance, and 2 in the next? What if in the target versification, verse 0
is made of 1&2&3. What about the following examples:
*Example 1: Inverted verses
*
2013/7/11 Chris Burrell
> I don't think an explicit superset is required. An implicit one yes. By
> that I mean that if you allow a versification X to map to the known KJV
> Versification with parts (say 'a' 'b', or 'firstSentence',
> 'secondSentence', etc. - i.e. arbitrary parts), then it means
sorry, this:
Psalm.51.1=Psalm.51.0@repentance-prayer
Psalm.51.2=Psalm.51.0@bathsheba-intro
would be better as:
Psalm.51.1=Psalm.51.0@musical-instruction
Psalm.51.2=Psalm.51.0@bathsheba-intro
Chris
On 10 July 2013 22:25, Chris Burrell wrote:
> I don't think an explicit superset is required.
I don't think an explicit superset is required. An implicit one yes. By
that I mean that if you allow a versification X to map to the known KJV
Versification with parts (say 'a' 'b', or 'firstSentence',
'secondSentence', etc. - i.e. arbitrary parts), then it means you can go
from X to Y via the KJV
Sorry, when i try to imagine your conception of 'superset', i found verses
scattered all around the room after translation procedure. Have you any
visual representation of what you would like to achieve in final, or would
you make such a table by your self?
Should verses content be always equivale
The issue with me not reading Greek/Hebrew is that I can't tell how things
are aligned...
Chris
On 5 July 2013 04:25, Jonathon wrote:
> On 07/04/2013 03:24 PM, Chris Burrell wrote:
> > I'm afraid, I'm not sure I follow. The screenshot looks ok,
>
> In the LXX, there are roughly eighty verses
On 07/04/2013 03:24 PM, Chris Burrell wrote:
> I'm afraid, I'm not sure I follow. The screenshot looks ok,
In the LXX, there are roughly eighty verses between what is displayed as
3:23 and what is displayed as 3:24.
>but then I don't read Greek or Hebrew so I don't really know.
The issue is not
On Jul 4, 2013, at 12:01 PM, Troy A. Griffitts wrote:
> We have a design in place which allows for the code example I previously
> mentioned:
>
> lxx->setKey(nasb->getKey())
What Chris might not realize in this simple statement: In SWORD a module has
the notion of current key. The module and
We have a design in place which allows for the code example I previously
mentioned:
lxx->setKey(nasb->getKey())
The engine recognized that the versifications are different and calls a
facility to do the translation. We have not finalized on this facility
yet. As also mentioned, ? has sub
I'm guess I've misunderstood as Ps.51 shows the wrong alignment between
Hebrew and English for the first two verses... What are these "translation
facilities currently designed in the engine"?
Chris
On 4 July 2013 16:24, Chris Burrell wrote:
> I'm afraid, I'm not sure I follow. The screenshot
I'm afraid, I'm not sure I follow. The screenshot looks ok, but then I
don't read Greek or Hebrew so I don't really know.
Are you saying Sword already has translation from 1 versification to
another transparently, by " the v11n translation facilities currently
designed in the engine"? From previou
13 matches
Mail list logo
