On 07/15/2015 06:25 PM, Kahunapule Michael Johnson wrote:
> I don't actually care if we line all Bibles up to the same content
> when they have different versification, although that would be nice. I
> care that they can be displayed and searched.
*^- *This.* -^
*Aligning variant v11ns is not some
2015-07-15 23:29 GMT+03:00 Troy A. Griffitts :
> :) Hi Konstantin,
>
> You have to know when I say something like this, "We could build it, but
> I'm afraid it might actually get used," that I'm being mostly facetious
> though there is some true concern in what I am writing. Of course I can
> see
Title: signature
Good morning, Troy and all!
Welcome to July, 2015! I feel like a time traveler. I have seen
this day from far away. Now it is here.
Here is the use case that is kind of like a herd of elephants in
the room: automated production of hu
On July 15, 2015 4:29:24 PM EDT, "Troy A. Griffitts"
wrote:
>:) Hi Konstantin,
>
>You have to know when I say something like this, "We could build it,
>but
>I'm afraid it might actually get used," that I'm being mostly facetious
>though there is some true concern in what I am writing. Of course
I have prompted the PocketSword developer to create the downloadable search
index for this new module.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/New-Turkish-module-tp4654792p4654817.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
:) Hi Konstantin,
You have to know when I say something like this, "We could build it, but
I'm afraid it might actually get used," that I'm being mostly facetious
though there is some true concern in what I am writing. Of course I can
see proper uses if the need arises. I didn't think the Danish
> And it shouldn't be used. :)
It should not be used for one only purpose and we will reject a usefull
feature? :^S
Today we have years from new v11n appeared in Sword and most of frontends be
released with that v11n. Same for if error was in v11n. And most annoying will
be when we will releas
On Wed, 2015-07-15 at 15:28 +0200, Peter von Kaehne wrote:
>
>
> I am now going to install the other two GB bibles we have to see if
> there is simply a problem with the module (GerLut1545lhgb).
There is certainly a problem with the code of the library -
I run mod2im GerLut1545lhgb and it goe
On Wed, 2015-07-15 at 09:05 -0400, Karl Kleinpaste wrote:
> On 07/15/2015 08:29 AM, Peter von Kaehne wrote:
> > Wrt the not display of book Doofus 1.1 or even the existing Malachi
> > 3.22 - if I remember correctly the GB av11n implementation was
> > added to
> > Xiphos at the same time when Xipho
On 07/15/2015 08:29 AM, Peter von Kaehne wrote:
> Wrt the not display of book Doofus 1.1 or even the existing Malachi
> 3.22 - if I remember correctly the GB av11n implementation was added to
> Xiphos at the same time when Xiphos added code to _not_crash_ on av11n
> modules.
Xiphos never had code s
Wrt the not display of book Doofus 1.1 or even the existing Malachi
3.22 - if I remember correctly the GB av11n implementation was added to
Xiphos at the same time when Xiphos added code to _not_crash_ on av11n
modules. Xiphos remained unable to show any KJV v11n external content
for significant ti
Yeah, that doesn't help me either. We abandoned GenBook Bible support
in favor of the VersificationMgr system. I am not against adding a
per-module v11n mechanism, but I fear it will be used. :) And it
shouldn't be used. :) Using this basically allows people to take
shortcuts bypassing the anal
I think that doesn't help my confusion.
If someone creates a genbook Bible containing a previously-unknown book
called Doofus, why should I not be able to navigate to Doofus 1:1, since
the v11n is self-contained?
___
sword-devel mailing list: sword-devel
> On Jul 15, 2015, at 6:59 AM, Karl Kleinpaste wrote:
>
> On 07/15/2015 06:35 AM, Peter von Kaehne wrote:
>> 1) Unlike the other av11n implementation it does not yet show non KJV
>> verse range content.
> I'm confused. If genbook Bibles are essentially self-contained in terms of
> v11n, how can
On 07/15/2015 06:35 AM, Peter von Kaehne wrote:
> 1) Unlike the other av11n implementation it does not yet show non KJV
> verse range content.
I'm confused. If genbook Bibles are essentially self-contained in terms
of v11n, how can a genbook Bible not display all its own content?
__
On Tue, 2015-07-14 at 07:12 -0400, Karl Kleinpaste wrote:
> On 07/13/2015 11:04 PM, Peter von Kaehne wrote:
> > What do you think?
> Is it completely invisible to the application (I know you said Xiphos
> was OK, but were there any rough edges?)
No it is not without rough edges. But I did not exp
2015-07-14 14:58 GMT+03:00 DM Smith :
> Chris has a script that will build the C data structures from an OSIS
> file.
>
> JSword does not handle genbook Bibles.
>
> I'm leery that the performance will be unacceptable. Fast lookup tables
> would need to be built to achieve parity. They'd need to be
17 matches
Mail list logo