[sword-devel] Sword developer's mailing list mail 100% labeled as spam

[Kahunapule Michael Johnson]

It seems that DKIM validation is always failing for this mailing list. Is there 
something we can do to the mailing list software to stop invalidating DKIM 
signatures? I really don't want to turn of DKIM validation on my in box, as 
that would result in a flood of spam. On the other hand, daily digging good 
emails out of the junk folder to keep in touch with you all is getting a bit 
tedious.

--
signature

Aloha,
*/Michael Johnson/**
26 HIWALANI LOOP • MAKAWAO HI 96768-8747*• USA
mljohnson.org  • eBible.org  • 
WorldEnglish.Bible  • PNG.Bible 
Signal/Telegram/WhatsApp/Telephone: +1 808-333-6921
Skype: kahunapule • Telegram: @kahunapule • Facebook: fb.me/kahunapule 

___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] OSHB module

[Kahunapule Michael Johnson]

Right now, all modules on eBible.org force Strong's numbers to be G or H 
followed by 4 or 5 digits, with leading zeroes as necessary to make 4 digits. 
The reason for this is that Paratext and the DBL software choke on any other 
format. The decision was forced on me, really.

Ideally, I would consider the Real Solution to be that any process that READS Strong's numbers should tolerate the presence or absence of leading zeroes. Indeed, the G or H, if missing, should be inferred from the Testament in which it is found. (Tagging of the longer Esther and Daniel should require an explicit G or H.) But if you write Strong's numbers, maximum compatibility would come from sticking to the Paratext/DBL pattern. Maximum encoding efficiency, of course, would be in the other direction, 
stripping out the redundant leading zeroes and implied G or H would save space, but at this point, I think maximum compatibility is more important.


Right now, asking for all modules to be rebuilt one way or another is a really 
big ask. It is probably easier to preprocess all Strong's numbers to make the 
format consistent within the back end. That way a string comparison in the 
search should work just fine. We would just have to decide what the search 
format should be. G or H should be supplied to disambiguate when necessary, and 
leading zeroes either supplied or stripped. Make sense?

Of course, if a strong consensus on Strong's number formatting could be 
obtained and manifested in code in all relevant Sword Project front and back 
end software, I could go either way. My Bible translation source would still 
have the Paratext/DBL format, but stripping out leading zeroes in writing OSIS 
files is not hard. For now, though, I must agree with Karl about the 
probability of his trademarked Real Solution coming to pass. Sigh.

On 3/14/24 11:23, Karl Kleinpaste wrote:
Quite honestly, the Real Solution™ to this problem is to bite the bullet, make a concrete decision that Strong's numbers are to be encoded in exactly one way, and re-work all existing modules to conform to that standard. Personally, I advocate that such a standard would stipulate Strong's numbers to be encoded in minimal (natural) digits: Encoding an OT reference as "1" means a Heb Strong's dictionary key of "1" and an NT "1401" means a Grk Strong's dictionary key of "01401", that is, zeroes to create 
dictionary module keys are prepended to natural numbers to fill exactly 5 digits.


I've never bothered to attempt a final fix to this problem in Xiphos for exactly the reason that, no matter which direction I might take, it will be an unreliable hack; that in turn is because the very concept of a leading '0' as a weak discriminant between Heb and Grk Strong's numbers is itself an unreliable hack. Whenever the subsequent conceptual change came along, to distinguish Heb/Grk numbers according to a leading H or G (that is, lucene search using e.g. "lemma:G1401"), /that/ was the point at 
which the leading-zero-encoding nonsense should have been forced into the trash bin.


It was not, and here we are.

Probability of the Real Solution™ coming to pass: Vanishingly close to zero.

___
sword-devel mailing list:sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



--
signature

Aloha,
*/Michael Johnson/**
26 HIWALANI LOOP • MAKAWAO HI 96768-8747*• USA
mljohnson.org  • eBible.org  • 
WorldEnglish.Bible  • PNG.Bible 
Signal/Telegram/WhatsApp/Telephone: +1 808-333-6921
Skype: kahunapule • Telegram/Twitter: @kahunapule • Facebook: fb.me/kahunapule 

___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Adding another Bible version

[Kahunapule Michael Johnson]

On 2/21/24 09:54, Allen Johnson wrote:


Thanks for writing.

 1. Yes, permission is granted as we want to distribute the text in as many 
ways possible.


Thank you very much! Would it be OK to standardize the license text using the 
closest matching Creative Commons license? See 
https://creativecommons.org/licenses/by-nc-nd/4.0/deed.es and 
https://creativecommons.org/licenses/by-nc-nd/4.0/deed.en for the wording. I 
think this matches your intent, but with very well-thought-out legal wording. 
(If not, we could just copy what you wrote in your PDF file.)


 2. We are happy to provide a working file but:

 1. Forgive my ignorance but I do the layout in InDesign. Previously, I 
have exported as a text file for others to develop the digital modules for 
E-sword, online bible, and Bible Analyzer. I currently do not see any of the 
formats mentioned in my export or save as options. I will do some research but 
thought you might already know what steps I would need to take.

If you mean that the master copy, or most authoritative text is in InDesign, then you can simply send me the InDesign file and/or an HTML export of that file. I have a copy of InDesign, and can experiment with the export options to get something close enough that I can write a custom script to convert to the format I really need. The large file can go directly to just me at kahunap...@ebible.org, or if it is too large to attach, share it with Google Drive, Dropbox, or similar service. We don't need to 
clutter the Sword Developer's mailing list with a large file.


 2. We are actually in the middle of further revision work, to be completed 
in March or April. Perhaps it would be best to wait for the updated file, 
rather than using the current 2019 edition and then having to update it later 
or being “stuck” with an “older” edition while other programs hopefully update 
theirs.


Since my strategy is to use a script to convert, with little manual labor, and 
lower chances of making mistakes, running an updated copy through the same 
script would be little additional work. So it may be best to start with what 
you have, then run your update through the same script when it is ready. Just 
please remember to send me the update when it is ready, as I might not think to 
ask for it, then. (I maintain well over a thousand Bible modules.)

I look forward to providing our Spanish-speaking readers with another good 
Bible translation option.

Any questions?


I look forward to your feedback on these matters. Thanks, and God bless.

Allen Johnson

Director

*Gracias / Thanks*

*valera logo jpg* <https://www.valera1602.org/>

PO Box 1781 - Mt Vernon, KY 40456 - (865) 773-2347

www.Valera1602.org <https://es.valera1602.org/>

*From: *Kahunapule Michael Johnson 
*Date: *Tuesday, February 20, 2024 at 8:35 PM
*To: *David Rez , SWORD Developers' Collaboration Forum 
, i...@valera1602.org 
*Subject: *Re: [sword-devel] Adding another Bible version

Hello David and all,

To add the Valera 1602 Purificada to the Sword project would require (1) 
permission, and (2) digital files in an acceptable format (OSIS, USFM, USX, or 
USFX).

It looks like the permission granted in 
https://www.valera1602.org/_files/ugd/804ef4_18fd4564ee2340f0ba4d3d661cef36d2.pdf
 is functionally equivalent to a CC-BY-ND-NC license, so the permission part is 
handled.

Whoever reads i...@valera1602.org email: do you have some digital files of this 
Bible translation in USFM, USX, OSIS, or something easy to convert to one of 
those formats? If so, could we please have a copy so that we can make it 
available to users of the Sword Project family of apps, including AndBible?

Thanks!

On 2/20/24 12:14, David Rez wrote:

Hello,

 I was wondering if you all can add a Spanish Bible version called Reina Valera 
Purificada 1602? It's a Spanish Bible created to read more like to the king James 
version. I use the "and Bible" app and they said to ask you all. Thank you

--

Aloha,
*/Michael Johnson/
26 HIWALANI LOOP • MAKAWAO HI 96768-8747*• USA
mljohnson.org <https://mljohnson.org/> • eBible.org <https://eBible.org> • 
WorldEnglish.Bible <https://WorldEnglish.Bible> • PNG.Bible <https://PNG.Bible>
Signal/Telegram/WhatsApp/Telephone: +1 808-333-6921
Skype: kahunapule • Telegram/Twitter: @kahunapule • Facebook: fb.me/kahunapule 
<https://www.facebook.com/kahunapule>



--
signature

