[sword-devel] KJV with strong numbers

[Michael Johnson]

On 11/15/19 6:56 AM, Michael H wrote:
>
> However, It's my best interpretation of the sword spec and communication on this subject that all KJV modules which contain red letter encoding would best be represented with the configuration OSISqToTick=false in their respective conf files.

That should not be necessary, but I will add it to eBible.org Sword modules with the next update.

>
> 1. The ebible module does not contain Chapter titles, while the KJV and KJVA modules do.

Odd, since I thought I started with the same source.


>>>         2. The ebible module has more white space between features (pilcrows have trailing spaces, Words of Jesus transitions introduce an extra space, etc.) These are not present in the KJV and KJVA modules.
>>
Non-significant white space variation is an artifact of ambiguities in OSIS interpretation.

>>>         3. Both the ebible and KJV module display quotation marks where the Words of Jesus transitions occur.  This is not present in the source text, but is apparently a quirk of OSIS (not sure if it's in the OSIS, or the conf file.) However, the KJVA module does NOT contain these quotations which is more appropriate. Yet it lists the same source as the KJV module. 
>>
Any quotation marks displayed in the KJV indicate a bug in OSIS interpretation, since they all contain the marker="" attribute.


>>>             Le 15/11/2019 à 09:08, David Haslam a écrit :
>>>>             AFAIK, The OSIS XML files that eBible.org uses for the engKJV1769eb module are not those that either I or DM used for the CrossWire KJV & KJVA modules.
>>>
The eBible.org KJV is taken straight from DM's source, at least for the 66 books of the protocanon.

>>>>
>>>             I have the feeling again that we are wasting a mad energy by the dispersion of sources and parallel works. Two "identical" modules developed from two sources...
>>>
I don't think there is any significant waste of resources going on, here. There is a lot of cooperation and coordination, though.

>>>>
>>>>             I’ve really not looked in detail at how Michael Johnson maintains his modules with Haiola.
>>>
But I have. ;-)

It is highly automated, with periodic regeneration of the modules whether they need it or not when Haiola gets updated. The actual text of the KJV in all of its output formats is the same as the text of DM's master source.

-- 
signature

Aloha,
*/Michael Johnson/**
26 HIWALANI LOOP • MAKAWAO HI 96768-8747*• USA
mljohnson.org <http://mljohnson.org> • Phone: +1 808-333-6921 • Skype: kahunapule