Aloha,
*/Michael Johnson/**
26 HIWALANI LOOP • MAKAWAO HI 96768-8747*• USA
mljohnson.org <https://mljohnson.org/> • eBible.org <https://eBible.org> • 
WorldEnglish.Bible <https://WorldEnglish.Bible> • PNG.Bible <https://PNG.Bible>
Signal/Telegram/WhatsApp/Telephone: +1 808-333-6921
Skype: kahunapule • Telegram/Twitter: @kahunapule • Facebook: fb.me/kahunapule 
<https://www.facebook.com/kahunapule>
___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire

Re: [sword-devel] Adding another Bible version

[Kahunapule Michael Johnson]

Hello David and all,

To add the Valera 1602 Purificada to the Sword project would require (1) 
permission, and (2) digital files in an acceptable format (OSIS, USFM, USX, or 
USFX).
It looks like the permission granted in 
https://www.valera1602.org/_files/ugd/804ef4_18fd4564ee2340f0ba4d3d661cef36d2.pdf
 is functionally equivalent to a CC-BY-ND-NC license, so the permission part is 
handled.

Whoever reads i...@valera1602.org email: do you have some digital files of this 
Bible translation in USFM, USX, OSIS, or something easy to convert to one of 
those formats? If so, could we please have a copy so that we can make it 
available to users of the Sword Project family of apps, including AndBible?

Thanks!

On 2/20/24 12:14, David Rez wrote:

Hello,

 I was wondering if you all can add a Spanish Bible version called Reina Valera 
Purificada 1602? It's a Spanish Bible created to read more like to the king James 
version. I use the "and Bible" app and they said to ask you all. Thank you


--
signature

Aloha,
*/Michael Johnson/**
26 HIWALANI LOOP • MAKAWAO HI 96768-8747*• USA
mljohnson.org  • eBible.org  • 
WorldEnglish.Bible  • PNG.Bible 
Signal/Telegram/WhatsApp/Telephone: +1 808-333-6921
Skype: kahunapule • Telegram/Twitter: @kahunapule • Facebook: fb.me/kahunapule 

___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Catholic versification / inter-versification mappings

[Kahunapule Michael Johnson]

Well said, Arnaud. It doesn't have to be an either/or choice between 
presentation as the translators intend and the ability to correlate matching 
content. Troy and I could both enjoy our different use cases, which are 
actually not unique just to Troy and me. It is worth the work to make both 
cases available.

On 2/20/24 05:09, Arnaud Vié wrote:

Thank you for your interest and your time !
And thanks Troy for your valuable historical explanation.

However, I can't help but feel that you all are underestimating the power of 
OSIS !
Your are splitting the use cases of "rendering a bible mostly as it was published" versus 
"making a bible searchable accurately for bible study and research", as if we had to 
choose one and neglect the other.
These use cases are both equally valid, but the good news is that OSIS is 
already a (mostly) perfect format to handle both at the same time.
That's part of the reason why I fell in love with the format and believe it's 
worth maintaining.


In particular, some cases Michael mentions :

Chapter and verse "numbers" aren't always pure numbers. Letters get 
involved in the Deuterocanon/Apocrypha.

Here, OSIS already provides a distinction between :

  * The OSIS ID, which is a "technical" ID supposed to be a unique identifier 
for the book/verse/chapter. On this, OSIS imposes a constrained format and structure 
because applications will need to process it.
  * The published number (the verse or chapter's "n" attribute) which is a free 
text, allowing to preserve the numbering from the published document.

In fact USFM provides a similar distinction between the "v" and "vp", "c" and 
"cp" keywords.
You can check the example in my first email about the proposed Catholic3 versification 
 for an example : it's 
perfectly fine to have an OSIS ID "Esth.3.20" for a verse that is labelled as "13G" 
in the published document, because the OSIS ID is technical.
The OSIS ID should be used almost exclusively for this need of referencing and 
mapping verses between different translations ; in an ideal world, the OSIS ID 
shouldn't even be visible to end users (even though I know that's not currently 
the case).
The "n" attributes are what should be presented to the users when reading a 
bible.

Verse bridges (like verse 1-3 with everything from verses 1 through 3 but 
possibly rearranged and with no other verse markings within them) are very 
common.


OSIS already natively supports its, without any changes to versifications : it allows 
several OSIS IDs on a single tag explicitly for this purpose. (section "15.4. 
Grouping" of the OSIS manual)
So it's perfectly valid to define verses 1,2,3 in the versification, and then have one single 
"verse" element with all of these IDs at once for this use case. This "verse" tag can 
then provide an n="1-3" attribute to preserve the published document notation.



My proposal for a new way of defining versifications aims purely at improving 
the mapping feature - the same one that Troy relies on for bible study and 
research.
It has no impact on the "presentation" side of things - because of these 
existing OSIS features I mentioned above which already allow preserving the original 
text's numbering.
The "principle 1" of my proposal in the other thread is the core of what a versification 
system should be : a versification system should assign a unique ID to identify a verse's contents 
(what I called the "meaning" of the verse in my proposal), so that this ID can be used to 
reference or map the equivalent or related text in other bibles.
That's where the current versification system is problematic, because many bibles do not 
fit exactly into one of the default versifications, and they have no way of building a 
"custom" versification. That's the problem I'm trying to solve.



Le mar. 20 févr. 2024 à 14:54, Peter von Kaehne  a écrit :

There are two aspects here:

Historical developments which have been by and large well explored by Chris 
and are mirrored well in our various av11n system - with specific and now 
largely known gaps - we have less clue on the Roman catholic development of 
versification systems and probably even less on a variety of autochthone 
churches with their own historical development of translations an 
versification. But these are well defined tasks and e.g. the work of Dominique 
to bring in the French systems documents well how we should
handle that side.

The complications coming in due to modern translation are actually very 
limited:

FWIW, most modern translations which play about with versifications still 
actually follow an underlying well known and documented plan.

NRSV(A) eg seems to be all what UBS and Wycliffe use - even when allowing 
for verse bridges, reordering and more.

Which makes me think we should think more about a presentation overlay 
which we have at the moment very rudimentary only. OSIS 

Re: [sword-devel] Catholic versification / inter-versification mappings

[Kahunapule Michael Johnson]

Dear All,

If I understand Arnaud correctly, I really like his ideas. The BEST part is 
that the next time a Bible is submitted for processing with yet another unique 
versification (after the changes are implemented), it doesn't have to be either 
force-fit into a versification that doesn't fit or wait for decades for someone 
to update the hard-coded versifications in the Sword engine, and for those to 
be incorporated into all of the front ends.

I regard the current minimalist versification system to be seriously in need of an upgrade. It is based on false assumptions (listed by Troy, no offense intended) that seemed good at the time they were made. However, with 1404 Bible translations (and counting) is that (1) 90% success is an over-estimate of how well it works, and (2) Sword versification is a complete failure for numerous projects because none of the existing versifications fit, the fall-back mechanisms fail and result in wrong outputs or 
crashes in osis2mod, and nobody is actively fixing the situation.


I have found the following to be true:

The number of versifications needed to represent all Bibles properly tomorrow 
is highly likely to be more than the number that works today. Hard-coding 
versifications into slowly-changing code that is only updated in fits and 
starts is doomed to fail (and already has, in my not-so-humble opinion).

Verse numbers in a chapter don't always proceed in numerical order. Several 
Bible translations move the statement about the motion of the shadow on 
Hezekaiah's steps to a more logical place in terms of discourse, without 
changing the verse numbers. Indeed, they split verses into segments and 
straddle other verses with them.

Chapter and verse "numbers" aren't always pure numbers. Letters get involved in 
the Deuterocanon/Apocrypha. Some Bible translators like to use verse segments (like 6a 
and 6b) heavily.

Verse bridges (like verse 1-3 with everything from verses 1 through 3 but 
possibly rearranged and with no other verse markings within them) are very 
common.

Mapping any arbitrary versification to any other is NICE, but NOT NECESSARY. 
Displaying the text as the translators intended is NECESSARY. If you can do 
both, do it. If you cannot, at least display the versification of the Bible 
translation as the translator intended.

I am fully aware of the changes in architecture and code adapting to the 
realities I perceive imply. At this point, I'm not sure if modifying the Sword 
engine or rewriting it would be easier. Either way, it is a lot of work.

It is my understanding that JSword is a bit better than Sword in this regard, 
in that it doesn't assume fixed versifications.

As far as volunteering for pumpkin holder for versifications, I nominate 
Arnaud. (I already bit off more than I can chew by myself. Sorry.)

On 2/19/24 14:23, Troy A. Griffitts wrote:


Dear all,

These comments are a mix of background, history, and thoughts:

1) VERSIFICATION (v11n):

Variation between reference systems sucks.  Until you get into the weeds of the 
details, it is normal to assume the problems are not complex.  SWORD tries to 
implement a simple 90% solution.

SWORD and JSword support defined abstract versification schemes with 3 simple 
dimensions: [bookid : chapterMax][chapterNumber : verseMax][verseNumber : 
verseEntry]

Conceptually we also operate on these assumptions (I've skimmed the proposal by 
Arnaud which differs here, but I haven't given it the thought it deserves to 
comment yet): that book order is defined in the v11n system; that chapter and 
verse numbers are numeric and begin at 1 and increase to verseMax.  We also 
allocate a special slot '0' for: Module Introduction; Testament Introduction; 
Book Introduction; and Chapter Introduction (e.g., Matt.0.0 can hold an 
introduction to Matthew).

Those who have been exposed to many Bibles will immediately think of places these 
assumption fall short.  But for >90% of our Bibles, these assumption hold true, 
and these assumption make many aspects of our work much simpler (abstract parsing 
of verse lists and ranges, bookmark ordering, etc.).

Historically, SWORD previously supported dynamic, per module, versification, 
with a 3 phase lookup:

index file .bks[book number] = book offset in next index;
index file .cps[book offset + chapter number] = chapter offset in next index;
index file .vss[chapter offset + verse number] = verse offset and entry size in 
data file.

20 years or so, we made the decision to begin the hard work to understand 
versification systems within Bibles so we could begin to map them 
appropriately.  This let us remove the .bks, and .cps index files and store 
that data in versification system definitions, leaving only the final .vss 
index file which gave the offsets and entry sizes into the data file.

Caring about versifications was a decision we made.  Our previous design let 
any Bible decide how many books, how many chapters, and how many verses each 
chapter contained. 

Re: [sword-devel] Fw: Is the Crosswire.org FTP mirror down -or- did it change locations?

[Kahunapule Michael Johnson]

It appears to be up right now.Aloha,Michaelhttp://mpj.usOn Jan 17, 2024, at 20:00, David Haslam  wrote:  -- Forwarded message --From: Jeff Martin Date: On Thu, Jan 18, 2024 at 02:08Subject: Fw: Is the Crosswire.org FTP mirror down -or- did it change locations?To: 'Fr Cyrille' ,'David Haslam' , Cc:   Is the Crosswire.org FTP mirror down -or- did it change locations? https://crosswire.org/ftpmirror/pub/sword/packages/rawzip/*.zip   Jeff Martin814-574-7957 cell"I remain confident of this: I will see the goodness of the Lord in the land of the living," Psalm 27:13. Virus-free.www.avast.com ___sword-devel mailing list: sword-devel@crosswire.orghttp://crosswire.org/mailman/listinfo/sword-develInstructions to unsubscribe/change your settings at above page___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Fwd: Message from 172.70.178.47

[Kahunapule Michael Johnson]

 Forwarded Message 
Subject:     Message from 172.70.178.47
Date:     Thu, 3 Mar 2022 11:06:53 + (UTC)
From:     mich...@ebible.org
Reply-To:     noctisde...@yahoo.com
To:     kahunap...@gmail.com





 Name-> anonymous
 Email-> noctisde...@yahoo.com
 Subject-> reporting typo/inconsistency--
 Form URL-> https://eBible.org/cgi-bin/contact.cgi
hello,

matthew 19:18's red-lettering (https://ebible.org/kjv/MAT19.htm -- after 'Jesus 
said,') is incomplete.

thank you




___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] NA28 shows no verses

[Kahunapule Michael Johnson]

Yes, indeed. It is in my work queue, to follow SILE integration with Haiola for 
PDF generation.

On 5/2/20 7:51 PM, David Haslam wrote:
> This underlined the need and urgency for PocketSword development to continue. 
> It’s also 2 years since PS 1.4.8 was released to support iOS 10 and 64-bit.
>
> Apple is about to release iOS & iPadOS 13.4.2
>
> Regards,
>
> David
>
> Sent from ProtonMail Mobile
>
>
> On Sun, May 3, 2020 at 03:19, Troy A. Griffitts  > wrote:
>> Hi Tom,
>> Your frontend needs a fairly new version of SWORD to support the unlock 
>> codes from the German Bible Society. I believe Xiphos is planning a release 
>> soon. Alternatively you can build Xiphos against SWORD trunk. Your key 
>> should work in Bishop for both Android and Apple. I have no idea what 
>> Bibletime is doing. You'll need to ask their team.
>>
>> My apologies frontends aren't caught up yet. It's likely due to my delay in 
>> a SWORD release with the latest unlock code and their rightful reluctance to 
>> release a build against SVN trunk.
>>
>> On May 2, 2020 5:17:31 PM MST, Tom Sullivan  wrote:
>>
>> Y'all:
>>
>> I finally got around to getting NA28, having had NA26 and 7 for a long 
>> time. I downloaded a key and Xiphos appears to have put it in the conf 
>> file correctly - it matches my downloaded text.
>>
>> But xiphos displays no text, only chapters and so on
>> Bibletime asks for a key each time, but displays the key, then crashes 
>> on OK.
>> BibleDesktop also shows no text.
>>
>> Any ideas anyone?
>>
>> Thanks,
>>
>>
>> -- 
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
>

-- 
signature

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

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Module upload: BlaMat

[Kahunapule Michael Johnson]

I would be happy to generate indexes for the eBible.org repo if (1) I knew how, 
and (2) I knew that PocketSword would actually look on the eBible.org 
repository for them in a location both I and PocketSword know about. I'm not 
quite flush enough with volunteer time to reverse engineer the answers to these 
questions, but if I were, it is more likely that I would just modify the source 
of PocketSword to generate indexes locally like the rest of the front ends. Or 
maybe just enhance Bishop/Crosswire Project
for Apple so that it displays footnotes, etc. I'm sure iOS devices that are 
currently supported by Apple are all powerful enough to generate indexes 
locally without any major problems.

On 12/16/18 12:02 PM, David Haslam wrote:
> As regards defining and documenting the requirements, CrossWire has never 
> made anything clear to provide adequate guidance to repository owners. 
>
> This sorry state of affairs has been allowed to slide for several years. 
>
> PocketSword users are still losing out. 
>
> If Karl could get it working for his repo, what’s hindering Michael from 
> following suit?
>
> Lack of knowledge or an unidentified  technical issue ?
>
> btw. Nic Carter has recently moved to New Zealand to take up a new teaching 
> post. 
>
> David
>
> Sent from ProtonMail Mobile
>
>
> On Sun, Dec 16, 2018 at 21:53, ref...@gmx.net  <mailto:ref...@gmx.net>> wrote:
>> No one is fobbing you off, David. Not answering on the mailing list is 
>> normal if you are not able to.help.
>>
>> There are two separate issues here. For one reason the indices I produce for 
>> CrossWire are sometimes visible and sometimes not. I am clueless why, but 
>> presume the two servers are the problem. I have not looked into that further 
>> due to.travel. dM gave me some hints.
>>
>> EBible is a separate matter. In short , this is Michael's repo and he needs 
>> to produce indices or find a way to produce them automatically.
>>
>> Peter
>>
>> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
>>
>>
>>  Original Message 
>> Subject: Re: [sword-devel] Module upload: BlaMat
>> From: David Haslam
>> To: SWORD Developers' Collaboration Forum
>> CC:
>>
>>
>> I keep pushing at this issue and I get fobbed off repeatedly. 
>>
>> None of the eBible.org modules have an installable search index for PS. 
>>
>> Why is nobody seeking to fix this?
>>
>> Where does PS look?
>> Which server?
>> Which path ?
>> What protocol?
>>
>> Who maintains such a sync ?
>> Has it ever been tested ?
>>
>> The requirements are not transparent. 
>> We ought to document them in our wiki. 
>>
>> If modules on the Xiphos repo do have a search index, why not eBible.org 
>> too?
>>
>> David
>>
>> Sent from ProtonMail Mobile
>>
>>
>> On Sun, Dec 16, 2018 at 21:32, ref...@gmx.net > <mailto:ref...@gmx.net>> wrote:
>>> I think the sync script runs only once every so often..
>>>
>>> Sent from my mobile. Please forgive shortness, typos and weird 
>>> autocorrects.
>>>
>>>
>>>  Original Message 
>>> Subject: Re: [sword-devel] Module upload: BlaMat
>>> From: David Haslam
>>> To: sword-devel@crosswire.org
>>> CC:
>>>
>>>
>>>     Installed bla1890eb from eBible.org to PocketSword. 
>>>
>>> No search index available!
>>>
>>> Is anyone working on providing all these for this repository? 
>>> What’s the main stumbling block?
>>> Where does PS look?
>>>
>>> Still no Blackfoot language or equivalent found in CrossWire Main. 
>>>
>>> Peter - what’s making it invisible?
>>>
>>> David
>>>
>>> Sent from ProtonMail Mobile
>>>
>>>
>>>     On Sun, Dec 16, 2018 at 19:52, Kahunapule Michael Johnson 
>>> mailto:kahunap...@ebible.org>> wrote:
>>>> Thank you very much, David, for pointing out that there was a 
>>>> problem with the eBible.org repository. It turns out that the ftp server 
>>>> was failing to follow a symbolic link, probably due to a "security" 
>>>> update. (Yes, following symbolic links CAN be a security risk, but this 
>>>> was a breaking change that I wasn't aware of until just now.) Anyway, we 
>>>> 

Re: [sword-devel] Module upload: BlaMat

[Kahunapule Michael Johnson]

Thank you very much, David, for pointing out that there was a problem with the 
eBible.org repository. It turns out that the ftp server was failing to follow a 
symbolic link, probably due to a "security" update. (Yes, following symbolic 
links CAN be a security risk, but this was a breaking change that I wasn't 
aware of until just now.) Anyway, we are back in service. The Blackfoot Matthew 
module is listed under the language autonym (Siksika).

On 12/16/18 9:01 AM, Kahunapule Michael Johnson wrote:
> Aloha!
>
> A Blackfoot Matthew module is in the eBible.org repository as bla1890eb, 
> sourced from Jon Bitgood's digitization. (Duplication of Public Domain texts 
> doesn't bother me, by the way, but it might be worth checking before working 
> on a module if duplicated effort might bother you.)
>
> I am trying to figure out what is going on with the eBible.org repository, 
> right now. It looks like it is visible via ftp, http, and https, but 
> refreshes on some front ends come up empty. Investigating...
>
> On 12/16/18 7:28 AM, David Haslam wrote:
>> Thanks Peter. 
>>
>> I was aware of Jon Bitgood having several projects on GitHub. I’ve even 
>> commented on some of them during 2017.
>>
>> Here’s my problem:
>> The language Blackfoot does not appear, nor does any unknown language code, 
>> looking at the CrossWire Main repo from PocketSword. And that’s after a 
>> contents refresh. 
>>
>> NB. Michael Johnson works closely with the Digital Bible Society. He knows 
>> Jon Bitgood. Are we potentially duplicating content that would ordinarily be 
>> hosted on the eBible.org rep?
>>
>> Btw. It looks right now as though the eBible.org repo has become 
>> unavailable. Is this the case for all users? Hopefully, this is merely a 
>> temporary outage. 
>>
>> David
>>
>> Sent from ProtonMail Mobile
>>
>>
>> On Sun, Dec 16, 2018 at 16:19, Peter von Kaehne > <mailto:ref...@gmx.net>> wrote:
>>> On Sun, 2018-12-16 at 14:28 +, David Haslam wrote:
>>>> Please tell us additionally in these announcements
>>>>
>>>> Module type
>>>> Language
>>> Added to work list
>>>
>>>> I’ve not yet been able to find BlaMat.
>>> It is Jon Bitgood's effort to digitise the Blackfoot Gospel of Mark.
>>> Blackfeet are one of the First Nations of Northern America.
>>>
>>> I found his work on GitHub and started taking it on. There are some
>>> problems with it still and i have opened issues but I think it is
>>> worthwhile to start publishing.
>>>
>>> I am far from sure how many Blackfoot speakers still exist but how ever
>>> few, I do think we owe them. Them and all other decimated First
>>> Nations.
>>>
>>> Peter
>>>
>>>
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> Instructions to unsubscribe/change your settings at above page
>>
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>

-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org <http://mljohnson.org> • Phone: +1 808-333-6921 • Skype: 
kahunapule


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Module upload: BlaMat

[Kahunapule Michael Johnson]

Aloha!

A Blackfoot Matthew module is in the eBible.org repository as bla1890eb, 
sourced from Jon Bitgood's digitization. (Duplication of Public Domain texts 
doesn't bother me, by the way, but it might be worth checking before working on 
a module if duplicated effort might bother you.)

I am trying to figure out what is going on with the eBible.org repository, 
right now. It looks like it is visible via ftp, http, and https, but refreshes 
on some front ends come up empty. Investigating...

On 12/16/18 7:28 AM, David Haslam wrote:
> Thanks Peter. 
>
> I was aware of Jon Bitgood having several projects on GitHub. I’ve even 
> commented on some of them during 2017.
>
> Here’s my problem:
> The language Blackfoot does not appear, nor does any unknown language code, 
> looking at the CrossWire Main repo from PocketSword. And that’s after a 
> contents refresh. 
>
> NB. Michael Johnson works closely with the Digital Bible Society. He knows 
> Jon Bitgood. Are we potentially duplicating content that would ordinarily be 
> hosted on the eBible.org rep?
>
> Btw. It looks right now as though the eBible.org repo has become unavailable. 
> Is this the case for all users? Hopefully, this is merely a temporary outage. 
>
> David
>
> Sent from ProtonMail Mobile
>
>
> On Sun, Dec 16, 2018 at 16:19, Peter von Kaehne  > wrote:
>> On Sun, 2018-12-16 at 14:28 +, David Haslam wrote:
>> > Please tell us additionally in these announcements
>> >
>> > Module type
>> > Language
>>
>> Added to work list
>>
>> > I’ve not yet been able to find BlaMat.
>>
>> It is Jon Bitgood's effort to digitise the Blackfoot Gospel of Mark.
>> Blackfeet are one of the First Nations of Northern America.
>>
>> I found his work on GitHub and started taking it on. There are some
>> problems with it still and i have opened issues but I think it is
>> worthwhile to start publishing.
>>
>> I am far from sure how many Blackfoot speakers still exist but how ever
>> few, I do think we owe them. Them and all other decimated First
>> Nations.
>>
>> Peter
>>
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
kahunapule


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Xiphos not seeing eBible.org repository?

[Kahunapule Michael Johnson]

I just set up a new Linux (Ubuntu Bionic Beaver) system for someone, including 
an install of Xiphos. When trying to preload a few Bible translations, I 
noticed that Xiphos couldn't see the eBible.org repository. However, I can see 
and use it just fine from some other front ends. Is anyone else having this 
problem? Is there anything I can do about it, or is this something that needs 
to be fixed in Xiphos?

-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
kahunapule


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] NASB

[Kahunapule Michael Johnson]

Thank you, TS. No offense was taken, here. For now, my NASB module can just 
rest in its copyright prison, as does Greg's. I'm sure both are great from a 
technical standpoint. The Lockman Foundation seems open to some limited 
distribution of the NASB, but for now, I am much more interested in unlimited 
distribution of the Holy Bible in as many languages as possible. In English, we 
are blessed with multiple free options for truly unlimited free distribution of 
God's Word, so let's rejoice!

Thank you, TS, Greg, Troy, and all of you who contribute to this forum and the 
work of digital Bible distribution! I'm particularly happy about recent work on 
automating testing and release of new Sword software. Great job!

May God bless all of you, and grant you a Christmas filled with true peace and 
joy as only our Saviour can provide!
Michael

On 12/23/2017 12:12 PM, TS wrote:
> Hi, I know that this post is old, but I believe that I need to clarify 
> something(s).
>
>  At the very beginning of my earlier email (below with Greg's replies), 
> when I was writing about Kahunapule's posts, I just meant his posts about the 
> NASB in specific being ignored. I was not meaning to refer to all his posts 
> in general which seems to be how my wording was taken. Also, I believe that 
> some time later an email was sent out (by the admin of the mailing list I 
> think?) letting everyone know that the mailing list server had some issues 
> during this period of time. So, perhaps this may be
> related as well to the confusion. At any rate though, I am sorry and do 
> apologize to Greg Hellings and, if needed, to Kahunapule Michael Johnson for 
> any offenses. None was meant. Greg's reply to what I had written regarding 
> Kahunapule's posts came across to me as a strong rebuttal and defense, but 
> also a misunderstanding. I think that I originally did not think that the 
> misunderstanding was worth replying to, but over time it has come to weigh on 
> me. Perhaps I'm being overly sensitive in this, but I do
> believe in honesty with others and trying to be "at peace with others" as 
> much as one can. So, it seemed good that I should write this.
>
> Sincerely,
> TS
>
> On Feb 24, 2017, at 01:47 PM, Greg Hellings <greg.helli...@gmail.com> wrote:
>
>>
>>
>> On Fri, Feb 24, 2017 at 3:22 PM, TS <outofthec...@icloud.com 
>> <mailto:outofthec...@icloud.com>> wrote:
>>
>> From what I can tell, a member named Kahunapule Michael Johnson seems to 
>> be able to already create a NASB Sword module.
>>
>> This is according to his post here and from last year as well.
>> http://www.crosswire.org/pipermail/sword-devel/2017-January/044041.html 
>> <http://www.crosswire.org/pipermail/sword-devel/2017-January/044041.html>
>>
>> I don’t quite understand why his posts keep getting ignored.
>>
>>
>> Kahunapule's posts are not ignored. Many of his are informative, rather than 
>> asking for response or help. But he is not ignored. For instance, he wasn't 
>> really looking for help in setting up his automated repository of modules - 
>> he was keeping the community apprised of his progress on it. And people have 
>> given him responses and feedback when appropriate.
>>  
>>
>>
>> He seems to have been in contact with the Lockman Foundation, but for 
>> some reason thinks or thought that the NASB Sword module would be for free.
>>
>> From what I understand from the forum discussions, in order for the NASB 
>> Sword module to be released, it would have to be a commercial module. Part 
>> of this means that it would obtainable through paying for it. So, the 
>> Lockman Foundation or Crosswire or some other entity would then host it on 
>> their website which allow for it to be downloaded only after paying for it. 
>> I’m guessing that a password would be provided to unlock the module.
>>
>>
>> It would not be sold by Crosswire. Crosswire is a non-income entity and does 
>> not sell any materials.
>>  
>>
>>
>> Can anyone tell me why Johnson's work is not being used? Generally 
>> speaking, could not Michael send it to Greg, Greg review it, and then if it 
>> passes, it be acceptable for release?
>>
>>
>> The goal was for us to be able to hand to Lockman, not a completed module, 
>> but a piece of software that they could feed their existing module through 
>> any time it changed and they could produce an updated version of the module 
>> themselves directly for distribution. So Kahunapule's work would not satisfy 
>> that requirement, unless he was starting from Lockman's internal text.
>>  
>>
>>

Re: [sword-devel] FYI geo IP lookups of repo access

[Kahunapule Michael Johnson]

I do a similar sort of processing of logs to create the metrics at 
http://ebible.org/metrics/. I use a custom Free Pascal program that is probably 
not useful to anyone else without modification, but let me know if you want to 
see it. The Sword module count is based on actual modules, not the individual 
parts. For privacy reasons, I don't keep the actual IP address after 
geolocation lookup, nor do I keep the exact latitude and longitude. I store an 
anonymous user ID based on a one-way cryptographic hash of
IP address and browser identity, plus the country and point that is 
intentionally limited in resolution (even more than the free 
lite.ip2location.com data is already limited to). I delete the original logs, 
then run some queries on the database to get the metrics. Bots are excluded 
both on the basis of well-known agent identifiers and by activity (i.e. massive 
numbers of downloads and page views by the same IP+agent combination makes it 
look more like a web spider than a human). The result is arguably
devoid of any useful personally identifying information, especially anything 
that could endanger anyone in a creative access country. It probably doesn't 
answer all of the questions you might have, but it does give something of an 
idea of where digital Bibles are going, and it what formats. It also shows 
which translations are being downloaded and/or viewed online. However, if you 
just want to look at the map on that page and feel good about how far and wide 
the Bibles are going, you can do that. Then pat
yourself on the back, praise God for letting us do something useful for His 
Kingdom, then get back to work. ;-)


On 09/10/2017 08:45 PM, ref...@gmx.net wrote:
> There is one thing of which I am not sure how relevant it is, but the EU has 
> created legislation counting IP addresses as personal data (among many other 
> things) and making them subject to storage restrictions and other 
> limitations. Here in the UK it becomes law early next year. Sites designed 
> and intended to be transnational have in the past been pulled up for privacy 
> invading stuff. So I would hazard a guess that while CW is not based in the 
> EU, given that many of the collaborators are and some of the
> front-ends too, we need to consider this.
>
> Peter
>
> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
>
>
>  Original Message 
> Subject: Re: [sword-devel] FYI geo IP lookups of repo access
> From: DM Smith
> To: SWORD Developers' Collaboration Forum
> CC:
>
>
> The country information is interesting. I’ve found that bots also skew 
> the counts.
>
> In my bin dir on the CW server, I have a perl program, moduleScrape.pl, 
> (~/bin/moduleScrape.pl) that slogs through the logs to figure out module 
> downloads counting each download once rather than by all the parts. It first 
> goes through the conf files to find the module in the repository and then 
> picks a single file for each module. Then it goes through the log files (ftp 
> and http) looking for downloads (including zip files) of modules. It tosses 
> hits by bots. The output format is normalized to:
> DateModuleFormatTransportIPCountrySimplified agent
> Note IP is obscured here.
> 20150628Easton  prt FTP xxx.xxx.xxx.xxx  United States   
> w4@xiphos.org 
> 20150628PolGdanska  zip HTTPxxx.xxx.xxx.xxxPoland 
>  Apache-HttpClient/UNAVAILABLE (java 1.4)
>
> The program needs tweaking for each server as it “knows” CrossWire’s 
> repositories and it’s logs.
>
> There are a bunch of flags that allow to specify a date range and is 
> geared to find that last full month.
>
> The program started out by J Ansorg and improved by N Carter.
>
> I’ve also a program moduleStats, that runs this program and analyzes the 
> output to produce statistics about the modules.
>
> Troy and I’ve been talking about tossing the data into a database.
>
> DM
>
>
>> On Sep 10, 2017, at 5:38 PM, Karl Kleinpaste > > wrote:
>>
>> Now and then I get curious about where all the accesses to 
>> ftp.xiphos.org come from.  This is a crude summary from my /var/log/xferlog 
>> since early August.  Counts of accesses can be gotten by substituting the 
>> last "uniq" stage of the pipeline with "uniq -c | sort -nr" but such counts 
>> are registering individual files accessed, which is not very informative, 
>> especially for modules that include dozens of image files.
>>
>> cat xferlog* | cut -f7 -d' ' | sed -e s/:::// | sort | uniq -c | 
>> sort -nr | awk '{ print $2 }' | fgrep . | while read ip ; do geoiplookup $ip 
>> ; done | grep 'GeoIP Country Edition' | sed -e 's/GeoIP Country Edition: //' 
>> | sort | uniq
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> 

Re: [sword-devel] BibleTechnologies dot net status?

[Kahunapule Michael Johnson]

I don't know who operates BibleTechnologies.net right now, but last I heard it 
was on a server operated by the American Bible Society.
Note that eBible.org/osis  is still online, and the 
OSIS schema is still available there.

On 08/31/2017 04:02 AM, David Haslam wrote:
> http://www.isitdownrightnow.com/bibletechnologies.net.html
>
> The host site for the OSIS 2.1.1 schema is down.
>
> Does anyone in this list have direct contact with their webmaster?
>
> Best regards,
>
> David
>
>
>
> --
> Sent from: http://sword-dev.350566.n4.nabble.com/
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
kahunapule


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] ERV issues in And Bible

[Kahunapule Michael Johnson]

Note: those preverse milestones and their sID values are generated with 
osis2mod. I have no control over them. It seems clear that osis2mod is the 
problem, here.


On 03/08/2017 12:20 PM, David Haslam wrote:
> Here's the *mod2imp* portion for Psalm 3:8 and the next verse.
>
> $$$Psalms 3:8
>  sID="gen11939"/>  subType="x-preverse" eID="pv6991"/>LORD, the victory osisID="Ps.3.8!note.1" osisRef="Ps.3.8" placement="foot" type="translation">
> 3:8 victory
> Or “salvation.” is yours!  level="2" sID="gen11941"/>You are so good to your people.  level="2"/>Selah type="selah"/> * subType="x-preverse" sID="pv6992"/>* eID="Ps.3.seID.14187"/>
> $$$Psalms 4:0
>  
> $$$Psalms 4:1
> ** canonical="true" type="psalm">To the director^: With stringed instruments. A
> song of David.^ 
> God, you showed
> that I was innocent.  sID="gen11946"/>You gave me relief from all my troubles.  level="2"/> sID="gen11948"/>So listen to me now when I call to you for help.  eID="gen11948" level="1"/>Be kind to me and
> hear my prayer. 
>
> I have bolded the duplicated elements.
>
> David
>
>
>
>
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/ERV-issues-in-And-Bible-tp4656923p4656934.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
kahunapule


-- 
Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
kahunapule


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] ERV issues in And Bible

[Kahunapule Michael Johnson]

You can see the source OSIS XML file at 
https://ebible.org/Scriptures/engerv_osis.zip if you like. All of the OSIS 
source files for Sword modules in the eBible.org repository are in that 
directory.

I'm referring this one to whoever the current pumpkin holder for osis2mod is 
for comment and/or further action, and waiting for a response before doing 
anything else. In the mean time, I just rebuilt engerv2006eb using osis2mod Rev 
3401 just to make sure we aren't dealing with an older and possibly already 
corrected problem. If I need to rebuild the eBible.org repository with a 
corrected version of osis2mod, please let me know.


On 03/08/2017 12:13 PM, David Haslam wrote:
> Dear Michael,
>
> I don't have access to your OSIS XML file, or if I do, I've not yet gone
> looking for it.
> I was merely going by what I saw in the output from *mod2imp*, which
> includes numerous OSIS snippets.
>
> I've never before come across duplication of internal items when a module
> content is exported using this Sword utility. It's supposed to be lossless
> (unlike what's on record for *mod2osis*).
>
> In theory, a round trip module rebuild ought to be feasible:
>
> module => *mod2imp* => IMP file => *imp2vs* => module
>
> I rather suspect therefore that the problem may be caused by *osis2mod* when
> you built the module.
>
> It being documented in the wiki, we know that *osis2mod* performs a
> transformation of its input.
> See https://crosswire.org/wiki/Osis2mod#Transformations
>
> That's where the milestone div elements are made, if they don't already
> exist.
> I was unaware that osis2mod inserts *type="x-milestone"* as well.
> That's not mentioned in the wiki page.
>
> *osis2mod* expects an input file that meets OSIS 2.1.1 or possibly the
> latest CrossWire updated schema.
>
> Neither of these schema allow for the milestone form of the *div* element.
>
> I've therefore started a discussion about this in the talk page:
>
> https://crosswire.org/wiki/Talk:OSIS_211_CR#A_milestone_form_of_the_div_element_.3F
>
> As far as I know, there's been next to no discussion of this before between
> the API developers.
> We do use the milestone form internally, but don't expect it as part of the
> XML input.
>
> With *And Bible* being a *JSword* app., one needs to understand that JSword
> does an XSLT on the internal OSIS XML of a module. What this might do if it
> encounters an orphaned/duplicated milestone *div* element is anyone's guess.
>
> Does any other module show signs of duplicated div elements when analysed
> using *mod2imp* ?
> I think we ought to have noticed this before, but it does require more
> researching.
>
> I've not yet looked at any other modules from *eBible.org* for this
> phenomenon.
>
> Martin reported that Psalm 2:12 was an example location of the issue, so
> that's the place I examined in detail.
>
> His other example Psalm 3:8 has exactly the same sort of triple occurrence,
> this time for *ID="pv6992"* where the previous letter is either "s" or "e",
> there being 2 of the former and 1 of the latter.
>
> Martin added that there are many more, and I counted a total of 503
> instances.
>
> It should be feasible to systematically remove one of the duplicates from
> every such location and rebuild the module using *imp2vs* to see whether
> this gives one that no longer crashes *And Bible* or other JSword apps.
>
> Once we learn which of the pair of sID elements is the delinquent one, we
> might then try and find out where these are coming from, and whether your
> copy of *osis2mod* is the culprit.
>
> Best regards,
>
> David
>
>
>
>
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/ERV-issues-in-And-Bible-tp4656923p4656933.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
kahunapule


-- 
Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
kahunapule


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] ERV issues in And Bible

[Kahunapule Michael Johnson]

Hello, David.

It sounds like my previous reply did not reach you.

I understand that the OSIS file that you extract from my module is flawed. 
However, those flaws do not exist in the OSIS file I used to create the same 
module. The milestone IDs in the OSIS source document are perfect in their 
uniqueness, although slightly more verbose than they need to be. Note that none 
of my milestones start with the characters "pp". The milestone IDs you get from 
mod2imp are flawed. I don't maintain mod2imp, and it is not used in the module 
creation process. I use osis2mod. It is
entirely possible that osis2mod is causing the problem. I do use osis2mod in 
the module creation process. Is osis2mod causing the problem? If the copy of 
osis2mod in the Ubuntu distribution is flawed, then that needs to be fixed. In 
the mean time, is there a non-broken version of osis2mod I should use? Do I 
need to build it from source?

Again, just for clarity, I understand that the OSIS you derive from my module 
has milestone IDs that are duplicated, but the OSIS I built that module from 
does not have that problem. Something else (osis2mod or mod2imp) is introducing 
those errors. I don't maintain those, but I'm happy to rebuild the eBible.org 
repository with a corrected osis2mod if that will fix the problem.

On 03/07/2017 10:51 PM, David Haslam wrote:
> Hi Michael,
>
> Not sure why my analysis is not getting through.
>
> It's quite feasible for an OSIS XML file to validate to a schema and yet to
> remain 'unfit for purpose'.
>
> There are things that the schema does not test for but which are required
> for use in SWORD, etc.
>
> One thing a schema cannot test for is the bad use of milestones:
>
> * Milestone elements in the wrong order (end before start, or overlaps
> between verses, etc)
> * Milestone elements that are completely missing, but which are a needed
> half of a pair
> * Milestone element pairs that do not have the same ID number but which
> ought to
> * Milestone elements that are duplicated
>
> Your module has OSIS that has 503 milestoned *div* elements that are
> *duplicated*.
>
> This probably validates to your MOSIS schema, but it will cause serious
> issues with JSword (based on Martin's evidence) and possibly also for SWORD
> apps too.
>
> Finally, the /milestoned/ for of the *div* element is not part of OSIS 2.1.1
> nor in the latest CrossWire schema.
> https://crosswire.org/wiki/OSIS_211_CR
>
> That might or might not give other problems, but it's probably not the root
> cause of And Bible crashes.
>
> btw. Did you get my email?
>
> Just in case the attachment couldn't be easily retrieved from the message
> here in the mailing list, I sent it you also by private email. 
>
> The IMP file for the whole Bible was fed into a simple filter to extract and
> count all the *div* elements with *type="x-milestone"*. The count is the
> first field in the output file.
>
> Every item for which count=2 is suspect, and there are 503 of them.
>
> NB. The sorted order in the file is largely irrelevant.
>
> Best regards,
>
> David
>
>
>
>
>
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/ERV-issues-in-And-Bible-tp4656923p4656931.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page



-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
kahunapule


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] ERV issues in And Bible

[Kahunapule Michael Johnson]

Is this a problem handling footnotes, perhaps?


Show that you are 
loyal to his son,
2:12
Show … his son
Literally, “Kiss the son.”
or the Lord will be angry and destroy you.
He is almost angry enough to do that now,
but those who go to him for protection will be blessed.


Or is it something to do with the conversion from OSIS to module back to OSIS 
again? (A fragment of the actual input OSIS is shown above.)
Note that there are no duplicate milestone IDs in the file anywhere in the OSIS 
source.


On 03/07/2017 12:57 PM, Kahunapule Michael Johnson wrote:
> I'm pretty sure the OSIS is valid, but if someone can point out a specific 
> problem with the OSIS, I'll look into it.
>
> On 03/07/2017 09:12 AM, Martin Denham wrote:
>> Would somebody mind checking the OSIS of the ERV in the eBible repository 
>> because it is breaking the And Bible OSIS processor in verses at the end of 
>> some chapters.
>>
>> Example problem verses are Psalm 2:12 and Psalm 3:8 but there are many more.
>>
>> The problem is that many verses at the end of chapters have a div with 
>> pre-verse and start-milestone attributes but there is no matching 
>> end-milestone div and the div does not appear to contain anything anyway.
>>
>> Other front ends seem to cope fine with the format so if the OSIS is valid I 
>> will need to change And Bible.
>>
>> Thanks
>> Martin
>>
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>
>



-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org <http://mljohnson.org> • Phone: +1 808-333-6921 • Skype: 
kahunapule


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] ERV issues in And Bible

[Kahunapule Michael Johnson]

I'm pretty sure the OSIS is valid, but if someone can point out a specific 
problem with the OSIS, I'll look into it.

On 03/07/2017 09:12 AM, Martin Denham wrote:
> Would somebody mind checking the OSIS of the ERV in the eBible repository 
> because it is breaking the And Bible OSIS processor in verses at the end of 
> some chapters.
>
> Example problem verses are Psalm 2:12 and Psalm 3:8 but there are many more.
>
> The problem is that many verses at the end of chapters have a div with 
> pre-verse and start-milestone attributes but there is no matching 
> end-milestone div and the div does not appear to contain anything anyway.
>
> Other front ends seem to cope fine with the format so if the OSIS is valid I 
> will need to change And Bible.
>
> Thanks
> Martin
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page



-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
kahunapule


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] NASB

[Kahunapule Michael Johnson]

A slight correction: I have an NASB Sword module, but haven't done anything 
with it, because it had no place to go. I don't think Lockman is interested 
either in distributing it for free or selling it, right now.

Honestly, the length of time that has been taken on the NASB module is 
embarrassing, and I'm not interested in getting mixed up in the conversation 
with the Lockman Foundation right now. The legal status and understanding of 
what the Lockman Foundation would like is hard. The technical part of the 
process: automatically adapting Lockman's master source to Sword is a solved 
problem, at least on my computer.

The real issue, as I see it, is that we have an amazing group of "plodders" who 
persistently keep doing some wonderful things with Bible software over a period 
of many years, but who seem to grow weary or drop out when it comes to timely 
releases and updates. Without some fresh volunteer efforts at a higher level of 
commitment, I don't think we can expect to be taken as seriously as we would 
like to be.

On 02/24/2017 11:22 AM, TS wrote:
> From what I can tell, a member named Kahunapule Michael Johnson seems to be 
> able to already create a NASB Sword module. 
>
> This is according to his post here and from last year as well.
> http://www.crosswire.org/pipermail/sword-devel/2017-January/044041.html
>
> I don’t quite understand why his posts keep getting ignored.
>
> He seems to have been in contact with the Lockman Foundation, but for some 
> reason thinks or thought that the NASB Sword module would be for free.
>
> From what I understand from the forum discussions, in order for the NASB 
> Sword module to be released, it would have to be a commercial module. Part of 
> this means that it would obtainable through paying for it. So, the Lockman 
> Foundation or Crosswire or some other entity would then host it on their 
> website which allow for it to be downloaded only after paying for it. I’m 
> guessing that a password would be provided to unlock the module.
>
> Can anyone tell me why Johnson's work is not being used? Generally speaking, 
> could not Michael send it to Greg, Greg review it, and then if it passes, it 
> be acceptable for release?
>
> In addition to this, Greg himself already seems to have the work done in 
> order to create the module. It seems that the real question is, does it work 
> with all the major SWORD/JSword frontends? DM Smith confirmed last year that 
> it worked with JSword and released a beta of BibleDesktop which supported it 
> as well. The only two problems left (it possibly seems at least) based on DM 
> Smith’s email are:
>
> 1) Does the Sword engine support having the lex as a single module (which is 
> apparently a requirement from the Lockman foundation)? This would mean, for 
> example, that Strong’s would have “G” (Greek) and “H” (Hebrew”) both as 
> “keys”. (I’m guessing having more than one key is the problem or the order of 
> the keys is? Would having them in the same module be a problem? Would having 
> two different keys be a problem or would the order of “G” and then “H” be a 
> problem?)
>
> 2) Does the text display the same on BibleDesktop, SwordWeb and The SWORD 
> Project for Windows? Apparently there’s a word which is accented differently?
>
> The writing on the mailing list regarding the NASB is quite convoluted. I 
> think it’s important though for Matt Zabojnik to know that it’s possible that 
> he doesn’t need to make a new module. He may instead be able to just 
> coordinate and or facilitate things between Greg and Kahunapule Michael 
> Johnson as I wrote above. They both have working modules from what I can tell.
>
> I also do apologize if I’m offending or mis-representing anyone. I’m trying 
> to distill the current situation of the NASB Sword module into its essentials.
>
> -TS
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page



-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org <http://mljohnson.org> • Phone: +1 808-333-6921 • Skype: 
kahunapule


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] anniversaries

[Kahunapule Michael Johnson]

On 01/09/2017 03:56 PM, Karl Kleinpaste wrote:
> On 01/09/2017 08:47 PM, Kahunapule Michael Johnson wrote:
>> I'm pretty sure the Lockman Foundation is not actually interested in 
>> releasing the NASB on Sword.
>
> You misunderstand. There has been a Lockman-sanctioned NASB in progress since 
> 2004.
>

Is nobody actually working on it? I have Lockman-supplied NASB 1995 source (for 
the posting on InScript.org), and can generate a Sword module in a matter of 
minutes if we have permission to post it. Normally, I just send modules to the 
eBible.org repository, but I'm guessing that one would have to be in Crosswire 
main, which is totally fine by me. Is anyone interested?


-- 
Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org <http://mljohnson.org> • Phone: +1 808-333-6921 • Skype: 
kahunapule


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] anniversaries

[Kahunapule Michael Johnson]

I'm pretty sure the Lockman Foundation is not actually interested in releasing 
the NASB on Sword. I could be wrong, but that is the impression I got when I 
last talked to them.

On 01/09/2017 05:44 AM, Karl Kleinpaste wrote:
> Today, NASB has been waiting 13 years.
> NASB was last asked about just this past weekend:
> [2017-01-08 01:34:20] <[nDy]> I am assuming that the NASB is not available on 
> xiphos?
>
> It has been 2 years 13 days since last (1.7.4) Sword release.
>
> It has been 16 months 20 days since the abortive 1.7.5a1 appeared.
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page



-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
kahunapule


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] #include in xzcomprs.cpp - is this a bug or ?

[Kahunapule Michael Johnson]

We are just using zip compression on eBible.org.

On 11/02/2016 09:45 PM, Peter von Kaehne wrote:
> I can categorically say that there are no released CW modules using any 
> compression other than zip. There might be some in our experimental repo. But 
> they would not be released so.
>
> I would think the same can be confirmed rapidly with all other official 
> repos, Xiphos, IBT and eBible. I am convinced they will say the same.
>
> It is unlikely that anyone else has done so, but who knows? I would not worry 
> about it. 
>
> Peter
>
> Sent from my phone. Apologies for brevity and typos.On 3 Nov 2016 07:31, Jaak 
> Ristioja  wrote:
>> I just tried `./configure && make` Sword 1.7.4 and it did compile in
>> xzcomprs.cpp. So I guess the stable releases DO include the experimental
>> code.
>>
>> Usually it helps when experimental features have their own feature
>> branches or similar. This not being a common practice in the Sword
>> project, is probably one cause for other experimental code reaching
>> trunk as well (see the "Infinite loop in SWModule multilemma window
>> search" thread on this mailing list).
>>
>> Anyway, are you saying that removing/disabling this code will not break
>> anything for end-users? Because there are no (known?) modules which have
>> XZ compression? I think there's a risk it has already been used for
>> production. Can you please elaborate?
>>
>> Best regards,
>> J
>>
>> PS: Unrelated to the issue at hand, but this article might be of
>> interest to the Sword project: "Xz format inadequate for long-term
>> archiving" http://www.nongnu.org/lzip/xz_inadequate.html
>>
>> On 03.11.2016 08:51, Peter von Kaehne wrote:
>>> Leaving aside the question of a bug, xzcompress.cpp is experimental code. 
>>> It is not included in any releases so far AFAIK and should not be compiled 
>>> into releases or used by frontends. 
>>>
>>> At least under autotools you need to ask to include it. 
>>>
>>> We have no modules created with it and would currently not allow any 
>>> either. The only currently used and acceptable compression is zip.
>>>
>>> HTH
>>>
>>> Peter
>>> Sent from my phone. Apologies for brevity and typos.On 3 Nov 2016 02:50, TS 
>>>  wrote:
 In xzcomprs.cpp, at line 30, there’s the code:

 #include 

 Xcode was not happy about this since there is no header named this. It 
 seems that in the previous version of PocketSword, the fix was just to set 
 Xcode as to not include this file when compiling so that’s what I’m doing 
 too. Since the SWORD framework does not include lzma.h as a file, this 
 seems like a bug to me, but perhaps there's a reason for it?

 I couldn’t find any reference regarding this matter in specific in the 
 wiki or mailing list.


 -TS
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> Instructions to unsubscribe/change your settings at above page
>>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page



-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
kahunapule


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Announcing Sword++

[Kahunapule Michael Johnson]

On 09/27/2016 03:08 AM, Fiona von Kaehne wrote:
> We try and negotiate as wide permissions as possible. All modules have 
> licensing info in their conf file. That information should be sufficient for 
> your purposes, no? 
>
> In essence all those which are PD or similarly freely licensed are fine, 
> those which are restricted carry appropriate info. The terms vary, but are 
> usually explicit, short and standardised as per our wiki. 

For what it is worth, all Bibles currently on eBible.org/sword/ are OK to use 
with both Sword and Sword++ and any front ends compatible with either. It is 
wise to check every conf file, though, regardless of repository source, to see 
where there might be a problem with permission only for distribution via Sword 
but not derivative software. Troy's suggestion may be a good one to solve that 
issue and let both libraries exist in peaceful coexistence.

Sometimes a little healthy competition among friends can be a good thing.

Aloha,
Michael Johnson
PO BOX 881143 • PUKALANI HI 96788-1143 • USA
mljohnson.org 


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] What is the lowest version of iOS to be currently supported in PocketSword?

[Kahunapule Michael Johnson]

I recommend updating PocketSword for iOS 6 and higher. People with older 
versions of iOS, if any, are unlikely to be updating PocketSword to the version 
you are working on.

On 09/20/2016 10:59 AM, TS wrote:
> I've been going through the code and making fixes, and in the process XCode 
> has warned me that libcurl is for version iOS 6 and higher and also I've 
> discovered that MBProgressHUD was also written for iOS 6 and higher. It seems 
> that the external frameworks were updated from the previous release of 
> PocketSword. So, is the lowest version supported iOS 6 now? or is it still 
> 5.1.1 and I can ignore the warnings? If 5.1.1 should still be supported, do 
> all of the newer frameworks still work with this version of
> the iOS or does compatibility need to be tested between iOS ver. 5.1.1 and 
> the newer frameworks (and workarounds be implemented if need be)?
>
> - Timothy
-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org 


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] OSIS to USFM conversion?

[Kahunapule Michael Johnson]

Hello, Matěj & all:

I'm starting to work on a OSIS to USFX converter. Once in USFX, Haiola can 
convert it to USFM.

I haven't done this before, because of the mismatch between OSIS and USFM/USFX 
in philosophy, but it turns out that the way OSIS is actually used in the Sword 
project, it can be done, and I have a need to do so for some other Bibles, so 
hopefully this will help you, too. I highly recommend using Paratext 
<http://paratext.org>, if you can get access to it. If not, there is Bibledit 
<http://bibledit.org>.

On 06/11/2016 09:18 AM, Matěj Cepl wrote:
> Hi,
>
> I know it is probably mildly heretical to ask here, but does 
> anybody know about a tool to covert OSIS formatted Bible into 
> USFM? I would like to propose Paratext as a new tool for 
> translating Bible instead of the home-made-never-finished 
> craziness translators of CzeCSP use now, and I have OSIS 
> formatted Bible, but I would need all this converted to USFM. Is 
> there any help for me, or do I have to get down and dirty to 
> write some conversion script myself?
>
> Blessings,
>
> Matěj
>


-- 

Aloha,
/Kahunapule Michael Johnson/

*MICHAEL JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143*
USA eBible.org <http://eBible.org>
MLJohnson.org <http://MLJohnson.org>
Mobile: +1 *808-333-6921*
Skype: kahunapule


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Missing verse in AndBible

[Kahunapule Michael Johnson]

On 05/20/2016 11:46 PM, Matěj Cepl wrote:
> OK, now finally to your original question. It's weird, but with 
> AndBible 2.5.1 (from the f-droid.org repository) and WEB module 
> (in the American spelling, just WEB, not any of the modified 
> modules, right now downloaded from the Sword repository), I see 
> Wis 16:1 quite clearly (actually, better than in Xiphos, where 
> I was not able to find out how to select non-canonical book).
>
> May we get the case of the corrupted download here?

So, where did Wisdom 16:29 from engWEB2015eb go in AndBible? This also affects 
the British/International and Catholic Book order variants of the World English 
Bible, but does not affect the Tok Pisin Bible, which was made with the exact 
same tool chain. It also works OK with KJVD and KJVA. Could Wisdom 16:28 ending 
with a colon instead of a period possibly trigger a bug?

-- 

Aloha,
/Kahunapule Michael Johnson/

*MICHAEL JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143*
USA eBible.org <http://eBible.org>
MLJohnson.org <http://MLJohnson.org>
Mobile: +1 *808-333-6921*
Skype: kahunapule



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Missing verse in AndBible

[Kahunapule Michael Johnson]

The World English Bible with Apocrypha/Deuterocanon (engWEB2015eb) uses NRSVA 
versification. Wisdom 16:29 shouldn't disappear unless the versification 
doesn't support that chapter. I think you are right in that it is probably a 
JSword vs. SWORD (C++) issue. Either that, or it is a bug unique to AndBible.

On 05/21/2016 12:26 AM, Troy A. Griffitts wrote:
> This is just a guess, but I know AndBible uses JSword and Xiphos uses SWORD 
> (C++), so could there be a difference in the versification scheme between 
> SWORD and JSword? What v11n is the module using?
>
> On May 21, 2016 1:35:30 AM GMT+02:00, Kahunapule Michael Johnson 
> <kahunap...@ebible.org> wrote:
>
> See below:
>
> On 05/20/2016 11:11 AM, Matěj Cepl wrote:
>
> a) Please, do not send HTML-only messages to the list. In Thunderbird 
> go to Account Settings/Composition & Addressing and unclick "Compose messages 
> in HTML format, please", or at least in the Composer window set in Options / 
> Delivery Format / HTML & Plain Text. 
>
>
> I think I successfully set up delivery to crosswire.org 
> <http://crosswire.org> addresses of both HTML and plain text alternate 
> formats in email. In the year 2016, insisting that only plain text messages 
> be sent to you is not a realistic expectation. All modern email clients send 
> HTML messages by default, and receive them without problems. Enough said.
>
> b) Concerning Wisdom 16:29, I don't understand it. I thought that 
> AndBible intentionally doesn't support deuterocanonical/apocryphal books 
> (http://thread.gmane.org/gmane.comp.literature.sword.devel/25943). Or did the 
> author of AndBible gave up and it supports non-canonical books as well? 
>
>
> AndBible displays Deuterocanonical/Apocryphal books. There is a "+" icon 
> to get to them in the book selection screen. I'm not interested in a 
> theological debate about canonicity in this forum, since we serve and are 
> represented by a wide variety of church traditions. My question is why the 
> last verse of Wisdom 16 would be missing in AndBible, but not in other Sword 
> front ends, and what can be done to prevent that and similar omissions.
>
>
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


-- 

Aloha,
/Kahunapule Michael Johnson/

*MICHAEL JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143*
USA eBible.org <http://eBible.org>
MLJohnson.org <http://MLJohnson.org>
Mobile: +1 *808-333-6921*
Skype: kahunapule


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Missing verse in AndBible

[Kahunapule Michael Johnson]

See below:

On 05/20/2016 11:11 AM, Matěj Cepl wrote:
> a) Please, do not send HTML-only messages to the list. In 
> Thunderbird go to Account Settings/Composition & Addressing and 
> unclick "Compose messages in HTML format, please", or at least 
> in the Composer window set in Options / Delivery Format / HTML 
> & Plain Text.

I think I successfully set up delivery to crosswire.org addresses of both HTML 
and plain text alternate formats in email. In the year 2016, insisting that 
only plain text messages be sent to you is not a realistic expectation. All 
modern email clients send HTML messages by default, and receive them without 
problems. Enough said.

> b) Concerning Wisdom 16:29, I don't understand it. I thought 
> that AndBible intentionally doesn't support 
> deuterocanonical/apocryphal books 
> (http://thread.gmane.org/gmane.comp.literature.sword.devel/25943).  
> Or did the author of AndBible gave up and it supports 
> non-canonical books as well?

AndBible displays Deuterocanonical/Apocryphal books. There is a "+" icon to get 
to them in the book selection screen. I'm not interested in a theological 
debate about canonicity in this forum, since we serve and are represented by a 
wide variety of church traditions. My question is why the last verse of Wisdom 
16 would be missing in AndBible, but not in other Sword front ends, and what 
can be done to prevent that and similar omissions.

-- 

Aloha,
/Kahunapule Michael Johnson/

*MICHAEL JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143*
USA eBible.org <http://eBible.org>
MLJohnson.org <http://MLJohnson.org>
Mobile: +1 *808-333-6921*
Skype: kahunapule



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Missing verse in AndBible

[Kahunapule Michael Johnson]

Title: signature

  
  
I just got a message from a Bible reader who said:
I have been using AndBible for Android since you mentioned it in a recent email newsletter. 

I came across an issue with the WEB in the AndBible. Wisdom 16:29 does not appear. Other translations in the AndBible show Wisdom 16:29, but the WEB does not show it. 

The verse (Wisdom 16:29) shows up in Xiphos (though I got the text from the eBible.org repository and not the crosswire repository). It is clearly found on your eBible.org website. 

Again, I am sorry if this is not the proper place to report this issue. I didn't see any easier option for doing it. AndBible did not have a readily apparent method for reporting such issues. 


I verified that Wisdom 16:29 is indeed missing in AndBible but shows
up in Xiphos, using the same Sword module. When I look at the OSIS
used with osis2mod to generate that verse, I don't see any thing
strange. Is this an AndBible bug?

-- 
  
  
  

  
  
  

Your partner in
electronic Bible publishing,

  
  

  
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Song of Solomon missing from ChiNCVt

[Kahunapule Michael Johnson]

  
  
I have source from the publisher for
  the ChiNCVt that includes Song of Solomon, BUT I need to make some
  utf-8 encoding corrections to it, first.
  Converting from traditional to simplified script is straight
  forward. The reverse is not, because there are multiple cases
  where two ideographs from the traditional script map to one in the
  simplified script.
  I hope to rebuild once the corrections mentioned above are made...
  
  
  On 03/08/2016 10:30 AM, David Haslam wrote:


  I just installed both modules ChiNCVt and ChiNCVs (in response to Martin's
email).

It's conceivable that the source text for one of these modules was derived
from the source text for the other.  cf. It is feasible to convert
Traditional Chinese to Simplified (and vice versa).

Observations:
1. Both are very early modules dated 2002-01-01
2. There is no DistributionLicense entry in the conf files, even though
these are copyrighted works.
(c) 2002 The Worldwide Bible Society Ltd. All rights reserved.
3. The About key text is made up of escaped RTF tags for Chinese Unicode.
Front-ends such as Xiphos do not display these as Chinese ideograms. Worse
still, 73 of the 284 tags are improperly formed by having a hyphen/minus
after the \u. The line needs correcting and converting to proper UTF-8
characters. We could at least implement this, and update the module conf
files.
4. Song of Solomon is missing from ChiNCVt but not from ChiNCVs.
5. There are further 28 missing verses in both modules, as detected by the
utility emptyvss.

Ideally, if we still have any links with the publisher, both these modules
ought to be rebuilt from a fresh copy of the source text files.

Best regards,

David Haslam







--
View this message in context: http://sword-dev.350566.n4.nabble.com/Song-of-Solomon-missing-from-ChiNCVt-tp4656171p4656172.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page




-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Bible submission process question

[Kahunapule Michael Johnson]

  
  
Hello, Russell.
  
  It sounds like you are on your way to duplicating the capabilities
  of Haiola. Haiola reads USFM and
  spits out Crosswire Sword modules, WordML, HTML, InScript, ePub,
  Amazon Kindle Mobi (created from the ePub with an Amazon program),
  PDF (in the pre-release development version), and more. It doesn't
  do RTF, but you can read the WordML into Microsoft Word or
  LibreOffice Writer and write out RTF from there. Haiola is free
  and open source software, except for the InScript generation
  module, but even that I will run on my computer for open access
  Bibles like the OEB. It has been tested on over 700 Bible
  translations. The PDF generation isn't released yet, because of
  some issues with bidirectional scripts, but that shouldn't be a
  problem with the OEB.
  
  So... feel free to carry on with the way you did it last time, or
  just point me to the OEB USFM files and help me with the metadata,
  and I can have your updated module in the eBible.org repository
  reasonably quickly.
  
  On 03/03/2016 01:57 PM, Russell Allen wrote:


  
  Hi guys,
  Sorry if this is the wrong place.
  
  
  There is an old version of the Open English Bible on
the website which needs updating. Someone helped me creating the
modules a few years back.
  
  
  I’m currently trying to automate building the OEB as
much as possible so that we can put out more regular updates.
Source is in USFM (which should be compliant now) and I have
software which parses USFM using a python parser framework and
can then spit out RTF, PDF, HTML etc etc with pluggable
renderers [1]. The software isn’t OEB specific - it should
handle most USFM - though it hasn’t been tested that much on
other sources.
  
  
  I would like to integrate this with the SWORD
framework so that new OEB versions can be pushed out with as
little human input as possible but I’m not sure what the
recommended process is.
  
  
  At the moment I don’t generate OSIS but could do
that fairly easily if I had some help on what the OSIS should
look like, or I could integrate with an existing USFM->OSIS
generator.
  
  
  Best wishes,
  Russell
  
  
  
  
  [1]: https://github.com/openenglishbible/USFM-Tools
  
  
  
  
  
  
  
  ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 
  
  Aloha,
      Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Firefox 44.0.2 and self-signed certs

[Kahunapule Michael Johnson]

Note: you can get FREE proper SSL certificates from https://www.startssl.com/, 
good for one year at a time.

On 2/12/16 9:28 AM, David Haslam wrote:
> I just selected a different tab in my browser and it complained about the
> self-signed cert.
>
> I've added an exception for crosswire.org for now.
>
> Even so, this is the way browsers are moving!
>
> The sooner we can move away from self signed the better.
>
> David
>
>
>
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/Firefox-44-0-2-and-self-signed-certs-tp4656120.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] FYI new TLD

[Kahunapule Michael Johnson]

  
  
sword.pw = 8 characters
  sword.Bible = 11 characters
  crosswire.org = 13 characters
  crosswire.Bible = 15 characters
  
  See
  http://www.nic.bible/blog/post/when-can-.bible-domain-names-be-registered#.VruHEnUrKho
  for registration opening information. You can preregister, now,
  but actual registration for the general public starts at 10:00 AM
  EST on March 8, 2016.
  
  I'm not too worried about blocks based on the TLD, although that
  will probably happen in some places, because it is already
  exceedingly easy to compile lists of Bible sites from search
  engines, keyword scans, etc. Even Kalaam Media's coy names on
  minority language Bible sites are but a very thin veil, easily
  seen through. Some national-level censors are very sophisticated.
  So, yes, this is an issue, but not a good reason to avoid .Bible
  domain names, any more than I would avoid domain names like
  eBible.org or Biblias.me. I just wouldn't go to .Bible names
  exclusively. Besides, they are kind of pricey. Still, the fees
  help support the American Bible Society, so I don't feel too bad
  about that. National firewalls tend to be a bit porous, especially
  when any sort of serious corporate use is allowed. Small leaks in
  firewalls become torrents, so to speak, when data that is easy to
  share comes through, even if it is hand carried.
  
  When I registered eBible.org, I could have had eBible.com and
  eBible.net, too. They were all available.
  
  If you preregister sword.Bible and Crosswire.Bible at Epik.com,
  chances are very good that you will get them on March 8, 2016.
  I just registered Sword.pw and set it to redirect to
  crosswire.org. Feel free to use that URL where brevity is at a
  premium, like on Twitter or in text messages. I think Sword.Bible
  would be more memorable than Sword.pw, though.
  
  On 02/10/2016 01:05 AM, David Haslam wrote:


  Thanks for the heads-up.

Were we to register and use, we'd end up having to use 6 more keys to type
the URL.

One thing for sure, the new TLD will be blocked by regimes hostile to the
Gospel of Christ.
Having such a TLD makes it easier to block than by examining content.
That could be a huge disadvantage should too many organisations jump on this
particular bandwagon.

Even so, it will have its uses.


David




-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Goodrick-Kohlenberger numbers?

[Kahunapule Michael Johnson]

  
  
On 02/02/2016 08:25 AM, David Haslam
  wrote:


  Anyone know what are Goodrick-Kohlenberger numbers?


According to
http://hermeneutics.stackexchange.com/questions/20024/what-do-the-goodrick-kohlenberger-numbers-represent-what-features-does-this-s,
they are kind of like Strong's numbers, but updated to provide
distinct numbers for homographs, include some words not in the KJV,
and make it proprietary to Zondervan. Zondervan may be on shaky
ground defending intellectual property on something that basic, but
there is probably enough creativity and labor involved that it would
work. I don't see much direct application in free software, at least
not for another 95 years.

-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Hosting non-US public domain modules

[Kahunapule Michael Johnson]

  
  
I can confirm that Jonathan's claim is
  false. See
  http://copyright.cornell.edu/resources/publicdomain.cfm
  http://www.copyright.gov/circs/circ15a.pdf
https://en.wikipedia.org/wiki/List_of_countries%27_copyright_lengths
  etc.
  
  We err on the side of caution, but don't need to react to
  assertions made by those without authority who cite incomplete or
  false information. The Malayalam Bible is clearly in the Public
  Domain, as is EVERYTHING first published before 1923. (OK,
  almost everything: the Crown Letters Patent pertaining to the King
  James Version of the Holy Bible and the Book of Common Prayer in
  the UK don't expire, but that isn't a real copyright, and has no
  effect in the USA, unless you are trying to export printed books
  to the UK.) In the USA, some works published as late as 1 March 1989
  can be in the Public Domain if they were not properly marked with
  a copyright notice and not registered.
  
  Copyright expiration is very complicated due to changes in law
  over time, the conditions of each of the laws, the variation in
  copyright law between countries, and the international treaties
  that exist in most, but not all, countries. One of the more
  difficult items in copyright law is the way that it often ties
  copyright term to the lifetime of the (last surviving) author(s),
  unless the copyright owner is a corporation. That means that
  sometimes it is necessary to research when the author(s) died to
  determine the copyright expiration date.
  
  Changes in copyright law in the USA and through treaties also many
  other nations have effectively paused the steady march of
  copyrighted works into the Public Domain until the end of 2018. At
  that time, all copyrights that have not already expired for
  copyrighted works first published in 1924 will expire. At the end
  of 2019, all remaining copyrights for works first published in
  1925 will expire. That is, unless congress annoys us by changing
  the law again.
  
  If you want competent legal advice, you can hire a lawyer who is
  an expert in intellectual property law. If you don't want to pay
  for that, at least read what is available from reputable and
  authoritative sources online, such as http://www.copyright.gov.
  
  On 01/22/2016 04:41 AM, Baiju M wrote:


  On Fri, Jan 22, 2016 at 7:47 PM, jonathon <jonathon.bl...@gmail.com> wrote:

  
On 22/01/2016 10:57, Baiju M wrote:



  What kind of proof will be required? Do we need complete scan available in public?



US Case Law implies that works first published in a language other
than English, and first published outside of the United States, and
first published after 1909, are under copyright within the United
States. Furthermore, copyright status in the country in which the work
was originally published does not appear to be a relevant factor.

  
  
If this is correct, we may need to take down the Malayalam bible from
the Crosswire server. The Malayalam bible was published in 1910. So,
can anyone please confirm on this?

Regards,
Baiju M

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page




-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] japanese sinkaiyaku bible (new testament 1965) is now in the public domain

[Kahunapule Michael Johnson]

  
  
Thank you for the corrections. An
  update is uploading, now, along with text reconverted from the
  source. If you find more opportunities to improve this work,
  please let me know.  :-) 
  
  On 01/13/2016 10:22 PM, ad...@bible.salterrae.net wrote:


  Re: http://ebible.org/epub/jpn1965.mobi

1.Copyright Notice is wrong (or is not accurate).

It says that
"First published in 1963, first copyrigt expired in 1991",
But only the book 'Gospel of John' was published in 1963,
the rest of New testament was published in 1965.

So the expired date of this translation is Dec 31, 2015 (or
Jan 1, 2016) except the book of John.
I am not certain that the Gospel of John published in 1963
and that published in 1965 is same. I wonder some differences
exist between these two editions.

2. The copyright owener nor the translator is not the Lockman
Foundation.

This translation was made by the Shinkaiyaku Seisho
Kankokai _sponsored_ by the Lockman Foundation.
Lockman Fundation claimed the copyrights, but as the
result of court, now the copyright owner is Sin-Nihon-Seisyo-
Kankou-Kai.

see also:
https://ja.wikipedia.org/wiki/%E6%96%B0%E6%94%B9%E8%A8%B3%E8%81%96%E6%9B%B8%E5%88%8A%E8%A1%8C%E4%BC%9A

--
ad...@bible.salterrae.net


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page




-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] japanese sinkaiyaku bible (new testament 1965) is now in the public domain

[Kahunapule Michael Johnson]

  
  
On 01/13/2016 09:01 PM,
  ad...@bible.salterrae.net wrote:


  I think it would be better to refetch the source texts from
our site and reconvert them, because I may corrected more errors
which I have forgotten.


Thank you. I just got them and reconverted.

-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] japanese sinkaiyaku bible (new testament 1965) is now in the public domain

[Kahunapule Michael Johnson]

  
  
Dear Peter,
  
  Thank you for your comments. You make some valid points. When you
  have a Japanese Sinkaiyaku New Testament in the Crosswire
  repository, we can discuss the merits of which repository(ies)
  is/are best to host it. In the mean time, I wasn't kidding about
  the 12 hours. It is in the eBible.org beta repository and working
  in all of its Public Domain glory.
  
  Shalom,
  Michael
  
  
  On 01/06/2016 11:46 PM, Peter Von Kaehne wrote:


  

  Dear Michael,
   
  We have an ongoing publishing relationship with salterrae
+ have several of their Bibles already  online. I have held
back as he describes his OSIS file as a "work in progress"
but can, given a working and signed off OSIS file produce a
module fast enough. While most of our frontends do not yet
have the ability to display all modules from one language
irrespective of origin (repository) I think it would be
preferable if the text came through the CrossWire repo and
not through eBible.
   
  Yours
   
  Peter
   

  Gesendet: Donnerstag,
07. Januar 2016 um 03:17 Uhr
Von: "Kahunapule Michael Johnson"
<kahunap...@ebible.org>
An: sword-devel@crosswire.org
Betreff: Re: [sword-devel] japanese sinkaiyaku
bible (new testament 1965) is now in the public domain
  

  Got it. Thanks! I have
started converting the 1965 Japanese Sinkaiyaku New
Testament. It should be converted and available on
the eBible.org beta repository within 12 hours if
the Good Lord is willing and everything works right.

On 01/06/2016 07:12 AM, ad...@bible.salterrae.net
wrote:
  

  Thanks for the information.

Is there a suitable online source?


1. Informations about bibliogrphy

https://nirc.nanzan-u.ac.jp/nfile/4128
Efforts in Japanese Bible Translation Since 1965
by Bernardin SCHNEIDER, OFM

Shinkaiyaku seisho (New Japanese Bible)
Organized and sponsored by the Lockman
Foundation in 1961 by a number of evangelical
groups who thought the 1954-55 Japan
Bible Society colloquial version too free in
some respects, the Shinkaiyaku Seisho
Kankokai undertook an entirely new translation
of the Bible. After a pilot edition issued
in July 1963, the Gospel of John was
published by the Inochi no Kotoba Sha in
December of that year. In November 1965,
the New Testament was published by the
newly-formed Nihon Seisho Kankokai
(Japan Bible Publishing Society), with Inochi
no Kotoba Sha as the agency. After a
separate publication of the Psalms in September
1968, the Old Testament and
slightly revised New Testament was published
in one volume in September 1970. It
soon became widely used, even among
Roman Catholics.


2. Informations about the source texts

http://bible.salterrae.net/sinkaiyaku/html/
(html formatted text)
or
http://bible.salterrae.net/sinkaiyaku/osis/sinkaiyaku.osis
(osis formatted text, -- work in progress )



  Please provide the link.  Thanks.

David


 
  
   
  --
Aloha,
        Kahunapule Michael Johnson

  

  MICHAEL JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143
  USA
  eBible.org
  MLJohnson.org
  Mobile: +1 808-333-6921
  Skype: kahunapule

  

  
  ___
  sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel
  Instructions to unsubscribe/change your settings at
  above page
  

  

  
  
  
  
  ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 
  
  Aloha,
      Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
 

Re: [sword-devel] SFM to OSIS handling of the markers \fr and \xo ?

[Kahunapule Michael Johnson]

  
  
On 01/07/2016 12:53 AM, David Haslam
  wrote:


  Thanks Michael,

I can imagine a situation where having a back link is useful, but typically
only for footnotes.

Suppose:
1. You click a note marker, and the note gets displayed.
2. You scroll to another passage, but the note remains visible.
3. You click the back link in the displayed note, and return to where you
were before.

NB. Some front-ends might not work this way.

i.e. I think there are two kinds of front-end behaviour in regard to
clicking cross-reference links.
A. It takes you directly to the cross-reference.
B. It displays the cross-reference note, requiring a further click to go to
the selected cross-reference.

For type B front-ends (e.g Xiphos) the back link is still potential useful
for the same reason as with ordinary footnotes.

Then what about cross-reference notes that do not wholly consist of a set of
reference links (ignoring the trivial punctuation marks) ?

i.e. Notes that contain additional text which helps to clarify the
cross-reference.

The Welsh Beibl Net has many of these.

Type A front-ends will deprive the user of the chance to read the additional
text.
Type B front-ends should display the full note.


Is my understanding correct?


Probably. Note that cross reference notes frequently contain
multiple references in the same note, so I'm not sure how a "type A"
front end would deal with that unless it made multiple links. I'm
not actually an expert in Sword front end behavior. For the back
end, it is probably best to include the back link.

-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] SFM to OSIS handling of the markers \fr and \xo ?

[Kahunapule Michael Johnson]

d gwahanol yn y wlad dŷn ni'n ei hadnabod fel
Twrci.\f* ond dyma Ysbryd Glân Iesu yn eu stopio nhw rhag mynd yno hefyd.

Paratext checking for consistency may have a software bug:

The above search result lines also contain three instances where a further
\fr tag is to a single verse.

\fr 19:30 
\fr 31:13 
\fr 21:10 

Maybe the check is only for the first footnote in a line of text??

This is worth reporting.  (I'm not registered).

Regards,

David



--
View this message in context: http://sword-dev.350566.n4.nabble.com/SFM-to-OSIS-handling-of-the-markers-fr-and-xo-tp4655619p4655643.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] NASB status

[Kahunapule Michael Johnson]

absolutely perfect and bug-free. If there are bugs 
in the module, we can certainly provide a fix. Where is the 
alpha version, how do you plan to make QA working? Twelve years.

 Historically, we have had at least 4 people own this effort 
 over the years.  It is not simply that one person has sat on 
 this and hasn't finished it for 12 years.

Yes, so where are products of work of all these people? What did 
they do? I mean, I honestly believe that some work was done, but 
without some presentation of the results, how can we know what's 
done? Here “Twelve years” makes it even more difficult to be 
persuaded.

 I think we are close.  In my mind, the current owner (Greg) 
 simply needs to have a list of outstanding items which keep us 
 from satisfying 1-3 and push each of them down the road until 
 they are done.

And where is that list? That is my question.

 I don't know what those items are.  I am just concerned that 
 we meet 1-3 before we give the data to Lockman to sell and 
 I feel these 3 items are reasonable requests.

I don't think Lockman expects the work to be ever done at this 
point, but that's another thing. If they do, they have my 
admiration (or something else).

However, if you (or Lockman) expect that you will hand over 
finished absolutely prefect module and Lockman will never ever 
see you (or anybody from the Sword project) again, than I think 
you are sorely mistaken.  Unless of course they are prepared to 
maintain the module themselves. After all, even NASB itself is 
(according to Wikipedia) in its tenth edition.

Blessings,

Matěj


  
  
  -- 
  Sent from my Android device with K-9 Mail. Please excuse my
  brevity.
  
  
  
  ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 
  
  Aloha,
      Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] SFM to OSIS handling of the markers \fr and \xo ?

[Kahunapule Michael Johnson]

sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



    -- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] SFM to OSIS handling of the \sr marker?

[Kahunapule Michael Johnson]

  
  
On 01/06/2016 07:07 AM, David Haslam
  wrote:


  As I continue to evaluate the efficacy of Aydeth's u2o.py script, this
subject surfaced in my thinking.

The \sr marker is described in the USFM Reference:

Section reference range. 
· The text reference range listed under a section heading. 
· \sr is not equivalent to \r which is used for marking parallel references. 

What real value is there in making these kind of references into OSIS links?

After all, when you see one of these headings, you're already at the
location.

...

  

I'm beginning to think that we should leave these as plain text headings
rather than active links.

Does anyone agree?


Yes.


-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] japanese sinkaiyaku bible (new testament 1965) is now in the public domain

[Kahunapule Michael Johnson]

  
  
Got it. Thanks! I have started
  converting the 1965 Japanese Sinkaiyaku New Testament. It should
  be converted and available on the eBible.org beta repository
  within 12 hours if the Good Lord is willing and everything works
  right.
  
  On 01/06/2016 07:12 AM, ad...@bible.salterrae.net wrote:


  
Thanks for the information.

Is there a suitable online source?

  
  
1. Informations about bibliogrphy

https://nirc.nanzan-u.ac.jp/nfile/4128
Efforts in Japanese Bible Translation Since 1965
by Bernardin SCHNEIDER, OFM

Shinkaiyaku seisho (New Japanese Bible)
Organized and sponsored by the Lockman
Foundation in 1961 by a number of evangelical
groups who thought the 1954-55 Japan
Bible Society colloquial version too free in
some respects, the Shinkaiyaku Seisho
Kankokai undertook an entirely new translation
of the Bible. After a pilot edition issued
in July 1963, the Gospel of John was
published by the Inochi no Kotoba Sha in
December of that year. In November 1965,
the New Testament was published by the
newly-formed Nihon Seisho Kankokai
(Japan Bible Publishing Society), with Inochi
no Kotoba Sha as the agency. After a
separate publication of the Psalms in September
1968, the Old Testament and
slightly revised New Testament was published
in one volume in September 1970. It
soon became widely used, even among
Roman Catholics.


2. Informations about the source texts

http://bible.salterrae.net/sinkaiyaku/html/
(html formatted text)
or
http://bible.salterrae.net/sinkaiyaku/osis/sinkaiyaku.osis
(osis formatted text, -- work in progress )


  

Please provide the link.  Thanks.

David

  
  




-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] PEG parser for USFM

[Kahunapule Michael Johnson]

  
  
On 01/02/2016 10:48 AM, Ryan Hiebert
  wrote:


  I'm completely new to USFM, so I'm sketching out my ideas on how the parser probably should look. This is unearthing some of the many things I don't understand about USFM, so I'll post my questions here. Feel free to forward me to a better forum if there is one.

These questions are all related:

1. Is text allowed to be on a line _without_ a marker starting the line?


Yes. Newline and space are equivalent.


  2. Are blank lines semantically meaningful?


No.


   That is, if all the blank lines are removed, does the file mean _exactly_ the same thing?


Yes. Two or more consecutive white spaces are the same as one white
space. A white space can be space, tab, or newline.


  3. Are the non-text markers (one that don't have the ending form( \usfm* ) required at the beginning of all meaningful lines?

No.

Note that there are FOUR classes of markers, not just two, the way I
parse them (which is regularly tested against Paratext output):
1: Starts and beginning of a line (normally), and indicates a
paragraph or metadata. Its effects extend until the next such
marker. Examples: \id, \c, \v, \p, \q1.
2: Footnote/cross reference styles, non-nestable, terminated by the
next such style. For historical reasons, these can also be
terminated by an end marker like the next case, so when reading,
allow either syntax. Examples: \fr, \ft or \ft ...\ft*, \fqa.
3: Normal character markers with both beginning and ending markers,
with the end marker the same as the beginning marker but ending with
"*". These are not allowed to be nested or nested within the above
style markers. Examples: \nd ...\nd*, \wj ...\wj*.
4: Nested character markers start with "\+" and terminate with the
same marker ended by "*". These are otherwise the same as #3, but
cannot occur unless they are inside of a style of case #2 or #3.
Examples: \+nd ...\+nd*, \+wj ...\+wj*

The class numbers above aren't in the USFM specification, but the
concepts are both there and in the master reference implementation
of USFM, which is Paratext.


Sometimes Paratext produces USFM files where markers of the first
kind can be in other positions than the beginning of a line. When
writing USFM, put them at the beginning of a line. When reading
USFM, be more tolerant.


  
4. Is only one non-text marker allowed per line?

No, but when writing USFM, class #1 markers, put them at the
beginning of a line.


  
5. Must a non-text marker be only at the beginning of a line?


That is best practice. Always write them there if you are writing,
but allow them elsewhere if you are reading.


  Thanks for any help you can give with assisting me in sorting this out. I'm obviously completely new to USFM, so I don't know what I don't know.


Take a look at some test cases from http://ebible.org/Scriptures/,
files ending in _usfm.zip. Also, if you want to read some C# code,
you can check out the Haiola source code for how I parse USFM.

Also, one word of caution: There is no proper way to do a
one-to-one, lossless, round tripable correspondence between USFM to
OSIS.

-- 

  
      Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] zip/unzip weirdness technical advice please

[Kahunapule Michael Johnson]

  
  
My first guess would be to check the
  operation of the engine's installer. The zip, unzip, and scp
  programs are all very stable, reliable, well tested, and highly
  unlikely to cause that sort of thing to happen by themselves.
  
  On 12/26/2015 07:18 AM, Peter von Kaehne wrote:


  I zip a finalised module (conf file ok). I scp it to the server. I
unzip it in a staging area. I use the engine's installer to move it
from my staging area to the server's module area and move the zip to
the zip packages.

As both zip conf file and ftp conf file are the same way corrupted the
problem is in the zip/scp/unzip process.



-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Submission of OSIS files for Bibles and Commentaries

[Kahunapule Michael Johnson]

  
  
Wow. A little grace would go a long way
  in this thread.
  
  I don't regard the idea of automatic conf file generation as
  fundamentally flawed. I recommend it, as long as it is done well.
  I do it all the time. I just start with a more complete set of
  metadata already stored in Haiola.
  
  Would it not be practical to automate the replacement
  of computed portions of the conf file, rather than addition? That
  way, if an existing entry is already correct, and the computed
  portion is also correct, no harm occurs, nor does it cause any
  extra work. If an existing entry is not correct, then the computed
  entry just corrects it. If it is missing, it is added. In all
  three cases, if the computed entry is correct, then the resulting
  conf file should be correct. Of course, if the computed entry is
  incorrect, the resulting conf entry would also be incorrect, so it
  is important to make sure that the computed entry is correct, as
  you already know.
  
  When running lean on volunteer power, effective use of automation
  is a good idea. So is walking in love.
  
  On 12/26/2015 06:10 AM, Peter von Kaehne wrote:


  On Sat, 2015-12-26 at 07:16 -0800, David Haslam wrote:

  

But it's not saving time overall because it's being done so badly.


  
  
Well it has saved my time - apart from answering your emails I have
even cumulatively spend less time on this than on any publication
prior, including republication that I would have otherwise. I am
celebrating Christmas with friends etc, I am on call medically and I
have still issued 7 modules in 3 days. 

As it is my time I am dealing with primarily I call it now a resounding success. And I am not sarcastic. Just pissed off. 



  
It's wasting time for those of us who submitted good working modules!
This causes a huge amount of frustration.

  
  
No one ever was supposed to submit good working modules - just a OSIS
and a conf file which can be compiled into good working modules. I now
say just an OSIS and a conf file fragment which can get compiled into a
good working module. No difference whatsoever.


  

I stick to my assertion that it's fundamentally flawed because it's
not fit
for purpose.

  
  
Well, it serves its purpose right now and it has served it well before
- i was able to apply corrections in seconds instead of waiting when I
have a half hour or more time and will not get disturbed - and it
already produces less delays and less problems than anything either
Chris or I did in the past.


  
I have no confidence that it can be reliably mended.

There are simply too many possible variations in conf files that no-
one can
predict.

  
  
No, there are not. There are calculated and not calculated parts. If I
did not have to delete the calculated parts from your files which are
simply all over the place in their order then I would have saved myself
(and you) half of the mistakes you moaned about. 

Submit what I ask you for and leave the rest to my scripts. Submit more
than I ask you then I waste time deleting the crap out of your
submissions so that I do not have doubled up lines or non-functional
parts. 

In absence of a wiki page on the process the confmaker.pl code is
public, has been announced ages ago on the mailing list, the process
has been discussed here and on modu...@crosswire.org, all in all it
 has been public as a direction of travel for over a three years. The
code is in our repositories and has been constantly updated - all
updates go through crosswire-svn so all in all it is selfexplanatory
and tells you exactly what detail you can expect will be calculated -
and what you need to supply. Supply too much as you did, then I will
need to delete and then we have problems. In future I will reject your
conf files and will ask you to shorten them yourself. 


  
Today I saw unrelated lines inserted before a continuation line.

  
  
?


  
It's not as if the line order was fixed, though there are a few items
that
must be in a particular order.

  
  
?

Which ones and why?

Peter


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http

Re: [sword-devel] CrossWire subversion server error

[Kahunapule Michael Johnson]

Title: signature

  
  
SVN access is working fine from my
  location in the USA, so it doesn't seem to be a server problem. It
  is probably a firewall (yours, your ISP's, or a national-level
  filter). I suggest using a VPN and trying again.
  
  On 11/06/2015 04:49 AM, Troy A. Griffitts wrote:

Dear John,
  
  I am sorry for not responding sooner. I have no idea what might be
  the problem. We do have some IP bans on the server but they are
  for all ports. And thinking of it, that SVN command should be
  using the same port as your web browser. It seems a very odd
  problem that your browser can get through but not that SVN
  command. Do you have any kind of proxy running that might either
  be interfering with the SVN command or helping the web browser?
  
  Troy
  
  On November 5, 2015 11:27:44 PM MST, John
Austin 
wrote:

  Something has changed so that for the past week now, the CrossWire 
subversion server has been unreachable from Central Asia.

This:
svn checkout http://crosswire.org/svn/sword/trunk ./

Only returns this (after a time-out wait):
svn: E000110: Error running context: Connection timed out

Access to http://crosswire.org/svn/sword/trunk through a web-browser 
works fine. But svn isn't working.

Does anyone know what is wrong?

-john


sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


-- 

Sent from my Android device with K-9 Mail. Please excuse my brevity.


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 




 
  
  
  Your partner in electronic Bible publishing,



  
  
  

 
   MICHAEL JOHNSON

PO BOX 881143

PUKALANI HI 96788-1143

USA
   
eBible.org

MLJohnson.org

Mobile: +1 808-333-6921

Skype: kahunapule

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Updated CzeBKR

[Kahunapule Michael Johnson]

  
  
Actually, the order is significant, due
  to quirks in Paratext and the USX schema. It should be:
  \id MAT
\h Matouš
\toc1 Evangelium podle Matouše
\toc2 Matouš
\toc3 Mt
\mt1 Matouš
\c 1
\v 1 Kniha rodu Ježíše Krista syna Davidova, syna Abrahamova.

  or maybe
  
  \id MAT
\h Matouš
\toc1 Evangelium podle Matouše
\toc2 Matouš
\toc3 Mt
\mt2 Evangelium podle
\mt1 Matouš
\c 1
\v 1 Kniha rodu Ježíše Krista syna Davidova, syna Abrahamova.

  
  It looks more redundant than it actually is. Normally, \toc2 has
  the same contents as \h, but might differ in case. Normally, \toc1
  has the same contents as the concatenation of the \mt# titles, but
  not always. If abbreviations are used, they definitely should be
  in \toc3. Otherwise, \toc3 can have the same contents as \toc2.
  
  For USFM to be validated for submission to the ETEN DBL, it has to
  be like that, so I spend a lot of time making it so on various
  Bibles.
  
  On 10/06/2015 07:21 AM, Matěj Cepl wrote:


  On 2015-10-06, 16:46 GMT, David Haslam wrote:

  
I was thinking merely of those more verbose book names.

  
  
OK, first, does it matter so much? Cannot we make version 1.2 
now, and I would update it in future with 1.2.1 (or 1.3)?


  
Though it will not substantially affect the module, you could include in the
USFM conversion

\toc1 Verbose book name
\toc2 Short book name
\toc3 Abbreviation

  
  
OK, I am completely confused what is the standard way how to 
deal with the beginning of a biblical book. I have now (Matthew, 
see http://is.gd/85eZ79 for the source):

\id MAT
\mt1 Matouš
\c 1
\v 1 Kniha rodu Ježíše Krista syna Davidova, syna Abrahamova.

And everything seems to work just fine (so I am not sure I see 
the reason why I should change anything). Should I change it 
into the following?

\id MAT
\mt1 Matouš
\h Matouš
\toc1 Evangelium podle Matouše
\toc2 Matouš
\toc3 Mt
\c 1
\v 1 Kniha rodu Ježíše Krista syna Davidova, syna Abrahamova.

Isn’t it a bit too many times repetition? How many times 
I should write down “Matouš” to make you happy?

Best,

Matěj





-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] eBible xref

[Kahunapule Michael Johnson]

  
  
On 09/21/2015 02:11 PM, DM Smith wrote:


  I found the following in eBible’s kud2008eb. The following is Matt.1.1.

Yeisu Besinana ana mumugao (Luke 3:23-38)  Laulele teina Besinana Yeisu ana mumugao vehabadi. Yeisu tubuna Deivida, na Deivida tubuna mugamugaina Abelaham. 

The problem is that the osisRef is incomplete. It should be osisRef="Luke.3.23-Luke.3.38”.

The impact is that clicking on the reference in Bible Desktop, it only shows Luke 3:23.


This is a known artifact of the current conversion from
human-readable references to machine readable references. USFM
doesn't directly handle reference links, so I synthesize them on
conversion to USFX, which is then converted to OSIS. This will
probably be fixed eventually, but don't hold your breath waiting for
it. It probably involves rewriting the code that does that, which is
currently a set of 7 XSLT processes. I have a lot of higher
priorities on my work list. If you prefer, I could inhibit such
osisRef entries altogether until such time as I might possibly get
around to improving the reference reading process. (It is kind of
complicated, since "human readable" actually means "human readable
in any of about 7,000 languages".) The alternative of getting all of
the translators (or anyone else) to go back and manually enter
machine-readable references probably won't happen during this
century.


  The following is just extra. It is in addition to the bug mentioned above.

It is also really odd that there is a second title that contains a parenthesized, inlined reference.

The type="sub” is meant to give a sub part of a title. Since there is no prior title, it shouldn’t be sub. As a plain title, it doesn’t need an attribute.


That "sub" in the title probably came from \s (section title), which
could be (but isn't always) under \ms (main section title). It does
no harm, as far as I can tell, and having it there covers the case
where \s follows \ms. Let's not move the goal posts any more than we
have to.


  Also, the type=“parallel” is inappropriate. The OSIS manual gives that parallel is meant to provide the title in another language. The type sub is probably more appropriate. Or even type="continued” which means that this title continues the last.


Page Appendix F, page 138 of the OSIS User Manual seems to disagree
with you about the proper conversion of the USFM \r tag.


  Note that canonical=“false” is redundant. All titles by default are canonical=“false”.


Yes, it is. That is certainly not the only redundancy. It is not
harmful.
    -- 
      
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Psalm titles in USFM with xrefs that use \xo ?

[Kahunapule Michael Johnson]

  
  
Footnotes in section headers and
  similar titles are allowed in USFM. I can't think of any reason
  why they shouldn't be. I can think of some reasons why they should
  be allowed, though. Haiola handles them as expected and intended
  by the translators, except on conversion to OSIS then Sword
  format. OSIS won't validate with those footnotes there, so I strip
  them out. This is clearly not optimal, but it prevents a worse
  problem of blocking publication of a whole Bible because of OSIS'
  inability to cope with a footnote in a title. Perhaps there is a
  workaround I overlooked that would be better, though.
  
  There are well over 1,000 Bibles that have had their source
  converted to USFM and/or USX. (Those two formats are basically
  interchangeable for anyone with Paratext.) The ETEN DBL has Bibles
  all in USX. OSIS maintenance and support seems to have died, or at
  least gone comatose, but it seems to me that it might be worth
  considering either tweaking OSIS to support everything that USFM
  supports, or replacing OSIS with another source format for Sword
  use. Or at least supplementing it. (I know that old formats die
  hard. GBF support is still in the Sword library, even though its
  inventor stopped using it years ago.)
  
  Just some food for thought...
  
  On 09/17/2015 10:22 AM, Peter von Kaehne wrote:


  I am not sure that this is good USFM, though having said this, the Welsh Bible has become something like a exhibition piece for USFM.

Sent from my phone. Apologies for brevity and typos.On 17 Sep 2015 13:01, David Haslam <dfh...@googlemail.com> wrote:

  

A feature of USFM is that for some translations a canonical Psalm title may
contain a cross-reference.

A peculiarity may occur when the title is not [part of] verse 1, and when
the xref contains an origin marker.

Here's an example: (Welsh beibl.net)

\c 3
\s1 Gweddi yn y bore
\d Salm gan Dafydd pan oedd yn ffoi oddi wrth ei fab Absalom.\x - \xo 3:0
\xt 2 Samuel 15:13—17:22\x*
\q1
\v 1 O \nd ARGLWYDD\nd*, mae gen i gymaint o elynion!
\q2 Mae cymaint o bobl yn ymosod arna i.
\q1

Observe that the origin marker refers to verse 0 of the Psalm. (\xo 3:0)

What's the preferred way to convert this to OSIS, and how would the result
be supported by SWORD ?

David


--
View this message in context: http://sword-dev.350566.n4.nabble.com/Psalm-titles-in-USFM-with-xrefs-that-use-xo-tp4655290.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

  
  ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] eBible repo - zip errors -- really a download problem

[Kahunapule Michael Johnson]

  
  
On 09/14/2015 12:22 PM, Martin Denham
  wrote:


  I don't know what has changed since I last tested
installation of zips from eBible repo but now
java.util.zip.ZipFile does not recognise the zip files as valid
zips.



  java.util.zip.ZipException: Not a zip archive
  at java.util.zip.ZipFile.readCentralDir(ZipFile.java:385)
  at java.util.zip.ZipFile.(ZipFile.java:163)
  at java.util.zip.ZipFile.(ZipFile.java:119)
  at
org.crosswire.common.util.IOUtil.unpackZip(IOUtil.java:86)



I have attempted to install WEBBE and BBE.
  


I can't reproduce the problem. It looks like an incomplete download
problem. On the eBible.org server, the zip integrity check reports
no errors. It also shows no separate entries for directories.

-bash-4.1$ ls eng*
engASV1901eb.zip    engDBY1884eb.zip  engKJV1769eb.zip 
engT4T2014eb.zip    engWEBBE2015eb.zip
engBBE1964eb.zip    engDRA1899eb.zip  engLXX2012eb.zip 
engUKLXX2012eb.zip  engWMB2015eb.zip
engBrent1851eb.zip  engGLW1996eb.zip  engRV1895eb.zip  
engWEB2015eb.zip    engWMBB2015eb.zip
-bash-4.1$ unzip -t engWEBBE2015eb.zip
Archive:  engWEBBE2015eb.zip
    testing: mods.d/engWEBBE2015eb.conf   OK
    testing: modules/texts/ztext/engWEBBE2015eb/nt.bzs   OK
    testing: modules/texts/ztext/engWEBBE2015eb/nt.bzz   OK
    testing: modules/texts/ztext/engWEBBE2015eb/ot.bzs   OK
    testing: modules/texts/ztext/engWEBBE2015eb/nt.bzv   OK
    testing: modules/texts/ztext/engWEBBE2015eb/ot.bzv   OK
    testing: modules/texts/ztext/engWEBBE2015eb/ot.bzz   OK
No errors detected in compressed data of engWEBBE2015eb.zip.
-bash-4.1$ unzip -t engBBE1964eb.zip
Archive:  engBBE1964eb.zip
    testing: mods.d/engBBE1964eb.conf   OK
    testing: modules/texts/ztext/engBBE1964eb/nt.bzs   OK
    testing: modules/texts/ztext/engBBE1964eb/nt.bzz   OK
    testing: modules/texts/ztext/engBBE1964eb/ot.bzs   OK
    testing: modules/texts/ztext/engBBE1964eb/nt.bzv   OK
    testing: modules/texts/ztext/engBBE1964eb/ot.bzv   OK
    testing: modules/texts/ztext/engBBE1964eb/ot.bzz   OK
No errors detected in compressed data of engBBE1964eb.zip.


-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] PocketSword indexes for the eBible.org repository?

[Kahunapule Michael Johnson]

Title: signature

  
  
Hello, Nic.
  
  I thought you might be thinking that. We need a new approach.
  
  The eBible.org repository will probably never be much more stable
  than it is right now. I'm not aware of any pressing need to do a
  whole-repository rebuild at this instant, but I would say that it
  is likely that this will happen from time to time, like when any
  adjustments are made to the versification selection (including
  adding new versification possibilities, as well as continuing to
  optimize the selection of existing versifications), changes to the
  OSIS generation, etc. I actually did just change one aspect of the
  OSIS generator, but it only affected one translation. And, I
  suspect that there may be a few more things that come up.
  Nevertheless, the repository is usable, right now, except for the
  lack of PocketSword index files and listing in the master
  repository list.
  
  I rebuild modules if any source file changes, even by one jot or
  tittle. I get emailed reports of typos at a rate that is actually
  difficult to keep up with, sometimes every day. Remember, I'm
  actively maintaining well over 700 Scripture projects, most of
  which feed into the eBible.org repository. A few of the projects
  are tied into active public projects, like the World English Bible
  family, the Translation for Translators, and several minority
  languages. Those could change weekly. Others are tied into active
  translation projects with slower release cycles, but with that
  many, there will be changes and additions coming out frequently.
  
  In other words, if you are waiting for the eBible.org repository
  to be really stable, you are probably waiting for something that
  might not happen.
  
  Alternatives include:
  
Go ahead and automate the index build in its current
  location. When space becomes an issue, either upgrade the
  server or discard any obsolete index over 3 months old.
Update PocketSword to not need pregenerated index files,
  i.e. by generating them itself on first access or by not using
  them.
Update PocketSword to look for the index files on eBible.org
  where I have plenty of space for them, or on a subdomain of
  crosswire.org on the same server.
Only keep the index for the current version active on the
  server. Honestly, you look for the index right after a
  download, so people with older versions of the module would
  probably already have the index.

  
  Other ideas?
  
  
  On 09/09/2015 01:22 AM, Nic Carter wrote:


  
  I was wanting to wait until things were a little more stable
before starting automatic generation.
  
  
  The way things work is that I create an index for each
module, but I create an index for each version of each module. I
don't delete them, either, as a user may have an older version
of a module and want the index for that particular version of
that particular module.
  With the rate of versioning of new modules for eBible, I have
avoided creating new modules for fear of very quickly filling
the HDD on the web server!
  
  
  I hope that helps you understand why this isn't happening
yet...
  
  
  Thanks, ybic
  Nic :)

Sent from my phone, hence this email may be short...
  
On 9 Sep 2015, at 12:58, Kahunapule Michael Johnson <kahunap...@ebible.org>
wrote:

  
  

  
  Has index generation for PocketSword to use with eBible.org
  repository modules been automated, yet?
  Is there anything I can do to help make that happen?
  I could create them on my local machine and upload them as
  necessary, if that would help...
  -- 



  



  
  Your partner in
  electronic Bible publishing,
  


  


  

  MICHAEL JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143
  USA
   eBible.org
  MLJohnson.org
  Mobile: +1 808-333-6921
  Skype: kahunapule

  

  

  
  
___
  sword-devel mailing list: sword-devel@crosswire.org
  http://www.crosswire.org/mailman/listinfo/sword-devel
  Instru

[sword-devel] PocketSword indexes for the eBible.org repository?

[Kahunapule Michael Johnson]

Title: signature

  
  
Has index generation for PocketSword to use with eBible.org
repository modules been automated, yet?
Is there anything I can do to help make that happen?
I could create them on my local machine and upload them as
necessary, if that would help...
-- 
  
  
  

  
  
  

Your partner in
electronic Bible publishing,

  
  

  
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification

[Kahunapule Michael Johnson]

  
  
The lack of documentation agreement on
  what the default versification is doesn't surprise me, but it
  should be fixed.
  It also doesn't affect me, because I never call osis2mod without
  specifying the versification to use, so I never use the default.
  This is a pretty minor point compared to the architectural issue
  of not really being able to optimally represent the world's Bibles
  with the current set of hard-coded versifications.
  An even bigger point is not being able to handle mid-verse section
  titles. Those are VERY common. (I just have all section titles
  disabled temporarily on the eBible.org repository because of
  this.)
  
  Priorities.
  
  On 09/05/2015 08:37 AM, David Haslam wrote:


  The de facto observation that recent builds of osis2mod make NRSV the default
v11n raises several questions:

When was this change sneaked in? 

Was there a formal agreement among developers?

Was there any announcement?

Why was this not mentioned on the Developers' wiki?

Which other SWORD utilities have been changed (if any)?

How come the change was not reflected in the SYNTAX HELP ? (as Michael H
reports)

IMHO, this change was unwarranted. 

It's very galling that such a significant change could be made without
adequate considerations of the implications.

Those who have scripts for module builds may well have omitted the -v KJV
switch for osis2mod.
It was wrong to assume that for such module developers it would be left to
chance to discover that their scripts were no longer working correctly.

Best regards,

David





--
View this message in context: http://sword-dev.350566.n4.nabble.com/osis2mod-default-versification-tp4655253p4655255.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page




-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification/MIDVERSE SECTION TITLES

[Kahunapule Michael Johnson]

  
  
I just tried a build with midverse
  section titles turned on with Xiphos, and lo and behold, it
  worked! Someone fixed something or my memory was faulty or both.
  Verified with kkl2015eb, Acts 9:19. (This is the newest Bible in
  the collection.)
  If you don't want to see the noncanonical section headings, you
  can always turn them off. The GlobalOptionFilter=OSISHeadings conf
  option is set where applicable (which will be for most of the
  Bibles in the collection).
  The eBible.org/swordbeta repository is being incrementally updated
  again, turning section titles on globally.
  
  On 09/05/2015 01:56 PM, Peter von Kaehne wrote:


  Yes

Sent from my phone. Apologies for brevity and typos.On 5 Sep 2015 11:44 pm, Kahunapule Michael Johnson <kahunap...@ebible.org> wrote:

  
>
> Should I re-enable section titles (including mid-verse section titles) in the OSIS I feed to osis2mod? I recall discussions about things not working right, but don't recall the details of what failed how in which front ends.
>
  



-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification/MIDVERSE SECTION TITLES

[Kahunapule Michael Johnson]

  
  
Should I re-enable section titles
  (including mid-verse section titles) in the OSIS I feed to
  osis2mod? I recall discussions about things not working right, but
  don't recall the details of what failed how in which front ends.
  
  
  On 09/05/2015 11:22 AM, DM Smith wrote:


  
  Osis2mod handles mid-verse section titles properly. The problem is
  elsewhere. They work just fine in Bible Desktop and other JSword
  applications.
  
  
  Regarding more v11n, this has nothing to do with
osis2mod. osis2mod merely knows what SWORD makes available and
allows that.
  
— DM

  

  On Sep 5, 2015, at 4:33 PM, Kahunapule
Michael Johnson <kahunap...@ebible.org>
wrote:
  
  


  The lack of documentation
agreement on what the default versification is
doesn't surprise me, but it should be fixed.
It also doesn't affect me, because I never call
osis2mod without specifying the versification to
use, so I never use the default.
This is a pretty minor point compared to the
architectural issue of not really being able to
optimally represent the world's Bibles with the
current set of hard-coded versifications.
An even bigger point is not being able to handle
mid-verse section titles. Those are VERY common. (I
just have all section titles disabled temporarily on
the eBible.org
repository because of this.)

Priorities.

On 09/05/2015 08:37 AM, David Haslam wrote:
  
  
The de facto observation that recent builds of osis2mod make NRSV the default
v11n raises several questions:

When was this change sneaked in? 

Was there a formal agreement among developers?

Was there any announcement?

Why was this not mentioned on the Developers' wiki?

Which other SWORD utilities have been changed (if any)?

How come the change was not reflected in the SYNTAX HELP ? (as Michael H
reports)

IMHO, this change was unwarranted. 

It's very galling that such a significant change could be made without
adequate considerations of the implications.

Those who have scripts for module builds may well have omitted the -v KJV
switch for osis2mod.
It was wrong to assume that for such module developers it would be left to
chance to discover that their scripts were no longer working correctly.

Best regards,

David





--
View this message in context: http://sword-dev.350566.n4.nabble.com/osis2mod-default-versification-tp4655253p4655255.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

  
  
  
  -- 

Aloha,
    Kahunapule Michael Johnson

  

  MICHAEL
JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143
  USA
   eBible.org
  MLJohnson.org
  Mobile: +1 808-333-6921
  Skype: kahunapule

  

  

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at
above page

  
  

  
  
  
  
  ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahu

Re: [sword-devel] osis2mod default versification

[Kahunapule Michael Johnson]

  
  
On 09/05/2015 02:23 PM, Peter von
  Kaehne wrote:


  Re versifications, the need for any v11n needs to be established and well documented. Once in use we can not easily withdraw any v11n, so introduction happens careful, but nothing should stop you making a good case for specific new v11n(s).


I understand the way things are and have been for years. It is hard
to change, but not impossible. If someone wanted to implement
per-module versifications such that code changes weren't necessary
to deal with the way someone else split up the Bible into chapters
and verses, I would be all for it. But not enough to code the
changes, at least not now.


   Domcox has just now produced two new v11ns which hopefully will make it into svn soon. You should check them esp with French Pacific island languages. 



I intend to add those v11ns to my versification checks when support
for them in Sword is real in the stable Sword utilities and they are
supported by the distribution versions of all actively-supported
front ends. Someone please let me know when that happens.

Seriously, there is no point making modules with a versification
nobody can read, yet. Once support is real, it is not hard for me to
check every single module again to see if the "least bad"
versification has changed with the addition of any new ones.
-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Namespace Proposal re eBible - collissions, duplication, clean-up etc

[Kahunapule Michael Johnson]

  
  
Welcome back, Troy. Enjoy the vacation
  from your vacation.  ;
  
  The "eb" namespace trailer has now been added to all of the Bible
  modules in the eBible.org repository. The last update cycle is
  complete, and the repository is at rest.
  
  eBible.org main repository: ftp://ftp.eBible.org/sword or
  http://eBible.org/sword
  
  eBible.org beta repository: ftp://ftp.eBible.org/swordbeta or
  http://eBible.org/swordbeta
  
  The previously-advertised ftp://ftp.eBible.org/pub/sword still
  works, and probably will continue to work, but the shorter URL
  seems preferable to make primary, right now.
  
  On 09/04/2015 03:46 AM, Troy A. Griffitts wrote:


  

On 09/03/2015 10:50 PM, Peter von Kaehne wrote:

  

Where is Troy and what does he think?

  
  
I have just arrived back from being tour-guide for my sister on vacation
and now I need a vacation :)

I've been following these threads, catching up when I have time, and I
think the conversations happening need to happen and everyone ultimately
is coming to sane and logical conclusions.  I am enjoying being a spectator.

I like Peter's suggestion to namespace with a trailing publisher code
for all the reasons everyone has said, and especially since it will get
the eBible repo online publicly without any engine changes right now.

Great work and I'm excited about all the movement and new resources for
the Gospel mission!

Troy




  

Peter



On Thu, 2015-09-03 at 10:21 -1000, Kahunapule Michael Johnson wrote:


  Based on Peter's good advice and sound reasoning, I'm appending an 
"eb" to every Bible module name in the eBible.org repository. I 
didn't want to lengthen the module names excessively with something 
like "eBible_org" or even "ebib" on the end-- just enough to avoid 
collisions among less than a dozen repositories. These module names 
get crammed into really small spaces at times, for better or for 
worse, at least for display. One letter appended didn't seem quite 
enough for clarity, but two letters provides 676 possible 
combinations and a reasonable chance of assigning sequences that make 
sense, like cw, ib, xi, etc. I'm not putting in an obsoletes line in 
the conf files for these changes, leaving a manual cleanup challenge 
behind. Such obsoletes lines would have undesired side-effects in the 
case of existing collisions, especially the worst kind, where names 
differ only by case. I'm assuming that the other modules probably 
won't change their module names for existing modules, being already 
fully public and in general use already, but might adopt a similar 
convention for all new modules.

I regret any inconvenience this naming convention change may cause 
for those awesome people who have been testing the eBible.org 
repositories. It seems that this little thing will solve more 
problems (including solving problems in advance) for more people than 
the inconvenience it may cause.

In the case of the non-Bible modules on the eBible.org repository, 
I'm not renaming them at this time, because they are bit-for-bit 
copies of the same modules from Crosswire main. Therefore, 
duplication should not be a problem. Those are there merely as a 
convenience. They could be removed if they actually do cause a 
problem.

Module abbreviations are mostly unchanged. Collisions could happen. I 
think the consensus is that those will be dealt with by the front 
ends when they happen for particular users.

In other news, I have (1) disabled morphology tags that don't use the 
same system as DM's KJV, and (2) corrected a bug in the code where it 
was possible for Haiola to miss generating a 
GlobalOptionFilter=OSISMorph line in the conf file. The new grcTisheb 
module should at least display correctly, even though it is missing 
some features. I'll deal with that later. Maybe. Ideally, I will 
restore the missing features when I learn some things I don't yet 
know and have time to implement that.

Thank you, front end developers, for making adjustments to handle 
another very large repository.

Thank you, all who have tested the new repository and pointed out 
opportunities for improvement, some of which have been essential.

With the addition of the new eBible.org repository:
More people will be able to use Sword project software for Bible 
study on their favorite devices and in their own language.
Adding new Bibles and Bible portions to the Crosswire Sword module 
collection just got orders of magnitude easier and faster.
Frequent revisions and additions for translations that are in 
progress are truly practical, now. New books can be added or updated 
as they are completed or revised.
We have a way of easily tapping into Paratext projects for rapid 
updates, which is actually happening now with about a dozen projects.
We have a way to quickly publish any Bible we 

Re: [sword-devel] Namespace Proposal re eBible - collissions, duplication, clean-up etc

[Kahunapule Michael Johnson]

  
  
See below:
  
  On 09/04/2015 01:43 AM, Karl Kleinpaste wrote:


  
  On 09/03/2015 07:09 PM, Kahunapule
Michael Johnson wrote:
  
  

Please make sure you get a fresh copy
  from the repository.
  I always refresh immediately before such tests; such was the case
  90 seconds before I wrote.
  
  the
morphology tags have been stripped from this module for now.
Those may come back, later, if I have time to deal with all of
that.
  
  ?!?
  
  Why did you do that?  As I wrote when first looking over grcTisch
  (Wed 09:02pm), all you needed to fix the problem was to add
  GlobalOptionFilter=OSISMorph in order to trigger the apps' ability
  to switch it on and off in the engine, and (in Xiphos' case) to
  provide for the needed separate subtext layer to hold it, apart
  from Strong's, when switching it on.
  
  There's nothing "to deal with," you just have to configure it
  properly.  Literally a one-line .conf fix.  I had already manually
  added it to my local copy and seen that it would then be fine.


Thank you for that information. There are two things to deal with
right now, for me, other than what looks like a one-line .conf fix.
One is a steep learning curve of how morphology tags work with the
markup variations and the different applications and front ends.
Your assurance that everything was fine except for the .conf line is
helpful. I was concerned that there might be other, deeper issues
and an unending quagmire of tweaks. The other thing is that I don't
do one-line .conf fixes directly. I fix the process, not the .conf
file, and let the process generate the correct .conf file. This is
slower for one module. It is orders of magnitude faster for hundreds
of modules. This is not a really hard thing, but I'm currently only
fixing repository show-stopper items for launching the eBible.org
repository. The rest will have to wait until the repository is
officially on line.

-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Namespace Proposal re eBible - collissions, duplication, clean-up etc

[Kahunapule Michael Johnson]

t is thankfully out of copyright. 

http://www.amazon.com/s/ref=nb_sb_ss_c_0_10?url="">
-alias%3Dstripbooks
-keywords=romeo+and+juliet=romeo+and+%2Caps%2C339

Most of these are by Shakespeare, some are some tribute plays or
whatever by other authors. Amazon can handle this, my bookshelf can
handle this, CrossWire should handle this. 


  

  the eBible repository is currently nowhere advertised. People who


*ahem*  Nobody's getting off that easily.  I alone had no less than 6 
reports about eBible's failure to deliver content, all because 
Michael wasn't testing his own repo before repeatedly announcing "all 
is well!" to the world even when nothing was working.  Others 
reported problems as well.  So I'm not buying that.  I don't expect 
us to have to deal with a repo that was effectively bricked without 
its owner even knowing it.

  
  
Leaving aside Michael's initial start-up difficulties, it remains a
fact that until eBible is part of the automatic repo updater,
advertised on the Wiki and elsewhere it remains a beta or even
experimental repo. People will need to live with breakage. 

And my proposal has the beauty that the only breakage some people will
experience is that they will suddenly have 2 SpaRV2009 from eBible (one
called SpaRV2009 and SpaRV2009ebib. Nothing will actually break. 


  

eBible repo has waited a long time to become available.  I think 
another week or three ...

  
  
I agree that we can wait a little while longer, but my proposal changes
nothing to the negative, but removes in one fell swoop a whole range of
options for damaging failure.

Peter

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

    
    

    -- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Module deduplication: ASV

[Kahunapule Michael Johnson]

  
  
Good point. For now, I'm going to
  assume that nobody else in CrossWire is as interested and active
  in ASV maintenance as I am, and put that Obsoletes line in. If I'm
  mistaken, please let me know.
  
  On 09/02/2015 07:54 AM, DM Smith wrote:


  
  Just a mechanical point. If you add Obsoletes=ASV, then it rules
  out CrossWire from updating it.
  
  
  — DM
  

  
On Sep 2, 2015, at 1:51 PM, Kahunapule Michael
  Johnson <kahunap...@ebible.org>
  wrote:


  
   The ASV
module (American Standard Version of 1901) in the
Crosswire main repository came from my eBible.org copy around 2006. Since that
time, there have been numerous typo corrections and
corrections to conform to the printed master copy, based
on emailed feedback diligently compared to the master
copy, public errata on the web (because most ASVs in
electronic format came from the same scan), and a
detailed Genesis-to-Revelation proofreading by Dale and
cross-checked by myself. While there were only a few
differences that I would consider theologically
significant, there were literally hundreds of
corrections made.

The current best text of the ASV I know of anywhere,
including in commercial software, is on eBible.org in many formats, including the
engASV1901 module. The ASV module on the main crosswire
repository could be replaced with the eBible.org copy or removed. I'll add on
"Obsoletes=ASV" line to the engASV1901.conf file with
the next rebuild.
-- 
  
  signature
  

  
  
  

Your
partner in electronic Bible publishing,

  
  

  
  

  
MICHAEL
  JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA
 eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  
  ___
  sword-devel mailing list: sword-devel@crosswire.org
  http://www.crosswire.org/mailman/listinfo/sword-devel
  Instructions to unsubscribe/change your settings at above
  page
  


  
  
  
  
  ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Namespace Proposal re eBible - collissions, duplication, clean-up etc

[Kahunapule Michael Johnson]

  
  
On 09/03/2015 12:02 PM, Karl Kleinpaste
  wrote:


  
  On 09/03/2015 04:21 PM, Kahunapule
Michael Johnson wrote:
  
  The
new grcTisheb module should at least display correctly, even
though it is missing some features.
  - grcTischeb.conf is not individually in
eBible's pub/sword/mods.d, though it is present within
pub/sword/mods.d.tar.gz.
  

Please make sure you get a fresh copy from
  the repository.
  

 - grcTischeb.conf still does not contain morph
config.
  

No, it doesn't. It isn't supposed to, right now, because the
morphology tags have been stripped from this module for now. Those
may come back, later, if I have time to deal with all of that. As it
is on the repository right now, it should at least be consistent, if
not ideal or complete.

 - grcTischeb.conf does not provide Obsoletes
for the newly-defunct grcTisch (though it has
Obsoletes=grc_tisch).
  

No, and it won't, just like all of the other modules renamed with
"eb" appended to the end. Please forgive the inconvenience.

 - grcTischeb directory is missing from
pub/sword/modules/texts/ztext so obviously install fails.
  

Please get a fresh copy from the repository.
  There was a glitch earlier today that I found and corrected
  already.

Thank you for your patience.

-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Namespace Proposal re eBible - collissions, duplication, clean-up etc

[Kahunapule Michael Johnson]

  
  
On 09/03/2015 10:50 AM, Peter von
  Kaehne wrote:


  Oy! :-)

Michael, we are still discussing and trying to find a consensus which
will last! Please do not do anything just yet. 


Too late. Actually, if I need to undo what I just did, that can be
done, but I don't think that is likely, even if we go with DM's
idea.

Putting a repository source in the datapath is actually a great
idea, but still doesn't solve the conf file name collision problem
by itself, nor does it solve the zip file name collision problem. We
would still need some sort of name space appendage in the module
name. And if we do that, we don't really need to change the data
path per repository unless we want to for other reasons.

If we were starting from scratch, we could do all sorts of things
that make more sense and/or are cleaner and more elegant. The
challenge comes with trying to find a solution that deals with the
following current realities, which will probably be true for at
least a year (and maybe forever in some front ends):

  Module names need to be unique across repositories, such that
one module name refers to exactly one module (or at least identical
copies of the same module if it is in more than one
place).
  Front ends tend to truncate the displayed module name
in some contexts, so the most interesting portions of
the module name need to come first.
  With hundreds of languages represented, the language code is
probably the most significant part of avoiding module collisions
and finding the right Bible. Module name space is the least
interesting to the Bible student, but still necessary to prevent
collisions.
  
  Module names have to be meaningful for human readers, or at
least not too obscure. (This rules out use of GUID strings, like
f365941f-598f-5332-8999-b52456c5f69a, which identifies my KJVD
in ePub format, but you can't tell just by looking.)
  Module name has to match the name of the .zip file and (give
or take case) the directory containing the module files.
  Any changes in the Sword Engine or front ends requires time to
roll out, even if we are quick to upload fixes. Not all front
ends have "push" upgrade mechanisms or even upgrade
notifications.
  




  

I think whatever we should do should be permanent and consensual

I remain convinced that my proposal is the best as it will work
immediately with all frontends of all kinds and requires no changes,
but DM's suggestion has also advantages, including being a cleaner
division for the long term. 

Where is Troy and what does he think?

Peter



On Thu, 2015-09-03 at 10:21 -1000, Kahunapule Michael Johnson wrote:

  
Based on Peter's good advice and sound reasoning, I'm appending an 
"eb" to every Bible module name in the eBible.org repository. I 
didn't want to lengthen the module names excessively with something 
like "eBible_org" or even "ebib" on the end-- just enough to avoid 
collisions among less than a dozen repositories. These module names 
get crammed into really small spaces at times, for better or for 
worse, at least for display. One letter appended didn't seem quite 
enough for clarity, but two letters provides 676 possible 
combinations and a reasonable chance of assigning sequences that make 
sense, like cw, ib, xi, etc. I'm not putting in an obsoletes line in 
the conf files for these changes, leaving a manual cleanup challenge 
behind. Such obsoletes lines would have undesired side-effects in the 
case of existing collisions, especially the worst kind, where names 
differ only by case. I'm assuming that the other modules probably 
won't change their module names for existing modules, being already 
fully public and in general use already, but might adopt a similar 
convention for all new modules.

I regret any inconvenience this naming convention change may cause 
for those awesome people who have been testing the eBible.org 
repositories. It seems that this little thing will solve more 
problems (including solving problems in advance) for more people than 
the inconvenience it may cause.

In the case of the non-Bible modules on the eBible.org repository, 
I'm not renaming them at this time, because they are bit-for-bit 
copies of the same modules from Crosswire main. Therefore, 
duplication should not be a problem. Those are there merely as a 
convenience. They could be removed if they actually do cause a 
problem.

Module abbreviations are mostly unchanged. Collisions could happen. I 
think the consensus is that those will be dealt with by the front 
ends when they happen for particular users.

In other news, I have (1) disabled morphology tags that don't use the 
same system as DM's KJV, and (2) corrected 

Re: [sword-devel] eBible.org beta repository updated

[Kahunapule Michael Johnson]

  
  
Thank you.
  I use the actual Ethnologue/ISO 693-3 language code for the first
  3 characters of the module names in the eBible.org repository. To
  do otherwise increases the risk of collisions and the risk of
  confusing myself. I could do like I do when matching up Bibles
  with FCBH and make a mapping to their language codes, but it can
  get confusing.
  See http://www.ethnologue.com/language/fra for the language code.
  The "2" in the date was a typo. I think more research is needed to
  figure out which text this really is. Like you said, there were
  many revisions over time...
  
  On 09/03/2015 11:40 AM, domcox wrote:


  On Tue, 1 Sep 2015 09:32:31 -1000
Kahunapule Michael Johnson <kahunap...@ebible.org> wrote:

Hi Michael,

About fraFOB1724, which is a module for the French Bible Ostervald, I think it must be renamed to FreFOB:
- Fre is the recommended prefix for French modules.
- The Ostervald Bible was first made public in the year 1744, so obviously 1724 is not the correct date. 
Anyway, if you compare verses from the module vs a printed Bible (1779), they don't match:
Printed Bible:
Gn 1:2 Et la terre était sans forme & vide.. (Old style)
fraFOB1724:
Gn 1:2 Or la terre était informe et vide, .. (Modern style)
The Ostervald Bible was revised and revised many times during its history, so it's not easy to define a date without error, but this version looks more like a modern revision, maybe the 1996 revision? 





-- 
  
      Aloha,
      Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] eBible.org repository minor tweak

[Kahunapule Michael Johnson]

  
  
Sorry, I should have said HTTPS is not
  supported by all front ends. Note that HTTPS is not HTTP.
  
  The eBible.org repository can be reached at:
  https://eBible.org/sword
  http://eBible.org/sword
  ftp://ftp.eBible.org/sword
  ftp://ftp.ebible.org/pub/sword
  
  All of those lead to the same physical files on the same disk.
  
  For the test/beta repository, substitute "swordbeta" for "sword"
  in the above URLs.
  
  On 09/02/2015 02:24 AM, Martin Denham wrote:


  The http link is missed from the first post but
works fine with JSword.  And Bible is using http to access the
repo.


Martin
  
  
On 2 September 2015 at 06:04, Chris
  Burrell <christopher.burr...@gmail.com>
  wrote:
  

  
It's
  the only supported protocol for jsword (step, and
  bible, ...) though I believe dm may have implemented
  ftp recently
  
  
From:
Greg Hellings
Sent:
‎02/‎09/‎2015
  04:20
To:
SWORD Developers' Collaboration
Forum
Subject:
Re:
  [sword-devel] eBible.org repository minor tweak

  
  

  Why is HTTPS not supported? It's
supported by the engine and by at least BibleTime
and Xiphos AFAIK.


--Greg
  
  
On Tue, Sep 1, 2015 at 9:03
          PM, Kahunapule Michael Johnson <kahunap...@ebible.org>
  wrote:
  
 The main
  repository has been updated with revised
  modules with Strong's numbers (5 of them). The
  update is about markup and conf files, with no
  change to source text.
  
  Also, I used symbolic links to allow the /pub
  in the directory to be omitted. In other
  words, ftp://ftp.eBible.org/sword
  works just as well as ftp://ftp.eBible.org/pub/sword
  and ftp://ftp.eBible.org/swordbeta
  works just as well as ftp://ftp.eBible.org/pub/swordbeta.
  
  If you ever wonder if you are getting the
  latest version and suspect ISP-level caching
  of defeating my updates, you can try using https://eBible.org/sword/.
  The HTTPS protocol isn't currently a supported
  repository access method, but you could use a
  browser to grab a copy of what you are
  interested in, then install locally from that
  copy.
  -- 

  



  
  Your
  partner in electronic Bible
  publishing,
  


  


  

  MICHAEL
JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143
  USA
   eBible.org
  MLJohnson.org
  Mobile: +1 808-333-6921
  Skype: kahunapule

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to 

Re: [sword-devel] eBible.org repository minor tweak

[Kahunapule Michael Johnson]

  
  
These are the latest versions at ftp://ftp.ebible.org/sword:
  
  engKJV1769 (KJVD)
  Version=8.1
  History_8.1=Automatically generated on 2015-09-01 from source
  files dated 2015-08-31
  
  spaRV1909 (RV1909)
  Version=2.11
  History_2.11=Automatically generated on 2015-09-01 from source
  files dated 2015-08-10
  
  grcTisch (Tischendorf)
  Version=2.9
  History_2.9=Automatically generated on 2015-09-01 from source
  files dated 2014-01-11
  
  hbo (Masoretic)
  Version=2.9
  History_2.9=Automatically generated on 2015-09-01 from source
  files dated 2013-12-11
  
  hboWLC (WLC)
  Version=2.10
  History_2.10=Automatically generated on 2015-09-01 from source
  files dated 2014-04-08
  
  
  
  On 09/02/2015 04:30 AM, David Haslam wrote:


  Xiphos will only categorize under "Updates" if the Version has changed.

For a minor tweak where only the conf file is changed, the third part of the
Revision ought to be incremented.  Did you ensure this was done?

I just refreshed the repo in Xiphos, but I see no updates.

On the other hand, I may not have previously installed all these 5 modules.

David



David



--
View this message in context: http://sword-dev.350566.n4.nabble.com/eBible-org-repository-minor-tweak-tp4655171p4655180.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page




-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Semantic problem: real module names vs. Abbreviation=XYZ

[Kahunapule Michael Johnson]

  
  
OK. On my end with module generation,
  I'll not worry about abbreviation uniqueness if there are strong
  traditional abbreviations to use, but try to be unique most of the
  time in module generation. Any conflicts that slip through
  (especially across repositories) will be left to front ends and
  users to resolve.
  
  On 09/02/2015 03:24 AM, Peter von Kaehne wrote:


  Karl, can I summarise :

1) Abbreviations need to be bidirectional

2) Uniqueness needs to happen at user-level for bidirectionality to
work. Not above. 

3) Both across repos and internal to repos we can have one, some and
many modules which carry the same abbreviation - KJV being the most
notorious. It will be (see 2) up to the user to resolve this - but we
should make an effort to create sensible defaults. 

4) Apart from all that, we should try and eliminate genuine
duplications and ensure that we do not confuse users more than
necessary. E.g. to have many KJV (English language 1769 King James
Bibles) modules is not desirable. 

I think this is sensible and good.

Peter


On Wed, 2015-09-02 at 08:28 -0400, Karl Kleinpaste wrote:

  
On 09/01/2015 09:45 PM, Kahunapule Michael Johnson wrote:


  The uniqueness of an abbreviation is not required as long as you 
never try to look up which module corresponds to that abbreviation. 
If all you do is use the abbreviation as a short way to display 
which text is selected, i.e. just looking up the abbreviation given 
the module name, collisions are no big deal.


"If all you do is..."

That's entirely the problem: That is not all we (need to) do.  You 
are proceeding from false assumption.  As DM said, you're wrongly 
insistent on demanding uni-directional "output" use, as a mere 
eyeball convenience.  And that is simply not the case in the real 
world, and actually hasn't been so for a long time, if it ever was.  
Joe Average wants to type "KJV" in many contexts.  Module authors 
want to cross-ref into "KJV" in their content as a matter of routine.
  Network protocols want to ship "KJV" as a commonly-understood 
reference name.


  Module ID -> abbreviation is OK.
abbreviation -> Module ID is not OK.


But it must be made OK.

You said to me in private email that you "live in a wider world than 
Crosswire."  I suppose that's true along one axis of consideration.  
I live in a wider world than Crosswire along a different axis: I am a 
network head, and absolutely positively anything that threatens to 
share data from Hither to Yon (or from Alice to Bob) must be not 
merely handled, but expected all the time.  You cannot expect that 
Bob will tell Alice -- the nature of whose Bible app is unknown to 
Bob -- that her app should locate a module absurdly named 
"engKJV2006."  It is entirely unreasonable to believe that other 
software producers will name any module that way, and Alice's app may 
not be from Crosswire.  So common abbreviations are the way to 
achieve generality across software architectures, and they must be 
accepted as input that way.  If Bob likes engKJV2006 as his KJV 
implementation, great, and he should tell Alice that he's using (what 
he thinks of as) "KJV," but Alice wants the official version as 
supplied for her software.  They must interoperate.

A cardinal rule of the Internet since the ARPAnet days has been "be 
conservative in what you send, and liberal in what you accept."  
Conservatively, "KJV" is the correct way to identify the King James 
Version to anyone on the planet.  Liberally, "KJV" is a correct 
identification of a Bible to be provided by someone else, yet it is 
not unique in a (Crosswire or any other) world where KJV and 
(something like) engKJV2006 try to co-exist.


   language ID + abbreviation -> Module ID is OK.


No, it is not.  At very best, you could claim that you have reduced 
the breadth of conflict, but sometime next week someone else will 
produce a different "Thai KJV" module that they want to show up in 
our module selector lists, and so again conflict resolution is needed 
because yours is not necessarily special to Thai speakers any more 
than Crosswire's KJV is necessarily special to English speakers.  
This example conflict just happens to become localized to the subset 
of modules specific to Thai.  One cannot expect that there is always 
and forever exactly one module implementation of XYZ in any language 
group.


  Stop doing that, and always require a full module ID whenever you 
want to find a module. (Requires some software rewriting and 
distribution.)


Absolutely impossible, for all the reasons discussed above.  Users 
type Bible names, common names with which they've been familiar since 
childhood.

Re: [sword-devel] eBible.org repository minor tweak

[Kahunapule Michael Johnson]

  
  
Thank you, Martin. 
  
  1. Well, that is embarrassing. I'm glad you pointed that out.
  Rebuilding is in progress. That one affects a lot of modules.
  2. I filled in the missing descriptions in the Haiola metadata. It
  will be in the conf files with the next rebuild (again, in
  progress). I also coded a fallback, such that the long English
  description will be used if there is no short English title in my
  input data.
  3. The stray globals.conf has been disposed of.
  
  An incremental rebuild is in progress live on
  ftp://ftp.eBible.org/swordbeta, alphabetically by module name. If
  no obvious problems with swordbeta present themselves, I'll
  overwrite ftp://ftp.eBible.org/sword with that repository once it
  is done and I do a spot check to make sure it worked.
  
  On 09/02/2015 10:18 AM, Martin Denham wrote:


  
And Bible/JSword is reporting errors in some conf files:

1. In cta1981.conf and many others the extra trailing '*'
  obstructs line continuation:


   \* 
You must give Attribution to the work. \
 \* 
You do not sell this work for a profit. \
 \* 

2. Many modules have no description
  e.g. kdc2014

  Malformed conf file for apeB2013. No
Description found. Using internal of apeB2013
  
  Malformed conf file for msk1975. No
Description found. Using internal of msk1975
  Malformed conf file for kmk2003. No
Description found. Using internal of kmk2003
  Malformed conf file for vid2014. No
Description found. Using internal of vid2014
  
  Malformed conf file for mbs1982. No
Description found. Using internal of mbs1982
  Malformed conf file for jae1980. No
Description found. Using internal of jae1980
  Malformed conf file for xon2014. No
Description found. Using internal of xon2014
  
  Malformed conf file for kdc2014. No
Description found. Using internal of kdc2014
  
  

3. In mods.d.tar.gz there is a
  miscellaneous file called globals.conf which causes JSword to
  throw an error and prevents And Bible loading the eBible repo.

  Book not supported: malformed conf
file for globals no ModDrv found.
  Malformed conf file for globals. No
Description found. Using internal of globals
  
  

Cheers

Martin

  On 2 September 2015 at 20:13, David
Haslam <dfh...@googlemail.com>
wrote:
In
  fact, it was even worse than that.
  
  The installed module [spaRV1909] got corrupted due to the
  fact that the
  earlier module had not been first removed by Xiphos, as it
  would have done
  in the normal course of events.
  
  I have just manually removed the eBible module, and
  reinstalled the
  CrossWire module [SpaRV1909].
  So apart from file date stamps, I'm back to where I was an
  hour ago.
  
  Another possible source of confusion is that the CrossWire
  module is
  encrypted, yet comes with its own key.
  The eBible module [spaRV1909] is not encrypted.
  
  David
  
  
  
  
  
  --
  View this message in context: http://sword-dev.350566.n4.nabble.com/eBible-org-repository-minor-tweak-tp4655171p4655200.html
  
Sent from the SWORD Dev mailing list
  archive at Nabble.com.
  
  ___
  sword-devel mailing list: sword-devel@crosswire.org
  http://www.crosswire.org/mailman/listinfo/sword-devel
  Instructions to unsubscribe/change your settings at
  above page

  

  
  

  
  
  
  
  ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
   

Re: [sword-devel] eBible.org repository minor tweak

[Kahunapule Michael Johnson]

  
  
Lacking a compelling reason to do
  otherwise, I have removed spaRV1909 from the eBible.org sword
  repository.
  
  I haven't bothered encrypting any Sword modules, yet. I might do
  that for proprietary copyrighted Bibles in the future if that is
  what it takes to get permission to distribute them, but I really
  don't want to get involved in key management and sales.
  
  The irony that the guy who contributed encryption algorithm and
  code to the Sword project currently sees little point in using it
  has not escaped me.
  
  On another topic, one use of cryptography in Bible modules that
  would be worthwhile would be implementing digital signatures for
  assurance that a module hasn't been tampered with since it was
  released. Perhaps another day...
  
  On 09/02/2015 09:13 AM, David Haslam wrote:


  In fact, it was even worse than that.

The installed module [spaRV1909] got corrupted due to the fact that the
earlier module had not been first removed by Xiphos, as it would have done
in the normal course of events.

I have just manually removed the eBible module, and reinstalled the
CrossWire module [SpaRV1909].
So apart from file date stamps, I'm back to where I was an hour ago.

Another possible source of confusion is that the CrossWire module is
encrypted, yet comes with its own key.
The eBible module [spaRV1909] is not encrypted.

David





--
View this message in context: http://sword-dev.350566.n4.nabble.com/eBible-org-repository-minor-tweak-tp4655171p4655200.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page




-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Semantic problem: real module names vs. Abbreviation=XYZ

[Kahunapule Michael Johnson]

  
  
On 08/31/2015 10:26 PM, David Haslam
  wrote:


  Yesterday, I added a note in the wiki page:

http://www.crosswire.org/wiki/DevTools:conf_Files#cite_note-1

1. We strongly advise to avoid using an Abbreviation that's identical to the
ModName or Abbreviation of any other module. It only leads to confusion, and
may have unexpected consequences for some front-ends.

Peter thought that this might confuse some module developers, but I'm more
concerned about the unexpected consequences of the semantic problem at the
software.


Yes. This module developer is confused. I can give you unique
abbreviations or short abbreviations that match traditional usage.
Choose one. You can't have both.

-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] eBible.org beta repository updated

[Kahunapule Michael Johnson]

  
  
On 08/30/2015 10:26 PM, David Haslam
  wrote:


  We should document this better in the wiki page.

Currently there is just a brief note attached to OSISLemma.

Must precede OSISStrongs.

See http://www.crosswire.org/wiki/DevTools:conf_Files#cite_ref-2

What is the background to this requirement? 
Is it still valid?

David


I missed that rather bizarre restriction. I recommend that it be
relaxed. Nevertheless, I have updated Haiola to always put OSISLemma
before OSISStrongs in the config files.

-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Semantic problem: real module names vs. Abbreviation=XYZ

[Kahunapule Michael Johnson]

  
  
The uniqueness of an abbreviation is
  not required as long as you never try to look up which module
  corresponds to that abbreviation. If all you do is use the
  abbreviation as a short way to display which text is selected,
  i.e. just looking up the abbreviation given the module name,
  collisions are no big deal. If you look at both the language code
  and the abbreviation when doing lookups, collisions are avoided.
  
  Module ID -> abbreviation is OK.
  abbreviation -> Module ID is not OK.
  language ID + abbreviation -> Module ID is OK.
  
  But the "not OK" case is in active use, now. Sigh.
  
  Possible solutions:
  
Stop doing that, and always require a full module ID
  whenever you want to find a module. (Requires some software
  rewriting and distribution.)

Require that all module abbreviations are globally unique
  across well over 1,000 translations. (This precludes using
  locally meaningful and traditional abbreviations in many
  cases, and results in longer abbreviations.)
Let the user assign abbreviations and disallow assignment of
  a duplicate. (You could suggest a default.)

  
  Personally, I don't like the idea of burdening the user with
  managing unique abbreviations, unless you have working defaults so
  that this level of customization is not required.
  
  As an aside, finding and picking the Bible(s) you want to read has
  gotten a bit more challenging. One long pulldown list isn't a
  great idea, now. It helps to have a way to search with some sort
  of hierarchy, like Country->Language->Translation and/or
  have a filter box to apply. This is something we do in inScript.
  (See http://eBible.org/study/ or http://inScript.org -- the latter
  has more Bibles on it.) That is a front end issue I'm not going to
  touch, right now, other than to point out the elephant in the UI
  room and go back to making it even more challenging by adding more
  Bibles.  ;-) 
  
  On 09/01/2015 12:42 PM, Peter von Kaehne wrote:


  On Tue, 2015-09-01 at 18:19 -0400, Karl Kleinpaste wrote:

  
On 09/01/2015 09:29 AM, DM Smith wrote:


  Having Abbreviation=KJV for a Thai module is clearly not the 
intent. To use it within a repo with uniqueness by language is 
entirely a bad idea.


I'm glad I didn't misunderstand this aspect.

  
  
Michael explains that "KJV" is what is - at least in missionary circles
- used for the ThaiKJV. So, yes, this is the intent for Abbreviation as
a user friendly option.

Certainly I can see that within the Latin script area there may well be
clashes for some modules - and we should simply not ever assume that
the Abbreviation entry will always be unique across all repos and all
modules in existence. 

It _must_ be unique for a user - and either the computer or the user
must be able to resolve clashes.

But we should neither assume uniqueness nor rely upon that until a
frontend has given for a particular moment the "all clear".  

Peter

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


    

    -- 
      
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] eBible.org repository minor tweak

[Kahunapule Michael Johnson]

Title: signature

  
  
The main repository has been updated with revised modules with
Strong's numbers (5 of them). The update is about markup and conf
files, with no change to source text.

Also, I used symbolic links to allow the /pub in the directory to be
omitted. In other words, ftp://ftp.eBible.org/sword works just as
well as ftp://ftp.eBible.org/pub/sword and
ftp://ftp.eBible.org/swordbeta works just as well as
ftp://ftp.eBible.org/pub/swordbeta.

If you ever wonder if you are getting the latest version and suspect
ISP-level caching of defeating my updates, you can try using
https://eBible.org/sword/. The HTTPS protocol isn't currently a
supported repository access method, but you could use a browser to
grab a copy of what you are interested in, then install locally from
that copy.
-- 
  
  
  

  
  
  

Your partner in
electronic Bible publishing,

  
  

  
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Semantic problem: real module names vs. Abbreviation=XYZ

[Kahunapule Michael Johnson]

  
  
On 09/01/2015 12:19 PM, Karl Kleinpaste
  wrote:

I am in the middle of adding code to Xiphos
that [a] ignores Abbreviation when it collides with an existing
real module name, and [b] provides for the user to change
Abbreviation at any time, which value is also retained across an
update (like CipherKey is retained), so the user can de-collide
as he wishes.

Good job. :-)

-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] eBible.org beta repository updated

[Kahunapule Michael Johnson]

  
  
Thank you. I'll trigger the OSISLemma
  filter on the morphology tags.
  
  On 08/28/2015 05:40 PM, DM Smith wrote:


  
  Only use it if that attr has something other than Strong's
numbers. 

Cent from my fone so theer mite be tipos. ;)
  
On Aug 28, 2015, at 10:33 PM, Kahunapule Michael Johnson kahunap...@ebible.org
wrote:

  
  

  
  On 08/28/2015 03:12 PM, Karl
Kleinpaste wrote:
  
  

I just keep running into oddities as
  I look these over the first time, having only dealt
  previously with the repo's ability to serve them properly.
  
  Why does your KJV conf contain
  "GlobalOptionFilter=OSISLemma" when there appears to be no
  lemma content?
  
  
  That option is triggered by the presence of at least one w tag
  with a lemma attribute in the OSIS source.
  
  -- 

Aloha,
    Kahunapule Michael Johnson

  

  MICHAEL JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143
  USA
   eBible.org
  MLJohnson.org
  Mobile: +1 808-333-6921
  Skype: kahunapule

  

  

  
  
___
  sword-devel mailing list: sword-devel@crosswire.org
  http://www.crosswire.org/mailman/listinfo/sword-devel
  Instructions to unsubscribe/change your settings at
above page
  
  
  
  
  ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] eBible.org beta repository updated

[Kahunapule Michael Johnson]

  
  
Here is an OSIS file: https://ebible.org/Scriptures/eng-kjv_osis.zip
  In fact, here are a multitude of OSIS files: https://ebible.org/Scriptures/.
  
  On 08/30/2015 05:41 PM, DM Smith wrote:


  
  That input should be OK. I’ll have to dig to see why. I may need
  an OSIS.xml file to do the analysis. Could you put it somewhere I
  can download it?
  
  
  It may take a few days for me to get to it. I’m
prioritizing the release of Bible Desktop and am in the process
of testing the installers.


Thanks,
	DM

  

  On Aug 30, 2015, at 11:11 PM, Kahunapule
Michael Johnson kahunap...@ebible.org
wrote:
  
  


  On 08/29/2015 10:31 AM,
Karl Kleinpaste wrote:
  
  

On 08/28/2015 10:30 PM,
  Kahunapule Michael Johnson wrote:

Should I try to make the
  paragraph-beginning verse number placement less
  odd?
When making modules,
  my perspective has always been that the preceding
  verse specifies the paragraph ending,
  so that the vertical whitespace is generated
  there.
  
  
  Right now, it seems like the funky beginning verse
  number placement is caused by something like:
  
  w lemma="strong:H4325"of the waters/w.
  verse eID="Gen.1.2.seID.3"
  //pp
  verse osisID="Gen.1.3" sID="Gen.1.3.seID.4"
  n="3" /
  w lemma="strong:H430"And God/w
  
  Note that the paragraph end and start are together,
  and before the the verse number. The vertical white
  space should come before the verse number, and the
  verse number should be at the beginning of the text
  for the verse.
  
  Since it doesn't work that way, I'm going to shrug and
  call it a peculiarity of osis2mod, the Sword library,
  or the front ends. It looks funny, but I'm disinclined
  to take perfectly good semantic markup and tweak it to
  make the presentation look more normal, unless someone
  has a reasonable suggestion that is easy to implement
  and doesn't assume that paragraphs always start
  between verses (because they don't). Honestly, I would
  think that such tweaks properly belong in osis2mod or
  the Sword library, not the source OSIS, if they are
  necessary.
  
  
  -- 

            Aloha,
Kahunapule Michael Johnson

  

  MICHAEL
JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143
  USA
   eBible.org
  MLJohnson.org
  Mobile: +1 808-333-6921
  Skype: kahunapule

  

  

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at
above page

  
  

  
  
  
  
  ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
    

    
-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mai

Re: [sword-devel] eBible.org beta repository updated

[Kahunapule Michael Johnson]

  
  
You are right, DM. I did understand.
  Thanks for the clarification! 
  :-) 
  
  On 08/30/2015 05:37 PM, DM Smith wrote:


  
  I think you misunderstand. If the lemma attribute has other kinds
  of lemma then use the GlobalOptionFilter=OSISLemma. It is not
  dependent on the morph attribute.
  Here is an example from our KJV where OSISLemma is
appropriate (new lines added for ease of reading):
  
verse osisID="Matt.1.1" sID="Matt.1.1”/
w src="" lemma="strong:G976 lemma.TR:βιβλος"
  morph="robinson:N-NSF"The book/w 
w src="" lemma="strong:G1078 lemma.TR:γενεσεως"
  morph="robinson:N-GSF"of the generation/w 
w src="" lemma="strong:G2424 lemma.TR:ιησου"
  morph="robinson:N-GSM"of Jesus/w 
w src="" lemma="strong:G5547 lemma.TR:χριστου"
  morph="robinson:N-GSM"Christ/w, 
w src="" lemma="strong:G5207 lemma.TR:υιου"
  morph="robinson:N-GSM"the son/w 
w src="" lemma="strong:G1138 lemma.TR:δαβιδ"
  morph="robinson:N-PRI"of David/w, 
w src="" lemma="strong:G5207 lemma.TR:υιου"
  morph="robinson:N-GSM"the son/w 
w src="" lemma="strong:G11 lemma.TR:αβρααμ"
  morph="robinson:N-PRI"of Abraham/w.
verse eID="Matt.1.1”/


I’ve highlighted what is an appropriate trigger
  for putting OSISLemma in the conf. Note, there is a value in
  the lemma attribute that doesn’t start with strong:


Basically what the GlobalOptionFilter=OSISLemma
  does is instruct the SWORD engine to enable a filter to
  show/hide the lemma independently from the Strong’s number
  show/hide filter.


Hope this helps.


In Him,
	DM



  
On Aug 30, 2015, at 11:02 PM, Kahunapule
  Michael Johnson kahunap...@ebible.org
  wrote:


  
  
Thank you. I'll trigger the
  OSISLemma filter on the morphology tags.
  
  On 08/28/2015 05:40 PM, DM Smith wrote:


  
      Only use it if that attr has something
other than Strong's numbers. 

Cent from my fone so theer mite be tipos. ;)
  
On Aug 28, 2015, at 10:33 PM, Kahunapule Michael
Johnson kahunap...@ebible.org

wrote:

  
  

  
  On 08/28/2015 03:12
PM, Karl Kleinpaste wrote:
  
  

I just keep
  running into oddities as I look these over the
  first time, having only dealt previously with
  the repo's ability to serve them properly.
  
  Why does your KJV conf contain
  "GlobalOptionFilter=OSISLemma" when there
  appears to be no lemma content?
  
  
  That option is triggered by the presence of at
  least one w tag with a lemma attribute in the OSIS
  source.
  
  -- 

Aloha,
Kahunapule Michael Johnson

  

  MICHAEL
JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143
  USA
   eBible.org
  MLJohnson.org
  Mobile: +1 808-333-6921
  Skype: kahunapule

  

  

  
  
___
  sword-devel mailing list: sword-devel@crosswire.org
  http://www.crosswire.org/mailman/listinfo/sword-devel
  Instructions to

Re: [sword-devel] eBible.org beta repository updated

[Kahunapule Michael Johnson]

  
  
On 08/29/2015 10:42 AM, Karl Kleinpaste
  wrote:


  
  On 08/28/2015 10:18 PM, Kahunapule
Michael Johnson wrote:
  
  
 At least as importantly,
how would Joe Average distinguish them?
  

Good question. That kind of depends on
  how much information is presented to Joe Average.
  My point in asking is that their mere
presence duplicates these modules, creating what amounts to
uncertainty and competition where none should exist.  Is not
Crosswire itself the source of these modules?

That you have named one of them peculiarly (Crosswire's KJVA
is essentially eBible's KJVD) adds to the
confusion.


I'm going to dispose of the following modules on the eBible.org
repository in hopes of reducing confusion without really taking
anything of value away from the public:
engRVX2012 - doesn't really add anything beyond what engRV1895 and
engWEB2015 provide. I'd rather remove it than explain it.
engUKWEB2015 - proper subset of engWEBBE2015 (omits
Deuterocanon/Apocrypha)
engWEBc2015 - proper subset of engWEB2015 (omits books not in the
Roman Catholic Bible)
engKJV2006 - redundant with the KJV in the main repository; subset
of engKJV1769

For the subset books, I would rather see filter options on searching
and displaying texts than make multiple modules from the same
source. I want to make these modules and this software useful for
Christians from a variety of church traditions while trying to stay
somewhat neutral on how to treat the books beyond the 66-book canon.
Attitudes towards those books are wildly diverse, so I don't know
how viable that strategy is. I may be convinced to backtrack on
that, later, but for now, this seems too hard to deal with in a
short module name, and not really worth the effort.

Regarding the naming of the KJV with Apocrypha: I try to make my
abbreviations mesh not only with Crosswire, but even more
importantly, with the American Bible Society's abbreviations. For
them, KJVA is the Americanized King James Version. Sigh.

For now, I'm leaving engKJV1769 in the eBible.org repository until
such time as DM and I come up with a better idea together. I've been
distributing the KJV from eBible.org, and before that from a
computer bulletin board, dating back to before the Sword Project
began. I have done some reconciliation with DM's copy on Sword from
time to time.  I'm using the KJV as a markup test, as well as an
additional output format for the KJV. Also, there are some
variations in the Apocrypha between the two copies, plus some typo
reports pending to implement. I'll start sharing those with DM as I
get them. If David's analysis of the text differences in the 66
books of the KJV canon is correct, there are only a handful of
variations where my printed copy and DM's differ, so we could just
overwrite mine with DM's latest KJV, give or take markup issues. I'm
sure we can figure out a way to collaborate effectively, but it may
take a bit of time to figure it out, and for me to write some
software to import a specific subset of OSIS. (I have resisted
making a general OSIS importer, because that is very difficult, and
nobody has ever done it to my knowledge, but it shouldn't be hard to
ingest just that tiny part of what OSIS allows that the KJV master
copy is in.)


-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] eBible.org beta repository updated

[Kahunapule Michael Johnson]

  
  
On 08/28/2015 03:12 PM, Karl Kleinpaste
  wrote:


  
  I just keep running into oddities as I look
these over the first time, having only dealt previously with the
repo's ability to serve them properly.

Why does your KJV conf contain "GlobalOptionFilter=OSISLemma"
when there appears to be no lemma content?


That option is triggered by the presence of at least one w tag with
a lemma attribute in the OSIS source.

-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] eBible.org beta repository updated

[Kahunapule Michael Johnson]

  
  
On 08/28/2015 02:49 PM, Karl Kleinpaste
  wrote:


  
  As well, why do you have both WEBUK and
WEBBE, both of whose descriptions say "World English Bible
British Edition," and again, how would Joe Average make an
intelligent choice between them?


You can't really tell from the abbreviation.
  You need to look at the fuller title. WEBBE includes the
  Deuterocanon/Apocrypha. WEBUK doesn't.
-- 

  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] eBible.org beta repository updated

[Kahunapule Michael Johnson]

  
  
On 08/28/2015 02:21 PM, Karl Kleinpaste
  wrote:


  
  On 08/28/2015 04:40 PM, Kahunapule
Michael Johnson wrote:
  
  The
engKJV1769, engKJV2006, and spaRV1909 look a lot better, now
  How are your KJV modules distinguished from
those in Crosswire main repo?
  

engKJV1769 (KJVD) includes the Apocrypha/Deuterocanon.
engKJV2006 (KJV) is essentially the same as the the KJV in the main
repo, and is identical to the canonical 66 books of engKJV1769.

 At least as importantly, how would Joe Average
distinguish them?
  

Good question. That kind of depends on how
  much information is presented to Joe Average.

-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] eBible.org beta repository updated

[Kahunapule Michael Johnson]

  
  
On 08/28/2015 03:04 PM, Karl Kleinpaste
  wrote:


  
  Are you aware of the odd placement of
paragraph-beginning verse#s in your modules?

Yes. I think it is an unintended result of my efforts to make verses
and paragraphs nest when practical. That is actually silly, because
those items just don't necessarily nest, but I think I was told at
some point that I should try to make them nest when possible. Maybe
my memory is faulty or the person telling me that was mistaken.
Certainly the OSIS standard puts no such constraint on verses and
paragraphs. That is why we milestone one or the other or both.

What do you all think? Should I try to make the paragraph-beginning
verse number placement less odd?


-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] eBible.org beta repository updating

[Kahunapule Michael Johnson]

  
  
On 08/28/2015 04:08 AM, David Haslam
  wrote:


  Michael,

Thanks for the announcement (and your private emails to me).

Leaving only until tomorrow for more beta testing (even on my own reported
module issues) is rather tight!


Yes, it is rather tight, but I'll be testing too. It isn't like we
can't fix problems you find a day or three later. Quality control
improvement is a continuous process.
My threshold for transferring from eBible.org/swordbeta to eBible.org/sword is just that
it is an improvement, not that it is perfect. A perfect Sword
repository doesn't yet exist, but we can keep improving.

-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] eBible.org beta repository updated

[Kahunapule Michael Johnson]

  
  
Aloha, Peter.
  
  Actually, during a rebuild, neither my main site or the beta site
  are "out", if all goes well. If all doesn't go so well, the beta
  site might go down, but not the main site. Even a full rebuild is
  done one module at a time, with all of the pieces of each module
  done consistently, so that at any time, you can pull one or more
  modules from either repository. The only reason my whole
  repository went down for a rebuild in the past was that (1) there
  was a major defect in the rebuild process AND (2) I didn't notice
  it and halt the process timely (due to such distractions as being
  at a conference and otherwise busy most of the time).
  
  The main purpose of the eBible.org swordbeta repository is to run
  the full process, as it currently exists, on a repository I can
  access from mobile devices, and try it out "live" before shunting
  those changes over to the eBible.org sword repository.
  
  The full rebuild paradigm has many advantages, including
  consistency of output quality for all modules and speed. The
  quality issue is important. Frankly, I don't expect much feedback
  on most of the minority language Bibles, even if there is a
  problem with it. But if the KJV or WEB have a problem, I expect to
  hear about it. (And I do, regularly-- and fix such problems when
  they are verified.) When it is the same process and the same input
  format, I can expect quality improvements in the process to
  benefit not just the English translations, but all of them.
  
  There are two classes of "fix": those affecting the process, which
  involve a total rebuild of the repository to correct, and those
  affecting the source files of a particular Bible translation.
  Those will be handled with a partial rebuild. These are usually an
  update of a translation work in progress, correcting a typo, or
  some similar thing, with no changes to the process.
  
  There is a third thing that can trigger a repository rebuild, and
  that is regression testing of the Haiola software. In this case,
  the eBible.org/sword repository would not be updated, but the
  eBible.org/swordbeta repository would be updated. Normally, there
  should be no difference between modules in the swordbeta and sword
  repository in that case, except maybe the module version number,
  which currently autoincrements for each build.
  
  So, Peter, I understand your concern. I think we have it covered.
  There were definitely some growing/labor pains in getting the
  eBible.org repository up and running, but I think it is OK, now.
  At least it is working for me. The eBible.org/sword repository
  should be available at least 99% of the time. Because of the size
  of the repository and the frequency of updates, it is a good idea
  to refresh the list of available modules before downloading or
  updating any modules.
  
  The full rebuild with all of the corrections I know to do has now
  been done. The repository pair is at rest and synchronized. The
  engKJV1769, engKJV2006, and spaRV1909 look a lot better, now, as
  do the Greek and Hebrew modules. The "about" pages look much
  better, too. And, some rare but troublesome missing spaces in the
  rest of the modules have been restored. Haiola is at rest, at
  least until I do some regression testing and testing of new PDF
  conversion code, or until I enter some language updates to the WEB
  and some typo corrections to the KJV Apocrypha/Deuterocanon.
  
  On 08/28/2015 09:34 AM, Peter von Kaehne wrote:


  Michael,

What bugs me in this process is emphatically not the need for ongoing fixes. That is entirely expected. But i am concerned that each fix results in a total rebuild, which takes your site out for some 24 hrs or so. 

I would think partial rebuilds should become the norm, no?

Peter

Sent from my phone. Apologies for brevity and typos.On 28 Aug 2015 6:37 pm, Kahunapule Michael Johnson kahunap...@ebible.org wrote:

  

On 08/28/2015 04:08 AM, David Haslam wrote:


  
Michael,



Thanks for the announcement (and your private emails to me).



Leaving only until tomorrow for more beta testing (even on my own reported

module issues) is rather tight!




Yes, it is rather tight, but I'll be testing too. It isn't like we can't fix problems you find a day or three later. Quality control improvement is a continuous process.
My threshold for transferring from eBible.org/swordbeta to eBible.org/sword is just that it is an improvement, not that it is perfect. A perfect Sword repository doesn't yet exist, but we can keep improving.

-- 

Aloha,
Kahunapule Michael Johnson

MICHAEL JOHNSON
PO BOX 881143
PUKALANI HI

[sword-devel] eBible.org beta repository updating

[Kahunapule Michael Johnson]

Title: signature

  
  
The eBible.org beta repository (ftp://ftp.ebible.org/pub/swordbeta
or http://eBible.org/swordbeta) is being updated with a full rebuild
to make the following improvements:

  Switched from "gloss" to "lemma" attributes for Strong's
numbers.
  Inhibited generation of blank Strong's number markup.
  Corrected two white space loss errors: one affecting white
space between markup (a big problem with texts tagged with
Strong's numbers), and another affecting loss of white space at
line breaks in "about" boxes.
  Added configuration file options for appropriate to texts with
Strong's numbers and Hebrew texts.
  Restored swh1850 to its place. (It was pulled temporarily
while investigating a potential misidentification issue.)

So far, the eBible.org beta repository looks better than the main
  eBible.org repository. If nobody (including me) finds a good
  reason not to, the contents of the eBible.org beta repository will
  be copied to the eBible.org main repository
  (ftp://ftp.ebible.org/pub/sword or http://eBible.org/sword)
  tomorrow, after the rebuild is done (which should be at about 1900
  UTC, at the earliest).

I think I'm done breaking the main eBible.org/sword repository.
  It should only be improvements and additions from here on out.
  I'll try to confine all of my repository breaking activity to the
  eBible.org beta repository. 
  ;-) 

-- 
  
  
  

  
  
  

Your partner in
electronic Bible publishing,

  
  

  
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[Kahunapule Michael Johnson]

  
  
If I use the new versifications to
  create Bibles, using the updated Sword library and osis2mod that
  includes these versifications, will those modules work properly
  with existing older Sword applications using older versions of the
  Sword library? Or should I wait for all field applications to be
  updated (which probably won't actually happen)?
  
  On 08/26/2015 09:50 AM, domcox wrote:


  
As I mailed on Sunday, 23rd, I created 3 new versification schemes for French Bibles in Sword:
* Calvin for the original Bible d'Olivétan and followers, 1560+ Bible de Genève, 1707-1855 Bible David Martin, 1744-1996 Bible Jean-Frederic Ostervald and so on
* DarbyFR for the French J.N. Darby Bible and revisions
* Segond for the Louis Segond Bible and modern revisions, 1910, 1978, 2002 (NBS), 2007 (SG21)
For more details, see: 
http://www.crosswire.org/wiki/Survey_of_versification_schemes_in_French_Bibles 

Attached are the corresponding files canon_calvin.h, canon_darbyfr.h, canon_segond.h, as well as a patch to apply to src/mgr/versificatiomgr.cpp.
These files can also be downloaded from my website: 
http://dom.corbex.org

Packages of Sword and Xiphos for Debian stable (Jessie 8),arch=amd64, based on Sword-1.7.5a1 and including these 3 new versification schemes can be downloaded from the same location:
http://dom.corbex.org/pkg. 
Please note that you'll have to remove your existing libsword before installing these packages.

Verifications:

For verification and functional tests, I used or made 3 Bibles in OSIS format. A Darby Bible made with the tools developped by Sebastien Koechlin from http://koocotte.org/darby, a D. Martin Bible from http://www.martin1707.com and a L. Segond Bible from http://www.richardlemay.com/AUD/BIB/LSG/Index.htm. 
Scripts for downloading and importing those Bibles are available at my website: 
http://dom.corbex.org/scripts
as well as modules ready to use : 
http://dom.corbex.org/sword 

osis2mod was used to convert each Bible into a Sword module, then emptyvss was run to detect empty verses. Verses causing problems with the previous versification schemes were checked with either Diatheke or Xiphos.

#1. Martin 1707 (canon Calvin):
osis2mod reports Acts.19.41 as a supplemental verse. That's correct, Acts.19.40 is split in 2 verses in the source file, although it is not in the printed Bible. Emptyvss does not detect any empty verses.

#2. Darby 1975 (canon DarbyFR)
osis2mod run without errors. Emptyvss reports 3 empty verses. That's correct, those 3 verses are also empty in the printed Bible, a footnote informs that they are only present in the Textus Receptus.

#3. Segond 1910 (canon Segond)
osis2mod reports Mark.10.53 as a supplemental verse. Depending of the revision of the Segond 1910, Mark.10.52 is divided in 2 verses or not, it is here. Emptyvss reports 4 empty verses from 2Tim.3.14 to 2.Tim.3.17, certainly a glitch in the digitization process, the 4 verses, although present in the printed Bible, are not in the source file.

--Dominique
 
domcox dominique.cor...@gmail.com

  
  
  
  ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] 1.8 release planning

[Kahunapule Michael Johnson]

Title: signature

  
  
On 08/22/2015 11:37 PM, Peter von
  Kaehne wrote:


  While Greg plans the next point release, can we also start thinking about the 1.8 release? 

Domcox's French versifications would break the ABI, so they require a new release, as do my LaTeX filters. Former need testing, latter need polish.

There are a bunch of patches Kalemas has put onto JIRA, but they could once tested and accepted go into a point release.

Anything else big in the wings? 


Yes. NRSVA versification in the current Sword library is broken. It
does not support having both Esther (the normal canonical version
from the traditional Hebrew text) and Esther from the Greek (the
deuterocanonical version translated from the Greek Septuagint). The
real NRSVA does. See the paper Bible ISBN 978-0-06-123119-3 or any
of the NRSV with Apocrypha/Deuterocanon ecumenical editions.

The World English Bible has the same set of books as the NRSVA, but
if you grab a copy of the current engWEB2015 from the eBible.org
repository, then try to navigate to Esther (Greek) in PocketSword,
you get to Revelation. Granted, Revelation is a really good book and
part of the full canon of Scripture, and that Esther (Greek) is
mostly redundant with the canonical Esther, but the extra bits are
apparently important to some church traditions. (I even find them
interesting as a Bible scholar from a church background that mostly
ignores the deuterocanon.) It would be better to not offer the
choice of going to an unsupported book than to redirect to another
one, but better still to just support the book.

Note: even with the Esther (Greek) - Revelation glitch, the
engWEB2015 module in the eBible.org repository is much better than
the WEB module in the Crosswire main repository, because it has the
rest of the books, and it has the latest typo corrections and
language updates, even those done yesterday. (There aren't a lot of
problems left to find, but someone found an "east" that should have
been "west" recently, because the ASV didn't match the Greek at that
point.)

I propose:
1. Create a new versification for Sword that is a true superset of
known Bible versifications, at least having all of the books defined
as Bible books in the OSIS and SIL+UBS Paratext book sets. This
might be the union of LXX with NRSVA, repaired to include Esther
(Greek), for starters.
2. Handle subsets gracefully. We need to, anyway, to support
Scripture portions (i.e. maybe one or two Books of the Bible from a
translation in progress).

Either that, or support per-module versification specifications
based on what is actually in the module, be it just the Gospel of
John, a New Testament, a 66-book full Bible, or a full Bible with
any or all of the deuterocanon/apocrypha books, no matter how many
chapters are in Malachi or how many verses are in John's Second
Letter.

Another issue in the wings is support for mid-verse section titles.
OSIS supports it, but Sword currently does not. For now, I have
worked around this issue by simply disabling all section titles in
the OSIS I feed osis2mod. This is not an optimal solution, but very
effective in evading the issue.

An issue that may require Sword library modification and probably
front end handling changes is how to handle modules with Strong's
numbers. Currently, the engKJV1769, engKJV2006, and spaRV1909
modules are affected, but more will be affected, later, as Strong's
numbers are added. Any suggestions as to how I can make the OSIS
source files I feed osis2mod better are welcome. (It is just a
matter of how to convert from USFX, so I don't actually have to
change the source to change the OSIS.) In general, osis2mod
complains regularly about well-formed OSIS not being well-formed.
This is not surprising to me given the nature of the OSIS standard,
but since my only use for OSIS is creating Sword modules, it isn't
out of the question to reinterpret the OSIS standard or alter it for
our purposes, as long as we do it in the same way. (KJV and Spanish
Reina Valera 1909 modules are redundant with the main repository,
but they are pilot tests in handling Strong's numbers.)

By the way, the eBible.org repository rebuild is still in progress,
working alphabetically by language code, and currently at swp. So
far, it is looking pretty good except for the missing book issue and
rendering of Strong's numbers. There also seems to be a problem with
footnote display in Xiphos, but it works fine in PocketSword. And,
of course, we are still missing PocketSword prebuilt indexes, so I
can't do searches in PocketSword.

I would test with AndBible, but I don't know how to add a custom
repository to it. Is there a way 

Re: [sword-devel] Versification discovery? [Was: Re: French versifications, was Re: FreJND and HebDelitzsch released]

[Kahunapule Michael Johnson]

Title: signature

  
  
On 08/23/2015 08:27 AM, Matěj Cepl
  wrote:


  On 2015-08-23, 09:29 GMT, Peter von Kaehne wrote:

  
Interesting and quite probably useful would be to know if any 
'colonial' translations would benefit from any of these three 
v11ns. I do think Malagassy was difficult to fit, also 
Kahunapule might have translations from French Polynesian 
background. 
  


Yes, I have a variety of difficult-to-fit translations. Mostly this
has convinced me that hard-coded versification is bad. This
is especially true when you consider intentionally omitted verses
for textual criticism reasons, which set tends to vary based on who
is analyzing the text and making the translational decisions.



  
There were some talks about script which would take a given OSIS 
XML (or something else) and tries to match the text against all 
available versifications looking for the best match. Does such 
animal exist at all? Is it possible?


Yes, this algorithm exists as part of Haiola
(next release). It picks the least bad versification of those
available (i.e. hard coded into the version of the Sword Library
that I'm using). Badness is minimized as follows:
1. Select the versification(s) with the minimum number of verses in
books not in the versification. (This narrows things down when
deuterocanon/apocrypha books are present.)
2. Of those selected in step 1, select the versification(s) with the
minimum number of verses in chapters not in the versification. (Some
versifications lack Malachi 4, for example.)
3. Of those selected in step 2, select the versification(s) with the
minimum number of verses that extend beyond the expected number of
verses in their chapter.
4. Of those selected in step 3, select a versification with the
minimum number of verses defined in the versification but not
present in the current text.

The actual implementation is more efficient than the above would
seem to indicate, as it does it with one pass through the Bible,
counting the misfits in each category, then one pass at the end
finding the least bad fit.

The real issue, here, is how well Sword handles each category of
badness. It turns out that badness levels 1 and 2 are pretty bad.
Badness level 3 just results in some verses being combined with the
previous verse-- maybe several verses combined. Badness level 4
isn't really that bad, and is, in fact, pretty much unavoidable
unless you go with per-module versification, because we have lots of
partial translations, like sometimes just one or two books of the
Bible. The only reason I retain that test is to select KJV instead
of KJVA, SynodalP instead of Synodal, and NRSV instead of NRSVA for
Bibles with just the regular canon of 66 books or a subset of that.

I'm also aware of some other scripts that try to find the best fit,
but they aren't as general or reliable as the above algorithm.
-- 
  
  
  

  
  
  

Your partner in
electronic Bible publishing,

  
  

  
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] eBible.org repository regeneration complete

[Kahunapule Michael Johnson]

Title: signature

  
  
I think the eBible.org repository is basically OK, now.
Known issues:

  Waiting on PocketSword index generation
  NRSVA versification lacks EsthGr = ESG = Esther (Greek)
support that the real NRSVA has, and sends people looking for
that book to Revelation in engWEB2015 and engWEBBE2015.
  
  Strong's numbers rendering and spacing is off in the
spaRV1909, engKJV1769, and engKJV2006 modules. 

eBible.org repository: ftp://ftp.ebible.org/pub/sword OR
  http://eBible.org/sword/

eBible.org beta repository: ftp://ftp.ebible.org/pub/swordbeta OR
  http://eBible.org/swordbeta/

The beta repository is for any testing where there is a risk of
  breaking the production repository. At this instant, both are
  identical.

-- 
  
  
  

  
  
  

Your partner in
electronic Bible publishing,

  
  

  
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Yet another iteration of the eBible.org repository is in progress.

[Kahunapule Michael Johnson]

  
  
On 08/20/2015 06:04 PM, DM Smith wrote:


  
  
  

  On Aug 20, 2015, at 11:37 PM, Kahunapule Michael
Johnson kahunap...@ebible.org
wrote:
  
  The fresh osis2mod
  build 3314 that I'm using produces modules that seem to be
  missing all text when viewed on PocketSword or Xiphos. I'm
  a little stumped…


  
  Wild guess: Take a look at file and directory permissions.
Look at size of the data and index files.


I think things are working, now. The eBible.org repository should be
rebuilt in a working fashion within 24 hours if all goes well,
except for one detail that is still a mystery to me:

Where is PocketSword looking for downloadable pre-built indexes? How
can I create those? Or is there an automatic process somewhere that
will build all of these as needed and catch up with the pace of
updates of the eBible.org repository?

-- 

  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Yet another iteration of the eBible.org repository is in progress.

[Kahunapule Michael Johnson]

  
  
Thank you, Nic. That information helps.
  At least I don't have an essential missing piece in the new
  eBible.org repository.
  A nightly cron job is a good idea. Yes, the indexes from 2 days
  ago are all out of date. Due to the size of the repository, you
  might want to check each module version number in its .conf file
  and only regenerate the index when the module is newer than your
  index, or the index hasn't been made, yet, to minimize server
  load. It will be updated regularly, so a nightly cron job would be
  a great idea.
  
  Alternatively, I could generate indexes locally and upload them.
  Let me know if you think that would be helpful. (I would need a
  working script for my Linux box to do that.)
  
  On 08/22/2015 03:00 PM, Nic Carter wrote:


  
  I need to get this running nightly (can I do cron stuff
myself? It's been about a decade since I played with this kind
of funky stuff).
  I did an initial run of creating the indices a day or 2 ago,
but they will now be out of date, I'm guessing?
  The zipped index files are located on the crosswire web
server, in a location I maintain under the ~pocketsword
folder...
  
  
  If I was still actively maintaining PocketSword, I'd look at
doing index-less searches on iOS devices now, given how powerful
handhelds have become ( given how optimised Troy has made
non-indexed searches!).
  
  
  I hope that helps?
  ybic,
  Nic :)
  
On 23 Aug 2015, at 10:09, Kahunapule Michael Johnson kahunap...@ebible.org
wrote:

  
  

  
  On 08/20/2015 06:04 PM, DM Smith
wrote:
  
  



  
On Aug 20, 2015, at 11:37 PM, Kahunapule
  Michael Johnson kahunap...@ebible.org

  wrote:

The fresh
osis2mod build 3314 that I'm using produces modules
that seem to be missing all text when viewed on
PocketSword or Xiphos. I'm a little stumped…
  
  

Wild guess: Take a look at file and directory
  permissions. Look at size of the data and index files.
  
  
  I think things are working, now. The eBible.org
  repository should be rebuilt in a working fashion within 24
  hours if all goes well, except for one detail that is still a
  mystery to me:
  
  Where is PocketSword looking for downloadable pre-built
  indexes? How can I create those? Or is there an automatic
  process somewhere that will build all of these as needed and
  catch up with the pace of updates of the eBible.org
  repository?
  
  -- 
  

Aloha,
Kahunapule Michael Johnson

  

  MICHAEL JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143
  USA
   eBible.org
  MLJohnson.org
  Mobile: +1 808-333-6921
  Skype: kahunapule

  

  

  
  
___
  sword-devel mailing list: sword-devel@crosswire.org
  http://www.crosswire.org/mailman/listinfo/sword-devel
  Instructions to unsubscribe/change your settings at
above page

  
  
  
  
  ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] 1.7.5a1

[Kahunapule Michael Johnson]

Title: signature

  
  
Thank you. I got the proposed package
  to compile, and osis2mod seems to be behaving itself properly,
  now.
  I did have to modify my OSIS generator to use q containers
  instead of milestones, though, otherwise osis2mod fails miserably
  by turning red letters on and never turning them off again in the
  modules that contain words of Jesus markup. Both ways are valid
  OSIS, but apparently just valid OSIS isn't enough. It doesn't
  matter much, though, as long as I can figure out what flavor of
  OSIS to feed osis2mod.
  
  On 08/21/2015 06:39 PM, Greg Hellings wrote:


  You shouldn't run that command from a distributed
tar. The autogen.sh is used by the release manager or developers
during package time. The command you are looking for is
usrgen.sh or just ./configure
  Running one of those should bring you to a state
where invoking make will suffice.
  --Greg
  On Aug 21, 2015 9:20 PM, "Kahunapule
    Michael Johnson" kahunap...@ebible.org
wrote:

  
On 08/20/2015 06:08 PM, Greg Hellings wrote:


  Developers and other interested parties,

I've created a tarball and an SVN tag for SWORD 1.7.5a1. Please test
it and let me know if there are issues. If I hear nothing or only
positive feedback, I'll bless the same tarball as the final 1.7.5
release.

http://crosswire.org/ftpmirror/pub/sword/source/v1.7/sword-1.7.5a1.tar.gz


How do I fix these errors?


source/sword-1.7.5$ ./autogen.sh
*** Sword build system generation
*** Recreating libtool
libtoolize
./autogen.sh: 8: ./autogen.sh: libtoolize: not found
...

source/sword-1.7.5$ make
Makefile:490: .deps/buildtest.Po: No such file or directory
make: *** No rule to make target `.deps/buildtest.Po'. 
Stop.

-- 
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA
 eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  
  
  ___
  sword-devel mailing list: sword-devel@crosswire.org
  http://www.crosswire.org/mailman/listinfo/sword-devel
  Instructions to unsubscribe/change your settings at above page

  
  
  
  
  ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 
  
  
  

  
  
  

Your partner in
electronic Bible publishing,

  
  

  
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] 1.7.5a1

[Kahunapule Michael Johnson]

  
  
On 08/20/2015 06:08 PM, Greg Hellings
  wrote:


  Developers and other interested parties,

I've created a tarball and an SVN tag for SWORD 1.7.5a1. Please test
it and let me know if there are issues. If I hear nothing or only
positive feedback, I'll bless the same tarball as the final 1.7.5
release.

http://crosswire.org/ftpmirror/pub/sword/source/v1.7/sword-1.7.5a1.tar.gz


How do I fix these errors?


source/sword-1.7.5$ ./autogen.sh
*** Sword build system generation
*** Recreating libtool
libtoolize
./autogen.sh: 8: ./autogen.sh: libtoolize: not found
...

source/sword-1.7.5$ make
Makefile:490: .deps/buildtest.Po: No such file or directory
make: *** No rule to make target `.deps/buildtest.Po'.  Stop.

-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Yet another iteration of the eBible.org repository is done.

[Kahunapule Michael Johnson]

  
  
Got it. It was zip-devel. I'm running
  on Ubuntu Trusty.
  
  On 08/19/2015 05:03 PM, Greg Hellings wrote:


  You'll need to install something like zip-devel or
libzip-dev or whatever is the appropriate development package
for the zip library and then recompile libsword. What platform
are you running these tools on?


--Greg
  
  
On Wed, Aug 19, 2015 at 9:54 PM,
  Kahunapule Michael Johnson kahunap...@ebible.org
  wrote:
  

  Yikes!

How do I make libzip available?

osis2mod: ERROR: SWORD library
not compiled with ZIP compression support.
      Be sure libzip is available when compiling
SWORD library
OSIS Bible/commentary module creation tool for The SWORD
Project

usage: osis2mod output/path osisDoc
[OPTIONS]
  output/path         an existing folder that
the module will be written
  osisDoc         path to the validated OSIS
document, or '-' to
                 read from standard input
  -a             augment module if exists (default is to
create new)
  -z             use ZIP compression (default no
compression)
  -Z             use LZSS compression (default no
compression)
  -b 2|3|4         compression block size
(default 4):
                 2 - verse; 3 - chapter; 4 - book
  -c cipher_key     encipher module using
supplied key
                 (default no enciphering)
  -s 2|4         bytes used to store entry size
(default is 2).
  -v v11n         specify a versification scheme
to use (default is KJV)
                 Note: The following are valid values
for v11n:
                   Catholic        Catholic2      
German  
                   KJV     KJVA       
LXX 
                   Leningrad       Luther     
MT  
                   NRSV        NRSVA      
Orthodox    
                   Synodal     SynodalProt    
Vulg    
  -h              print verbose usage text

See http://www.crosswire.org/wiki/osis2mod
for more details.

  


On 08/19/2015 03:24 PM, Karl Kleinpaste wrote:
  

  
  

   *sIGh*

$ grep DataPath aau2006.conf 
  DataPath=./modules/texts/ztext/aau2006/
  
  ftp cd /pub/sword/modules/texts/ztext/aau2006
  250 CWD command successful
  ftp dir -a
  227 Entering Passive Mode (74,208,71,128,216,118).
  150 Opening ASCII mode data connection for file
  list
  drwxrwxr-x   2 ebible   psacln   4096 Aug 19
  22:42 .
  drwxrwxr-x 719 ebible   psacln  20480 Aug 20
  01:00 ..
  226 Transfer complete
  
  There's no there there.
  
  One of many.



  

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
 
   
  

  -- 
Aloha,
Kahunapule Michael Johnson
  
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA
 eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule

Re: [sword-devel] Yet another iteration of the eBible.org repository is in progress.

[Kahunapule Michael Johnson]

  
  
Agreed. As soon as we get the recipe
  right for the eBible.org repository, I'll shift automated updates
  over to another directory. For now, though, the whole thing is
  essentially experimental.
  
  On 08/20/2015 05:27 PM, Michael H wrote:


  A live production repository probably shouldn't be
the immediate landing place for a developmental script. Can I
suggest a 2nd development ebible repository, where untested
modules generated by the script can land to be validated without
destroying a known working version?



  
Main sword repositories currently support a very large
  number of installs (on the 500,000 - 10,000,000 order of
  magnitude), on 8-10 programs, across ~30 operating
  systems. It would be very wise that every module is
  validated before it goes live onto a main repo, and once a
  module goes live, it isn't replaced daily or randomly with
  another untested copy, but only when there is a valid
  reason to update; and then only after the new version is
  validated. The dev repo or 'nightly build' can continue to
  be for those willing to live dangerously or participating
  in trials of a specific language. When we've validated a
  module that needs updating actually works, it can be
  copied over.  
   

  

  
  
On Thu, Aug 20, 2015 at 9:00 PM, Karl
  Kleinpaste k...@kleinpaste.org
  wrote:
  
 InstallSize support has evaporated.

$ pwd
/home/karl/.sword/InstallMgr
$ grep eBible InstallMgr.conf
HTTPSource=eBible|ebible.org|/sword|||20150816130503
$ cd 20150816130503/mods.d/
$ grep 'InstallSize=0$' * | wc -l
678

You don't test your own repo.  You should be doing your
own testing -- I'm merely using Xiphos' module manager,
and you could be doing the same -- instead of only
reacting to testing from others.  This is at least
Round#5 of How EBible Repo Can Fail and it's still not
right.


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above
page
  


  
  
  
  
  ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Yet another iteration of the eBible.org repository is in progress.

[Kahunapule Michael Johnson]

  
  
Actually, I am doing my own testing in
  parallel, and trying to fix things, but I appreciate test feedback
  from others, too. I don't have a whole lot of time to devote to
  this, and I'm doing what I can with what I have. Remember, this is
  volunteer work for me, too, and 680 modules is a lot to test. I
  just got Xiphos updated to the non-crashing version a few minutes
  ago.
  Right now, the eBible.org repository is badly broken.
  
  In addition to what others found, I found that there was some
  unexpected behavior in the versification chooser. With the next
  iteration, it should really be what I intended:
  1. Pick versifications with the minimum number of verses in books
  that the versification doesn't have. (Missing books is treated as
  the worst offense in a versification.)
  2. If there is a tie, pick the versifications with the minimum
  number of verses in chapters that the versification doesn't have.
  (Malachi 4 in a versification that only goes to Malachi 3 is not
  so good.)
  3. If there is a tie, pick the versifications with the minimum
  number of verses that go beyond the maximum verse number of a
  chapter. (This picks up some of the more subtle versification
  variations.)
  4. If there is still a tie, pick the versification with the
  minimum number of verses that are in the versification but not in
  the current Bible. (Since we always need to handle subsets of a
  full Bible or New Testament, anyway, KJV, NRSV, and SynodalP are
  kind of redundant, but I pick them anyway when they fit more
  closely.)
  
  There is a worse problem, though, right now. The fresh osis2mod
  build 3314 that I'm using produces modules that seem to be missing
  all text when viewed on PocketSword or Xiphos. I'm a little
  stumped...
  
  On 08/20/2015 04:00 PM, Karl Kleinpaste wrote:


  
  InstallSize support has evaporated.

$ pwd
/home/karl/.sword/InstallMgr
$ grep eBible InstallMgr.conf
HTTPSource=eBible|ebible.org|/sword|||20150816130503
$ cd 20150816130503/mods.d/
$ grep 'InstallSize=0$' * | wc -l
678

You don't test your own repo.  You should be doing your own
testing -- I'm merely using Xiphos' module manager, and you
could be doing the same -- instead of only reacting to testing
from others.  This is at least Round#5 of How EBible Repo Can
Fail and it's still not right.
  
  
  
  ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page