Re: [sword-devel] Suggestion for markup of Romans 3:26 in module KJV

[DM Smith]

David and I’ll look at this soon. We’ll try to figure out how this happened and 
whether the problem is bigger than this. 

— DM Smith

> On Apr 3, 2021, at 5:40 PM, David Haslam  wrote:
> 
> 
> Hi Troy,
> 
> I will discuss the reported issue with DM as and when I have enough free 
> time. 
> 
> We should definitely not revert to 2.4 as that would simply undo all the good 
> work from 2.5 through 2.9
> 
> If there’s a mistake, we can include the corrections in version 2.10 which is 
> still in preparation and has been for several years. 
> 
> I didn’t respond earlier simply because I’ve had other matters to attend to 
> today. 
> 
> Happy Easter!
> 
> David
> 
> Sent from ProtonMail for iOS
> 
> 
>> On Sat, Apr 3, 2021 at 21:42, Troy A. Griffitts  wrote:
>> A bit more investigation, this seems to be introduced between versions of 
>> our KJV 2.4 and 2.5. 
>> 
>> 2.4 reads correctly.  2.5 has this problem.  Unfortunately we have 
>> uninformative information in our History .conf entries between these 
>> versions.
>> 
>> I am tempted to roll back this module to 2.4.
>> 
>> Can anyone speak to the issue of how Strong's number values could possibly 
>> change between version 2.4 and 2.5; and when we discover how this could 
>> happen, what other problems this might have introduced in revision 2.5?
>> 
>> Troy
>> 
>> 
>> 
>> On 4/3/21 7:58 AM, Troy A. Griffitts wrote:
>>> This is a bit disturbing I just check our lastest KJV and TR modules (which 
>>> was the base for the Strong's markup in the KJV). I can confirm that Romans 
>>> 3:25 has Strong's 3688 whereas the TR does not.
>>> 
>>> DM and David have been the primary curators of our KJV text. Any 
>>> speculation on how an error like this could have entered the text and how 
>>> that might be the cause of other corruptions?
>>> 
>>> Troy
>>> 
>>> On April 3, 2021 4:18:01 AM MST, vtamara  wrote:
>>>> 
>>>> Sorry, I made mistake in my previos email, Romans 3:25 would show that
>>>> the word with Strong number 3688 is also τω.  But according to
>>>> https://www.blueletterbible.org/lang/lexicon/lexicon.cfm?Strongs=G3688=KJV
>>>> the word with strong number 3688 is ὄνος  (donkey).
>>>> 
>>>> https://biblehub.com/greek/3688.htm  also shows that the word would be
>>>> ὄνος
>>>> 
>>>> Even KVJ module in verse John 12:15 shows that the word with Strong
>>>> number G3688 is ὄνος:
>>>> 
>>>> an
>>>> ass’s
>>>> 
>>>> (so as well as in Mat 21:2, Mat 21:5, Mat 21:6, Luk 13.15, Luk 14:5).
>>>> 
>>>> Anyway I think in Romans 3:25 and 3:26 the word τῷ should have Strong
>>>> number 3588.
>>>> 
>>>> I see similar problem with G3688 in the following verses of the KJV
>>>> module:
>>>> 
>>>> * Mat 26:11
>>>> * Mat 26:12
>>>> * Mat 26:45
>>>> * Mat 26:69
>>>> * Mat 27:46
>>>> * Mark 1:9
>>>> * Mark 5:30
>>>> * Mark 13:20
>>>> * Luke 2:38
>>>> * Luke 8.46
>>>> * Luke 14:21
>>>> * Luke 16:9
>>>> * II Corinthians 1:8
>>>> * II Corinthians 1:9
>>>> * II Corinthians 8:14
>>>> * Revelation of John 11:4
>>>> * Revelation of John 14:7
>>>> 
>>>> 
>>>> Blessings.
>>>> 
>>>> El 2021-04-03 06:34, vtamara escribió:
>>>>> Good morning in the Lord
>>>>> 
>>>>> 
>>>>> For the module KJV the markup of Romans 3:26 is:
>>>>> 
>>>>> >>>> morph="robinson:T-DSM robinson:N-DSM" src="12 14">time
>>>>> 
>>>>> that says that word number 12 in Greek is τω with Strong number 3688
>>>>> 
>>>>> However Romans 3:25 shows that the word with Strong number 3688 is
>>>>> αιματι:
>>>>> >>>> morph="robinson:T-DSN robinson:N-DSN" src="10 12">blood
>>>>> 
>>>>> And for example at
>>>>> https://www.blueletterbible.org/lang/lexicon/lexicon.cfm?Strongs=G3588=KJV
>>>>> I read that the Strong number 3588 corresponds to ὁ that is
>>>>> interchangeable
>>>>> with τῷ.
>>>>> 
>>>>> Then I think the Markup for the word number 12 of Romans 3:26 should
>>>>> stay as τῷ but with Strong number 3588.
>>>>> 
>>>>> Blessings
>>>> 
>>>> 
>>> 
>>> -- 
>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. 
>>> 
>>> ___
>>> 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 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] How to fix book names in Ukrainian/Russian

[DM Smith]

I had though about this, but it won’t work as expected. The user should be able 
to type in such a reference and have it recognized. They’ll expect to type what 
they think that character should be.

For JSword, we try three parsings of the input. First as an osisID (or 
osisRef). If that fails then we try a localized parse. Finally we try to parse 
as English. This is no means sufficient, but it works in most cases.

In Him,
DM

> On Apr 23, 2021, at 3:11 PM, David Haslam  wrote:
> 
> OK - so the ordinary common ANSI hyphen/minus character cannot be used.
> 
> But what about the Unicode HYPHEN character U+2010 ‐ ?
> 
> That has no special use in OSIS as a separator, surely ?
> 
> Would this cause a problem to parse vernacular references?
> 
> Or does SWORD somehow reduce this under the hood?
> 
> David
> 
> Sent from ProtonMail for iOS
> 
> 
> On Fri, Apr 23, 2021 at 16:23, Troy A. Griffitts  > wrote:
>> 
>> Generally, Fr. Cyrille is correct. Specifically, in this instance there is a 
>> deficiency in the SWORD engine which will not allow what you wish.
>> 
>> Let me explain a bit.
>> 
>> First, SWORD always overlays a chosen locale on top of English. This means 
>> that when choosing, say, Ukrainian, both Луки and Luke will work for the 3rd 
>> Gospel. The referencing language in SWORD uses OSIS which has a set of books 
>> defined using English names.
>> 
>> That shouldn't pose a problem for you, but does give a bit of background for 
>> the real problem...
>> 
>> OSIS (osisRef) and English ranges and verse lists use the three "- , ;" 
>> characters for special delimiters, each with a specific meaning. These 
>> characters cannot currently be used as part of a localized book name.
>> 
>> Eventually, SWORD should allow localization of verse reference and list 
>> symbols, but this will require no longer supporting 2 locales at once (both 
>> OSIS / English underlying a selected localization) but will require either 
>> the parser to be smarter in determining context within a verse list and 
>> determining how to parse symbols (OSIS / English, or using the 
>> locale-provided symbol meaning, if they contradict each other), or else the 
>> client of the library will need to manually state which mode to use.
>> 
>> Bottom line, right now, "- , ;" cannot be used in localized book names.
>> 
>> I am sorry for the bad news. Welcome! Thank you for your willingness to work 
>> together.
>> 
>> Troy
>> 
>> On April 23, 2021 7:31:50 AM MST, Fr Cyrille  wrote:
>> Probably download sword http://www.crosswire.org/sword/develop/index.jsp 
>>  and use svn for your 
>> changes. You need to change the file
>> locales.d/uk-utf8.conf and then send a patch to Troy.
>> 
>> Le 23/04/2021 à 16:02, Evgen Kucherov a écrit :
>>> Hi guys,
>>> 
>>> I'm new to the SWORD project. I'm currently contributing a bit to the Ezra 
>>> Bible App (Ezra project). In general I'm interested in improving the 
>>> quality of Russian and Ukrainian modules. 
>>> 
>>> But for now I want to fix book names that has numbers in their titles:
>>> 
>>> It should be "1-e Коринтян" instead of "1. Коринтян" and so on.
>>> 
>>> How I can do this? Is there a git repository?
>>> 
>>> 
>>> 
>>> -- 
>>> sincerely,
>>> Evgen Kucherov
>>> 
>>> 
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org 
>>> 
>>> http://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://crosswire.org/mailman/listinfo/sword-devel
> Instructions 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

Re: [sword-devel] Suggestion for markup of Romans 3:26 in module KJV

[DM Smith]

Troy,

Again, thank you for the emergency fix.

My apologies for the error. It’s my bad.

It has taken some effort to find when and how it happened.

The problem was introduced Feb 2013 by my hand edit to merge empty  tags 
having G3588 with the appropriate  having the following position.

Example: Matthew 26:11
Before: Jan 30, 2013
For ye have the poor always with you; but me ye have not always.

After: Feb 3, 2013
For ye have the poor always with you; but me ye have not always.mailto:dfh...@protonmail.com>> wrote:
>> 
>> Hi Troy,
>> 
>> I will discuss the reported issue with DM as and when I have enough free 
>> time. 
>> 
>> We should definitely not revert to 2.4 as that would simply undo all the 
>> good work from 2.5 through 2.9
>> 
>> If there’s a mistake, we can include the corrections in version 2.10 which 
>> is still in preparation and has been for several years. 
>> 
>> I didn’t respond earlier simply because I’ve had other matters to attend to 
>> today. 
>> 
>> Happy Easter!
>> 
>> David
>> 
>> Sent from ProtonMail for iOS
>> 
>> 
>> On Sat, Apr 3, 2021 at 21:42, Troy A. Griffitts > > wrote:
>>> 
>>> A bit more investigation, this seems to be introduced between versions of 
>>> our KJV 2.4 and 2.5. 
>>> 
>>> 2.4 reads correctly.  2.5 has this problem.  Unfortunately we have 
>>> uninformative information in our History .conf entries between these 
>>> versions.
>>> 
>>> I am tempted to roll back this module to 2.4.
>>> 
>>> Can anyone speak to the issue of how Strong's number values could possibly 
>>> change between version 2.4 and 2.5; and when we discover how this could 
>>> happen, what other problems this might have introduced in revision 2.5?
>>> 
>>> Troy
>>> 
>>> 
>>> 
>>> On 4/3/21 7:58 AM, Troy A. Griffitts wrote:
 This is a bit disturbing I just check our lastest KJV and TR modules 
 (which was the base for the Strong's markup in the KJV). I can confirm 
 that Romans 3:25 has Strong's 3688 whereas the TR does not.
 
 DM and David have been the primary curators of our KJV text. Any 
 speculation on how an error like this could have entered the text and how 
 that might be the cause of other corruptions?
 
 Troy
 
 On April 3, 2021 4:18:01 AM MST, vtamara  
  wrote:
 Sorry, I made mistake in my previos email, Romans 3:25 would show that
 the word with Strong number 3688 is also τω.  But according to
 https://www.blueletterbible.org/lang/lexicon/lexicon.cfm?Strongs=G3688=KJV
  
 
 the word with strong number 3688 is ὄνος  (donkey).
 
 https://biblehub.com/greek/3688.htm   
 also shows that the word would be
 ὄνος
 
 Even KVJ module in verse John 12:15 shows that the word with Strong
 number G3688 is ὄνος:
 
 an
 ass’s
 
 (so as well as in Mat 21:2, Mat 21:5, Mat 21:6, Luk 13.15, Luk 14:5).
 
 Anyway I think in Romans 3:25 and 3:26 the word τῷ should have Strong
 number 3588.
 
 I see similar problem with G3688 in the following verses of the KJV
 module:
 
 * Mat 26:11
 * Mat 26:12
 * Mat 26:45
 * Mat 26:69
 * Mat 27:46
 * Mark 1:9
 * Mark 5:30
 * Mark 13:20
 * Luke 2:38
 * Luke 8.46
 * Luke 14:21
 * Luke 16:9
 * II Corinthians 1:8
 * II Corinthians 1:9
 * II Corinthians 8:14
 * Revelation of John 11:4
 * Revelation of John 14:7
 
 
 Blessings.
 
 El 2021-04-03 06:34, vtamara escribió:
 Good morning in the Lord
 
 
 For the module KJV the markup of Romans 3:26 is:
 
 >>> morph="robinson:T-DSM robinson:N-DSM" src="12 14">time
 
 that says that word number 12 in Greek is τω with Strong number 3688
 
 However Romans 3:25 shows that the word with Strong number 3688 is
 αιματι:
 >>> morph="robinson:T-DSN robinson:N-DSN" src="10 12">blood
 
 And for example at
 https://www.blueletterbible.org/lang/lexicon/lexicon.cfm?Strongs=G3588=KJV
  
 
 I read that the Strong number 3588 corresponds to ὁ that is
 interchangeable
 with τῷ.
 
 Then I think the Markup for the word number 12 of Romans 3:26 should
 stay as τῷ but with Strong number 3588.
 
 Blessings
 
 
 
 -- 
 Sent from my Android device with K-9 Mail. Please excuse my brevity. 
 
 ___
 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] The OSIS abbr element & SWORD ?

[DM Smith]

JSword shows it with a tooltip of the expansion if provided.

In Him,
DM

> On Apr 9, 2021, at 3:27 AM, David Haslam  wrote:
> 
> Does SWORD have a means to show the expansion of an abbreviation for words 
> marked using the OSIS abbr element?
> 
> If so, does any front-end have UI support for this OSIS feature ?
> 
> If not, any thoughts on how this might best be implemented?
> 
> David
> 
> Sent from ProtonMail for iOS
> ___
> 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 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] strongMorph definitions

[DM Smith]

Sure. The size is immaterial, but either send a link or the file to me 
directly. It’ll be interesting to see how the KJV OT lines up with the OSHB. 
I’m not sure when I’ll be able to attend to it, but I’ll have it at that point.

In Him,
DM

> On Apr 7, 2021, at 11:08 AM, David Troidl  wrote:
> 
> We have Strong's numbers in the OSHB. I assembled the books into a single 
> file and put the lemmas in SWORD format. I could send it to you, if you want. 
> It is 3.76 MB zipped.
> 
> David
> 
> On 4/6/2021 10:25 AM, DM Smith wrote:
>> That was the basic idea that David I-B described for the codes. This is akin 
>> to Robinson’s Greek Morphology codes, where a skilled reader wouldn’t need 
>> the expansion but at first.
>> 
>> If a map were made between Thayer and these codes, then we could apply them 
>> to the KJV(A). We might be able to map OSHB to the KJV(A) if we have 
>> Strong’s numbers in both.
>> 
>> DM
>> 
>>> On Apr 5, 2021, at 11:35 AM, David Troidl >> <mailto:davidtro...@aol.com>> wrote:
>>> 
>>> We have Hebrew morphology codes, 
>>> https://hb.openscriptures.org/parsing/HebrewMorphologyCodes.html 
>>> <https://hb.openscriptures.org/parsing/HebrewMorphologyCodes.html>, that 
>>> are applied in the OSHB module and interpreted by the OSHM module. Those 
>>> could certainly be applied to the KJVA.
>>> 
>>> David
>>> 
>>> On 4/5/2021 10:19 AM, DM Smith wrote:
>>>> These are coded to Thayer’s. These have no corresponding module. I’ve had 
>>>> discussions with David Instone-Brewer about creating a morphology for 
>>>> Hebrew and mapping them to Thayer's so that we can replace the one with 
>>>> the other. That was years ago and hasn’t come to fruition.
>>>> 
>>>> DM Smith
>>>> 
>>>>> On Apr 5, 2021, at 9:30 AM, Tuomas Airaksinen 
>>>>> mailto:tuomas.airaksi...@gmail.com>> wrote:
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> KJVA has hebrew morph definition tags such as >>>> morph="strongMorph:TH8804">. 
>>>>> I wonder from which dictionary these morph definitions should be looked 
>>>>> for? 
>>>>> 
>>>>> Related to: https://github.com/AndBible/and-bible/issues/835 
>>>>> <https://github.com/AndBible/and-bible/issues/835> 
>>>>> 
>>>>> Best regards,
>>>>> Tuomas
>>>>> ___
>>>>> sword-devel mailing list: sword-devel@crosswire.org 
>>>>> <mailto:sword-devel@crosswire.org>
>>>>> http://crosswire.org/mailman/listinfo/sword-devel 
>>>>> <http://crosswire.org/mailman/listinfo/sword-devel>
>>>>> Instructions to unsubscribe/change your settings at above page
>>>> 
>>>> 
>>>> 
>>>> ___
>>>> sword-devel mailing list: sword-devel@crosswire.org 
>>>> <mailto:sword-devel@crosswire.org>
>>>> http://crosswire.org/mailman/listinfo/sword-devel 
>>>> <http://crosswire.org/mailman/listinfo/sword-devel>
>>>> Instructions to unsubscribe/change your settings at above page
>>> 
>>>  
>>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient_term=icon>
>>> Virus-free. www.avast.com 
>>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient_term=link>
>>>  
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org 
>>> <mailto:sword-devel@crosswire.org>
>>> http://crosswire.org/mailman/listinfo/sword-devel 
>>> <http://crosswire.org/mailman/listinfo/sword-devel>
>>> Instructions to unsubscribe/change your settings at above page
>> 
>> 
>> 
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org 
>> <mailto:sword-devel@crosswire.org>
>> http://crosswire.org/mailman/listinfo/sword-devel 
>> <http://crosswire.org/mailman/listinfo/sword-devel>
>> Instructions 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 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] strongMorph definitions

[DM Smith]

That was the basic idea that David I-B described for the codes. This is akin to 
Robinson’s Greek Morphology codes, where a skilled reader wouldn’t need the 
expansion but at first.

If a map were made between Thayer and these codes, then we could apply them to 
the KJV(A). We might be able to map OSHB to the KJV(A) if we have Strong’s 
numbers in both.

DM

> On Apr 5, 2021, at 11:35 AM, David Troidl  wrote:
> 
> We have Hebrew morphology codes, 
> https://hb.openscriptures.org/parsing/HebrewMorphologyCodes.html 
> <https://hb.openscriptures.org/parsing/HebrewMorphologyCodes.html>, that are 
> applied in the OSHB module and interpreted by the OSHM module. Those could 
> certainly be applied to the KJVA.
> 
> David
> 
> On 4/5/2021 10:19 AM, DM Smith wrote:
>> These are coded to Thayer’s. These have no corresponding module. I’ve had 
>> discussions with David Instone-Brewer about creating a morphology for Hebrew 
>> and mapping them to Thayer's so that we can replace the one with the other. 
>> That was years ago and hasn’t come to fruition.
>> 
>> DM Smith
>> 
>>> On Apr 5, 2021, at 9:30 AM, Tuomas Airaksinen >> <mailto:tuomas.airaksi...@gmail.com>> wrote:
>>> 
>>> Hi,
>>> 
>>> KJVA has hebrew morph definition tags such as >> morph="strongMorph:TH8804">. 
>>> I wonder from which dictionary these morph definitions should be looked 
>>> for? 
>>> 
>>> Related to: https://github.com/AndBible/and-bible/issues/835 
>>> <https://github.com/AndBible/and-bible/issues/835> 
>>> 
>>> Best regards,
>>> Tuomas
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org 
>>> <mailto:sword-devel@crosswire.org>
>>> http://crosswire.org/mailman/listinfo/sword-devel 
>>> <http://crosswire.org/mailman/listinfo/sword-devel>
>>> Instructions to unsubscribe/change your settings at above page
>> 
>> 
>> 
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org 
>> <mailto:sword-devel@crosswire.org>
>> http://crosswire.org/mailman/listinfo/sword-devel 
>> <http://crosswire.org/mailman/listinfo/sword-devel>
>> Instructions to unsubscribe/change your settings at above page
> 
>  
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient_term=icon>
>   Virus-free. www.avast.com 
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient_term=link>
>  
> ___
> 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 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] strongMorph definitions

[DM Smith]

These are coded to Thayer’s. These have no corresponding module. I’ve had 
discussions with David Instone-Brewer about creating a morphology for Hebrew 
and mapping them to Thayer's so that we can replace the one with the other. 
That was years ago and hasn’t come to fruition.

DM Smith

> On Apr 5, 2021, at 9:30 AM, Tuomas Airaksinen  
> wrote:
> 
> Hi,
> 
> KJVA has hebrew morph definition tags such as . 
> I wonder from which dictionary these morph definitions should be looked for? 
> 
> Related to: https://github.com/AndBible/and-bible/issues/835 
> <https://github.com/AndBible/and-bible/issues/835> 
> 
> Best regards,
> Tuomas
> ___
> 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 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] Suggestion for markup of Romans 3:26 in module KJV

[DM Smith]

The history of the module is listed in the wiki: 
https://wiki.crosswire.org/CrossWire_KJV#Module_Versions 
<https://wiki.crosswire.org/CrossWire_KJV#Module_Versions>. That listing isn’t 
meant to be cryptic but rather complete. The version history in the conf is not 
as complete. We can make it more complete/in sync.

The version 2.6 has the problem. In that version we added the Greek words as 
found in the TR, using the version by Maurice Robinson, which can now be found 
at https://sites.google.com/a/wmail.fi/greeknt/home/greeknt 
<https://sites.google.com/a/wmail.fi/greeknt/home/greeknt>.

I still have the TR download and the scripts from that change. So with some 
effort David and I can figure it out.

DM

> On Apr 3, 2021, at 8:31 PM, DM Smith  wrote:
> 
> David and I’ll look at this soon. We’ll try to figure out how this happened 
> and whether the problem is bigger than this. 
> 
> — DM Smith
> 
>> On Apr 3, 2021, at 5:40 PM, David Haslam > <mailto:dfh...@protonmail.com>> wrote:
>> 
>> Hi Troy,
>> 
>> I will discuss the reported issue with DM as and when I have enough free 
>> time. 
>> 
>> We should definitely not revert to 2.4 as that would simply undo all the 
>> good work from 2.5 through 2.9
>> 
>> If there’s a mistake, we can include the corrections in version 2.10 which 
>> is still in preparation and has been for several years. 
>> 
>> I didn’t respond earlier simply because I’ve had other matters to attend to 
>> today. 
>> 
>> Happy Easter!
>> 
>> David
>> 
>> Sent from ProtonMail for iOS
>> 
>> 
>> On Sat, Apr 3, 2021 at 21:42, Troy A. Griffitts > <mailto:scr...@crosswire.org>> wrote:
>>> 
>>> A bit more investigation, this seems to be introduced between versions of 
>>> our KJV 2.4 and 2.5. 
>>> 
>>> 2.4 reads correctly.  2.5 has this problem.  Unfortunately we have 
>>> uninformative information in our History .conf entries between these 
>>> versions.
>>> 
>>> I am tempted to roll back this module to 2.4.
>>> 
>>> Can anyone speak to the issue of how Strong's number values could possibly 
>>> change between version 2.4 and 2.5; and when we discover how this could 
>>> happen, what other problems this might have introduced in revision 2.5?
>>> 
>>> Troy
>>> 
>>> 
>>> 
>>> On 4/3/21 7:58 AM, Troy A. Griffitts wrote:
>>>> This is a bit disturbing I just check our lastest KJV and TR modules 
>>>> (which was the base for the Strong's markup in the KJV). I can confirm 
>>>> that Romans 3:25 has Strong's 3688 whereas the TR does not.
>>>> 
>>>> DM and David have been the primary curators of our KJV text. Any 
>>>> speculation on how an error like this could have entered the text and how 
>>>> that might be the cause of other corruptions?
>>>> 
>>>> Troy
>>>> 
>>>> On April 3, 2021 4:18:01 AM MST, vtamara  
>>>> <mailto:vtam...@pasosdejesus.org> wrote:
>>>> Sorry, I made mistake in my previos email, Romans 3:25 would show that
>>>> the word with Strong number 3688 is also τω.  But according to
>>>> https://www.blueletterbible.org/lang/lexicon/lexicon.cfm?Strongs=G3688=KJV
>>>>  
>>>> <https://www.blueletterbible.org/lang/lexicon/lexicon.cfm?Strongs=G3688=KJV>
>>>> the word with strong number 3688 is ὄνος  (donkey).
>>>> 
>>>> https://biblehub.com/greek/3688.htm <https://biblehub.com/greek/3688.htm>  
>>>> also shows that the word would be
>>>> ὄνος
>>>> 
>>>> Even KVJ module in verse John 12:15 shows that the word with Strong
>>>> number G3688 is ὄνος:
>>>> 
>>>> an
>>>> ass’s
>>>> 
>>>> (so as well as in Mat 21:2, Mat 21:5, Mat 21:6, Luk 13.15, Luk 14:5).
>>>> 
>>>> Anyway I think in Romans 3:25 and 3:26 the word τῷ should have Strong
>>>> number 3588.
>>>> 
>>>> I see similar problem with G3688 in the following verses of the KJV
>>>> module:
>>>> 
>>>> * Mat 26:11
>>>> * Mat 26:12
>>>> * Mat 26:45
>>>> * Mat 26:69
>>>> * Mat 27:46
>>>> * Mark 1:9
>>>> * Mark 5:30
>>>> * Mark 13:20
>>>> * Luke 2:38
>>>> * Luke 8.46
>>>> * Luke 14:21
>>>> * Luke 16:9
>>>> * II Corinthians 1:8
>>>> * II Corin

Re: [sword-devel] Suggestion for markup of Romans 3:26 in module KJV

[DM Smith]

David and I’ll look at this soon. We’ll try to figure out how this happened and 
whether the problem is bigger than this. 

— DM Smith

> On Apr 3, 2021, at 5:40 PM, David Haslam  wrote:
> 
> Hi Troy,
> 
> I will discuss the reported issue with DM as and when I have enough free 
> time. 
> 
> We should definitely not revert to 2.4 as that would simply undo all the good 
> work from 2.5 through 2.9
> 
> If there’s a mistake, we can include the corrections in version 2.10 which is 
> still in preparation and has been for several years. 
> 
> I didn’t respond earlier simply because I’ve had other matters to attend to 
> today. 
> 
> Happy Easter!
> 
> David
> 
> Sent from ProtonMail for iOS
> 
> 
> On Sat, Apr 3, 2021 at 21:42, Troy A. Griffitts  <mailto:scr...@crosswire.org>> wrote:
>> 
>> A bit more investigation, this seems to be introduced between versions of 
>> our KJV 2.4 and 2.5. 
>> 
>> 2.4 reads correctly.  2.5 has this problem.  Unfortunately we have 
>> uninformative information in our History .conf entries between these 
>> versions.
>> 
>> I am tempted to roll back this module to 2.4.
>> 
>> Can anyone speak to the issue of how Strong's number values could possibly 
>> change between version 2.4 and 2.5; and when we discover how this could 
>> happen, what other problems this might have introduced in revision 2.5?
>> 
>> Troy
>> 
>> 
>> 
>> On 4/3/21 7:58 AM, Troy A. Griffitts wrote:
>>> This is a bit disturbing I just check our lastest KJV and TR modules (which 
>>> was the base for the Strong's markup in the KJV). I can confirm that Romans 
>>> 3:25 has Strong's 3688 whereas the TR does not.
>>> 
>>> DM and David have been the primary curators of our KJV text. Any 
>>> speculation on how an error like this could have entered the text and how 
>>> that might be the cause of other corruptions?
>>> 
>>> Troy
>>> 
>>> On April 3, 2021 4:18:01 AM MST, vtamara  
>>> <mailto:vtam...@pasosdejesus.org> wrote:
>>> Sorry, I made mistake in my previos email, Romans 3:25 would show that
>>> the word with Strong number 3688 is also τω.  But according to
>>> https://www.blueletterbible.org/lang/lexicon/lexicon.cfm?Strongs=G3688=KJV
>>>  
>>> <https://www.blueletterbible.org/lang/lexicon/lexicon.cfm?Strongs=G3688=KJV>
>>> the word with strong number 3688 is ὄνος  (donkey).
>>> 
>>> https://biblehub.com/greek/3688.htm <https://biblehub.com/greek/3688.htm>  
>>> also shows that the word would be
>>> ὄνος
>>> 
>>> Even KVJ module in verse John 12:15 shows that the word with Strong
>>> number G3688 is ὄνος:
>>> 
>>> an
>>> ass’s
>>> 
>>> (so as well as in Mat 21:2, Mat 21:5, Mat 21:6, Luk 13.15, Luk 14:5).
>>> 
>>> Anyway I think in Romans 3:25 and 3:26 the word τῷ should have Strong
>>> number 3588.
>>> 
>>> I see similar problem with G3688 in the following verses of the KJV
>>> module:
>>> 
>>> * Mat 26:11
>>> * Mat 26:12
>>> * Mat 26:45
>>> * Mat 26:69
>>> * Mat 27:46
>>> * Mark 1:9
>>> * Mark 5:30
>>> * Mark 13:20
>>> * Luke 2:38
>>> * Luke 8.46
>>> * Luke 14:21
>>> * Luke 16:9
>>> * II Corinthians 1:8
>>> * II Corinthians 1:9
>>> * II Corinthians 8:14
>>> * Revelation of John 11:4
>>> * Revelation of John 14:7
>>> 
>>> 
>>> Blessings.
>>> 
>>> El 2021-04-03 06:34, vtamara escribió:
>>> Good morning in the Lord
>>> 
>>> 
>>> For the module KJV the markup of Romans 3:26 is:
>>> 
>>> >> morph="robinson:T-DSM robinson:N-DSM" src="12 14">time
>>> 
>>> that says that word number 12 in Greek is τω with Strong number 3688
>>> 
>>> However Romans 3:25 shows that the word with Strong number 3688 is
>>> αιματι:
>>> >> morph="robinson:T-DSN robinson:N-DSN" src="10 12">blood
>>> 
>>> And for example at
>>> https://www.blueletterbible.org/lang/lexicon/lexicon.cfm?Strongs=G3588=KJV
>>>  
>>> <https://www.blueletterbible.org/lang/lexicon/lexicon.cfm?Strongs=G3588=KJV>
>>> I read that the Strong number 3588 corresponds to ὁ that is
>>> interchangeable
>>> with τῷ.
>>> 
>>> Then I think the Markup for the word number 12 of Romans 3:26 should
>>> stay as τῷ but with Strong number 3588.
>>> 
>>> Blessings
>>> 
>>> 
>>> 
>>> -- 
>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. 
>>> 
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org 
>>> <mailto:sword-devel@crosswire.org>
>>> http://crosswire.org/mailman/listinfo/sword-devel 
>>> <http://crosswire.org/mailman/listinfo/sword-devel>
>>> Instructions 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 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] License of SWORD (and BibleTime)

[DM Smith]

Yes. SWORD is 2.0 only. JSword is 2.0 or later.

> On Jun 6, 2020, at 7:11 AM, ref...@gmx.net wrote:
> 
> I think it is strictly. 
> 
> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
> 
> 
>  Original Message 
> Subject: [sword-devel] License of SWORD (and BibleTime)
> From: Jaak Ristioja 
> To: SWORD Developers' Collaboration Forum 
> CC: 
> 
> 
> Hello!
> 
> We're having a small confusion about the license of BibleTime on GitHub:
> 
> https://github.com/bibletime/bibletime/issues/249
> 
> To sum up we are uncertain whether the BibleTime source code is GPL-2.0
> only or GPL-2.0 "or later version".
> 
> I'm writing here to clarify the license of SWORD:
> 
> Is the source code for SWORD licensed strictly under the GNU GENERAL
> PUBLIC LICENSE version 2.0 ONLY, or under the GNU GENERAL PUBLIC LICENSE
> version 2.0 and "any later version"?
> 
> Best regards,
> J
> ___
> 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

Re: [sword-devel] Chapter descriptions

[DM Smith]

In the AKJV link you gave, line 11 is:

\cd 1 Elimelech driven by famine into Moab, dies there. 4 Mahlon and Chilion, 
having married wives of Moab, die also. 6 Naomi returning homeward, 8 dissuades 
her two daughters in law from going with her, 14 Orpah leaves her, but Ruth 
with great constancy accompanies her. 19 They two come to Bethlehem, where they 
are gladly received.

Is that what you are calling a chapter index?

David and I have been wondering how we should mark those up in OSIS for the KJV 
1769.

I think that chapter also has titles.

In Him,
DM

> On May 9, 2020, at 12:43 PM, Michael H  wrote:
> 
> Reading the list of provided tags, these chapter descriptions should be 
> marked ".index" when they provide reference information, and ".summary" where 
> they do not.  That is, the original KJV1611 has chapter indexes.  The 
> original Douay Rheims Challoner has Chapter summaries. The recent update to 
> the CPDV includes chapter summaries. The AKJV update includes Chapter indexes 
> (which is ready, but I haven't heard from Peter on how to proceed.)
> 
> CPDV with chapter summaries: 
> https://gitlab.com/cmahte/cpdv/-/blob/master/usfm/08-RUT-ENG%5BB%5DCPDV2009%5Bpd%5D.p.sfm
>  
> <https://gitlab.com/cmahte/cpdv/-/blob/master/usfm/08-RUT-ENG%5BB%5DCPDV2009%5Bpd%5D.p.sfm>
> 
> AKJV with chapter indexes: 
> https://github.com/BibleCorps/ENG-B-AKJV2018-pd-PSFM/blob/master/p.sfm/ENG%5BB%5DAKJV2018%5BPD%5D08-RUT.p.sfm
>  
> <https://github.com/BibleCorps/ENG-B-AKJV2018-pd-PSFM/blob/master/p.sfm/ENG%5BB%5DAKJV2018%5BPD%5D08-RUT.p.sfm>
> 
> 
> On Sat, May 9, 2020 at 10:51 AM DM Smith  <mailto:dmsm...@crosswire.org>> wrote:
> See the wiki!!! 
> https://wiki.crosswire.org/Osis2mod#Handling_of_Introductions.2C_Titles_and_Inter-Verse_Material
>  
> <https://wiki.crosswire.org/Osis2mod#Handling_of_Introductions.2C_Titles_and_Inter-Verse_Material>
> 
> DM
> 
>> On May 9, 2020, at 2:14 AM, David Haslam > <mailto:dfh...@protonmail.com>> wrote:
>> 
>> Discussion starter
>> 
>> OSIS has no dedicated element specifically for a chapter description. 
>> 
>> These are not section titles per se but they come before verse 1. 
>> 
>> In printed Bibles, they are typically in italics and are never in bold. 
>> Usually centred and often contain verse numbers that could be thought of as 
>> references to locate the text described following. They can flow onto more 
>> than one line in pages with two columns of text. In some editions these are 
>> allowed to be full page width rather than column width. The text size is 
>> never larger than verse text. 
>> 
>> The Blayney 1769 Oxford edition of the KJV has such chapter descriptions. 
>> 
>> How best to mark these ?
>> 
>> Best regards
>> 
>> David
>> 
>> Sent from ProtonMail Mobile
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org 
>> <mailto:sword-devel@crosswire.org>
>> http://www.crosswire.org/mailman/listinfo/sword-devel 
>> <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 
> <mailto:sword-devel@crosswire.org>
> http://www.crosswire.org/mailman/listinfo/sword-devel 
> <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

Re: [sword-devel] Chapter descriptions

[DM Smith]

See the wiki!!! 
https://wiki.crosswire.org/Osis2mod#Handling_of_Introductions.2C_Titles_and_Inter-Verse_Material
 


DM

> On May 9, 2020, at 2:14 AM, David Haslam  wrote:
> 
> Discussion starter
> 
> OSIS has no dedicated element specifically for a chapter description. 
> 
> These are not section titles per se but they come before verse 1. 
> 
> In printed Bibles, they are typically in italics and are never in bold. 
> Usually centred and often contain verse numbers that could be thought of as 
> references to locate the text described following. They can flow onto more 
> than one line in pages with two columns of text. In some editions these are 
> allowed to be full page width rather than column width. The text size is 
> never larger than verse text. 
> 
> The Blayney 1769 Oxford edition of the KJV has such chapter descriptions. 
> 
> How best to mark these ?
> 
> Best regards
> 
> David
> 
> Sent from ProtonMail Mobile
> ___
> 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] NASB Psalm titles

[DM Smith]

While the OSIS spec has one definition of canonical, being part of the 
published text. Regarding Bibles, Troy pointed out, we use it in the 
theological sense for Bible modules.

There are many versifications that have the canonical titles as verse 1. and 
what we have as verse 1 to n in verse 2 to n + 1.

I once surveyed all of our modules for verse 3.0 and verse 3.1 to note how they 
handled the canonical Psalm title. It was very inconsistent. Some had it in 
verse 0, some had it in verse 1. Many didn’t have it marked as canonical. 
That’s an entirely issue than what we are talking about here.

In Him,
DM

> On May 8, 2020, at 10:49 AM, Tom Sullivan  wrote:
> 
> Y'all:
> 
> My Biblia Hebraica treats Psalm titles as the first verse, indicating 
> biblical canonacity and in line with Hebrew versification.
> 
> Note the following from OSIS doc, OSIS.pdf:
> 
> Appendix B.2.10 titles
> The type attribute on the title element is used to allow special rendering of 
> particular titles, as well as
> searching for particular types of titles in the text.identify the type of 
> note that appears in the text. Note that
> the values for the type attribute must be entered exactly as shown, all 
> others must use the "x-" extension
> mechanism.
> If the user needs to record a type of title in the text that is not covered 
> by these values, please use the OSIS
> attribute extension mechanism, "x-" in front of the name of your value for 
> this attribute.
> .
> .
> psalm Use in the Psalms where what are considered "titles" in the English 
> text are actually numbered
> as verses in the Hebrew text.
> 
> David's point about canonicity is well taken, but we must consider:
> 1. Are we considering canonicity with respect to the NASB as published,
> OR
> 2. Are we considering canonicity with respect to how the NASB publishers saw 
> it, that is that the Scripture text is cannonical. If we make this decision, 
> we are simply electronically duplicating the paper publication.
> 
> IMHO, 2. is the far better choice.
> 
> Hope this helps, and thanks again to all.
> 
> Tom Sullivan
> i...@beforgiven.info
> FAX: 815-301-2835
> -
> 
> On 5/8/20 10:28 AM, David Haslam wrote:
>> One of the subtleties of OSIS is that the canonical attribute is actually 
>> not a theological matter.
>> It’s easy to jump to the wrong conclusion that SWORD treats it as if it was.
>> It’s actually a technical attribute relating to the published work it 
>> represents in digital format.
>> So it can just as well appear in a Commentary module as a Bible module.
>> Anything with canonical=“false” should in theory at least be only because 
>> the marked text was not in the original work.
>> Then the question becomes “What was the original work?”
>> I will leave you to ponder
>> David
>> Sent from ProtonMail Mobile
>> On Fri, May 8, 2020 at 15:09, Karl Kleinpaste > > wrote:
>>> On 5/8/20 10:00 AM, Tom Sullivan wrote:
>>> > because Psalm titles are canonical, front-ends should put a difference
>>> > in display between them and human editor supplied titles.
>>> 
>>> It's a fine idea, but it requires (in the xhtml case) the engine to wrap
>>> such titles in a suitable  so that a CSS control can put it
>>> to use, with appropriate new default render header content for it.
>>> 
>>> ___
>>> 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
>> __
>> This email has been scanned by the Symantec Email Security.cloud service.
>> For more information please visit http://www.symanteccloud.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


___
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 Psalm titles

[DM Smith]

The pre-verse div is a construct by osis2mod. These are milestoned to mark the 
beginning and end of pre-verse material.

DM

> On May 8, 2020, at 8:55 AM, David Haslam  wrote:
> 
> Is this simply because the OSIS file used for module build made use of the 
> milestone form of the div element ?
> 
> SWORD does not support that, IIRC.
> 
> I just looked at the mod2imp dump for the NASB.
> 
> There are 2250 instances of this type of div, each with an sID and an eID.
> 
> Aside: Repeating the type and subType attributes with the eID is also 
> superfluous.
> 
> Troy can look into this, and propose an improvement to the source OSIS.
> 
> Best regards,
> 
> 
> David
> 
> Sent from ProtonMail Mobile
> 
> 
> On Fri, May 8, 2020 at 13:21, Tom Sullivan  > wrote:
>> 
>> Yes, the box is checked.
>> 
>> Note also that diatheke has the same problem.
>> 
>> Tom Sullivan
>> i...@beforgiven.info
>> FAX: 815-301-2835
>> -
>> 
>> On 5/8/20 7:06 AM, Karl Kleinpaste wrote:
>> > On 5/8/20 5:55 AM, Tom Sullivan wrote:
>> >> Xiphos 4.1.0 displays titles for ESV2011, not NASB
>> >
>> > Have you enabled headings in NASB's module options?
>> >
>> > __
>> > This email has been scanned by the Symantec Email Security.cloud service.
>> > For more information please visit http://www.symanteccloud.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
> 
> 
> ___
> 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] NASB Psalm titles

[DM Smith]

osis2mod preserves properly marked Psalm titles before verse 1 as part of that 
verse. Other titles (and other pre-verse content) will either be put in verse 0 
or in verse 1 based on other considerations. This is documented in the wiki for 
osis2mod.

In Him,
DM

> On May 8, 2020, at 10:28 AM, Tom Sullivan  wrote:
> 
> Y'all:
> 
> Thanks David.
> 
> The Psalm titles are considered canonical because they are the Word of God! 
> If Sword does not display them when the user would expect them, that that is 
> monkeying with God's Word and completely unacceptable. The Psalm titles are 
> theologically and exegetically significant.
> 
> Switching off human editor titles should *not* switch off Psalm titles any 
> more than switching off any of the verses of the Psalm would be acceptable.
> 
> So, we have a Sword issue here in addition to a module issue.
> 
> Obviously, there are questions here in terms of presentation of partial 
> Psalms, and decisions must be carefully made. A request for "Ps 5" should 
> always present the title because God put it there. A request for "Ps 5:2-4" 
> need not. But what about "Ps 5:1"? I am OK either way, so long as the user 
> can do "Ps 5.0" or Ps 5:0-1" or something to get it, and it is clearly 
> documented. But probably GUI front ends should display title unless only "Ps 
> 5:1" is requested and the GUI would normally return just that verse. If the 
> GUI normally shows the whole Psalm (perhaps after scrolling up) the title 
> should be there.
> 
> In contrast to GUI front ends, with diatheke, I recognize the problem with 
> versification here, and am not sure what to suggest. Should they be verse 0?
> 
> diatheke should display them above the first verse. But perhaps either a 
> command line option should switch them on or off, or maybe use verse 0?
> 
> In sum here, we have a Sword issue here as well as a module issue.
> 
> Hope this helps, and thanks all.
> 
> Tom Sullivan
> i...@beforgiven.info
> FAX: 815-301-2835
> -
> 
> 
> On 5/8/20 10:04 AM, David Haslam wrote:
>> The difference is that JSword never hides titles with canonical=“true” even 
>> with Headings OFF.
>> SWORD does and always has done.
>> David
>> Sent from ProtonMail Mobile
>> On Fri, May 8, 2020 at 15:00, Tom Sullivan > > wrote:
>>> Karl:
>>> 
>>> I cannot explain the difference between your linked picture and my
>>> results on Xiphos 4.1.0. The problem survived unchecking/rechecking and
>>> reboot.
>>> 
>>> But if you look at my first email, you will note that diatheke does
>>> produce Psalm titles for ESV2011 and KJV, but after the first verse. You
>>> have to ask for verses 1 to 2 or higher. That is an issue in diatheke,
>>> but I can live with that. But I do not get them for NASB via diatheke.
>>> 
>>> So this reinforces my (amateur) guess that the issue is in the module
>>> and the Psalm titles are not being recognized as canonical by front-ends.
>>> 
>>> IMHO, because Psalm titles are canonical, front-ends should put a
>>> difference in display between them and human editor supplied titles.
>>> 
>>> Hope this helps.
>>> 
>>> Thanks all.
>>> 
>>> Tom Sullivan
>>> i...@beforgiven.info
>>> FAX: 815-301-2835
>>> -
>>> 
>>> 
>>> On 5/8/20 9:28 AM, Karl Kleinpaste wrote:
>>> > On 5/8/20 8:21 AM, Tom Sullivan wrote:
>>> >> Yes, the box is checked.
>>> >
>>> > The reason I ask is that I see this just fine in Xiphos.
>>> > http://karl.kleinpaste.org/xiphos/nasb-ps-5-1.png
>>> > (pardon the colors, I do CSS things to make certain stuff really obvious.)
>>> >
>>> > diatheke doesn't produce headers, not even when asked with "-o h".
>>> >
>>> > __
>>> > This email has been scanned by the Symantec Email Security.cloud service.
>>> > For more information please visit http://www.symanteccloud.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
>> __
>> This email has been scanned by the Symantec Email Security.cloud service.
>> For more information please visit http://www.symanteccloud.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
> 
> 

Re: [sword-devel] SWORD search issue / search type multi Word

[DM Smith]

With the underlying lucene mechanism you can set the connector to OR or to AND. 
I believe that OR is the default. With ranked search this works well.

In Him,
DM

> On May 4, 2020, at 4:15 PM, Tobias Klein  wrote:
> 
> Hi,
> 
> I have the impression that the SWORD multi word search is returning some 
> results that actually do not seem to match the search term.
> 
> For example when searching for the term "faith Jesus" in the NASB module I 
> get 86 results.
> 
> The first result that seems invalid is Matthew 9:28:
> 
> 28 When He entered the house, the blind men came up to Him, and Jesus said to 
> them, " “Do you believe that I am able to do this?”" They said to Him, “Yes, 
> Lord.”
> 
> This verse matches only part of the multi word term, namely "Jesus".
> 
> Matthew 9:29 is also returned as a result and this verse interestingly only 
> matches the other part of the term ("faith"):
> 
> 29 Then He touched their eyes, saying, " “It shall be done to you according 
> to your faith.”"
> 
> What is happening here? My assumption would be that only verses containing 
> both parts of the multi word term should be returned if the searchType is 
> multiWord (-2). Is this a bug?
> 
> The code can be found here: 
> https://github.com/tobias-klein/node-sword-interface/blob/master/src/sword_backend/module_search.cpp#L121
>  
> 
> Best regards,
> Tobias
> 
> ___
> 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] Status of OSIS?

[DM Smith]

Can you clarify what you mean by “I’m encoding the entire spec for storage in a 
source form….”?

What has happened so far is that we’ve been responding with the 2006 2.1.1 
version of the OSIS Spec. We host the file at 
https://crosswire.org/osis/OSIS%202.1.1%20User%20Manual%2006March2006.pdf 
. If 
I remember correctly, the PDF is generated from a different document to which 
we don’t have access. If we wish to fix and improve that document, I think we 
should see if we can formally take responsibility for it by contacting Patrick 
Duruasau.

Short of that we’ve been documenting shortcomings in the wiki.

We do require valid OSIS. There have been bugs and shortcomings in the schema. 
I’m the pumpkin keeper of that and have made a few changes that are agreeable 
to this mailing list. We’ve attempted to document that in the wiki. One of the 
considerations is whether the suggested change works with how the SWORD and 
JSword engines understand the spec.

You are right that the wiki is not issue tracker and gets harder to understand 
as more gets added to it. David and I have tried to have the wiki on OSIS be an 
addendum to the spec. And guidance on how to build a SWORD module using it.

Do you have a suggestion on to get from where we are to where you think we 
should be? 

In Him,
DM

> On May 4, 2020, at 3:12 PM, Michael H  wrote:
> 
> David, 
> 
> That page you refer to is the problem that created this email. 
> 
> The page you refer to shouldn't exist like it does.. that information should 
> be going onto a problem ticket system. (Think the 'issue tracker' on the USFM 
> 3 list.  It's searchable and the status of most items is clear, and anything 
> already acted on is already on the official documentation pages.) 
> 
> That collection of pages in its current form provides little information. 
> it's not sorted by status of investigation/implementation, nor by the spec's 
> organization, but rather by the impression of the author as to it's nature.  
> It seems to be a collection of writings, some of which describe real problems 
> that have been acted on already, some that describe misspellings (but can 
> safely be ignored for module creation.), and some that fit into "wishlist" 
> meaning even if they're in the 'bug' category and actually bugs, they aren't 
> affecting what happens today. Each writing in the wiki will have to be 
> processed before I can code. I can't see any clear status marker present so I 
> can sort the already dones from the wishlist. 
> 
> THATS what I'm suggesting/working toward.  I'm encoding the entire spec for 
> storage in a source form, so that implemented bugfixes can be updated into 
> the spec. We should not have to go through megabytes of text to find 3 
> misleading characters in the spec that will break every module someone trying 
> to follow the spec will run into. I've seen enough in the wiki that I'm 
> pretty sure there's at least on issue listed there that is likely to be in 
> that class, but I'm going to have to sort through each and every sentence on 
> each and every page to find them all. 
> 
> 
> 
> On Mon, May 4, 2020 at 1:25 PM David Haslam  > wrote:
> Have you looked at our Wiki page?
> 
> OSIS 211 CR
> 
> It was even edited again today!
> 
> The Bible Technologies Group has not met for years & the original website 
> went AWOL. 
> 
> It may well be the case that CrossWire is the only remaining de facto 
> maintainer of OSIS. 
> 
> Best regards,
> 
> David 
> 
> Sent from ProtonMail Mobile
> 
> 
> On Mon, May 4, 2020 at 19:07, Michael H  > wrote:
>> 
>> I've got 40 works and growing that I've been meaning to look at creating 
>> Sword Modules. All of these are genbooks. Almost 100% currently are works by 
>> Andrew Murray (but the list is much bigger.) 
>> 
>> But, as I try to make sense of the OSIS spec, I'm facing a 2006 spec in not 
>> very well done PDF, and another one with comments, and an xslt file, and a 
>> mountain of comments on the wiki that span from outright errors, to support 
>> gaps, to wishlist. 
>> 
>> What is the status of OSIS? Is there a draft or official source, or even 
>> Crosswire source that we can at least fix typos to? I've started one, just 
>> to turn Appendix F into a real table... but as I read through the wiki, now 
>> it seems I'm going to have to process everything to be able to trust what 
>> I'm reading, and it makes sense that I should be dropping the result 
>> somewhere more official than my google drive. 
>> 
>> If we have permission to host the OSIS spec, do we have permission to bugfix 
>> it (at least the spelling gaps, and fixing the tables of information to be 
>> tabular?) 
> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> 
> 

Re: [sword-devel] Question about backwards compatibility and search index download-ability, especially in relation to low-cost, low-power computers (such as might be in developing countries?)

[DM Smith]

I maintain JSword. We try to maintain backward compatibility with the lowest 
common denominator version of Java on devices that are up to 10 years old for 
computers and 5 years for mobiles. The OS version needs to be vendor supported. 
Android at this point is our boat anchor.

For me the most important backward compatibility is that old module continue to 
work. If an old module is updated then I’m not concerned with the prior version.

The other kind of compatibility is whether a frontend will work with a simple 
recompile with the current engine.

WRT to C++ SWORD, binary compatibility is not that important because linking is 
static. The interface has been backward compatible for over a decade. It still 
supports very old modules.

DM

> On Apr 7, 2019, at 7:20 PM, TS  wrote:
> 
> Hi,
> 
>  To put it simply, I was wondering what is Crosswire's or perhaps Troy's 
> position on backwards compatibility. I thought that the desired goal, if 
> possible, was for Sword to be able to run on as many devices as possible. 
> However, recently I've seen in mailing list postings or emails that perhaps I 
> was mistaken? It's also occurred to me that perhaps my impression is with 
> regards to the Sword engine only and that this does not include front-end 
> backwards compatibility? So, I'd appreciate some clarity on the matter.
>  In specific, I'm asking this question because in the past, I know that 
> organizations have made projects to create simple, low-cost computers (such 
> as OLPC). I know that the first gen OLPC was made around the same time as the 
> first iPhone and had roughly similar specs (if I'm interpreting the specs 
> correctly). It was the size of a small laptop, but did not have enough 
> processing power to play videos. This type of computer was created for 
> developing countries. So, if computers such as these exist enough, then it 
> also seems to me that they may have problems generating search indexes the 
> same way that the first iPhone did. Therefore, I'm wondering if perhaps there 
> is still a good reason for the search indexes to be downloadable?
>  On the other hand, David's post back in Feb. 16,2019, titled 
> "[sword-devel] ParaTExt Lite (Android OS)", contained a link to an article 
> about the development of ParaText Lite. This article seemed to suggest that 
> smartphones have penetrated even the most remote of places. So, it makes me 
> wonder if the situation of people (such as those in developing countries) 
> being stuck with old computers is perhaps not very large? I guess I don't 
> know either way, but since nobody here (I think?) has brought it up and it 
> would possibly be impacted by search indexes download-ability, this all seems 
> like something worthwhile to ask/talk about.
>  (Btw, it seems to me that Android would probably be the dominant 
> smartphone OS. I don't want to derail this post explaining "why", so it may 
> be sufficient enough to mention that ParaText Lite was only made for Android 
> OS.)
> (Also, the current gen laptop of OLPC does have enough power, I think. I 
> would also imagine that the current Raspberry Pi computers have enough power 
> as well.)
> 
> -TS
> 
> -- 
> - Timothy
> 
> 
> ___
> 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] Osis Psalms canonical titles

[DM Smith]

In the Bible, some translations the Psalm titles stand before verse 1. This is 
how the KJV does it. Other translations have it as verse 1.

osis2mod tries to identify whether a title that stands before verse 1 should be 
a chapter title (i.e. verse 0) or should be a verse title (i.e. verse 1). And 
it marks up titles in a fashion that SWORD engine expects. Dumping the module 
using mod2imp, will show how well or badly this was done.

I think the problem here is the order of elements. So rather than … use ….

The attribute canonical=“true” is supposed to tell the SWORD engine to always 
show the title. I think there are still problems with that. So, try turning 
Headers on, when you don’t see them.

In Him,
DM

> On Mar 31, 2019, at 5:13 AM, Cyrille  wrote:
> 
> Hello,
> I'm working on a text with canonical Psalms titles. When I convert it from 
> usfm to osis I have this result:
> 
> 
> Invocazione mattutina del giusto perseguitato
> 
> 
>  osisID="Ps.3.1" n="1"/>Salmo di Davide quando fuggiva il figlio 
> Assalonne.
> 
>   Signore, 
> quanti sono i miei oppressori!
>   Molti contro di me insorgono. 
> 
> Is it correct? Because Bibletime doesn't display it 
> .
> 
> ___
> 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] Question regarding special markup in Psalms and SWModule::stripText

[DM Smith]

The filters don’t care that the tags are repurposed. The GBFPlain documents 
 as tense.

That they were and that you know what they mean is perhaps helpful.

In Him,
DM

> On Mar 18, 2019, at 10:56 AM, David Haslam  wrote:
> 
> The GBF tags in GerSch that we’re discussing have nothing whatsoever to do 
> with Strongs or Tense. 
> 
> They are quite clearly all used for recording the original references before 
> the text was squished in 2006 to the only v11n that SWORD supported at the 
> beginning. 
> 
> To satisfy my own curiosity, I have since developed a bespoke TextPipe filter 
> to Restore the IMP file to the original v11n. 
> 
> Yet to try it as an input for imp2vs to see which v11n gives the best match. 
> 
> Best regards,
> 
> David
> 
> Sent from ProtonMail Mobile
> 
> 
> On Mon, Mar 18, 2019 at 13:49, DM Smith  <mailto:dmsm...@crosswire.org>> wrote:
>> 
>> I took a look at the GBF Plain filter. It does recognize these and is 
>> specifically handling them.
>> 
>> Basically the plain filter has a little bit of markup:
>> New lines for  (this is a hack), , .
>> It will put notes stuff between this is a note> Greek Strongs Numbers , Hebrew Strongs Numbers  and Tense 
>>  become .
>> 
>> Everything else is passed as text.
>> 
>> In Him,
>>  DM
>> 
>>> On Mar 18, 2019, at 8:51 AM, Troy A. Griffitts >> <mailto:scr...@crosswire.org>> wrote:
>>> 
>>> This likely means that our GBFPlain filter doesn't recognize these GBF tags 
>>> and ignores them this should be a simple fix in the filter.
>>> 
>>> http://crosswire.org/svn/sword/trunk/src/modules/filters/gbfplain.cpp 
>>> <http://crosswire.org/svn/sword/trunk/src/modules/filters/gbfplain.cpp>
>>> 
>>> 
>>> 
>>> On March 18, 2019 12:12:59 AM MST, Tobias Klein >> <mailto:cont...@tklein.info>> wrote:
>>> I tried to initialize my SWMgr object like this:
>>> 
>>> mgr = new SWMgr(new MarkupFilterMgr(FMT_PLAIN));
>>> 
>>> Yet the results are still the same for the GerSch module as described 
>>> earlier.
>>> 
>>> Best regards,
>>> Tobias
>>> 
>>> 
>>> On 17.03.19 19:46, Troy A. Griffitts wrote:
>>>> Hi Tobias. SWORD renders these tags for you if the planets are aligned. 
>>>> When you create your SWMgr, you tell it what "Render" markup you would 
>>>> like. We highly recommend XHTML. This will tell the SWMgr factory class to 
>>>> construct SWModule oblects with all the necessary filters added to produce 
>>>> your requested render markup when you call SWModule::renderText. The 
>>>> SWModule::stripText will also render plaintext output because SWMgr will 
>>>> add appropriate filters (as Greg has said GBFPlain, in this case). If the 
>>>> old GBF German Bible module you are using is made correctly, its .conf 
>>>> file will include a SourceType=GBF. This will allow SWMgr to pick the 
>>>> right filters to add. You shouldn't need to add any manually.
>>>> 
>>>> You can find examples in the source under: sword/examples
>>>> 
>>>> Here's a good one to steal from which contains most of the coded needed to 
>>>> write frontend display code.
>>>> 
>>>> http://crosswire.org/svn/sword/trunk/examples/tasks/parallelbibles.cpp 
>>>> <http://crosswire.org/svn/sword/trunk/examples/tasks/parallelbibles.cpp>
>>>> 
>>>> 
>>>> 
>>>> On March 17, 2019 10:45:34 AM MST, Tobias Klein  
>>>> <mailto:cont...@tklein.info> wrote:
>>>> On 17.03.19 18:38, Greg Hellings wrote:
>>>>  You might need to add an instance of the GBFPlain class to the filter
>>>>  set before calling for stripText. It is specifically crafted to strip
>>>>  the tags you're talking about.
>>>> 
>>>>  In general, you'll want to add a Plain object to the filter
>>>>  set for any module you're processing to plain text, where  can
>>>>  be picked up by a query to the conf for the given module. Classes
>>>>  should exist for GBF, OSIS, TEI, and ThML source formatted text.
>>>> 
>>>> Thanks, makes sense.
>>>> 
>>>> Before figuring out the details myself - can you point me to any code
>>>> example already existing? I think I once tried to add the GBFPlain class
>>>> to the filter set, but somehow it didn't 

Re: [sword-devel] Question regarding special markup in Psalms and SWModule::stripText

[DM Smith]

I took a look at the GBF Plain filter. It does recognize these and is 
specifically handling them.

Basically the plain filter has a little bit of markup:
New lines for  (this is a hack), , .
It will put notes stuff between this is a note, Hebrew Strongs Numbers  and Tense  
become .

Everything else is passed as text.

In Him,
DM

> On Mar 18, 2019, at 8:51 AM, Troy A. Griffitts  wrote:
> 
> This likely means that our GBFPlain filter doesn't recognize these GBF tags 
> and ignores them this should be a simple fix in the filter.
> 
> http://crosswire.org/svn/sword/trunk/src/modules/filters/gbfplain.cpp 
> 
> 
> 
> 
> On March 18, 2019 12:12:59 AM MST, Tobias Klein  wrote:
> I tried to initialize my SWMgr object like this:
> 
> mgr = new SWMgr(new MarkupFilterMgr(FMT_PLAIN));
> 
> Yet the results are still the same for the GerSch module as described earlier.
> 
> Best regards,
> Tobias
> 
> 
> On 17.03.19 19:46, Troy A. Griffitts wrote:
>> Hi Tobias. SWORD renders these tags for you if the planets are aligned. When 
>> you create your SWMgr, you tell it what "Render" markup you would like. We 
>> highly recommend XHTML. This will tell the SWMgr factory class to construct 
>> SWModule oblects with all the necessary filters added to produce your 
>> requested render markup when you call SWModule::renderText. The 
>> SWModule::stripText will also render plaintext output because SWMgr will add 
>> appropriate filters (as Greg has said GBFPlain, in this case). If the old 
>> GBF German Bible module you are using is made correctly, its .conf file will 
>> include a SourceType=GBF. This will allow SWMgr to pick the right filters to 
>> add. You shouldn't need to add any manually.
>> 
>> You can find examples in the source under: sword/examples
>> 
>> Here's a good one to steal from which contains most of the coded needed to 
>> write frontend display code.
>> 
>> http://crosswire.org/svn/sword/trunk/examples/tasks/parallelbibles.cpp 
>> 
>> 
>> 
>> 
>> On March 17, 2019 10:45:34 AM MST, Tobias Klein  
>>  wrote:
>> On 17.03.19 18:38, Greg Hellings wrote:
>>  You might need to add an instance of the GBFPlain class to the filter 
>>  set before calling for stripText. It is specifically crafted to strip 
>>  the tags you're talking about.
>> 
>>  In general, you'll want to add a Plain object to the filter 
>>  set for any module you're processing to plain text, where  can 
>>  be picked up by a query to the conf for the given module. Classes 
>>  should exist for GBF, OSIS, TEI, and ThML source formatted text.
>> 
>> Thanks, makes sense.
>> 
>> Before figuring out the details myself - can you point me to any code 
>> example already existing? I think I once tried to add the GBFPlain class 
>> to the filter set, but somehow it didn't work as expected? Maybe I used 
>> it wrongly ...
>> 
>> Best regards,
>> Tobias
>> 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.
> 
> -- 
> 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

___
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] Question regarding special markup in Psalms and SWModule::stripText

[DM Smith]

Plain GBFPlain is probably not the filter that PocketSword uses. Probably 
GBFHtmlHRef or GBFHtml. No reason to expect that these independent pieces of 
software would work the same.

In Him,
DM

> On Mar 18, 2019, at 8:58 AM, David Haslam  wrote:
> 
> Hi Troy,
> 
> That does not seem consistent with the observation that PocketSword v 1.4.8 
> renders them suitably. See my earlier reply. 
> 
> Unless maybe a new bug has occurred in SWORD since PS 1.4.8 was released and 
> that was made with SWORD 1.7.x
> 
> Or perhaps if different compiler directives were in play. 
> 
> Best regards 
> 
> David
> 
> Sent from ProtonMail Mobile
> 
> 
> On Mon, Mar 18, 2019 at 12:51, Troy A. Griffitts  > wrote:
>> 
>> This likely means that our GBFPlain filter doesn't recognize these GBF tags 
>> and ignores them this should be a simple fix in the filter.
>> 
>> http://crosswire.org/svn/sword/trunk/src/modules/filters/gbfplain.cpp 
>> 
>> 
>> 
>> 
>> On March 18, 2019 12:12:59 AM MST, Tobias Klein  wrote:
>> I tried to initialize my SWMgr object like this:
>> 
>> mgr = new SWMgr(new MarkupFilterMgr(FMT_PLAIN));
>> 
>> Yet the results are still the same for the GerSch module as described 
>> earlier.
>> 
>> Best regards,
>> Tobias
>> 
>> 
>> On 17.03.19 19:46, Troy A. Griffitts wrote:
>>> Hi Tobias. SWORD renders these tags for you if the planets are aligned. 
>>> When you create your SWMgr, you tell it what "Render" markup you would 
>>> like. We highly recommend XHTML. This will tell the SWMgr factory class to 
>>> construct SWModule oblects with all the necessary filters added to produce 
>>> your requested render markup when you call SWModule::renderText. The 
>>> SWModule::stripText will also render plaintext output because SWMgr will 
>>> add appropriate filters (as Greg has said GBFPlain, in this case). If the 
>>> old GBF German Bible module you are using is made correctly, its .conf file 
>>> will include a SourceType=GBF. This will allow SWMgr to pick the right 
>>> filters to add. You shouldn't need to add any manually.
>>> 
>>> You can find examples in the source under: sword/examples
>>> 
>>> Here's a good one to steal from which contains most of the coded needed to 
>>> write frontend display code.
>>> 
>>> http://crosswire.org/svn/sword/trunk/examples/tasks/parallelbibles.cpp 
>>> 
>>> 
>>> 
>>> 
>>> On March 17, 2019 10:45:34 AM MST, Tobias Klein  
>>>  wrote:
>>> On 17.03.19 18:38, Greg Hellings wrote:
>>>  You might need to add an instance of the GBFPlain class to the filter
>>>  set before calling for stripText. It is specifically crafted to strip
>>>  the tags you're talking about.
>>> 
>>>  In general, you'll want to add a Plain object to the filter
>>>  set for any module you're processing to plain text, where  can
>>>  be picked up by a query to the conf for the given module. Classes
>>>  should exist for GBF, OSIS, TEI, and ThML source formatted text.
>>> 
>>> Thanks, makes sense.
>>> 
>>> Before figuring out the details myself - can you point me to any code
>>> example already existing? I think I once tried to add the GBFPlain class
>>> to the filter set, but somehow it didn't work as expected? Maybe I used
>>> it wrongly ...
>>> 
>>> Best regards,
>>> Tobias
>>> 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.
>> 
>> -- 
>> 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

___
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] Color in osis

[DM Smith]

> On Mar 17, 2019, at 10:07 AM, Karl Kleinpaste  wrote:
> 
> However, for this purpose, the deeper problem is that Sword erroneously 
> generates self-closing  tags, which do not work. Search "html 
> self-closing div" and discover all the conflicting noise over it. My solution 
> in Xiphos was simply to obliterate these tags in introductory material; they 
> have no visual manifestation and I don't know why the XHTML filters pass them 
> in the 1st place. They look like
> 
> 
> 
> and they caused my .introMaterial change to bleed throughout the chapter 
> until I implemented the obliteration. See 
> https://github.com/crosswire/xiphos/issues/845 
> 

I don’t know why the OSIS->XHTML renderer passes the self-closing divs from 
OSIS to XHTML. I do know why they are that way in OSIS. OSIS’s schema allows a 
div to be milestoned, meaning it has an sID or an eID and is self-closing.

At this time … is the only container div in the OSIS 
document that osis2mod preserves. All others are converted to milestoned divs.

SWORD’s OSIS->XHTML filter can be changed to output OSIS’s milestoned, 
self-closed divs as empty but not self closing, e.g. .

As to why they are passed, they can be styled with top and bottom margin and 
padding.

The fundamental reason is that a module defines the addressable verse as the 
presentation unit. This notion of a verse is more than just the marked up 
content of the verse but also includes all the markup between verses. So that 
unit has to be well-formed xml. The only way is for structural elements that 
span verses to be milestoned when the module is built.

The largest front-end use case is that a chapter is displayed all at once. In 
this case, the chapter needs to be well-formed and it could be composed of 
verses that are not well-formed.

The other front-end use case is the rendering of search hits, where a search 
hit is an individual verse. In this case, it needs to be well-formed or 
presented differently.

JSword uses an XML parser to parse each verse as XML to build the DOM for it. 
An XML parser requires well-formed XML to parse.

In Him,
DM

___
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] XHTML vs HTML (was: Color in osis)

[DM Smith]

> On Mar 17, 2019, at 8:48 PM, Nathan Phillip Brink 
>  wrote:
> 
> Hi Karl,
> 
> On Sun, Mar 17, 2019 at 07:47:22PM -0400, Karl Kleinpaste wrote:
>> On 3/17/19 2:44 PM, Nathan Phillip Brink wrote:
>>> It sounds like you’re trying to render XHTML using an HTML parser.
>> If there is a way to make WebKit /*not*/ operate in an XHTML mode, I'm
>> not aware of it.
> 
> Sorry, I may be going a bit off-topic by pursuing this.
> 
> I am quite sure you are running WebKit in HTML mode and not XHTML
> mode.
> 
> I don’t have an easy way to directly test WebKit per se. But I can
> demonstrate what I am describing and have tested it with Midori-0.5.11
> which claims to be WebKit. The following also works in any modern
> browser (IE, Edge, Firefox, Chrome, or Mobile Safari to name a few).
> 
> I have defined CSS rules which set anything with a class of div2 to be
> green and used it for both of the following files. In each file, I
> have text, an empty div div1, more text, an empty div div2, and more
> text. Each empty div uses the self-closing syntax “”:
> 
> HTML: http://cdn.ohnopub.net/cdn/binki/sword-devel/xhtml-vs-html/index.html
> 
> XHTML/XML: 
> http://cdn.ohnopub.net/cdn/binki/sword-devel/xhtml-vs-html/index.xhtml 
> 

I noticed that not only did you have the xml pre-processor as the first line

But you also had the namespace declaration for xhtml.
http://www.w3.org/1999/xhtml”>

Is the later necessary to put the parser into XML mode?

Are either really needed if you are delivering it with a 
Content-Type:text/xhtml?

In Him,
DM

> 
> If you visit the first link, then WebKit is reading the markup using
> an HTML parser. This causes the behavior you describe of self-closed
> “” tags being treated as equivalent to opening “”
> tag. The resulting document tree has the trailing text inside div2,
> making it green. If you visit the second link, then WebKit is reading
> the markup in XHTML (XML) mode because Content-Type is set. This
> causes it to parse it as an XML document and then render the resulting
> DOM as a second step. The resulting document tree has the trailing
> text after div2 as a direct descendent of body. Thus the text is not
> part of div2 and does not become green.
> 
> The HTML parser is special and you are seeing the effects of using an
> HTML parser to parse XHTML instead of using an XML or XHTML parser to
> parse XHTML.
> 
> HTML does not have a self-closing tag syntax. For elements which would
> normally be self-closed in XML/XHTML such as br and link, it relies
> instead on a list of void elements which the parser itself knows
> about: https://www.w3.org/TR/html/syntax.html#void-elements . Whenever
> it encounters one of these elements, it immediately closes it out in
> the document tree and doesn’t give it any children.
> 
> The HTML parser is required to basically ignore the forward-slash in
> “” or “”. This was intended to allow websites to slowly
> transition to XHTML if proper care was taken. The result is that
> “” will be treated the same as “” when using an HTML
> parser to parse the file. See rule 6 regarding SOLIDUS at
> https://www.w3.org/TR/html/syntax.html#start-tags and 0x2F under step
> 4 at https://www.w3.org/TR/html/syntax.html#get-an-attribute .
> 
> If you want to get the expected results, you should either process the
> XHTML into HTML before feeding it to WebKit or set WebKit to parse the
> file as XHTML instead of HTML.
> 
> -- 
> binki
> 
> Don’t forget to check for missing or extraneous apostrophes!
> ___
> 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] Color in osis

[DM Smith]

JSword has a different mechanism than SWORD to produce HTML. JSword has a bug 
that prevents it from reading a CSS file, but JSword supplies the mechanism to 
read the CSS.

For SWORD, the different renderers produce different output. Unless all the 
frontends have settled on the same renderer, don’t expect them to be able to 
use the same CSS file. Also, I’m not sure if it is the engine or the frontend 
that supplies the mechanism to read the CSS.

And CSS that might be appropriate for a desktop application might not be 
appropriate for a mobile application. It’s likely that color might be something 
that works across platforms.

In Him,
DM

> On Mar 17, 2019, at 7:18 AM, Cyrille  wrote:
> 
> I found the solution
> We need to use "subsectionNUMBER" and after modify the css like that:
> .subSection1 { -webkit-column-count: 1 ; background-color:Yellow ; 
> color:violet ; text-align: center; }
> .subSection2 { -webkit-column-count: 1 ; background-color:Yellow ; 
> color:white ; text-align: center; }
> 
> But it is very important to place well the tags , the problem with the 
> bible module, is that the tag are not in the good place for instance the tags 
> doesn't close a title but all a section (with the part of the text). Then the 
> css have difficulties to read well the file.
> 
> Il 17/03/2019 10:10, David Haslam ha scritto:
>> Suggest you approach Karl directly for further help. 
>> 
>> I’m not an expert on CSS. 
>> 
>> David
>> 
>> Sent from ProtonMail Mobile
>> 
>> 
>> On Sun, Mar 17, 2019 at 09:06, Cyrille > > wrote:
>>> 
>>> 
>>> 
>>> Il 17/03/2019 09:58, David Haslam ha scritto:
 The usual way to implement different colours and other styles of text 
 would be to provide an ancillary CSS file for use by the rendering engine. 
 
 In the past, Karl has provided a few examples for how this can be done 
 with Xiphos. 
>>> He I remember, but it doesn't work very well its operation seems random 
>>> especially with the levels of titles. It is possible that I did not manage 
>>> correctly to use it. A little help wouldn't be refused.
 
 
 Red letters for words of Jesus are part of how the SWORD engine renders 
 that particular OSIS construction. 
 
 Best regards,
 
 David
 
 Sent from ProtonMail Mobile
 
 
 On Sun, Mar 17, 2019 at 08:43, Cyrille >>> > wrote:
> 
> Hello,
> I'm working on a devotional catholic calendar. I would like to use
> colour for some words or for titles.  Is it possible? The only way I
> found is to use  for the read ;)
> I would like also to know if it is possible to use different style of
> titles like title 1 or title 2...
> Thank you for help.
> 
> ___
> 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
> 
> ___
> 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] Platform for the distribution of non-free Sword Modules

[DM Smith]

For the parser built into Java, the schema (BTW, a nitpick, it’s not a DTD) 
needs to be local. It will not go across the network to retrieve it.

DM Smith

> On Mar 15, 2019, at 10:36 AM, David Haslam  wrote:
> 
> Ah - but you do have to somewhere have an accessible copy of the DTD file. 
> 
> You can change its path to something else online (CrossWire or eBible) or 
> (faster still) somewhere local and validation will work. 
> 
> But you have to first know that this is required, especially if you use a 
> conversion script that uses the original path for the schema. 
> 
> As Tom explains, the other instances of the URL are not used for remote 
> access. 
> 
> David
> 
> Sent from ProtonMail Mobile
> 
> 
> On Fri, Mar 15, 2019 at 14:26, Tom Sullivan  <mailto:i...@beforgiven.info>> wrote:
>> 
>> Y'all:
>> 
>> If this question involves the use of that address www.bibletechnologies.net
>> with respect to XML and validation of an XML file, please note that it
>> has been a point of general confusion for XML users, but the address is
>> only a unique identifier. There is no need for any parser or validator
>> to actually access that URL. This is a rather obscure point.
>> 
>> If the question is otherwise, sorry for another email.
>> 
>> Tom Sullivan
>> i...@beforgiven.info
>> FAX: 815-301-2835
>> -
>> 
>> 
>> On 3/15/19 10:11 AM, David Haslam wrote:
>> > As regards the BibleTech conference.
>> >
>> > Much though I’d love to come to something I’ve never been to, there are
>> > personal circumstances preventing it this year.
>> >
>> > If Troy does attend, please can something be done about the permanent
>> > timeout that occurs for the domain specified in the OSIS header!
>> >
>> > http://www.bibletechnologies.net/
>> >
>> > This still needs fixing, even if the OSIS committee no longer convenes.
>> >
>> > Who is able to unravel this ?
>> >
>> > Best regards,
>> >
>> > David
>> >
>> > Sent from ProtonMail Mobile
>> >
>> >
>> > On Thu, Mar 14, 2019 at 00:44, Troy A. Griffitts > > <mailto:scr...@crosswire.org>> wrote:
>> >>
>> >> To piggy-back on what Peter is saying...  from the last few emails, I
>> >> am not sure everyone is on the same page...
>> >>
>> >> Michael Paul Johnson already converts the free DBL texts to SWORD
>> >> modules automatically and makes them available for all of our software
>> >> (the ebible.org remote installation source).  As Peter says, I don't
>> >> believe an automated conversion of USX to OSIS is ideal, but it works
>> >> well enough to mostly read the text.  I think Michael has done the
>> >> best job he can do with an automated conversion of USX to OSIS to
>> >> SWORD module.
>> >>
>> >> My previous encouragement to proceed to pursue one Bible of interest
>> >> with a publisher was not an encouragement to do this with the intent
>> >> to start a 3rd party company to sell content for CrossWire software
>> >> for that publisher.  My encouragement was to follow our policy and
>> >> negotiate as a volunteer of CrossWire and explain CrossWire's policy
>> >> to the publisher and offer to do the work and let the publisher sell
>> >> their unlock key.  To be clear, I would discourage anyone from
>> >> pursuing an effort to start another organization to become a middleman
>> >> selling publisher data for CrossWire software.  There are very good
>> >> reasons we are a non-income organization and it has served us well.
>> >> It removes jealousy from any individual making money from the
>> >> collaboration of so many.  I would make very clear to any publisher we
>> >> speak with that we discourage and do not endorse any organization who
>> >> wishes to sell that publishers content for CrossWire software, other
>> >> than the publisher themselves.  To repeat, I am not against modern
>> >> content being sold for CrossWire software.  We have spent much effort
>> >> into facilitating this for publishers and have a plan for them which
>> >> they have been happy to follow.  Summarily, in my experience over the
>> >> past 5 years, any publisher I have pursued has been willing to take
>> >> advantage of our current policy, as I have explained.  They are happy
>> >> to sell their own content.  They are surpr

Re: [sword-devel] CrossWire repos?

[DM Smith]

The URL that PocketSword uses https://ftp.crosswire.org/ftpmirror/pub/sword/raw 
<https://ftp.crosswire.org/ftpmirror/pub/sword/raw> has no problems.

DM 

> On Mar 6, 2019, at 1:34 PM, David Haslam  wrote:
> 
> Did DM find out anything?
> 
> David
> 
> Sent from ProtonMail Mobile
> 
> 
> On Fri, Mar 1, 2019 at 13:43, DM Smith  <mailto:dmsm...@crosswire.org>> wrote:
>> 
>> I’ll look at the server this weekend to see if I can see a problem there. 
>> 
>> It’s not the certificate. 
>> 
>> — DM Smith
>> From my phone. Brief. Weird autocorrections. 
>> 
>> On Mar 1, 2019, at 6:35 AM, David Haslam > <mailto:dfh...@protonmail.com>> wrote:
>> 
>>> Not just one device. 
>>> 
>>> My wife & I each have an iPad Mini as well as an iPhone. 
>>> 
>>> David
>>> 
>>> Sent from ProtonMail Mobile
>>> 
>>> 
>>> On Fri, Mar 1, 2019 at 11:10, Tuomas Airaksinen 
>>> mailto:tuomas.airaksi...@gmail.com>> wrote:
>>>> 
>>>> Is this reproducible with other devices with PocketSword? Or only on this 
>>>> one device?
>>>> 
>>>> Best regards, 
>>>> Tuomas
>>>> 
>>>> pe 1. maalisk. 2019 klo 13.08 David Haslam (dfh...@protonmail.com 
>>>> <mailto:dfh...@protonmail.com>) kirjoitti:
>>>> The symptom is that the download process indicator shows no progress and 
>>>> then suddenly shows Done. Weird!
>>>> 
>>>> How do we find root cause?
>>>> 
>>>> David
>>>> 
>>>> Sent from ProtonMail Mobile
>>>> 
>>>> 
>>>> On Thu, Feb 28, 2019 at 13:40, David Haslam >>> <mailto:dfh...@protonmail.com>> wrote:
>>>>> 
>>>>> Me too with Xiphos on Windows 7.
>>>>> 
>>>>> So why all of a sudden has it stopped working for PocketSword?
>>>>> 
>>>>> David
>>>>> 
>>>>> Sent from ProtonMail Mobile
>>>>> 
>>>>> 
>>>>> On Thu, Feb 28, 2019 at 10:23, Daniel Glassey >>>> <mailto:dglas...@gmail.com>> wrote:
>>>>>> 
>>>>>> I just tried xiphos and it installed one OK.
>>>>>> 
>>>>>> Regards,
>>>>>> Daniel
>>>>>> 
>>>>>> On Thu, Feb 28, 2019 at 9:59 AM David Haslam >>>>> <mailto:dfh...@protonmail.com>> wrote:
>>>>>> >
>>>>>> > That may simply reflect the different protocols used by JSword vs 
>>>>>> > SWORD for module install.
>>>>>> >
>>>>>> > Yet to try with Xiphos.
>>>>>> >
>>>>>> > David
>>>>>> >
>>>>>> > Sent from ProtonMail Mobile
>>>>>> >
>>>>>> >
>>>>>> > On Thu, Feb 28, 2019 at 09:14, Tuomas Airaksinen 
>>>>>> > mailto:tuomas.airaksi...@gmail.com>> 
>>>>>> > wrote:
>>>>>> >
>>>>>> > Just checked that with And Bible I can install modules from crosswire.
>>>>>> >
>>>>>> > Best regards,
>>>>>> > Tuomas
>>>>>> >
>>>>>> > to 28. helmik. 2019 klo 10.29 David Haslam (dfh...@protonmail.com 
>>>>>> > <mailto:dfh...@protonmail.com>) kirjoitti:
>>>>>> >>
>>>>>> >> From yesterday or before, I cannot install any module from our repos 
>>>>>> >> into PocketSword.
>>>>>> >>
>>>>>> >> Is there an outage or is it a certificate expired?
>>>>>> >>
>>>>>> >> I can still install modules from eBible.org <http://ebible.org/> and 
>>>>>> >> Xiphos, so it’s not due to anything in the latest iOS 12.1.4 release.
>>>>>> >>
>>>>>> >> David
>>>>>> >>
>>>>>> >> Sent from ProtonMail Mobile
>>>>>> >> ___
>>>>>> >> sword-devel mailing list: sword-devel@crosswire.org 
>>>>>> >> <mailto:sword-devel@crosswire.org>
>>>>>> >> http://www.crosswire.org/mailman/listinfo/sword-devel 
>>>>&

Re: [sword-devel] CrossWire repos?

[DM Smith]

I’ll look at the server this weekend to see if I can see a problem there. 

It’s not the certificate. 

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Mar 1, 2019, at 6:35 AM, David Haslam  wrote:
> 
> Not just one device. 
> 
> My wife & I each have an iPad Mini as well as an iPhone. 
> 
> David
> 
> Sent from ProtonMail Mobile
> 
> 
>> On Fri, Mar 1, 2019 at 11:10, Tuomas Airaksinen 
>>  wrote:
>> Is this reproducible with other devices with PocketSword? Or only on this 
>> one device?
>> 
>> Best regards, 
>> Tuomas
>> 
>> pe 1. maalisk. 2019 klo 13.08 David Haslam (dfh...@protonmail.com) kirjoitti:
>>> The symptom is that the download process indicator shows no progress and 
>>> then suddenly shows Done. Weird!
>>> 
>>> How do we find root cause?
>>> 
>>> David
>>> 
>>> Sent from ProtonMail Mobile
>>> 
>>> 
>>>> On Thu, Feb 28, 2019 at 13:40, David Haslam  wrote:
>>>> Me too with Xiphos on Windows 7.
>>>> 
>>>> So why all of a sudden has it stopped working for PocketSword?
>>>> 
>>>> David
>>>> 
>>>> Sent from ProtonMail Mobile
>>>> 
>>>> 
>>>>> On Thu, Feb 28, 2019 at 10:23, Daniel Glassey  wrote:
>>>>> I just tried xiphos and it installed one OK.
>>>>> 
>>>>> Regards,
>>>>> Daniel
>>>>> 
>>>>> On Thu, Feb 28, 2019 at 9:59 AM David Haslam  
>>>>> wrote:
>>>>> >
>>>>> > That may simply reflect the different protocols used by JSword vs SWORD 
>>>>> > for module install.
>>>>> >
>>>>> > Yet to try with Xiphos.
>>>>> >
>>>>> > David
>>>>> >
>>>>> > Sent from ProtonMail Mobile
>>>>> >
>>>>> >
>>>>> > On Thu, Feb 28, 2019 at 09:14, Tuomas Airaksinen 
>>>>> >  wrote:
>>>>> >
>>>>> > Just checked that with And Bible I can install modules from crosswire.
>>>>> >
>>>>> > Best regards,
>>>>> > Tuomas
>>>>> >
>>>>> > to 28. helmik. 2019 klo 10.29 David Haslam (dfh...@protonmail.com) 
>>>>> > kirjoitti:
>>>>> >>
>>>>> >> From yesterday or before, I cannot install any module from our repos 
>>>>> >> into PocketSword.
>>>>> >>
>>>>> >> Is there an outage or is it a certificate expired?
>>>>> >>
>>>>> >> I can still install modules from eBible.org and Xiphos, so it’s not 
>>>>> >> due to anything in the latest iOS 12.1.4 release.
>>>>> >>
>>>>> >> David
>>>>> >>
>>>>> >> Sent from ProtonMail Mobile
>>>>> >> ___
>>>>> >> 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
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > T: Tuomas
>>>>> >
>>>>> >
>>>>> >
>>>>> > ___
>>>>> > 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
>> 
>> 
>> -- 
>> T: Tuomas
> 
> 
> ___
> 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] InstallSize

[DM Smith]

Same answer. No punctuation. No other scripts (e.g. arabic). Just a sequence of 
0-9.

JSword uses it in its install manager to build a progress meter.

BTW, In C the common routine is atoi, which stops on the first non-digit. So 
your example would come back as 1.

> On Feb 23, 2019, at 2:24 PM, David Haslam  wrote:
> 
> Typo correction.  
> 
> Both separators should have been keyed as a comma. 
> 
>> InstallSize=1,744,408
> 
> 
> Sent from ProtonMail Mobile
> 
> 
> On Sat, Feb 23, 2019 at 19:21, DM Smith  <mailto:dmsm...@crosswire.org>> wrote:
>> 
>> JSword would. It uses a parser to convert it from a string to an integer and 
>> it doesn’t understand that format.
>> 
>> > On Feb 23, 2019, at 10:00 AM, David Haslam  wrote:
>> >
>> > Would SWORD baulk if the InstallSize key contained commas as thousands 
>> > separators? e.g.
>> >
>> > InstallSize=1,744.408
>> >
>> > David
>> >
>> > Sent from ProtonMail Mobile
>> > ___
>> > 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

Re: [sword-devel] InstallSize

[DM Smith]

JSword would. It uses a parser to convert it from a string to an integer and it 
doesn’t understand that format.

> On Feb 23, 2019, at 10:00 AM, David Haslam  wrote:
> 
> Would SWORD baulk if the InstallSize key contained commas as thousands 
> separators? e.g.
> 
> InstallSize=1,744.408
> 
> David
> 
> Sent from ProtonMail Mobile
> ___
> 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] OSIS files with Tables and Nesting warnings from osis2mod

[DM Smith]

The problem of a table per row is that cell widths may vary from one row to the 
next.

In Him,
DM

> On Feb 19, 2019, at 3:15 AM, ref...@gmx.net wrote:
> 
> I think Michael's advice might be sound. 
> 
> Which texts are set in this way?
> 
> I presume stuff like the population counts in Exodus etc? Or genealogy?
> 
> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
> 
> 
>  Original Message 
> Subject: Re: [sword-devel] OSIS files with Tables and Nesting warnings from   
> osis2mod
> From: Michael H 
> To: SWORD Developers' Collaboration Forum 
> CC: 
> 
> 
> In usfm, and paratext, each row of a table is independent. That is, several 
> separate "paragraphs" that start \tr are displayed in a grid form, but each 
> row (\tr) is treated separately. 
> 
> As you approach 'tables' in OSIS, I think you'll find that you won't have a 
> problem if you consider this the same way, each row is it's own table. 
> 
> On Mon, Feb 18, 2019 at 4:54 PM DM Smith  <mailto:dmsm...@crosswire.org>> wrote:
> When ever a non-milestonable construct is not wholly contained in a verse, it 
> will not work as a SWORD module in all contexts.
> 
> From a module perspective, a verse is what is stored as a verse. It includes 
> all the content between what we know as verses, such as titles, sections, 
> paragraphs.
> 
> Basic reason is that modules are verse oriented. Each verse has to be able to 
> display in isolation. When a verse is not well formed XML, then it cannot.
> 
> We recommend that authors of OSIS see the major constructs of a module to be 
> Books, Chapters, Sections and Paragraphs, expressed as containers. And that 
> verses are milestoned.
> 
> osis2mod will reverse this and complain where it cannot.
> 
> Anything that converts a different format to OSIS has to work around this 
> limitation. osis2mod will tell when it is not so.
> 
> One way around this is to have the osisID be for multiple verses and that 
> contain the construct.
> 
> Another way is for the converter to throw away the “offending” construct and 
> just keep the content. That’s what JSword does on a verse by verse basis.
> 
> In Him,
>   DM
> 
> 
>> On Feb 18, 2019, at 5:34 PM, David Haslam > <mailto:dfh...@protonmail.com>> wrote:
>> 
>> Thanks DM.
>> 
>> Sound advice if you were speaking to a translator but it’s not as if any of 
>> us are. 
>> 
>> The context is preparing the text for building a SWORD module for a modern 
>> translation done by a third party. 
>> 
>> We’re not at liberty to change the SFM markup already provided. 
>> 
>> We have to deal with things as they are; not with how we’d like them to be. 
>> 
>> And the tables markup is in the USFM. 
>> 
>> David
>> 
>> Sent from ProtonMail Mobile
>> 
>> 
>> On Mon, Feb 18, 2019 at 22:04, DM Smith > <mailto:dmsm...@crosswire.org>> wrote:
>>> 
>>> Don’t do it. Tables are often used for presentation when they shouldn’t. 
>>> Tables should be used for tabular data.
>>> 
>>> Basically, nothing should start or end within a verse that is not 
>>> milestoned or able to be converted to a milestone.
>>> 
>>> In Him,
>>> DM
>>> 
>>> > On Feb 18, 2019, at 10:39 AM, David Haslam >> > <mailto:dfh...@protonmail.com>> wrote:
>>> >
>>> > Dear all,
>>> >
>>> > Ryan V wrote about a Bible we're looking at for module build.
>>> >
>>> >> As for the nesting errors, I haven't look at all of them yet. But the 
>>> >> ones I did look at have verses starting inside a table, and then ending 
>>> >> outside of a table. It's not possible to fix the nesting errors that 
>>> >> osis2mod reports in that situation.
>>> >
>>> > Now this is rather odd, seeing as ParaTExt/USFM is quite happy for a 
>>> > table in which the above happens.
>>> >
>>> > What advice is there from SWORD developers about how to proceed?
>>> >
>>> > Must we simply accept the warnings, and just accept the consequences?
>>> >
>>> > Best regards,
>>> >
>>> > David
>>> >
>>> > Sent with ProtonMail Secure Email.
>>> >
>>> >
>>> >
>>> > ___
>>> > sword-devel mailing list: sword-devel@crosswire.org 
>>> > <mailto:sword-devel@crosswire.org>
>>> >

Re: [sword-devel] OSIS files with Tables and Nesting warnings from osis2mod

[DM Smith]

When ever a non-milestonable construct is not wholly contained in a verse, it 
will not work as a SWORD module in all contexts.

From a module perspective, a verse is what is stored as a verse. It includes 
all the content between what we know as verses, such as titles, sections, 
paragraphs.

Basic reason is that modules are verse oriented. Each verse has to be able to 
display in isolation. When a verse is not well formed XML, then it cannot.

We recommend that authors of OSIS see the major constructs of a module to be 
Books, Chapters, Sections and Paragraphs, expressed as containers. And that 
verses are milestoned.

osis2mod will reverse this and complain where it cannot.

Anything that converts a different format to OSIS has to work around this 
limitation. osis2mod will tell when it is not so.

One way around this is to have the osisID be for multiple verses and that 
contain the construct.

Another way is for the converter to throw away the “offending” construct and 
just keep the content. That’s what JSword does on a verse by verse basis.

In Him,
DM


> On Feb 18, 2019, at 5:34 PM, David Haslam  wrote:
> 
> Thanks DM.
> 
> Sound advice if you were speaking to a translator but it’s not as if any of 
> us are. 
> 
> The context is preparing the text for building a SWORD module for a modern 
> translation done by a third party. 
> 
> We’re not at liberty to change the SFM markup already provided. 
> 
> We have to deal with things as they are; not with how we’d like them to be. 
> 
> And the tables markup is in the USFM. 
> 
> David
> 
> Sent from ProtonMail Mobile
> 
> 
> On Mon, Feb 18, 2019 at 22:04, DM Smith  <mailto:dmsm...@crosswire.org>> wrote:
>> 
>> Don’t do it. Tables are often used for presentation when they shouldn’t. 
>> Tables should be used for tabular data.
>> 
>> Basically, nothing should start or end within a verse that is not milestoned 
>> or able to be converted to a milestone.
>> 
>> In Him,
>> DM
>> 
>> > On Feb 18, 2019, at 10:39 AM, David Haslam  wrote:
>> >
>> > Dear all,
>> >
>> > Ryan V wrote about a Bible we're looking at for module build.
>> >
>> >> As for the nesting errors, I haven't look at all of them yet. But the 
>> >> ones I did look at have verses starting inside a table, and then ending 
>> >> outside of a table. It's not possible to fix the nesting errors that 
>> >> osis2mod reports in that situation.
>> >
>> > Now this is rather odd, seeing as ParaTExt/USFM is quite happy for a table 
>> > in which the above happens.
>> >
>> > What advice is there from SWORD developers about how to proceed?
>> >
>> > Must we simply accept the warnings, and just accept the consequences?
>> >
>> > Best regards,
>> >
>> > David
>> >
>> > Sent with ProtonMail Secure Email.
>> >
>> >
>> >
>> > ___
>> > 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

Re: [sword-devel] OSIS files with Tables and Nesting warnings from osis2mod

[DM Smith]

Don’t do it. Tables are often used for presentation when they shouldn’t. Tables 
should be used for tabular data.

Basically, nothing should start or end within a verse that is not milestoned or 
able to be converted to a milestone.

In Him,
DM

> On Feb 18, 2019, at 10:39 AM, David Haslam  wrote:
> 
> Dear all,
> 
> Ryan V wrote about a Bible we're looking at for module build.
> 
>> As for the nesting errors, I haven't look at all of them yet. But the ones I 
>> did look at have verses starting inside a table, and then ending outside of 
>> a table. It's not possible to fix the nesting errors that osis2mod reports 
>> in that situation.
> 
> Now this is rather odd, seeing as ParaTExt/USFM is quite happy for a table in 
> which the above happens.
> 
> What advice is there from SWORD developers about how to proceed?
> 
> Must we simply accept the warnings, and just accept the consequences?
> 
> Best regards,
> 
> David
> 
> Sent with ProtonMail Secure Email.
> 
> 
> 
> ___
> 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] Orphaned verse tags in SWORD modules

[DM Smith]

osis2mod does not understand the CDATA construct  nor 
does the SWORD parser. The OSIS schema (xsd) defines text as xs:string, not 
xs:normalizeString. So spaces, tabs and newlines are not to be collapsed or 
replaced. I think CDATA and #PCDATA is an SGML construct, not an XML one.

However, osis2mod does convert newlines to spaces and collapses consecutive 
strings of spaces to a single space. The only newline in the module is at the 
end of the each stored entry in the module’s data file.

DM

> On Feb 9, 2019, at 5:45 PM, Greg Hellings  wrote:
> 
> Are we sure that this is a problem with the OSIS and not just an issue with 
> the render filters? All consecutive strings of whitespace characters in XML 
> cdata segments is supposed to be collapsed to a single space character upon 
> processing. If we've got newlines showing up in places that a newline isn't 
> indicated from markup, then it sounds like the issue is in the render filter, 
> not the OSIS. But I'd have to know what OSIS construct you're referring to.
> 
> --Greg
> 
> On Sat, Feb 9, 2019 at 6:21 AM David Haslam  > wrote:
> Issue added:
> 
> https://github.com/adyeths/u2o/issues/82 
> 
> 
> Best regards,
> 
> David
> 
> Sent with ProtonMail  Secure Email.
> 
> ‐‐‐ Original Message ‐‐‐
> On Saturday, 9 February 2019 11:17, David Haslam  > wrote:
> 
>> Thanks Ryan,
>> 
>> I will add an issue. 
>> 
>> Aside: Are we all certain that this isn’t due to a bug in the SWORD API ?
>> 
>> David
>> 
>> Sent from ProtonMail Mobile
>> 
>> 
>> On Fri, Feb 8, 2019 at 22:36, Ryan V > > wrote:
>>> A special utility isn't needed. This is a bug in the usfm to osis converter 
>>> being used.
>>> 
>>> If this happens with the output of u2o.py please submit a bug report so i 
>>> can fix my converter.
>>> 
>>> On Fri, Feb 8, 2019, 4:48 PM David Haslam >>  wrote:
>>> Friends,
>>> 
>>> How to ensure that modules made from OSIS do not display orphaned verse 
>>> tags (verse number followed by a new line before the paragraph starts) has 
>>> been known and understood for years.
>>> 
>>> Why is there not a simple Sword utility that fixes OSIS files for this one 
>>> issue?
>>> 
>>> We still see far too many module releases in which a Bible with paragraphed 
>>> text is splattered with such orphaned verse tags.
>>> 
>>> 
>>> Best regards,
>>> 
>>> David
>>> 
>>> Sent with ProtonMail Secure Email.
>>> 
>>> 
>>> 
>>> ___
>>> 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

___
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] XML whitespace - significant and insignificant?

[DM Smith]

I’d also add that using XSLT can introduce unwanted white space.

— DM Smith

> On Feb 9, 2019, at 9:41 AM, DM Smith  wrote:
> 
> There are several things in play wrt to whitespace in an OSIS document as it 
> pertains to a CrossWire module rendered by SWORD or JSword to a frontend.
> 1) osis2mod’s handling of whitespace.
> 1a) The parser that osis2mod uses to read the OSIS document is not a 
> validating parser. This means that whitespace between elements is always 
> considered important.
> 1b) Newlines \n are replaced by a space. Note: carriage returns \r which are 
> part of a Windows style document are not permitted in valid XML. Nor are 
> tabs. If present they are passed as is.
> 1c) Multiple spaces are folded into a single space.
> 1d) Verses are trimmed of leading and trailing space.
> 1e) Verses in the index have a trailing dos newline, even if not present in 
> the input.
> 
> 2) Rendering
> 2a) The parser that SWORD uses to render an OSIS module is not a validating 
> parser. This means that whitespace between elements is always considered 
> important.
> 2b) HTML and RTF are different beasts. In HTML elements such as , , 
>  produce newlines in the output which are rendered by CSS, perhaps 
> implicit. RTF is precise and controlled by the document.
> 
> 3) Pretty print of an OSIS XML document.
> 3a) Nearly all pretty printers will introduce spaces between elements.
> 
> 
>Apple
>Banana
>Pear
> 
> This introduces text.
> If the pretty printing put the newlines and spaces within the element it 
> would not have introduced extra content.
> 
> >Apple>Banana>Pear> 
> 
> 3b) Some pretty printers will introduce spaces at the beginning of text.
> 
> 
>
>Apple
>
>
>Banana
>
>
>Pear
>
> 
> If the pretty printing put the newlines and spaces within the element it 
> would not have introduced extra content.
> 
> >>Apple>>Banana>>Pear> 
> 
> Best advice for an OSIS module:
> Verse per line.
> Don’t put spaces or new lines after an opening .
> 
> In Him,
>DM
> 
>> On Feb 8, 2019, at 2:02 PM, David Haslam  wrote:
>> 
>> Here's a question that I'd like our OSIS experts to ponder.
>> 
>> In XML, there's a longstanding topic relating to whitespace.
>> 
>> See http://usingxml.com/Basics/XmlSpace
>> 
>> When we make a module from an OSIS file, are there any aspects of XML 
>> whitespace that can make a significant difference to how the module displays 
>> text or features?
>> 
>> E.g. Might we inadvertently get a space inserted between a tagged word and a 
>> note tag?
>> 
>> i.e. As maybe the result of performing a "pretty print" operation on the 
>> OSIS source text.
>> 
>> cf. I'm sure you can think of other potential areas of interest.
>> 
>> AFAIK, this has never been discussed before among us.
>> 
>> With various software tools available for making "innocuous" changes to XML 
>> files, it's certainly the case that there's nothing to dissuade module 
>> providers from using them to "prettify" the OSIS file, even though there 
>> might - theoretically at least - be consequences.
>> 
>> 
>> Best regards,
>> 
>> David
>> 
>> Sent with ProtonMail Secure Email.
>> 
>> 
>> 
>> ___
>> 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

Re: [sword-devel] XML whitespace - significant and insignificant?

[DM Smith]

Regarding ws and notes, it depends. Some modules put the marker before the item 
so don’t follow that w a space but precede with one if appropriate. Most follow 
the item and then don’t precede with one but follow if appropriate. 

In the print 1769 KJV many have markers with surrounding whitespace. This poses 
a problem w RTF renderers when markers are not shown as it show 2 spaces at 
that point. It’ll be fine in most HTML contexts. If CSS merely hides the marker 
then it’d may show 2 spaces. 

— DM Smith

> On Feb 9, 2019, at 9:56 AM, David Haslam  wrote:
> 
> Thanks DM.
> 
> Very helpful. 
> 
> Any thoughts about XML ws before or after a note element ?
> 
> Clearly, a space just after a note should never be inadvertently removed. 
> 
> And equally so, a space should never be inadvertently inserted just before a 
> note. 
> 
> I suspect some XML prettifiers may break one or both of these rules. 
> 
> Best regards 
> 
> David
> 
> Sent from ProtonMail Mobile
> 
> 
>> On Sat, Feb 9, 2019 at 14:41, DM Smith  wrote:
>> There are several things in play wrt to whitespace in an OSIS document as it 
>> pertains to a CrossWire module rendered by SWORD or JSword to a frontend.
>> 1) osis2mod’s handling of whitespace.
>> 1a) The parser that osis2mod uses to read the OSIS document is not a 
>> validating parser. This means that whitespace between elements is always 
>> considered important.
>> 1b) Newlines are replaced by a space. Note: carriage returns which are part 
>> of a Windows style document are not permitted in valid XML. Nor are tabs. If 
>> present they are passed as is.
>> 1c) Multiple spaces are folded into a single space.
>> 1d) Verses are trimmed of leading and trailing space.
>> 1e) Verses in the index have a trailing dos newline, even if not present in 
>> the input.
>> 
>> 2) Rendering
>> 2a) The parser that SWORD uses to render an OSIS module is not a validating 
>> parser. This means that whitespace between elements is always considered 
>> important.
>> 2b) HTML and RTF are different beasts. In HTML elements such as , , 
>>  produce newlines in the output which are rendered by CSS, perhaps 
>> implicit. RTF is precise and controlled by the document.
>> 
>> 3) Pretty print of an OSIS XML document.
>> 3a) Nearly all pretty printers will introduce spaces between elements.
>> 
>> 
>> Apple
>> Banana
>> Pear
>> 
>> This introduces text.
>> If the pretty printing put the newlines and spaces within the element it 
>> would not have introduced extra content.
>> 
>> > >Apple> >Banana> >Pear> >
>> 
>> 3b) Some pretty printers will introduce spaces at the beginning of text.
>> 
>> 
>> 
>> Apple
>> 
>> 
>> Banana
>> 
>> 
>> Pear
>> 
>> 
>> If the pretty printing put the newlines and spaces within the element it 
>> would not have introduced extra content.
>> 
>> > >> >Apple> >> >Banana> >> >Pear> >
>> 
>> Best advice for an OSIS module:
>> Verse per line.
>> Don’t put spaces or new lines after an opening .
>> 
>> In Him,
>> DM
>> 
>> > On Feb 8, 2019, at 2:02 PM, David Haslam  wrote:
>> >
>> > Here's a question that I'd like our OSIS experts to ponder.
>> >
>> > In XML, there's a longstanding topic relating to whitespace.
>> >
>> > See http://usingxml.com/Basics/XmlSpace
>> >
>> > When we make a module from an OSIS file, are there any aspects of XML 
>> > whitespace that can make a significant difference to how the module 
>> > displays text or features?
>> >
>> > E.g. Might we inadvertently get a space inserted between a tagged word and 
>> > a note tag?
>> >
>> > i.e. As maybe the result of performing a "pretty print" operation on the 
>> > OSIS source text.
>> >
>> > cf. I'm sure you can think of other potential areas of interest.
>> >
>> > AFAIK, this has never been discussed before among us.
>> >
>> > With various software tools available for making "innocuous" changes to 
>> > XML files, it's certainly the case that there's nothing to dissuade module 
>> > providers from using them to "prettify" the OSIS file, even though there 
>> > might - theoretically at least - be consequences.
>> >
>> >
>> > Best regards,
>> >
>> > David
>> >
>> > Sent with ProtonMail Secure Email.
>> >
>> >
>> >
>> > ___
>> > 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

Re: [sword-devel] XML whitespace - significant and insignificant?

[DM Smith]

There are several things in play wrt to whitespace in an OSIS document as it 
pertains to a CrossWire module rendered by SWORD or JSword to a frontend.
1) osis2mod’s handling of whitespace.
1a) The parser that osis2mod uses to read the OSIS document is not a validating 
parser. This means that whitespace between elements is always considered 
important.
1b) Newlines \n are replaced by a space. Note: carriage returns \r which are 
part of a Windows style document are not permitted in valid XML. Nor are tabs. 
If present they are passed as is.
1c) Multiple spaces are folded into a single space.
1d) Verses are trimmed of leading and trailing space.
1e) Verses in the index have a trailing dos newline, even if not present in the 
input.

2) Rendering
2a) The parser that SWORD uses to render an OSIS module is not a validating 
parser. This means that whitespace between elements is always considered 
important.
2b) HTML and RTF are different beasts. In HTML elements such as , , 
 produce newlines in the output which are rendered by CSS, perhaps 
implicit. RTF is precise and controlled by the document.

3) Pretty print of an OSIS XML document.
3a) Nearly all pretty printers will introduce spaces between elements.


Apple
Banana
Pear

This introduces text.
If the pretty printing put the newlines and spaces within the element it would 
not have introduced extra content.

AppleBananaPear

3b) Some pretty printers will introduce spaces at the beginning of text.



Apple


Banana


Pear


If the pretty printing put the newlines and spaces within the element it would 
not have introduced extra content.

AppleBananaPear

Best advice for an OSIS module:
Verse per line.
Don’t put spaces or new lines after an opening .

In Him,
DM

> On Feb 8, 2019, at 2:02 PM, David Haslam  wrote:
> 
> Here's a question that I'd like our OSIS experts to ponder.
> 
> In XML, there's a longstanding topic relating to whitespace.
> 
> See http://usingxml.com/Basics/XmlSpace
> 
> When we make a module from an OSIS file, are there any aspects of XML 
> whitespace that can make a significant difference to how the module displays 
> text or features?
> 
> E.g. Might we inadvertently get a space inserted between a tagged word and a 
> note tag?
> 
> i.e. As maybe the result of performing a "pretty print" operation on the OSIS 
> source text.
> 
> cf. I'm sure you can think of other potential areas of interest.
> 
> AFAIK, this has never been discussed before among us.
> 
> With various software tools available for making "innocuous" changes to XML 
> files, it's certainly the case that there's nothing to dissuade module 
> providers from using them to "prettify" the OSIS file, even though there 
> might - theoretically at least - be consequences.
> 
> 
> Best regards,
> 
> David
> 
> Sent with ProtonMail Secure Email.
> 
> 
> 
> ___
> 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] LXX Strongs & Morphology

[DM Smith]

The only morphology that was expected was robinson:
  



  

  


  

  


  

  





   

  


> On Feb 7, 2019, at 8:51 PM, Dudeck, John  wrote:
> 
> 
> > JSword allows the setting of a Greek Mophology module. It doesn’t use the 
> > work given in the morph or lemma attributes. Forked XST can provide a 
> > different mechanism.
> 
> Ok so this answers why Packard seems to be ignored. But the question remains 
> why LXX does not display the Morphology, whereas TR does.
> 
> John
> 
> > — DM Smith
> > From my phone. Brief. Weird autocorrections.
> >
> > > On Feb 7, 2019, at 3:26 PM, pierre amadio  wrote:
> > >
> > > Hi there !
> > >
> > > I find it strange that the LXX module tells it is using packard's
> > > morphological code.
> > >
> > > Earlier in 2018, I started to use the LXX module (Version 2.5) and
> > > installed the Packard module as well.
> > > Then, i realised that the tool I was using gave me a lot of wrong 
> > > information.
> > >
> > > The error were visible with diatheke as well, so it was not a bug in
> > > the frontend i was using:
> > >
> > > $ diatheke -b LXX -o avm -f PLAIN -k Gen 1:1
> > > Genesis 1:1: εν (PREP) αρχη (N-DSF) εποιησεν (V-AAI-3S) ο (T-NSM) θεος
> > > (N-NSM) τον (T-ASM) ουρανον (N-ASM) και (CONJ) την (T-ASF) γην (N-ASF)
> > > (LXX)
> > >
> > > θεος (N-NSM) is obviously nominative, however asking for the packard
> > > key gives vocative as a result.
> > >
> > > $ diatheke -b Packard  -f PLAIN -k N-NSM
> > > : Part of speech: noun, indeclinable proper noun Case: vocative
> > > Number: singular Gender: neuter
> > >
> > > Looking at εποιησεν (V-AAI-3S), it tells me it is a passive pluperfect 
> > > 3s...
> > >
> > > Now, for the same codes, the robinson module gives result thats looks 
> > > correct:
> > >
> > > $ diatheke -b Robinson  -f PLAIN -k N-NSM
> > > : * Part of Speech *: Noun
> > > * Case *: Nominative
> > > * Number *: Singular
> > > * Gender *: Masculine
> > > (Robinson)
> > >
> > > $ diatheke -b Robinson  -f PLAIN -k V-AAI-3S
> > > : * Part of Speech *: Verb
> > > * Tense *: Aorist
> > > * Voice *: Active
> > > * Mood *: Indicative
> > > * Person *: third
> > > * Number *: Singular
> > > (Robinson)
> > >
> > > I do not know if this is related to your problem, nor why LXX is
> > > mentionning packard in the morph code tag, but it could be interesting
> > > to see what happen if you try to use the Robinson module instead of
> > > the Packard one.
> > >
> > >> On Thu, 7 Feb 2019 at 20:41, Dudeck, John  wrote:
> > >>
> > >> Further info:
> > >>
> > >> I dumped the LXX and TR modules using mod2imp.
> > >>
> > >> 1) I see that the LXX morphology uses the module packard. So I 
> > >> downloaded packard from Crosswire.
> > >>
> > >> 2) I see that those words that do not have a Strongs number have the 
> > >> morphology duplicated in the Strongs field (!!!) So in Malachi 1:1 you 
> > >> can see for the first word it shows:
> > >>
> > >> λημμα
> > >>
> > >> which is wrong!
> > >>
> > >> $$$Malachi 1:1
> > >> λημμα  > >> lemma="strong:G3056" morph="packard:N-GSM">λογου  > >> lemma="strong:G2962" morph="packard:N-GSM">κυριου  > >> lemma="strong:G1909" morph="packard:PREP">επι  > >> lemma="strong:G3588" morph="packard:T-ASM">τον  > >> lemma="strong:G2474" morph="packard:N-PRI">ισρα·»  > >> lemma="strong:G1722" morph="packard:PREP">εν̼̯ͷ>  > >> morph="packard:N-DSF">ǵ¹ρι̼̯ͷ>  > >> morph="packard:N-GSM">±³³µ»ου̼̯ͷ̾  > >> morph="packard:D-GSM">±ÅÄ¿υ̼̯w>  > >> morph="packard:V-AMM-2P"̾θεøµ  > >> morph="packard:PRT"̾δη̼/w>  > >> morph="packard:PREP">µÀ¹̼̯ͷ̠̾ > >> morph="packard:T-APF">ı > >> morph="packard:N-APF">º±Á´¹±Â̼̯ͷ̠̼̾w lemma="strong:G5216" 
> > >> morph="packard:P-GP">żɽ > >>

Re: [sword-devel] LXX Strongs & Morphology

[DM Smith]

JSword allows the setting of a Greek Mophology module. It doesn’t use the work 
given in the morph or lemma attributes. Forked XST can provide a different 
mechanism.

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Feb 7, 2019, at 3:26 PM, pierre amadio  wrote:
> 
> Hi there !
> 
> I find it strange that the LXX module tells it is using packard's
> morphological code.
> 
> Earlier in 2018, I started to use the LXX module (Version 2.5) and
> installed the Packard module as well.
> Then, i realised that the tool I was using gave me a lot of wrong information.
> 
> The error were visible with diatheke as well, so it was not a bug in
> the frontend i was using:
> 
> $ diatheke -b LXX -o avm -f PLAIN -k Gen 1:1
> Genesis 1:1: εν (PREP) αρχη (N-DSF) εποιησεν (V-AAI-3S) ο (T-NSM) θεος
> (N-NSM) τον (T-ASM) ουρανον (N-ASM) και (CONJ) την (T-ASF) γην (N-ASF)
> (LXX)
> 
> θεος (N-NSM) is obviously nominative, however asking for the packard
> key gives vocative as a result.
> 
> $ diatheke -b Packard  -f PLAIN -k N-NSM
> : Part of speech: noun, indeclinable proper noun Case: vocative
> Number: singular Gender: neuter
> 
> Looking at εποιησεν (V-AAI-3S), it tells me it is a passive pluperfect 3s...
> 
> Now, for the same codes, the robinson module gives result thats looks correct:
> 
> $ diatheke -b Robinson  -f PLAIN -k N-NSM
> : * Part of Speech *: Noun
> * Case *: Nominative
> * Number *: Singular
> * Gender *: Masculine
> (Robinson)
> 
> $ diatheke -b Robinson  -f PLAIN -k V-AAI-3S
> : * Part of Speech *: Verb
> * Tense *: Aorist
> * Voice *: Active
> * Mood *: Indicative
> * Person *: third
> * Number *: Singular
> (Robinson)
> 
> I do not know if this is related to your problem, nor why LXX is
> mentionning packard in the morph code tag, but it could be interesting
> to see what happen if you try to use the Robinson module instead of
> the Packard one.
> 
>> On Thu, 7 Feb 2019 at 20:41, Dudeck, John  wrote:
>> 
>> Further info:
>> 
>> I dumped the LXX and TR modules using mod2imp.
>> 
>> 1) I see that the LXX morphology uses the module packard. So I downloaded 
>> packard from Crosswire.
>> 
>> 2) I see that those words that do not have a Strongs number have the 
>> morphology duplicated in the Strongs field (!!!) So in Malachi 1:1 you can 
>> see for the first word it shows:
>> 
>> λημμα
>> 
>> which is wrong!
>> 
>> $$$Malachi 1:1
>> λημμα > lemma="strong:G3056" morph="packard:N-GSM">λογου > morph="packard:N-GSM">κυριου > morph="packard:PREP">επι > morph="packard:T-ASM">τον > morph="packard:N-PRI">ισραηλ > morph="packard:PREP">εν > morph="packard:N-DSF">χειρι > morph="packard:N-GSM">αγγελου > morph="packard:D-GSM">αυτου > morph="packard:V-AMM-2P">θεσθε > morph="packard:PRT">δη > morph="packard:PREP">επι > morph="packard:T-APF">τας > morph="packard:N-APF">καρδιας > morph="packard:P-GP">υμων
>> 
>> A quick regular expression shows that there are 30512 words where the 
>> strongs number has morphology in the field out of 475348 total words.
>> 
>> 3) The morphology field is not being displayed by AndBible. Only Strongs is 
>> being displayed. I see no differences in the tagging syntax used.
>> 
>> 
>> The mods.d/lxx.conf and tr.conf files both contain:
>> 
>> GlobalOptionFilter=OSISStrongs
>> GlobalOptionFilter=OSISMorph
>> Feature=StrongsNumbers
>> 
>> So I don't understand why one displays the Morphology codes and the other 
>> does not.
>> 
>> Any ideas?
>> 
>> John
>> 
>>> The behavior in AndBible for the LXX is rather odd. It doesn't matter where 
>>> you look in the text,
>>> the symptoms appear the same everywhere.
>>> 
>>> When you tap '' to display Strongs numbers, it displays the Strongs 
>>> numbers, BUT for those
>>> words where there is no Strongs, it displays a Morphology code. As David 
>>> mentions, in Mal 1:1, it
>>> shows N-NSN for the first word, and Strongs numbers for the rest of the 
>>> words in the verse.
>>> 
>>> If you open the display menu (three dots menu), Strongs and Morphology are 
>>> both checked. If you
>>> uncheck Morphology, nothing changes in the display. If you check Morphology 
>>> and uncheck
>>> Strongs, all of the Strongs disappear, and no Morphology codes are 
>

Re: [sword-devel] LXX Strongs & Morphology

[DM Smith]

JSword does not use the GlobalOptionFilter or Feature values for rendering.

Overview:
JSword converts module content into OSIS then renders that with  parameterized 
XSLT. Each JSword frontend uses a forked version of Bible Desktop’s XSLT. All 
bets are off if the module is badly encoded. It makes assumptions about what is 
proper in a SWORD module.

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Feb 7, 2019, at 2:39 PM, Dudeck, John  wrote:
> 
> Further info:
> 
> I dumped the LXX and TR modules using mod2imp.
> 
> 1) I see that the LXX morphology uses the module packard. So I downloaded 
> packard from Crosswire.
> 
> 2) I see that those words that do not have a Strongs number have the 
> morphology duplicated in the Strongs field (!!!) So in Malachi 1:1 you can 
> see for the first word it shows:
> 
> λημμα
> 
> which is wrong!
> 
> $$$Malachi 1:1
> λημμα  lemma="strong:G3056" morph="packard:N-GSM">λογου  morph="packard:N-GSM">κυριου  morph="packard:PREP">επι  morph="packard:T-ASM">τον  morph="packard:N-PRI">ισραηλ  morph="packard:PREP">εν  morph="packard:N-DSF">χειρι  morph="packard:N-GSM">αγγελου  morph="packard:D-GSM">αυτου  morph="packard:V-AMM-2P">θεσθε  morph="packard:PRT">δη  morph="packard:PREP">επι  morph="packard:T-APF">τας  morph="packard:N-APF">καρδιας  morph="packard:P-GP">υμων
> 
> A quick regular expression shows that there are 30512 words where the strongs 
> number has morphology in the field out of 475348 total words.
> 
> 3) The morphology field is not being displayed by AndBible. Only Strongs is 
> being displayed. I see no differences in the tagging syntax used.
> 
> 
> The mods.d/lxx.conf and tr.conf files both contain:
> 
> GlobalOptionFilter=OSISStrongs
> GlobalOptionFilter=OSISMorph
> Feature=StrongsNumbers
> 
> So I don't understand why one displays the Morphology codes and the other 
> does not.
> 
> Any ideas?
> 
> John
> 
> > The behavior in AndBible for the LXX is rather odd. It doesn't matter where 
> > you look in the text,
> > the symptoms appear the same everywhere.
> >
> > When you tap '' to display Strongs numbers, it displays the Strongs 
> > numbers, BUT for those
> > words where there is no Strongs, it displays a Morphology code. As David 
> > mentions, in Mal 1:1, it
> > shows N-NSN for the first word, and Strongs numbers for the rest of the 
> > words in the verse.
> >
> > If you open the display menu (three dots menu), Strongs and Morphology are 
> > both checked. If you
> > uncheck Morphology, nothing changes in the display. If you check Morphology 
> > and uncheck
> > Strongs, all of the Strongs disappear, and no Morphology codes are 
> > displayed. If you then touch
> > '' again, it displays Strongs, but in the display menu Strongs is 
> > unchecked and Morphology is
> > checked but grayed out.
> >
> > If you touch a Strongs number, it displays the entry as expected. If you 
> > touch a Morphology code
> > (eg. N-NSN as above), it looks up the word 'N-NSN' in Strongs Hebrew and 
> > displays the entry
> > 3476 Naasson. If you touch 'V-PAPRP', it displays entry 3578 xenia from 
> > Strong's Greek.
> >
> > By comparison with the TR Textus Receptus, when you tap '' to display 
> > Strongs numbers, it
> > displays the Strongs number followed by the Morphology (with no space 
> > between). You can touch
> > the number and it brings up the Strongs entry from Strongs Greek. You can 
> > touch the Morphology
> > and it brings up the Robinson's codes. If you open the display menu and 
> > uncheck Morphology, it
> > shows only the Strongs numbers. However you cannot display Morphology if 
> > Strongs is not
> > displayed.
> >
> > I would assume that the behavior of the display menu in AndBible is an 
> > AndBible issue, and it's
> > not really a problem, just a minor logic bug. But the inability to display 
> > Morphology in LXX is an
> > issue.
> >
> > I imagine this could either be addressed in AndBible, or in the LXX source. 
> > Is Tuomas reading
> > this, or do I need to write him separately?
> >
> > Where do I find the LXX source? Maybe this is something that can be 
> > corrected fairly easily.
> >
> > John
> >
> > > LXX installed in PocketSword can display both or either. 
> > >
> > > There are some tagging errors such as the one I spotted in the first word 

Re: [sword-devel] Q re search indexes

[DM Smith]

Yes, indexes created can be copied to another device having AndBible.

You can contact the current developer of AndBible on how to automate the 
creation of the indexes using JSword. It will be faster.

AndBible has recently changed hands and the creation of AndBible’s Lucene 
indexes on the CrossWire server is out of date. We are updating modules at a 
crazy rate and as Troy said, we don’t support/encourage the downloading of 
indexes. So it is behind. And might be dropped altogether.

Part of the reason that indexes should be created locally is that they handle 
versioning so much better. If AndBible/JSword is updated with regard to index 
creation or the module is updated, then you’ll need to maintain an index for 
every combination. If AndBible or the module is updated it can invalidate the 
index forcing the creation of a new one.

In Him,
DM

> On Feb 4, 2019, at 8:34 PM, Dudeck, John  wrote:
> 
> Ok a follow-up question:
> 
> BTW for now I am really only interested as this relates to AndBible. We are 
> creating a collection of about 50 modules for our first release for 
> French-speaking African pastors. In the future we may make these modules 
> available to customers in Europe, too.
> 
> Last week I sat down and went into each Bible, Commentary,  and Dictionary 
> and created a search index on my phone. Whenever you tap the search icon, if 
> there is no index, it says you either need to download or create one. On a 
> larger resource such as a full-bible commentary it can take a couple minutes 
> to create. Doing the entire collection was a rather tedious exercise. 
> Downloading, if it exists, is a lot quicker, but the rest of the modules are 
> our own and we don't have downloadable indexes for them. In any case our 
> target clientele can not be expected to have good internet connectivity, so 
> our objective is to side-load everything.
> 
> I see that AndBible creates a lucene folder when you create indexes, and also 
> a file named org.crosswire.jsword.index.lucene.InstalledIndex.properties. I'm 
> wondering if it is sufficient to copy the contents of the lucene folders. Ie. 
> when side-loading the modules, the indexes could be copied over at the same 
> time. The goal would be to avoid the manual creation process.
> 
> Of course with AndBible, one only needs to launch the index creation at the 
> first use. So the users can be taught that whenever they see the dialog box 
> about indexes, they should just hit Create and wait for it to finish. I think 
> you are saying also that AndBible will automatically create them on demand in 
> the next release. From your responses already, it looks to me like we should 
> not even try to provide indexes, and let the front ends create them.
> 
> I'm still wondering where the indexes came from that I downloaded on 
> AndBible. The two Bibles that had them are FreCrampon and FreJND, which are 
> in the Crosswire Raw repository. The module fraLSG1910eb did not have it. Is 
> it possible that AndBible has a store of indexes somewhere for the known 
> modules from Crosswire?
> 
> Thanks for your help.
> 
> John
> 
> > I think AndBible has committed a change to make creation of search indexes 
> > be the new
> > mechanism.
> >
> > DM
> >
> > On Feb 4, 2019, at 7:10 PM, Troy A. Griffitts  wrote:
> >
> > Ah, read more closely... You are asking about creating search indices for 
> > DOWNLOAD.
> > There is no good answer to this.  We don't officially support downloadable 
> > search indicies. 
> > Some frontends have chosen to support this on their own and they each have 
> > their own
> > methods of doing such.  My preference would be for them to discontinue this 
> > practice and
> > create the search indices on demand on the user device, as all other 
> > frontend do.  I
> > understand the reasoning behind having these available for download when 
> > creating the
> > search indices on older mobile devices 10 years ago wasn't the speediest 
> > operation, but
> > now it likely will take less time than downloading on many mobile networks.
> > So, in summary, what I described previously (below) will create the search 
> > index for a
> > module.  Where it's placed for some mobile apps to able to download varies 
> > and at least
> > one mobile app requires it to be in a subfolder on crosswire.org-- not in 
> > your own download
> > repo.
> > Troy
> > On 2/4/19 5:01 PM, Troy A. Griffitts wrote:
> > Hi John,
> > SWORD support searching with or without a search index and has 3 methods for
> > maintaining any search index.  The implementation depends on which index 
> > system
> > option is turned on at configuration time when building (default is 
> > clucene; ximian is
> > also supported).  The calls are:
> >
> > virtual signed char SWModule::createSearchFramework(
> > void (*percent) (char, void *) = ,
> > void *percentUserData = 0);
> > virtual void SWModule::deleteSearchFramework();
> > virtual bool 

Re: [sword-devel] Q re search indexes

[DM Smith]

I think AndBible has committed a change to make creation of search indexes be 
the new mechanism.

DM

> On Feb 4, 2019, at 7:10 PM, Troy A. Griffitts  wrote:
> 
> Ah, read more closely... You are asking about creating search indices for 
> DOWNLOAD.
> 
> There is no good answer to this.  We don't officially support downloadable 
> search indicies.  Some frontends have chosen to support this on their own and 
> they each have their own methods of doing such.  My preference would be for 
> them to discontinue this practice and create the search indices on demand on 
> the user device, as all other frontend do.  I understand the reasoning behind 
> having these available for download when creating the search indices on older 
> mobile devices 10 years ago wasn't the speediest operation, but now it likely 
> will take less time than downloading on many mobile networks.
> 
> So, in summary, what I described previously (below) will create the search 
> index for a module.  Where it's placed for some mobile apps to able to 
> download varies and at least one mobile app requires it to be in a subfolder 
> on crosswire.org-- not in your own download repo.
> 
> Troy
> 
> On 2/4/19 5:01 PM, Troy A. Griffitts wrote:
>> Hi John,
>> 
>> SWORD support searching with or without a search index and has 3 methods for 
>> maintaining any search index.  The implementation depends on which index 
>> system option is turned on at configuration time when building (default is 
>> clucene; ximian is also supported).  The calls are:
>> 
>> virtual signed char SWModule::createSearchFramework(
>>  void (*percent) (char, void *) = ,
>>  void *percentUserData = 0);
>> virtual void SWModule::deleteSearchFramework();
>> virtual bool SWModule::hasSearchFramework();
>> 
>> http://crosswire.org/svn/sword/trunk/include/swmodule.h 
>> 
>> There is a simple command line utility which does nothing more than call 
>> SWModule::createSearchFramework on a module which you might find bundled 
>> with whatever binaries you are using.  The tool is called: mkfastmod
>> 
>> http://crosswire.org/svn/sword/trunk/utilities/mkfastmod.cpp 
>> 
>> 
>> 
>> 
>> On 2/4/19 4:32 PM, Dudeck, John wrote:
>>> Sorry for what might be a frequently asked question, but I can't find it on 
>>> the Crosswire wiki:
>>> 
>>> I am working on creating our own in-house repository. How are we supposed 
>>> to create the search indexes for download?
>>> 
>>> AndBible has a button for downloading the index, which works on some 
>>> modules but not on others.
>>> 
>>> I've looked on the various ftp repositories, but don't see anything that 
>>> looks like search indexes.
>>> 
>>> Can anybody give me a pointer on this?
>>> 
>>> Thanks.
>>> 
>>> John Dudeck
>>> Programmer at Editions Cle Lyon, France
>>> john.dud...@sim.org 
>>> j...@editionscle.com 
>>> --
>>> "Most people know more about how the Vatican works than
>>>  what programmers do." -- Alan Cooper
>>>   
>>> 
>>> 
>>> ___
>>> 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

___
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] Q re repository access ftp or https

[DM Smith]

AndBible needs Http(s). 

— DM Smith. 

> On Feb 4, 2019, at 6:37 PM, Dudeck, John  wrote:
> 
> Another question:
> 
> Does a repository need to have http/https access or is ftp sufficient?
> 
> Do the various front end module managers do http/https?
> 
> Thanks.
> 
> John Dudeck
> Programmer at Editions Cle Lyon, France
> john.dud...@sim.orgj...@editionscle.com
> --
> "Everything hinges on your view of Scripture. Either Scripture will be the
>  lens through which you view the world or the world (science, politics,
>  worldview, etc) will be the lens through which you view Scripture.
>  Ultimately one or the other will be your authority." -- Rachel Miller
>   
> ___
> 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] Mobile JiM - Client for Atlassian JIRA

[DM Smith]

Sure. That’s me. I’ll first have to update Jira to the latest-and-greatest. 
I’ll announce when that’s done and then you can remind me of that and any 
others that you’ve mentioned before such as git integration.

DM

> On Feb 2, 2019, at 2:04 PM, David Haslam  wrote:
> 
> Please would our Jira admin install the "Mobile Jira in Motion" add-on to our 
> tracker on the CrossWire server.
> 
> That's needed to support write operations from Mobile JiM or similar apps.
> 
> Thanks.
> 
> 
> Best regards,
> 
> David
> 
> Sent with ProtonMail Secure Email.
> 
> ‐‐‐ Original Message ‐‐‐
> On Saturday, 2 February 2019 17:37, David Haslam  
> wrote:
> 
>> I'm sure we could improve our use of the tracker if we can access it 
>> conveniently even when we're away from our usual workstations.
>> 
>> cf. I've already found that to be so for GitHub when using the iOS app 
>> called CodeHub.
>> 
>> Well here goes
>> 
>> I just installed the iOS app called Mobile JiM from Lean Walk Ltd.
>> 
>> I can now use my iPhone SE to access the CrossWire Tracker.
>> 
>> Note: Some features may require an add-on installed by our JIRA admin.
>> Even so, I've not yet hit that obstacle.
>> 
>> btw. There's an Atlassian iOS app called JIRA Cloud but that does not 
>> provide a means to connect to a third party server in which the JIRA 
>> software has been installed and setup for an "Enterprise" (such as we are).
>> 
>> I suppose there may be a similar apps for Android OS.
>> 
>> Enjoy!
>> 
>> Best regards,
>> 
>> David
>> 
>> Sent with ProtonMail Secure Email.
>> 
>> 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

Re: [sword-devel] Kjva v11n

[DM Smith]

Yes it is correct. The prayer has no verse numbers in the printed 1st edition.

In Him,
DM Smith 

> On Jan 31, 2019, at 5:08 AM, Cyrille  wrote:
> 
> Hello,
> Is the number "1" right in the kjva v11n for the Prayer of Manasses?
> 
> 
> 
> ___
> 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] Markdown?

[DM Smith]

Changes need to be added to the engine first. No sense having a module that 
would otherwise work on an earlier version of the engine be blocked by having 
such a change in the conf. Then the question of which markdown and of that what 
subset.

We’ve had support for other compression types for years now, but we still won’t 
release a module that is compressed with a different compression.

In Him,
DM

> On Jan 28, 2019, at 4:17 PM, David Haslam  wrote:
> 
> Further to the earlier discussion about HTML in module .conf files, what 
> would it take to support Markdown for some of the keys such as About?
> 
> David
> 
> Sent from ProtonMail Mobile
> ___
> 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] [sword-support] oshb 2.0 module: bug tracker

[DM Smith]

Thanks for giving the page with the broken url. It has been many years since it 
was at that url. It was moved to crosswire.org/tracker and a redirect from bugs 
went there. When we changed the url to tracker.crosswire.org we put a redirect 
from the prior and removed the older redirect. 

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Jan 19, 2019, at 6:08 AM, pierre amadio  wrote:
> 
> Hello.
> 
> OSHB was recently released sa version 2.0
> https://github.com/openscriptures/morphhb/releases/tag/v.2.0
> 
> I wanted to open a bug to request the associated sword module to be
> updated, but fail to find the bug tracker anymore.
> 
> https://www.crosswire.org/sword/support/index.jsp point to  a 404 page
> 
> http://www.crosswire.org/bugs
> 
> I have cc sword-b...@crosswire.org .
> 
> Let me know if the url of the official tracker if i should create a
> new bug there to request the update of the OSHB module:
> https://www.crosswire.org/sword/modules/ModInfo.jsp?modName=OSHB
> 
> ___
> sword-support mailing list
> sword-supp...@crosswire.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] Second versions, Scottish Metric Psalter

[DM Smith]

If you make one module do it as variations verse by verse.  JSword works on 
this basis. Each needs to be well-formed XML. Otherwise it will toss the markup.

Do the canonical headings vary too? That might pose a single module problem.

David and I have discussed supporting multiple KJV modules from a single xml 
doc using a filter (e.g. XSLT) to produce subsets. Examples, with Apocrypha, 
without such, long s variant, .

I already have a couple of XSLT filters that others requested: no notes or 
Strong’s numbers; Plaintext.

In Him,
   DM Smith

> On Jan 12, 2019, at 7:38 AM, David Haslam  wrote:
> 
> Sparsely populated
> 
> Sent from ProtonMail Mobile
> 
> 
>> On Sat, Jan 12, 2019 at 12:37, ref...@gmx.net  wrote:
>> Never looked at it. Why?
>> 
>> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
>> 
>> 
>>  Original Message 
>> Subject: Re: [sword-devel] Second versions, Scottish Metric Psalter
>> From: David Haslam 
>> To: sword-devel@crosswire.org
>> CC: 
>> 
>> 
>> You mean the Samaritan Pentateuch Dead Sea Scrolls variant module SPDSS 
>> isn't rather more of an overkill ?
>> Have you ever looked at the contents?
>> 
>> I was about to suggest the same as Tom Sullivan did.
>> 
>> A second module with just the alternative versions of these 11 or 12 Psalms,
>> 
>> But is there a third metrical version of any Psalm?
>> 
>> David
>> 
>> Sent from ProtonMail Mobile
>> 
>> 
>>> On Sat, Jan 12, 2019 at 10:30, Peter von Kaehne  wrote:
>>> On Sat, 2019-01-12 at 05:15 -0500, Tom Sullivan wrote:
>>> > Peter:
>>> >
>>> > Suggestion: Make 2 modules, one for each translation. Most front
>>> > ends
>>> > will do parallel display.
>>> 
>>> For 11 or 12 (I need to count them) psalms that seems overkill.
>>> 
>>> 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
___
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 search indices

[DM Smith]

I think I’ve narrowed down the problem. More later. 

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Jan 6, 2019, at 10:05 AM, DM Smith  wrote:
> 
> Nic is in the process of moving and that might affect his availability.
> 
> I’ve PocketSword and access to the logs. I’ll look to see what I can figure 
> out.
> 
> Yesterday Peter, Troy and I worked on fixing the server module issues. I’m 
> certain there’s more we will discover. Like this.
> 
> — DM Smith
> From my phone. Brief. Weird autocorrections. 
> 
>> On Jan 6, 2019, at 8:59 AM, "ref...@gmx.net"  wrote:
>> 
>> David points out that search indices on PocketSword for the newest modules 
>> do not work. I have no way of debugging that as I do not have an idevice. 
>> 
>> The indices are currently built on my computer and pushed to the server 
>> whenever I build a new module. My system is a debian testing amd64 system, 
>> rolling release. 
>> 
>> I guess, either I updated at one point liblucene or the general roll of 
>> libsword updates rendered my indices incompatible eventually - but I have No 
>> clue and can not test for that. 
>> 
>> Wrt solutions, depending on the outcome of someone investigating and 
>> reporting back, if it is simply a matter of holding to an older libsword and 
>> set of utilities, this can be easily done. Doing that together with an older 
>> liblucene is significantly more if a challenge and I would not know how to 
>> do that. 
>> 
>> Peter
>> 
>> 
>> 
>> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
>> ___
>> 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

Re: [sword-devel] Remarks before [ModuleName] ?

[DM Smith]

I’m pretty sure earlier versions of JSword expect [name] to be the first line 
in the file and have no leading or trailing whitespace or other stuff. BOM will 
definitely goof it up. 

I’ve rewritten it to be compliant w this ini standard. But not all frontend 
have been updated or d/l by end users.

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Jan 7, 2019, at 3:30 AM, David Haslam  wrote:
> 
> Thanks Greg,
> 
> DM - does the same hold for JSword ?
> 
> Background: .conf file for module FreBDM1707 has lots of remark lines, with 3 
> at the top of the file before the [ModuleName].
> 
> Aside: I imagine this is because Cyrille uses a template that he himself 
> created.
> 
> David
> 
> Sent from ProtonMail Mobile
> 
> 
>> On Mon, Jan 7, 2019 at 08:16, Greg Hellings  wrote:
>> There aren't any frontends that read conf files that I'm aware of. They all 
>> use the library to do that. The question is if the library can handle ini 
>> files with comments. A few basic tests should allow you to figure that out.
>> 
>> --Greg
>> 
>>> On Sun, Jan 6, 2019 at 4:04 AM David Haslam  wrote:
>>> Are there any front-ends that might baulk if there are any 
>>> 
>>> # Remarks
>>> above the
>>> [ModuleName]
>>> 
>>> in the .conf file?
>>> 
>>> Regards,
>>> 
>>> David
>>> 
>>> Sent from ProtonMail Mobile
>>> ___
>>> 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

Re: [sword-devel] PocketSword search indices

[DM Smith]

Nic is in the process of moving and that might affect his availability.

I’ve PocketSword and access to the logs. I’ll look to see what I can figure out.

Yesterday Peter, Troy and I worked on fixing the server module issues. I’m 
certain there’s more we will discover. Like this.

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Jan 6, 2019, at 8:59 AM, "ref...@gmx.net"  wrote:
> 
> David points out that search indices on PocketSword for the newest modules do 
> not work. I have no way of debugging that as I do not have an idevice. 
> 
> The indices are currently built on my computer and pushed to the server 
> whenever I build a new module. My system is a debian testing amd64 system, 
> rolling release. 
> 
> I guess, either I updated at one point liblucene or the general roll of 
> libsword updates rendered my indices incompatible eventually - but I have No 
> clue and can not test for that. 
> 
> Wrt solutions, depending on the outcome of someone investigating and 
> reporting back, if it is simply a matter of holding to an older libsword and 
> set of utilities, this can be easily done. Doing that together with an older 
> liblucene is significantly more if a challenge and I would not know how to do 
> that. 
> 
> Peter
> 
> 
> 
> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
> ___
> 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] Module upload: JapDenmo

[DM Smith]

Peter and I spent some time on this today. More to do. Let me know if the 
vlsJoNT is visible now.

BTW, the extraneous emails regarding a new module were part of testing fixes.

DM

> On Jan 5, 2019, at 9:43 AM, DM Smith  wrote:
> 
> I appreciate your eagerness and your service.
> 
> I can work with specifics fairly quickly. That vlsJoNT doesn’t work is 
> helpful and I can look to see what’s where on the guest and host, but that 
> still leaves me sleuthing for the specifics. I don’t know the text type to 
> know what category to look under (though I can guess that NT means that it is 
> a Bible) and I don’t know the language as it would appear in a front-end. 
> Then I don’t know what front-end can see it and which cannot. (There are 
> three different mechanisms: SWORD, PocketSword and JSword and each has a 
> different issues that needs to be diagnosed.) When I have little time and 
> hardly any specifics, I don’t try as it might be more than I have.
> 
> Can you be more specific?
> 
> I’m looking for a simple solution (e..g. sync more often) or a solvable 
> problem (we also need to sync xyz, but didn’t) and have limited time.
> 
> In Him,
>   DM
> 
>> On Jan 5, 2019, at 9:23 AM, David Haslam  wrote:
>> 
>> 2 days delay or less I could live with.
>> 
>> But it's more than that since module vlsJoNT was announced and it's still 
>> unobtainable via the module manager UI in most front-ends.
>> Likewise for most if not all module releases since sometime in May 2018.
>> Hence the sighing "When, oh, when...?"
>> 
>> My interest is in providing speedy feedback on any technical issues I can 
>> detect in new/updated modules.
>> e.g. If I can report any obvious faults in the .conf file, then the modules 
>> team can speedily fix them before there are too many complaints from end 
>> users.
>> 
>> I should hope that there are others in this mailing list that would like to 
>> provide a similar service.
>> 
>> Announcing module releases that users cannot install is akin to the inverse 
>> of "crying wolf".
>> 
>> Best regards,
>> 
>> David
>> 
>> Sent with ProtonMail Secure Email.
>> 
>> ‐‐‐ Original Message ‐‐‐
>> On Saturday, 5 January 2019 14:07, DM Smith  wrote:
>> 
>>> I’m very encourage that there’s lots of interest in the module making 
>>> process. If I can help maintain that momentum, I will.
>>> 
>>> I’ve privately asked Peter, in response to his lament about the problem, 
>>> for specific things he wants fixed. I have not heard back from him. It is 
>>> now early morning for me on the weekend and I’m able to help. At least for 
>>> a few hours.
>>> 
>>> There has always been a lag of a day from when a module is “published” to 
>>> when it is available to all of SWORD, PocketSword and JSword.
>>> 
>>> I got your email less than 2 hours after announcement. Wait 2 days for it 
>>> to be fully published.
>>> 
>>> There are several parts to this:
>>> The email is published the moment that the module is put in mods.d and 
>>> module.
>>> Daily mods.d.tar.gz is rebuilt with the listing of mods.d.
>>> The module is zipped when a user requests the download via the website’s 
>>> listing of modules.
>>> The indexes for PocketSword and AndBible are built on a daily basis.
>>> The module sizes are updated into the conf daily.
>>> The host and guest repositories are synchronized daily.
>>> Front end users only know of the module when they refresh their module 
>>> listing.
>>> 
>>> Note, the day lag has always been hit by JSword and noticed every now and 
>>> then, but we’ve lived with it as long as JSword has been around. It only 
>>> uses the compressed files.
>>> 
>>> I think your question really is, “When is 'status quo' going to be 
>>> achieved?” The answer is “Not today, tomorrow or this week.” So, thus my 
>>> question back to Peter, "What can we do in the meantime?”
>>> 
>>> I also, don’t like where we were before we had a split server and would 
>>> like to solve that as well. But it’s not going to happen soon, either.
>>> 
>>> DM
>>> 
>>>> On Jan 5, 2019, at 7:11 AM, David Haslam dfh...@protonmail.com wrote:
>>>> I downloaded JapDenmo (via Xiphos) and still got the old 2008 module.
>>>> When, oh when, is the server sync issue going to be fixed
>>>> Best regards,
>>>> David
>>>> Sent with ProtonMail Secu

Re: [sword-devel] Module upload: JapDenmo

[DM Smith]

You should be able to call it on either the host or guest. Let me know if you 
cannot. If you run it without parameters it’ll give a usage statement.

Run it with -n at first. It will not do any work, but will state what it’s 
considering. The one option -o is useful only if your root as it changes 
ownership.

DM

> On Jan 5, 2019, at 12:00 PM, Peter von Kaehne  wrote:
> 
> On Sat, 2019-01-05 at 10:38 -0500, DM Smith wrote:
>> Thanks for the info. That’s very helpful.
>> 
>> I’ve a script ~dmsmith/bin/packageModules.sh which will examine a
>> repository for lots of issues and attempt to fix them.
>> 
> 
> Please let me have that. I can make it part of my routine too. 
> 
> 
> 
> ___
> 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] Module upload: JapDenmo

[DM Smith]

Thanks for the info. That’s very helpful.

I’ve a script ~dmsmith/bin/packageModules.sh which will examine a repository 
for lots of issues and attempt to fix them.

I just ran it and found many issues with the repo, most are benign. There were 
some zips that weren’t rebuilt when the conf was updated. There were some zips 
that were not removed when the module was taken down. Some files had bad 
ownership. There was a module that was taken down by removing the conf but not 
removing the module files.

I’m looking to find the daily sync job. I’m not seeing it.

DM

> On Jan 5, 2019, at 10:10 AM, Peter von Kaehne  wrote:
> 
> On Sat, 2019-01-05 at 09:07 -0500, DM Smith wrote:
>> There are several parts to this:
>> The email is published the moment that the module is put in mods.d
>> and module.
> 
> No. It is published on conclusion of a bunch of things - see below
> 
>> Daily mods.d.tar.gz is rebuilt with the listing of mods.d.
> 
> I trigger that myself immediately after uploading a new module 
> 
>> The module is zipped when a user requests the download via the
>> website’s listing of modules.
> 
> I drop a zip into the right place, bypassing that need. 
> 
>> The indexes for PocketSword and AndBible are built on a daily basis.
> 
> I push the zip into the right place too. 
> 
>> The module sizes are updated into the conf daily.
> 
> That is done by the cron scripts still, yes
> 
>> The host and guest repositories are synchronized daily.
> 
> That seems to happen occasionally, not daily for the modules and has
> not happened for the indices for a long time - several months. 
> 
>> Front end users only know of the module when they refresh their
>> module listing.
> 
> Unless they listen into our mailing lists. Also, I tend to put out a
> news item on Facebook and Server News page if I upload a significant
> update or a totally new module - but this has become a bit hit and miss
> with the delays 
> 
> 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

Re: [sword-devel] Module upload: JapDenmo

[DM Smith]

I appreciate your eagerness and your service.

I can work with specifics fairly quickly. That vlsJoNT doesn’t work is helpful 
and I can look to see what’s where on the guest and host, but that still leaves 
me sleuthing for the specifics. I don’t know the text type to know what 
category to look under (though I can guess that NT means that it is a Bible) 
and I don’t know the language as it would appear in a front-end. Then I don’t 
know what front-end can see it and which cannot. (There are three different 
mechanisms: SWORD, PocketSword and JSword and each has a different issues that 
needs to be diagnosed.) When I have little time and hardly any specifics, I 
don’t try as it might be more than I have.

Can you be more specific?

I’m looking for a simple solution (e..g. sync more often) or a solvable problem 
(we also need to sync xyz, but didn’t) and have limited time.

In Him,
DM

> On Jan 5, 2019, at 9:23 AM, David Haslam  wrote:
> 
> 2 days delay or less I could live with.
> 
> But it's more than that since module vlsJoNT was announced and it's still 
> unobtainable via the module manager UI in most front-ends.
> Likewise for most if not all module releases since sometime in May 2018.
> Hence the sighing "When, oh, when...?"
> 
> My interest is in providing speedy feedback on any technical issues I can 
> detect in new/updated modules.
> e.g. If I can report any obvious faults in the .conf file, then the modules 
> team can speedily fix them before there are too many complaints from end 
> users.
> 
> I should hope that there are others in this mailing list that would like to 
> provide a similar service.
> 
> Announcing module releases that users cannot install is akin to the inverse 
> of "crying wolf".
> 
> Best regards,
> 
> David
> 
> Sent with ProtonMail Secure Email.
> 
> ‐‐‐ Original Message ‐‐‐
> On Saturday, 5 January 2019 14:07, DM Smith  wrote:
> 
>> I’m very encourage that there’s lots of interest in the module making 
>> process. If I can help maintain that momentum, I will.
>> 
>> I’ve privately asked Peter, in response to his lament about the problem, for 
>> specific things he wants fixed. I have not heard back from him. It is now 
>> early morning for me on the weekend and I’m able to help. At least for a few 
>> hours.
>> 
>> There has always been a lag of a day from when a module is “published” to 
>> when it is available to all of SWORD, PocketSword and JSword.
>> 
>> I got your email less than 2 hours after announcement. Wait 2 days for it to 
>> be fully published.
>> 
>> There are several parts to this:
>> The email is published the moment that the module is put in mods.d and 
>> module.
>> Daily mods.d.tar.gz is rebuilt with the listing of mods.d.
>> The module is zipped when a user requests the download via the website’s 
>> listing of modules.
>> The indexes for PocketSword and AndBible are built on a daily basis.
>> The module sizes are updated into the conf daily.
>> The host and guest repositories are synchronized daily.
>> Front end users only know of the module when they refresh their module 
>> listing.
>> 
>> Note, the day lag has always been hit by JSword and noticed every now and 
>> then, but we’ve lived with it as long as JSword has been around. It only 
>> uses the compressed files.
>> 
>> I think your question really is, “When is 'status quo' going to be 
>> achieved?” The answer is “Not today, tomorrow or this week.” So, thus my 
>> question back to Peter, "What can we do in the meantime?”
>> 
>> I also, don’t like where we were before we had a split server and would like 
>> to solve that as well. But it’s not going to happen soon, either.
>> 
>> DM
>> 
>>> On Jan 5, 2019, at 7:11 AM, David Haslam dfh...@protonmail.com wrote:
>>> I downloaded JapDenmo (via Xiphos) and still got the old 2008 module.
>>> When, oh when, is the server sync issue going to be fixed
>>> Best regards,
>>> David
>>> Sent with ProtonMail Secure Email.
>>> ‐‐‐ Original Message ‐‐‐
>>> On Saturday, 5 January 2019 11:08, ref...@crosswire.org wrote:
>>> 
>>>> Dear All,
>>>> This is to announce that we have just now uploaded JapDenmo.
>>>> This is is an updated version of JapDenmo.
>>>> Many thanks to Cyrille for the hard work.
>>>> yours
>>>> The Module Team
>>>> P.S.: This email is sent automatically on upload of a new/updated module
>>>> sword-devel mailing list: sword-devel@crosswire.org
>>>> http://www.crosswire.org/mailman/list

Re: [sword-devel] Module upload: JapDenmo

[DM Smith]

I’m very encourage that there’s lots of interest in the module making process. 
If I can help maintain that momentum, I will.

I’ve privately asked Peter, in response to his lament about the problem, for 
specific things he wants fixed. I have not heard back from him. It is now early 
morning for me on the weekend and I’m able to help. At least for a few hours.

There has always been a lag of a day from when a module is “published” to when 
it is available to all of SWORD, PocketSword and JSword.

I got your email less than 2 hours after announcement. Wait 2 days for it to be 
fully published.

There are several parts to this:
The email is published the moment that the module is put in mods.d and module.
Daily mods.d.tar.gz is rebuilt with the listing of mods.d.
The module is zipped when a user requests the download via the website’s 
listing of modules.
The indexes for PocketSword and AndBible are built on a daily basis.
The module sizes are updated into the conf daily.
The host and guest repositories are synchronized daily.
Front end users only know of the module when they refresh their module listing.

Note, the day lag has always been hit by JSword and noticed every now and then, 
but we’ve lived with it as long as JSword has been around. It only uses the 
compressed files.

I think your question really is, “When is 'status quo' going to be achieved?” 
The answer is “Not today, tomorrow or this week.” So, thus my question back to 
Peter, "What can we do in the meantime?”

I also, don’t like where we were before we had a split server and would like to 
solve that as well. But it’s not going to happen soon, either.

DM

> On Jan 5, 2019, at 7:11 AM, David Haslam  wrote:
> 
> I downloaded JapDenmo (via Xiphos) and still got the old 2008 module.
> 
> When, oh when, is the server sync issue going to be fixed
> 
> Best regards,
> 
> David
> 
> Sent with ProtonMail Secure Email.
> 
> ‐‐‐ Original Message ‐‐‐
> On Saturday, 5 January 2019 11:08,  wrote:
> 
>> Dear All,
>> This is to announce that we have just now uploaded JapDenmo.
>> This is is an updated version of JapDenmo.
>> Many thanks to Cyrille for the hard work.
>> 
>> yours
>> 
>> The Module Team
>> 
>> P.S.: This email is sent automatically on upload of a new/updated module
>> 
>> 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

Re: [sword-devel] Short/Long Bible & Commentary Modules

[DM Smith]

osis2mod still defaults to KJV. From the SVN logs, that hasn’t changed. BTW, 
osis2mod doesn’t care about a conf.

If Peter built it, perhaps Peter’s scripted calls to osis2mod default to -v 
NRSV and didn’t catch that your conf was explicit. 

DM

> On Jan 2, 2019, at 9:07 AM, David Haslam  wrote:
> 
> Ah - but when I submitted the updated module PolUGdanska for release, the 
> .conf file specifically included
> 
> Versification=KJV
> 
> so there's still no accounting for your observation of the two extra verses.
> 
> Unless, of course, when Peter rebuilt the module using osis2mod, he actually 
> used -v NRSV in the command line,
> or unless, perhaps, he's using a user-compiled version of the Sword utilities 
> in which the default v11n has already been changed to NRSV,
> even though this was merely mooted tentatively in the wiki page as being a 
> potential candidate for default v11n.
> 
> Notwithstanding, the command line should always match the v11n when it's 
> specified in the .conf file.
> 
> Aside: Whenever I build a module, I'm constrained to using the most recently 
> downloaded utilities for Windows (or earlier).
> I never compile any programs from source.
> 
> Best regards,
> 
> David
> 
> Sent with ProtonMail <https://protonmail.com/> Secure Email.
> 
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, 2 January 2019 13:47, DM Smith  wrote:
> 
>> When osis2mod creates a module it uses its default v11n is used unless the 
>> user specifies a v11n. That v11n is used to lay out the index files and fill 
>> them with 0s. This is done before any of the input file is read. That index 
>> in the files listed have the number of verses in the NRSV not the KJV. If I 
>> understand correctly, the length of the index files don’t change once the 
>> module is created.
>> 
>> DM
>> 
>>> On Jan 2, 2019, at 4:30 AM, David Haslam >> <mailto:dfh...@protonmail.com>> wrote:
>>> 
>>> I'm rather puzzled by one section of DM's observations
>>> 
>>> DM wrote:
>>> 
>>> The CrossWire Bible modules that have a visible NT problem having 2 extra 
>>> verses: (All are KJV, but maybe should be NRSV av11n)
>>> HebDelitzsch
>>> PorAlmeida1911
>>> PolUGdanska
>>> Shona
>>> TurHADI
>>> 
>>> As the submitter for PolUGdanska, I can confirm that KJV is the correct 
>>> v11n for this module.
>>> There were no APPEND warnings when the module was made with osis2mod.
>>> 
>>> IIRC the NRSV av11n splits Rev 12:17 and 3John14 each into two verses.
>>> I do not think that any of these 5 modules do that, though I've not checked 
>>> the other 4.
>>> 
>>> These 2 extra NT verses that NRSV has relative to the KJV are therefore not 
>>> the cause of DM's reported problems here.
>>> 
>>> A different explanation should be sought.
>>> 
>>> Aside: Even some modules built with v11n=NRSV omit Rev 12:18 (e.g. ESV2011).
>>> Aside: The NRSV also moves Romans 16:24 to a different location.
>>> 
>>> NB. I do not understand how there can be any "extra verses" in a module if 
>>> there were no APPEND warnings from osis2mod.
>>> 
>>> 
>>> Best regards,
>>> 
>>> David
>>> 
>>> Sent with ProtonMail <https://protonmail.com/> Secure Email.
>>> 
>>> ‐‐‐ Original Message ‐‐‐
>>> On Tuesday, 1 January 2019 18:22, DM Smith >> <mailto:dmsm...@crosswire.org>> wrote:
>>> 
>>>> I’ve found an oddness in some Bible and commentary modules. (They share 
>>>> the same storage mechanism).
>>>> 
>>>> For each module there’s an index file for the OT and for the NT. Even many 
>>>> single testament modules have an index file for the other testament.
>>>> 
>>>> The index file has a slot for every verse in the testament. Intros for the 
>>>> Bible, Testaments, books and chapters are treated as verses and have slots 
>>>> in the index.
>>>> 
>>>> When the module is created, the indexes are initialized to all zeros, 
>>>> indicating that there is no data. When a verse is written to the module, 
>>>> the verse’s slot in the index is updated to point to the verse.
>>>> 
>>>> So for a versification, each index has a fixed size.
>>>> 
>>>> For years, I’ve noticed a debug statement from JSword indicating that some 
>>>> indexes have a different size than expected.
>>>> 

Re: [sword-devel] Short/Long Bible & Commentary Modules

[DM Smith]

When osis2mod creates a module it uses its default v11n is used unless the user 
specifies a v11n. That v11n is used to lay out the index files and fill them 
with 0s. This is done before any of the input file is read. That index in the 
files listed have the number of verses in the NRSV not the KJV. If I understand 
correctly, the length of the index files don’t change once the module is 
created.

DM

> On Jan 2, 2019, at 4:30 AM, David Haslam  wrote:
> 
> I'm rather puzzled by one section of DM's observations
> 
> DM wrote:
> 
> The CrossWire Bible modules that have a visible NT problem having 2 extra 
> verses: (All are KJV, but maybe should be NRSV av11n)
> HebDelitzsch
> PorAlmeida1911
> PolUGdanska
> Shona
> TurHADI
> 
> As the submitter for PolUGdanska, I can confirm that KJV is the correct v11n 
> for this module.
> There were no APPEND warnings when the module was made with osis2mod.
> 
> IIRC the NRSV av11n splits Rev 12:17 and 3John14 each into two verses.
> I do not think that any of these 5 modules do that, though I've not checked 
> the other 4.
> 
> These 2 extra NT verses that NRSV has relative to the KJV are therefore not 
> the cause of DM's reported problems here.
> 
> A different explanation should be sought.
> 
> Aside: Even some modules built with v11n=NRSV omit Rev 12:18 (e.g. ESV2011).
> Aside: The NRSV also moves Romans 16:24 to a different location.
> 
> NB. I do not understand how there can be any "extra verses" in a module if 
> there were no APPEND warnings from osis2mod.
> 
> 
> Best regards,
> 
> David
> 
> Sent with ProtonMail <https://protonmail.com/> Secure Email.
> 
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, 1 January 2019 18:22, DM Smith  wrote:
> 
>> I’ve found an oddness in some Bible and commentary modules. (They share the 
>> same storage mechanism).
>> 
>> For each module there’s an index file for the OT and for the NT. Even many 
>> single testament modules have an index file for the other testament.
>> 
>> The index file has a slot for every verse in the testament. Intros for the 
>> Bible, Testaments, books and chapters are treated as verses and have slots 
>> in the index.
>> 
>> When the module is created, the indexes are initialized to all zeros, 
>> indicating that there is no data. When a verse is written to the module, the 
>> verse’s slot in the index is updated to point to the verse.
>> 
>> So for a versification, each index has a fixed size.
>> 
>> For years, I’ve noticed a debug statement from JSword indicating that some 
>> indexes have a different size than expected.
>> 
>> So for the last couple of days, I’ve been debugging the problem. Quite a few 
>> OT are a verse short. For the most part these modules are NT only, but a few 
>> are missing Malachi 4:6. Some NT have two more slots in the index.
>> 
>> The Bible modules that have a visible OT problem, not having the last verse 
>> of the OT:
>> DanDetteBiblen (Xiphos)
>> FarFLB (Xiphos)
>> JapMeiji (CrossWire)
>> Mg1865 (CrossWire) Looks like all of Malachi 4 is appended to 3:18
>> PolBibTysia (Xiphos)
>> 
>> The CrossWire Bible modules that have a visible NT problem having 2 extra 
>> verses: (All are KJV, but maybe should be NRSV av11n)
>> HebDelitzsch
>> PorAlmeida1911
>> PolUGdanska
>> Shona
>> TurHADI
>> 
>> The CrossWire commentary module DTN seems to be really bad. The NT index 
>> file is way too long. Looking at the module content,  I find lots of verses 
>> that are present but w empty content. I find verse 0 for many chapters is 
>> filled with wrong content.
>> 
>> The CrossWire Bibles that have the short OT index, but it isn’t really a 
>> problem because the module doesn’t have the OT or only has part of the OT:
>> ArmEastern
>> Chamorro
>> Cro
>> CzeB21
>> Est
>> GerAlbrecht
>> GerGruenewald
>> GerTafel
>> GerTextbibel
>> Leeser
>> ManxGaelic
>> SweKarlXII
>> Tyndale
>> VietLCCMN
>> Vulgate_HebPs
>> Wulfila
>> Wycliffe
>> 
>> The following CrossWire commentaries also have a non-problematic short OT 
>> index:
>> MAK
>> Spurious
>> VietLCCMNCT
>> 
>> 
>> In Him,
>> DM
>> 
>> 
>> 
> 
> ___
> 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] Short/Long Bible & Commentary Modules

[DM Smith]

I’ve found an oddness in some Bible and commentary modules. (They share the 
same storage mechanism).

For each module there’s an index file for the OT and for the NT. Even many 
single testament modules have an index file for the other testament.

The index file has a slot for every verse in the testament. Intros for the 
Bible, Testaments, books and chapters are treated as verses and have slots in 
the index.

When the module is created, the indexes are initialized to all zeros, 
indicating that there is no data. When a verse is written to the module, the 
verse’s slot in the index is updated to point to the verse.

So for a versification, each index has a fixed size.

For years, I’ve noticed a debug statement from JSword indicating that some 
indexes have a different size than expected.

So for the last couple of days, I’ve been debugging the problem. Quite a few OT 
are a verse short. For the most part these modules are NT only, but a few are 
missing Malachi 4:6. Some NT have two more slots in the index.

The Bible modules that have a visible OT problem, not having the last verse of 
the OT:
DanDetteBiblen (Xiphos)
FarFLB (Xiphos)
JapMeiji (CrossWire)
Mg1865 (CrossWire) Looks like all of Malachi 4 is appended to 3:18
PolBibTysia (Xiphos)

The CrossWire Bible modules that have a visible NT problem having 2 extra 
verses: (All are KJV, but maybe should be NRSV av11n)
HebDelitzsch
PorAlmeida1911
PolUGdanska
Shona
TurHADI

The CrossWire commentary module DTN seems to be really bad. The NT index file 
is way too long. Looking at the module content,  I find lots of verses that are 
present but w empty content. I find verse 0 for many chapters is filled with 
wrong content.

The CrossWire Bibles that have the short OT index, but it isn’t really a 
problem because the module doesn’t have the OT or only has part of the OT:
ArmEastern
Chamorro
Cro
CzeB21
Est
GerAlbrecht
GerGruenewald
GerTafel
GerTextbibel
Leeser
ManxGaelic
SweKarlXII
Tyndale
VietLCCMN
Vulgate_HebPs
Wulfila
Wycliffe

The following CrossWire commentaries also have a non-problematic short OT index:
MAK
Spurious
VietLCCMNCT


In Him,
DM



___
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] RTFHTML filter not escaping HTML entities

[DM Smith]

What is the likelihood/risk of an untrustworthy conf?

— DM Smith
From my phone. Brief. Weird autocorrections. 

On Dec 30, 2018, at 4:14 PM, Jaak Ristioja  wrote:

>> It looks like BibleTime, too, is guilty of not properly escaping those.
> 
> Actually it seems that the RTFHTML filter in Sword (and Sword++ for that
> matter) does not properly escape HTML entities included in the RTF. So
> if the RTF includes  or any other HTML tags, these are passed on
> unmodified, wherease they should instead be escaped using ,  and
> similar entities. This could allow arbitrary HTML injection from the RTF.
> 
> J
> 
> 
> 
>> On 30.12.18 23:03, Jaak Ristioja wrote:
>> Btw, grepping my ~/.sword/mods.d/*.conf shows that  tags are used
>> elsewhere as well, e.g. in About= and DistributionNotes=. There are even
>> some ,  and  tags in About= and History_x.x= entries.
>> 
>> It looks like BibleTime, too, is guilty of not properly escaping those.
>> 
>> J
>> 
>>> On 30.12.18 10:32, David Haslam wrote:
>>> Wouldn’t the points about HTML apply just as equally to the existing 
>>> ShortPromo key ?
>>> 
>>> Some front-ends already jump to the URL specified in the href, and can open 
>>> a browser to do so.
>>> 
>>> David
>>> 
>>> Sent from ProtonMail Mobile
>>> 
>>>> On Sun, Dec 30, 2018 at 00:39, Jaak Ristioja  wrote:
>>>> 
>>>> I like the idea, because it is useful information for the users. Here
>>>> are some of the thoughts I gathered for this:
>>>> 
>>>> https://en.wikipedia.org/wiki/Brainstorming;>
>>>> 
>>>> Why can't the About= entry contain this information?
>>>> 
>>>> I'm unsure whether "UnlockInfo" is the best name.
>>>> 
>>>> Is it safe to assume that this entry will only be relevant for modules
>>>> with a CipherKey= entry?
>>>> 
>>>> Using HTML might be a can of worms:
>>>> * What version of HTML is permitted?
>>>> * How do we ensure future-compatibility?
>>>> * If the contents for the UnlockInfo field are to contain a segment of
>>>> HTML (and not a whole HTML document), what is the content model?
>>>> * For example, would it be safe to embed the contents of the
>>>> UnlockInfo field directly inside a  element or should it be a ?
>>>> * Can UnlockInfo= contain
>>>> /

Re: [sword-devel] UnlockInfo .conf entry

[DM Smith]

JSword only allows  in the fields as documented in the wiki. In other fields 
it escapes the HTML.

The CrossWire repo should not have spurious HTML. 


— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Dec 30, 2018, at 4:03 PM, Jaak Ristioja  wrote:
> 
> Btw, grepping my ~/.sword/mods.d/*.conf shows that  tags are used
> elsewhere as well, e.g. in About= and DistributionNotes=. There are even
> some ,  and  tags in About= and History_x.x= entries.
> 
> It looks like BibleTime, too, is guilty of not properly escaping those.
> 
> J
> 
>> On 30.12.18 10:32, David Haslam wrote:
>> Wouldn’t the points about HTML apply just as equally to the existing 
>> ShortPromo key ?
>> 
>> Some front-ends already jump to the URL specified in the href, and can open 
>> a browser to do so.
>> 
>> David
>> 
>> Sent from ProtonMail Mobile
>> 
>>> On Sun, Dec 30, 2018 at 00:39, Jaak Ristioja  wrote:
>>> 
>>> I like the idea, because it is useful information for the users. Here
>>> are some of the thoughts I gathered for this:
>>> 
>>> https://en.wikipedia.org/wiki/Brainstorming;>
>>> 
>>> Why can't the About= entry contain this information?
>>> 
>>> I'm unsure whether "UnlockInfo" is the best name.
>>> 
>>> Is it safe to assume that this entry will only be relevant for modules
>>> with a CipherKey= entry?
>>> 
>>> Using HTML might be a can of worms:
>>> * What version of HTML is permitted?
>>> * How do we ensure future-compatibility?
>>> * If the contents for the UnlockInfo field are to contain a segment of
>>> HTML (and not a whole HTML document), what is the content model?
>>> * For example, would it be safe to embed the contents of the
>>> UnlockInfo field directly inside a  element or should it be a ?
>>> * Can UnlockInfo= contain
>>> /

Re: [sword-devel] Is there a server outage?

[DM Smith]

Everything should be working now.

> On Dec 18, 2018, at 9:13 AM, DM Smith wrote:
> 
> I’m on my way to work. I’ll see if I can get a moment to look once there. 
> Those two are different web servers.
> 
> — DM Smith
> From my phone. Brief. Weird autocorrections. 
> 
> On Dec 18, 2018, at 8:13 AM, Tuomas Airaksinen  
>> My observations:
>> 
>> tracker.crosswire.org <http://tracker.crosswire.org/> does not respond 
>> (seems down), 
>> but crosswire.org <http://crosswire.org/> seems responsive (module installs 
>> in And Bible work).
>> 
>> ti 18. jouluk. 2018 klo 10.35 David Haslam kirjoitti:
>> Attempting to refresh the module source gives long duration egg timer, 
>> followed by "no modules here" after time out.
>> 
>> Is there a server outage?
>> 
>> David
>> 
>> Sent from ProtonMail Mobile
>> 
>> 
>> -- 
>> T: Tuomas
___
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] Is there a server outage?

[DM Smith]

I’m on my way to work. I’ll see if I can get a moment to look once there. Those 
two are different web servers.

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Dec 18, 2018, at 8:13 AM, Tuomas Airaksinen  
> wrote:
> 
> My observations:
> 
> tracker.crosswire.org does not respond (seems down), 
> but crosswire.org seems responsive (module installs in And Bible work).
> 
> ti 18. jouluk. 2018 klo 10.35 David Haslam (dfh...@protonmail.com) kirjoitti:
>> Attempting to refresh the module source gives long duration egg timer, 
>> followed by "no modules here" after time out.
>> 
>> Is there a server outage?
>> 
>> David
>> 
>> Sent from ProtonMail Mobile
>> ___
>> 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
> 
> 
> -- 
> T: Tuomas
> ___
> 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] Modules, Tracker - some remarks

[DM Smith]

The Internet Wayback Machine is useful for dead URLs. I’ve used it to find 
resources no longer available and to make contact w people. 

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Dec 2, 2018, at 10:47 AM, "ref...@gmx.net"  wrote:
> 
> Regarding how to find source:
> 
> In our newer and better modules a source is given in the conf file. But 
> sometimes that link is now dead.
> 
> 
> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
> 
> 
>  Original Message 
> Subject: [sword-devel] Modules, Tracker - some remarks
> From: ref...@gmx.net
> To: sword-devel 
> CC: 
> 
> 
> Hi to all
> 
> 1) I am so pleased and grateful for all the activity checking and testing 
> modules wrt issues mentioned on the tracker
> 
> 2) There is a substantial minority of modules we do have source texts for 
> (around 100) and I hold the key for them. They can not be shared to anyone, 
> usually, as they tend to be not public domain texts. But the upshot for them 
> is, I feel responsible in a direct way for them and take care of much in 
> these weeks. So if you see me commenting on a module as the matter being in 
> work, just move on , as it is in hand. 
> 
> 3) There is a majority of texts, and some of them are very old in terms of 
> CrossWire and we need to find sources for them, because we do not hold them. 
> So, if you do not see me commenting that things are in hand, the module 
> clearly requires a rebuilt and you want to push this actively forward, go and 
> find the source. 
> 
> 4) How to find sources:
> 
> Many public domain texts have been pushed forward and backward between 
> projects since the start of the internet, are in a poor state and badly or 
> not at all marked up, forced into KJV versification , or sometimes even 
> chopped up in order to support sectarian views. Commonly for important texts 
> though there exists somewhere someone who has decided to fix things. People 
> who do try and fix things make this often very clear. Others refer/defer to 
> them. It pays to get into direct contact with them to establish a link and 
> maybe even let them produce OSIS or USFM for our use. We certainly always 
> want to feed back any and all improvements we make to Mark Up etc.
> 
> 5)You find good authoritative source, put at least the link underneath the 
> tracker and explain shortly why this is in your view the best source, 
> particularly if there is a big choice. If you want to go and start working on 
> a module, even better
> 
> Thanks again to all!
> 
> 
> 
> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
> ___
> 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

Re: [sword-devel] Issue in AraNav (New arabic version)

[DM Smith]

The website is mis-configured. It should result in a 404 NOT FOUND. 
bugs.crosswire.org  has never been an URL for the 
bugs/tracker.

DM

> On Dec 1, 2018, at 7:56 AM, Karl Kleinpaste  wrote:
> 
> On 12/1/18 4:24 AM, Tuomas Airaksinen wrote:
>> where is bug tracker?
> http://bugs.crosswire.org/ 
> ("http" required?!?)
> 
> (somebody please explain to me: how does accessing this w/https make it show 
> VMR CRE?)
> ___
> 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] Issue in AraNav (New arabic version)

[DM Smith]

Probably a more complete answer than most want.

The url bugs.crosswire.org <http://bugs.crosswire.org/> is absolutely wrong. It 
should yield a 404 NOT FOUND.

Way back when we had crosswire.org/bugs <http://crosswire.org/bugs>. We use 
Jira for more than just bugs but also feature requests and project planning. So 
some years ago, I renamed it to crosswire.org/tracker 
<http://crosswire.org/tracker> and redirected bugs to tracker. I think that the 
old url no longer redirects.

We are slowly upgrading CrossWire’s server’s OS, running both the old and new 
in parallel. To migrate web content, we’ve resorted to sub-domain type URLs. So 
crosswire.org/tracker <http://crosswire.org/tracker> becomes 
tracker.crosswire.org <http://tracker.crosswire.org/> and the former redirects 
to the latter.

crosswire.org/ <http://crosswire.org/>… and www.crosswire.org/ 
<http://www.crosswire.org/>… will go to the old OS webserver. All other 
sub-domains will go to the new OS webserver. (If you ping the URLs you’ll note 
different IP addresses)

As to VMR CRE coming up, it is the default website on the new OS. It was 
migrated first. Once everything is migrated www.crosswire.org 
<http://www.crosswire.org/> will become the default.

We’ve got www2 as a temporary sub-domain to help with the migration.

Complicating the finishing of the migration:
Replacing old hardware.
Moving mailing lists (which have a web interface). Mailman 3.0 is available, 
but last time I checked there’s no migration path from 2.0 to 3.0.
Troy and I are doing the work. Greg has volunteered to help.

In His Service,
DM

> On Dec 1, 2018, at 8:57 AM, David Haslam  wrote:
> 
> Troy should be able to explain why https://bugs.crosswire.org/ 
> <https://bugs.crosswire.org/>
> (using HTTPS rather than HTTP) 
> takes users to a page called "Virtual Manuscript Room Collaborative Research 
> Environment (VMR CRE)"
> 
> AFAICT, this is related to the project he's involved with at Münster.
> 
> NB. The correct URL for our issues tracker is now 
> https://tracker.crosswire.org/ <https://tracker.crosswire.org/>
> 
> I'm sure DM Smith can confirm this, as it was he that made the change from 
> the tracker being on a directory under crosswire.org/
> After he made this change, I updated all my open tabs in Firefox that were 
> pointing to the previous URL.
> 
> Best regards,
> 
> David
> 
> Sent with ProtonMail <https://protonmail.com/> Secure Email.
> 
> ‐‐‐ Original Message ‐‐‐
> On Saturday, 1 December 2018 12:56, Karl Kleinpaste  
> wrote:
> 
>> On 12/1/18 4:24 AM, Tuomas Airaksinen wrote:
>>> where is bug tracker?
>> http://bugs.crosswire.org/ <http://bugs.crosswire.org/>
>> ("http" required?!?)
>> 
>> (somebody please explain to me: how does accessing this w/https make it show 
>> VMR CRE?)
> 
> ___
> 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] Problem with verse range linking osis2mod Windows v3431

[DM Smith]

The 32-bit was an earlier version. I don’t think the bit-ness matters. 

— DM Smith
 

> On Nov 24, 2018, at 6:23 AM, David Haslam  wrote:
> 
> So the reported bug arises only from the 64 bit compilation of osis2mod.exe 
> for Windows?
> 
> Have I got this right?
> 
> AFAIK, the 64 bit utilities are only maintained by Karl as bundled with 
> Xiphos releases. I think Greg only provides 32 bit utilities where he 
> compiles them from time to time for CrossWire as a service for Windows users. 
> 
> This being the case, the issue should really be picked up by Karl and tracked 
> accordingly. 
> 
> As the 32 bit utility works exactly as required, solving the 64 bit issue 
> would not be priority for SWORD developers, unless the root cause turns out 
> to be something more fundamental. 
> 
> Regards,
> 
> David
> 
> Sent from ProtonMail Mobile
> 
> 
>> On Sat, Nov 24, 2018 at 03:28, Dudeck, John  wrote:
>> Greetings.
>> 
>> Here is the pertinent info for reproducing my problem. (You'll have to copy 
>> and paste the OSIS source below into an xml file).
>> 
>> The text is a snippet of a commentary in French. There is only one article 
>> (div), for Romans 1:2-5.
>> 
>> I have tested this using osis2mod.exe with and without -z z compression, and 
>> with both -s 4 and -s 2, with no change in results.
>> 
>> When using the 64-bit osis2mod.exe that is furnished with the current 
>> Xiphos, I use this command line (the variables are filled in by a script):
>> "c:Program FilesXiphosinosis2mod.exe" %modpath% %srcfile% -s 4 -z z -b 3 
>> Segond > %modules%compilerr.txt 2>&1
>> This does not link verses 3, 4, and 5 to verse 2.
>> 
>> When using the 32-bit osis2mod.exe from the older Sword utilities, I use 
>> this command line:
>> "c:Program Files (x86)CrossWiresword-utilitiesosis2mod.exe" %modpath% 
>> %srcfile% -z z -b 3 Segond -s 4 > %modules%compilerr.txt 2>&1
>> This links verses 3-5 to verse 2 correctly.
>> 
>> This is the OSIS source text:
>> ==
>> 
>> http://www.crosswire.org/osis/namespace 
>> http://www.crosswire.org/osis/osisCore.2.1.1.xsd; 
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;  
>> xmlns="http://www.bibletechnologies.net/2003/OSIS/namespace;>
>> > canonical="false">
>> 
>>
>>Romains Commentaire biblique
>>Dickson, Brad
>>Bible. N.T. Romains--Commentaires.
>>2006
>>« C’est le mérite de ce commentaire de 
>> Brad Dickson de nous présenter le texte de cette épître d’une manière 
>> complète et facile d’accès. » - Alfred KuenTous sont-ils perdus sans Christ 
>> ? Comment être transformé à l’image du Christ ? Le salut est-il définitif ? 
>> Qu’est-ce que la prédestination ? Dieu a-t-il un projet particulier pour le 
>> peuple juif ? Comment vivre l’unité de la foi avec ceux qui ont des opinions 
>> différentes des nôtres ?Dans ce commentaire, Brad Dickson donne des outils 
>> au lecteur pour comprendre et vivre ce texte central de 
>> l’Écriture.
>>Éditions CLÉ
>>fr
>>Copyright 2006 Éditions 
>> CLÉ
>>
>>
>>Bible
>>
>> 
>> 
>> 
>> > annotateRef="Rom.1.2-Rom.1.5">
>> 
>> Parenthèse : l’Évangile (v. )
>> 
>>  cet Évangile, Dieu l’avait promis auparavant par ses prophètes dans les 
>> saintes Écritures, 3 il concerne son Fils, né de la 
>> descendance de David selon la chair, 4 et déclaré Fils de Dieu avec 
>> puissance selon l’Esprit de sainteté, par sa résurrection d’entre les morts 
>> : 5 Jésus-Christ notre Seigneur. C’est par lui que nous avons reçu la grâce 
>> et l’apostolat pour amener, en son nom, à l’obéissance de la foi toutes les 
>> nations, …
>> Paul nous communique en toute hâte deux informations concernant 
>> l’Évangile. D’abord, son ancienneté, car « Dieu l’avait 
>> promis auparavant » et ensuite, son centre d’intérêt car > type="bold">« il concerne son Fils ».
>> L’enracinement de l’Évangile dans les « 
>> saintes Écritures » est capital pour Paul. Il se défend ainsi de créer 
>> une nouvelle religion. Il voit dans la personne du Christ l’accomplissement 
>> des nombreuses prophéties qu’il citera tout au long de l’épître

Re: [sword-devel] Problem with verse range linking osis2mod Windows v3431

[DM Smith]

I’m on holiday and won’t be able to look at this for a while. I don’t know if 
someone else can sooner. Either way having your minimal test file would help. 

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Nov 21, 2018, at 8:03 PM, Dudeck, John  wrote:
> 
> Greetings,
> 
> I have been having fits trying to build commentary modules, because the 
> verses in a verse range are not linking to the first verse of the range. In 
> the past this was working.
> 
> I am working in Windows 10, with 64-bit Sword utilities.
> 
> I had updated to osis2mod Rev 3431 in order to get support for the French 
> versifications. Previously I was using Rev 2893.
> 
> I pared an osis file down to one single article (div) that was a commentary 
> on Rom.1.2-Rom.1.5. Verses 3-5 were not being linked to verse 2 using the 
> 64-bit version 3431 osis2mod.exe.
> 
> I then changed the path to the 32-bit version 2893 osis2mod.exe file and ran 
> the exact same compile script. The module that was generated DOES link verses 
> 3-5 to verse 2.
> 
> Is there something that I need to do differently with the newer version of 
> osis2mod to get it to link? Or how can I get a fully functional set of Sword 
> utilities for Windows?
> 
> Thanks!
> 
> John Dudeck
> Programmer at Editions Cle Lyon, France
> john.dud...@sim.orgj...@editionscle.com
> --
> "The tar pit of software engineering will continue to be sticky
>  for a long time to come." -- Brooks
>   
> ___
> 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] How are linked verses encoded in our modules?

[DM Smith]

And for an arbitrary reference you may have to check the previous verses, too. 

— DM Smith

> On Nov 15, 2018, at 9:05 AM, Greg Hellings  wrote:
> 
> In the olden days this was detected by incrementing to the next verse, 
> calling renderText(), and doing a string comparison between it and the 
> previous verse to determine if they were the same.
> 
> Nowadays there is a method on SWModule named "isLinked(SWKey*, SWKey*)". It 
> has slightly more complicated logic (it doesn't render out the text, so it's 
> not susceptible to differences in filter and option settings, etc) and should 
> be more efficient than just a string comparison. You can pass it two verse 
> keys and it will tell you if they both point to the same entry or not. You 
> need to keep two copies of two different keys, increment one, ask the module 
> if they're linked. If they are, then keep incrementing one until you get to 
> the next verse that isn't linked. If they are not, then set the base key 
> equal to the incremented key and render out the next verse.
> 
> --Greg
> 
>> On Thu, Nov 15, 2018 at 5:09 AM Peter Von Kaehne  wrote:
>> How are linked verses practically encoded? 
>> 
>> I would like to fix the diatheke etc at some point to not put out duplicate 
>> verses and I do know that xiphos etc do not do so, so what wouldl I need to 
>> look for?
>> 
>> Thanks
>> 
>> 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
___
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] Search error in PocketSword for ancient Greek text

[DM Smith]

The SimpleAnalyzer does not “fold” these to the same value. If the text has a 
mix of upper and lower Greek, it uses latin to_upper to convert, which won’t.

For JSword, we pick an analyzer based upon the text’s script/language.

In Him,
DM

> On Nov 1, 2018, at 5:21 PM, Tom Sullivan  wrote:
> 
> On my keyboard, the two sigmas, are two different keys. They also have 
> different UTF-8 numbers. It seems that this could be a host program problem 
> to fix.
> 
> Tom Sullivan
> i...@beforgiven.info
> FAX: 815-301-2835
> -
> Great News!
> God created you, owns you and gave you commands to obey.
> You have disobeyed God - as your conscience very well attests to you.
> God's holiness and justice compel Him to punish you in Hell.
> Jesus Christ became Man, was crucified, buried and rose from the dead
> as a substitute for all who trust in Him, redeeming them from Hell.
> If you repent (turn from your sin) and believe (trust) in Jesus Christ,
> you will go to Heaven. Otherwise you will go to Hell.
> Warning! Good works are a result, not cause, of saving trust.
> More info is at www.esig.beforgiven.info
> Do you believe this? Copy this signature into your email program
> and use the Internet to spread the Great News every time you email.
> 
> On 11/1/18 4:31 PM, TS wrote:
>> Hi,
>>  In the past, when I have tried searching Greek text in PocketSword, it 
>> causes an error. I seem to recall, that it went something like this. If I 
>> put the full Greek word in, it won't find the word, but if I enter part of 
>> the Greek letters of a word in, then it will find the word. It seems to, for 
>> some reason, not like the Greek "s" suffix. I think, it may even be possible 
>> for me to enter a word and only leave out the last Greek character "s", and 
>> it can find the word. But if I add the "s", then it cannot find the word. 
>> Quite a lot of Greek words, by the way, end with an "s".
>>  I have searched Old Testament Greek text this way. Such as the 
>> Septuagint (LXX). It was in order to see how certain Hebrew words/concepts 
>> translate into Greek. And perhaps vice a versa.
>> -TS
>> --Sent from phone--
>> ___
>> 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
>> __
>> This email has been scanned by the Symantec Email Security.cloud service.
>> For more information please visit http://www.symanteccloud.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] Does the CLucene indexing work for non-English texts?

[DM Smith]

From memory, SWORD uses SimpleAnalyzer. This analyzer works well for Western 
European languages. It won’t for non-latinate texts. It may work in part.

The basic rule of thumb is that both the index has to be created with an 
analyzer and the search request has to be analyzed the same.

PocketSword uses externally created indexes which need to be downloaded to 
work. It uses the SWORD library for creation and for searching.

In Him,
DM



> On Nov 1, 2018, at 4:14 PM, TS  wrote:
> 
> Does the CLucene indexing work for non-English texts?
> 
> David's recent question about languages without spaces caused me to be a bit 
> curious about this matter. Briefly looking at the current Apache Lucene code, 
> their appears to be extra code for non-English text. However, this is in 
> comparison to the Clucene code for PocketSword. And I seem to recall that, in 
> general, the CLucene code in PocketSword may only be for reading indices and 
> not for writing them. Also, to clarify  further, it is possible that an index 
> is created, but with errors?
> For example, when I search Koine Greek texts, it does so erroneously. I 
> think that I'll start a separate post regarding the Greek search and indexing 
> in specific. 
> 
> -TS
> 
> --Sent from phone--
> ___
> 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] SWORD search index creation for Khmer, Thai and other languages with no space between words?

[DM Smith]

I don’t know what SWORD does.

JSword uses a Thai word break algorithm that’s part of Lucene. So to do a 
search, you have to know Thai well enough to know where words break or do an OR 
search.

Don’t remember if JSword does Khmer. Don’t think so.

The other technique that is available in Lucene is a windowing technique that 
breaks the search request into overlapping windows with a window size of a few 
characters (i think it is 4 to 5). I haven’t played with it.

DM

> On Oct 8, 2018, at 12:29 PM, David Haslam  wrote:
> 
> How does SWORD index a module written in a language whose writing system has 
> no space between words?
> 
> Examples include Khmer and Thai.
> 
> David
> 
> Sent from ProtonMail Mobile
> ___
> 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] Versification test modules in CrossWire Experimental ...

[DM Smith]

There’s also the need for v11n mapping to the KJV.

In Him,
DM

> On Sep 29, 2018, at 1:09 PM, Andrew T.  wrote:
> 
> Is this just a matter of creating the canon_xxx.h files or is there more to 
> it?  I've been playing around with alternate versifications (creating 
> canon_xxx.h files and them modifying versificationmgr.cpp to support).  But 
> I'm not a professional programmer even if I dabble ..
> 
> On Wed, Apr 4, 2018 at 9:53 AM David Haslam  > wrote:
> Would somebody like to volunteer to create the missing Versification test 
> modules in CrossWire Experimental?
> 
> i.e. For all those av11n more recent than for 
> MinimumVersion=1.6.1
> SwordVersionDate=2009-12-22
> 
> 
> Best regards,
> 
> David
> 
> Sent with ProtonMail  Secure Email.
> 
> ___
> 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

Re: [sword-devel] Module version numbers

[DM Smith]

Initially, JSword only accepted Major.Minor, converting that into a decimal. 
That was based on a poor understanding of the CrossWire wiki. That was changed 
to match SWORD’s 4 part “number” with a minor modification.

JSword will reject any version that doesn’t match the pattern: 
^(\d+)(?:.(\d+))?(?:.(\d+))?(?:.(\d+))?$

I think I encoded this to allow pretty much any single non-digit separator. The 
. will match any single character and \d+ is greedy. So it will accept Karl’s 
encoding.

The wiki on the conf clearly states: “Do not use non-numbers, such as 1.4a”
(See: http://wiki.crosswire.org/DevTools:conf_Files 
<http://wiki.crosswire.org/DevTools:conf_Files>)

The conf also documents that the third part should be incremented when only the 
conf is affected. The first or second when the module is different.

Here is JSword's code:
/**
 * Distribution License:
 * JSword is free software; you can redistribute it and/or modify it under
 * the terms of the GNU Lesser General Public License, version 2.1 or later
 * as published by the Free Software Foundation. This program is distributed
 * in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even
 * the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
 * See the GNU Lesser General Public License for more details.
 *
 * The License is available on the internet at:
 *  http://www.gnu.org/copyleft/lgpl.html
 * or by writing to:
 *  Free Software Foundation, Inc.
 *  59 Temple Place - Suite 330
 *  Boston, MA 02111-1307, USA
 *
 * © CrossWire Bible Society, 2011 - 2016
 *
 */
package org.crosswire.common.util;

import java.util.regex.Matcher;
import java.util.regex.Pattern;

/**
 * Version is an immutable representation of dotted "number" consisting of 1 to 
4 parts.
 * 
 * 
 * Here is the grammar for version strings:
 * 
 * 
 * version ::= major('.'minor('.'micro('.'nano)?)?)?
 * major ::= [0-9]+
 * minor ::= [0-9]+
 * micro ::= [0-9]+
 * nano  ::= [0-9]+
 * 
 * 
 * @see gnu.lgpl.License The GNU Lesser General Public License for details.
 * @author DM Smith
 */
public class Version implements Comparable {
public static final Pattern VERSION_PATTERN = 
Pattern.compile("^(\\d+)(?:.(\\d+))?(?:.(\\d+))?(?:.(\\d+))?$");

/**
 * Created a version identifier from the specified string.
 * 
 * @param version String representation of the version identifier.
 * @throws IllegalArgumentException If version is improperly
 * formatted.
 */
public Version(String version) {
if (version == null) {
throw new IllegalArgumentException("Null version not allowed.");
}
this.original = version;
this.parts = new int[] { -1, -1, -1, -1 };
Matcher matcher = VERSION_PATTERN.matcher(this.original);
if (matcher.matches()) {
int count = matcher.groupCount();
for (int i = 1; i <= count; i++) {
String part = matcher.group(i);
if (part == null) {
break;
}
parts[i - 1] = Integer.parseInt(part);
}
} else {
throw new IllegalArgumentException("invalid: " + version);
}
}

/**
 * Returns the original string representation of this version identifier.
 *
 * @return The original string representation of this version identifier.
 */
@Override
public String toString() {
return original;
}

@Override
public int hashCode() {
return original.hashCode();
}

/**
 * Compares this Version object to another object.
 * 
 * 
 * A version is considered to be equal to another version if all the
 * parts are equal.
 * 
 * @param object The Version object to be compared.
 * @return true if the two objects are equal.
 */
@Override
public boolean equals(Object object) {
if (!(object instanceof Version)) {
return false;
}

Version that = (Version) object;
if (that == this) {
return true;
}

for (int i = 0; i < parts.length; i++) {
if (parts[i] != that.parts[i]) {
return false;
}
}

return true;
}

/**
 * Compares this Version object to another object.
 * 
 * 
 * The comparison considers each of the parts (major, minor, micro, nano) 
in turn,
 * comparing like with like. At any point the comparison is not equal, a 
result is
 * known.
 * 
 * 
 * @param object The Version object to be compared.
 * @return A negative integer, zero, or a positive integer if this object is
 * less than, equal to, or greater than the specified
 * Version object.
 * @throws ClassCastException If the specified object is not a 
Version.
 */
publi

Re: [sword-devel] milestone element, osisRef attribute

[DM Smith]

Semantics:
osisID marks the address of the current item.
osisRef points the address of a different item that the current item references.

I think that the osis manual gives a suggested mechanism for two v11ns in the 
same document. My computer is in the shop and I cannot check. 
— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Sep 17, 2018, at 3:16 AM, David Haslam  wrote:
> 
> Thanks Horst for explaining. 
> 
> Why is osisRef used rather than osisID ?
> 
> The latter would be valid to the schema. 
> 
> David
> 
> Sent from ProtonMail Mobile
> 
> 
>> On Mon, Sep 17, 2018 at 06:22, Horst Sclemmer  
>> wrote:
>> Hi all, 
>> 
>> It's good to see this discussion going on. 
>> I try to briefly explain the need for having the osisRef in a milestone. 
>> As many people are able to read Russian, most translations for languages 
>> in the former Soviet Union use the SynadalProt versification. So, people 
>> comparing their translation with Russian scriptures won't be confused. 
>> On the other hand most of the (former Soviet Union) scriptures don't 
>> follow the versification in every detail. 
>> A very common difference is the problem you see in the Uighur Cyrillic 
>> with Romans 14 and 16. 
>> As Peter already mentioned, there is an anomalie with the last three 
>> verses of Romans 14 and 16. Most western translations (KJV) follow 
>> manuscripts that have these verses in Romans 16:25-27, whereas 
>> SynodalProt has them in Romans 14:24-26. 
>> Romans 16:25-27 seems to be the better place to have them, so most 
>> Central Asian translations decided, not to follow the SynodalProt 
>> versification here. 
>> 
>> The milestone types "x-vsys-..." and annotateRef 
>> annotateTypes="x-vsys-..." are used to reference these moved verses to 
>> the right verses. 
>> See 
>> https://github.com/JohnAustinDev/osis-converters/blob/master/scripts/bible/osis2sourceVerseSystem.xsl
>>  
>> for all the details and possible types. 
>> These milestone and annotateRef types are already used in a lot of OSIS 
>> files for scriptures in the IBT repository 
>> (http://ibt.org.ru/ftpmirror/pub/). 
>> 
>> I can remove the parts that are currently not supported by the OSIS schema. 
>> But as this is a general solution to deal with translations that vary 
>> from their versification, I would suggest to take the effort to adjust 
>> the OSIS schema and add the osisRef attribute to the milestone element. 
>> 
>> Kind regards 
>> 
>> Horst 
>> 
>> 
>> 
>> On 9/13/2018 6:21 PM, David Haslam wrote: 
>> > In the OSIS 2.1 Users Manual, for the milestone element only three 
>> > attribute names are mentioned: type, n, marker 
>> > 
>> > The osisRef attribute is currently defined only for the following OSIS 
>> > elements: catchWord, chapter, div, figure, note, q, reference 
>> > 
>> > If we wish to enhance the CrossWire updated OSIS schema, the request 
>> > should be added as a new subsection in this wiki page: 
>> > https://wiki.crosswire.org/OSIS_211_CR
>> > 
>> > What does the Uighur translation team envisage as the practical use of 
>> > osisRef in the OSIS example given? 
>> > What would we expect SWORD to do with it? 
>> > 
>> > Best regards, 
>> > 
>> > David 
>> > 
>> > Sent with ProtonMail Secure Email. 
>> > 
>> > ‐‐‐ Original Message ‐‐‐ 
>> > On Thursday, 13 September 2018 10:01, Peter von Kaehne  
>> > wrote: 
>> > 
>> >> Deal all, 
>> >> 
>> >> I am in the process of uploading an update to our cyrillic Uygyur 
>> >> module. 
>> >> 
>> >> There are a few instances where the new text does not validate due to 
>> >> use of osisRef in the milestone element. The author asserts that 
>> >> osisRef should be possible inside the milestone element and I can not 
>> >> see any reason indeed why it should not - other than "the schema does 
>> >> not allow it". Below an example. The textual background is a manuscript 
>> >> anomaly in Romans 14 and 16, where a couple of verses appear commonly 
>> >> at the end of Romans 16, but in some manuscript in Romans 14. 
>> >> 
>> >> 30965 > >> sID="Rom.14.23 Rom.14.24 Rom.14.25 Rom.14.26" type="x-vsys- 
>> >> fitted"/>> >> annotateType="x-vsys-source"/>Лекин бирәр йемәкликкә шәк кәлтүрүп 

Re: [sword-devel] Introductory material in OSIS (osis2mod)

[DM Smith]

The latest JSword should handle it just fine. When you grab an entire chapter 
it will grab verse 0 for the chapter. You have to get the entire book to get 
chapter 0. Or explicitly request 0. E.g. Matt.0.0-1.ff.

AndBible is the place to go. It uses an earlier version of JSword. Martin 
Denham is the author but he is unable to work on it. Volunteers are welcome. 

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Jun 15, 2018, at 4:19 PM, John Dudeck  wrote:
> 
> Ok. I think I just realized where my problem lies.
> 
> In Xiphos, the Introductory material is displaying the way you describe, 
> which is what I want.
> 
> But in AndBible, only the text that is withing the  tags is 
> displaying.
> 
> So I'm guessing this is a JSword or AndBible issue.
> 
> Whom do we contact about this?
> 
> John
> 
> > I’ll see if I can explain from memory. I’m the most recent contributor to 
> > osis2mod.
> >
> > Below “first” means the first encountered. For a complete Bible it is as 
> > you’d think, but if there is
> > only one testament or an incomplete testament, first may not refer to 
> > Genesis or Matthew. Also,
> > if a book or chapter doesn’t start with chapter or verse 1, then first 
> > doesn’t refer to 1.
> >
> > BTW, Intro, Heading, and Title are treated as the same. The toggle for 
> > headings handles all
> > three the same. Initially the thought was that there were only titles and 
> > sub-titles.
> >
> > Bible Intro. Osis2mod doesn’t know how to properly handle this. Everything 
> > before the first
> > testament is gathered as the Bible intro. OSIS doesn’t require testament 
> > divisions, but these are
> > needed to identify a Bible intro. 
> >
> > Testament Intro. Osis2mod doesn’t know how to properly handle this. 
> > Everything before the first
> > book is gathered as a testament intro. Everything after the last book of 
> > the Old Testament and
> > before the first book of the New Testament is gathered as the NT intro.
> >
> > Because osis2mod doesn’t know how to address Bible and Testament intro it 
> > is put in the first
> > location it knows is after that point. Practically, it becomes intro 
> > material in the first chapter.
> >
> > Book Intro. Everything inside the book tag before the first chapter tag is 
> > a Book intro. While it is
> > placed in chapter 0, verse 0 for the book, you never explicitly address 0. 
> > Osis2mod will figure it
> > out.
> >
> > Chapter Intro. This is the most difficult. A chapter intro comes after the 
> > chapter tag and comes
> > before the tag for verse 1. But some can be an intro that goes with the 
> > chapter and some is
> > taken as the intro to a verse. Since it is hard to control where one ends 
> > and the next begins, the
> > wiki has carefully laid out how osis2mod distinguishes the two. Special 
> > treatment is needed for
> > canonical Psalm headings. That which goes with the chapter intro is put 
> > into verse 0 for that
> > chapter, but you never explicitly address 0. Osis2mod will figure it out as 
> > well. The rest is
> > prefixed to verse 1 with special markup that osis2mod adds.
> >
> > Verse intro (aka titles). This is everything between 2 verses after the 
> > last closing tag of the prior
> > verse and before the start verse tag. Often this contains no text but only 
> > structural tags.
> >
> > Many frontends do not show intro material but only material from verse 1 
> > and following.
> > (Hopefully, I’m wrong.)
> >
> > If you make an uncompressed module and use the debug flag to show markers 
> > for verses you
> > can view the built data files in a readable format.
> >
> > If someone can explain to me how to address the intros using the SWORD 
> > engine, I’ll update
> > osis2mod to properly store them.
> >
> > The wiki can be improved. Feel free to make it read better.
> >
> > Hope this helps,
> >
> > DM
> >
> > On Jun 11, 2018, at 8:11 PM, John Dudeck  wrote:
> >
> > Would somebody please clarify the documentation on the wiki page for 
> > osis2mod.exe for
> > "Handling of Introductions, Titles and Inter-Verse Material". I can't make 
> > heads nor tails out
> > of it.
> >
> > Specifically, how are we supposed to tag (in OSIS) the introductory 
> > material in a Bible?
> > The wiki page says that SWORD looks for module, testament, book and chapter
> > introductory material." In the Bibles I am working on, everything inside of 
> &

Re: [sword-devel] Introductory material in OSIS (osis2mod)

[DM Smith]

I’ll see if I can explain from memory. I’m the most recent contributor to 
osis2mod.

Below “first” means the first encountered. For a complete Bible it is as you’d 
think, but if there is only one testament or an incomplete testament, first may 
not refer to Genesis or Matthew. Also, if a book or chapter doesn’t start with 
chapter or verse 1, then first doesn’t refer to 1.

BTW, Intro, Heading, and Title are treated as the same. The toggle for headings 
handles all three the same. Initially the thought was that there were only 
titles and sub-titles.

Bible Intro. Osis2mod doesn’t know how to properly handle this. Everything 
before the first testament is gathered as the Bible intro. OSIS doesn’t require 
testament divisions, but these are needed to identify a Bible intro. 

Testament Intro. Osis2mod doesn’t know how to properly handle this. Everything 
before the first book is gathered as a testament intro. Everything after the 
last book of the Old Testament and before the first book of the New Testament 
is gathered as the NT intro.

Because osis2mod doesn’t know how to address Bible and Testament intro it is 
put in the first location it knows is after that point. Practically, it becomes 
intro material in the first chapter.

Book Intro. Everything inside the book tag before the first chapter tag is a 
Book intro. While it is placed in chapter 0, verse 0 for the book, you never 
explicitly address 0. Osis2mod will figure it out.

Chapter Intro. This is the most difficult. A chapter intro comes after the 
chapter tag and comes before the tag for verse 1. But some can be an intro that 
goes with the chapter and some is taken as the intro to a verse. Since it is 
hard to control where one ends and the next begins, the wiki has carefully laid 
out how osis2mod distinguishes the two. Special treatment is needed for 
canonical Psalm headings. That which goes with the chapter intro is put into 
verse 0 for that chapter, but you never explicitly address 0. Osis2mod will 
figure it out as well. The rest is prefixed to verse 1 with special markup that 
osis2mod adds.

Verse intro (aka titles). This is everything between 2 verses after the last 
closing tag of the prior verse and before the start verse tag. Often this 
contains no text but only structural tags.

Many frontends do not show intro material but only material from verse 1 and 
following. (Hopefully, I’m wrong.)

If you make an uncompressed module and use the debug flag to show markers for 
verses you can view the built data files in a readable format.

If someone can explain to me how to address the intros using the SWORD engine, 
I’ll update osis2mod to properly store them.

The wiki can be improved. Feel free to make it read better.

Hope this helps,

DM

> On Jun 11, 2018, at 8:11 PM, John Dudeck  wrote:
> 
> Would somebody please clarify the documentation on the wiki page for 
> osis2mod.exe for "Handling of Introductions, Titles and Inter-Verse 
> Material". I can't make heads nor tails out of it.
> 
> Specifically, how are we supposed to tag (in OSIS) the introductory material 
> in a Bible? The wiki page says that SWORD looks for module, testament, book 
> and chapter introductory material." In the Bibles I am working on, everything 
> inside of chapter tags is being displayed, but none of the stuff outside the 
> chapter tags is being displayed.
> 
> It says that "A module introduction should be place into testament 0, book 0, 
> chapter 0, verse 0. A testament introduction should be placed into testament 
> 1 or 2, book 0, chapter 0, verse 0." What does this mean? Where do you tag 
> the testament number, the book number, etc? This is not explained in the OSIS 
> documentation, which only mentions book abbreviations, and nothing about 
> testaments.
> 
> It says "See OSIS Bibles for best practices in marking up titles and 
> introductions." But that page says nothing at all about introductions.
> 
> Thanks.
> 
> John Dudeck
> Programmer at Editions Cle Lyon, France
> john.dud...@sim.orgj...@editionscle.com
> --
> It's not a bug; it's an undocumented feature.
>   
> ___
> 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] Module upload: FreLXX

[DM Smith]

JSword doesn’t show/hide “accents”. This is a deliberate design decision. 

— DM Smith


> On Jun 11, 2018, at 7:46 AM, David Haslam  wrote:
> 
> Has anything similar been done for the equivalent JSword filter?

___
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: FreLXX

[DM Smith]

I think it is a bug in the SWORD engine if single right quotation mark is seen 
as a Greek diacritic.

Will look later to verify.

If it is then the module should not have the option. 

— DM Smith


> On Jun 7, 2018, at 8:54 AM, "ref...@gmx.net"  wrote:
> 
> If a Greek accent is in use, the filter will be there. If this is a bug, I.e. 
> there should not be a Greek accent, please highlight this at source. I guess 
> this is the right approach here too. Then the next iteration will not have a 
> spurious filter
> 
> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
> 
> 
>  Original Message 
> Subject: Re: [sword-devel] Module upload: FreLXX
> From: David Haslam 
> To: SWORD Developers' Collaboration Forum 
> CC: 
> 
> 
> This line in frelxx.conf is superfluous:
> 
> GlobalOptionFilter=UTF8GreekAccents
> 
> I think it's triggered in confmaker script by the presence of these 
> characters.
> U+2019’   656 RIGHT SINGLE QUOTATION MARK
> 
> NB. The source text is inconsistent in which character is used for the 
> typographical apostrophe. cf.
> U+0027'   39,200  APOSTROPHE
> 
> Example:
> Exodus 3:13 contains "les fils d'Israël" (character U+0027 used)
> Exodus 3:15 contains "aux fils d’Israël" (character U+2019 used)
> 
> When the Greek Accents filter is disabled (in Xiphos) the latter becomes "aux 
> fils dIsraël" (without the apostrophe).
> 
> There are no Greek letters in the module, so the GreekAccents filter should 
> not be included.
> 
> ​Best regards,
> 
> David
> 
> Sent with ProtonMail Secure Email.​
> 
> ‐‐‐ Original Message ‐‐‐
> 
> On 4 June 2018 7:38 AM, wrote:
> 
> > Dear All,
> > 
> > This is to announce that we have just now uploaded FreLXX.
> > 
> > This is is an updated version of FreLXX.
> > 
> > Many thanks to update for the hard work.
> > 
> > yours
> > 
> > The Module Team
> > 
> > P.S.: This email is sent automatically on upload of a new/updated module
> > 
> > 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
___
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] CrossWire site certificate expired on 4 May

[DM Smith]

Which url? I thought I got them all earlier today. 

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On May 30, 2018, at 7:07 AM, David Haslam  wrote:
> 
> Modern browsers will not let me connect via HTTPS to the CrossWire wiki (and 
> other places on the server) because the certificate expired on 4 May.
> 
> How soon can this be fixed?
> 
> Best regards,
> 
> David
> 
> Sent with ProtonMail Secure Email.
> 
> ___
> 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] osisID for merged verses

[DM Smith]

XML doesn’t allow for an attribute to be listed twice. It will either error or 
use one. 

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On May 17, 2018, at 6:10 PM, Michael H <cma...@gmail.com> wrote:
> 
> This is a question: 
> 
> Is there anything in OSIS (or Sword coding) that limits the osisID 1 to 1 to 
> a milestone?  Would including more than one osisID within a milestone create 
> errors? 
> 
> 
>  />Dieu dit à Noé de construire un grand bateau
> 9-10Voici l’histoire de Noé. Noé est le père de trois fils : Sem, Cham et 
> Japhet. Parmi les hommes de son époque, Noé est un homme juste, il fait ce 
> qui plaît à Dieu. Il suit le chemin de Dieu.
> 
> 
> 
> 
> 
>> On Thu, May 17, 2018 at 2:06 PM, Troy A. Griffitts <scr...@crosswire.org> 
>> wrote:
>> Hi John,
>> 
>> Yes, an osisID does not allow a range.  I believe our import tool osis2mod 
>> will accept a range even though it is not valid OSIS.  Give it a try and see 
>> how it goes.
>> 
>> Troy
>> 
>>> On 05/17/2018 11:59 AM, John Dudeck wrote:
>>> Greetings,
>>> 
>>> I am trying to create a module for a Bible (French Parole de Vie) that has 
>>> about 160 verses that are merges of two or more verses. My source file 
>>> (from Logos) has milestones that give the verse range.
>>> 
>>> I converted these to OSIS milestones such as:
>>> 
>>> Dieu dit à 
>>> Noé de construire un grand bateau
>>> 9-10Voici l’histoire de Noé. Noé est le père de trois fils : Sem, Cham 
>>> et Japhet. Parmi les hommes de son époque, Noé est un homme juste, il fait 
>>> ce qui plaît à Dieu. Il suit le chemin de Dieu.
>>> 
>>> 
>>> 
>>> When I validate this with http://www.crosswire.org/osis/osisCore.2.1.1.xsd 
>>> I get errors of not being valid osisIDtype.
>>> 
>>> How should I tag verse milestones for verses that cover more than one verse 
>>> reference?
>>> 
>>> Thanks.
>>> 
>>> John Dudeck
>>> Programmer at Editions Cle Lyon, France
>>> john.dud...@sim.orgj...@editionscle.com
>>> --
>>> It's not a bug; it's an undocumented feature.
>>>   
>>> 
>>> 
>>> ___
>>> 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
___
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] osisID for merged verses

[DM Smith]

Yes. Osis2mod should accept a range. 

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On May 17, 2018, at 3:06 PM, Troy A. Griffitts <scr...@crosswire.org> wrote:
> 
> Hi John,
> 
> Yes, an osisID does not allow a range.  I believe our import tool osis2mod 
> will accept a range even though it is not valid OSIS.  Give it a try and see 
> how it goes.
> 
> Troy
> 
>> On 05/17/2018 11:59 AM, John Dudeck   wrote:
>> Greetings,
>> 
>> I am trying to create a module for a Bible (French Parole de Vie) that has 
>> about 160 verses that are merges of two or more verses. My source file (from 
>> Logos) has milestones that give the verse range.
>> 
>> I converted these to OSIS milestones such as:
>> 
>> Dieu dit à 
>> Noé de construire un grand bateau
>> 9-10Voici l’histoire de Noé. Noé est le père de trois fils : Sem, Cham et 
>> Japhet. Parmi les hommes de son époque, Noé est un homme juste, il fait ce 
>> qui plaît à Dieu. Il suit le chemin de Dieu.
>> 
>> 
>> 
>> When I validate this with http://www.crosswire.org/osis/osisCore.2.1.1.xsd I 
>> get errors of not being valid osisIDtype.
>> 
>> How should I tag verse milestones for verses that cover more than one verse 
>> reference?
>> 
>> Thanks.
>> 
>> John Dudeck
>> Programmer at Editions Cle Lyon, France
>> john.dud...@sim.orgj...@editionscle.com
>> --
>> It's not a bug; it's an undocumented feature.
>>   
>> 
>> 
>> ___
>> 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

Re: [sword-devel] osisID for merged verses

[DM Smith]

osisID doesn’t allow for ranges. Just a space separated list. 

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On May 17, 2018, at 2:59 PM, John Dudeck <john.dud...@sim.org> wrote:
> 
> Greetings,
> 
> I am trying to create a module for a Bible (French Parole de Vie) that has 
> about 160 verses that are merges of two or more verses. My source file (from 
> Logos) has milestones that give the verse range.
> 
> I converted these to OSIS milestones such as:
> 
> Dieu dit à 
> Noé de construire un grand bateau
> 9-10Voici l’histoire de Noé. Noé est le père de trois fils : Sem, Cham et 
> Japhet. Parmi les hommes de son époque, Noé est un homme juste, il fait ce 
> qui plaît à Dieu. Il suit le chemin de Dieu.
> 
> 
> 
> When I validate this with http://www.crosswire.org/osis/osisCore.2.1.1.xsd I 
> get errors of not being valid osisIDtype.
> 
> How should I tag verse milestones for verses that cover more than one verse 
> reference?
> 
> Thanks.
> 
> John Dudeck
> Programmer at Editions Cle Lyon, France
> john.dud...@sim.orgj...@editionscle.com
> --
> It's not a bug; it's an undocumented feature.
>   
> ___
> 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] Android common module storage location

[DM Smith]

Apparently Troy found a way to search for repositories and use them. AndBible 
requests a standard storage location from the Android API and uses that. The 
path is specific to AndBible. I’ll check w Troy to see what he has done.

Martin is unable by current job to work on AndBible. I’m trying to figure it 
out. I’ve got the SDK installed and can emulate the app. I’ve also got Bishop 
source. I’ve very little time I can devote to it and it is all new to me.

DM

> On Apr 30, 2018, at 6:23 PM, Matt Zabojnik  wrote:
> 
> No. I installed modules on AndBible only and Bishop finds all of them. No 
> duplication.
> 
> On Mon, Apr 30, 2018 at 4:20 PM, Karl Kleinpaste  > wrote:
> Is there no one who has modules seen on Android by both AndBible and Bishop?
> Does everyone duplicate modules?
> 
> ___
> 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

Re: [sword-devel] intro material CSS

[DM Smith]

I’ll look into updating Osis2mod to not create self-closing divs. 

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Apr 9, 2018, at 8:30 AM, Karl Kleinpaste <k...@kleinpaste.org> wrote:
> 
>> On 04/08/2018 02:57 PM, Karl Kleinpaste wrote:
>> Anyway... I can do it myself for Xiphos. I just figure that generality would 
>> say that the engine is well-positioned to provide this
> 
> Never mind. I have a bug to report.
> 
> I decided to do CSS on my own after all, at least as a better stopgap. All 
> N:0 intro sections deliver content including their own  sections, 
> marking them as type=introduction. The problem is that they are self-closing 
> i.e. . This is seriously disliked by (in my case) WebKit.
> 
> Example, ESV2011 Gen.1.1:
> 
> As its name implies, Genesis is about beginnings. [...plain text elided...] 
> some prefer a date around 1260 b.c.
> 
> 
> The "introMaterial"  is my addition, along with its closing , and 
> the other  are provided from Sword. Xiphos (WebKit) reacts 
> very poorly to this, with my introMaterial handler turning everything from 
> here to end of chapter italic and yellow because the self-closing div are not 
> recognized as having closed at all.
> 
> Some web searching about self-closing div reveals, on the one hand, a lot of 
> confusion and mixed opinion, but on the other hand generally siding with the 
> idea that div is not self-closing, at least in practice/as implemented in 
> XHTML renderers like WebKit. I've gone to the trouble to catch this in gdb, 
> wipe out the errant self-closing div to spaces, and watch the result give me 
> a correct intro-only italic and yellow. (No, I don't intend yellow to be part 
> of my eventual plan here. This was just testing.)
> 
> It doesn't help to use span instead.
> 
> The use of self-closing div will have to end pretty much immediately.
> 
> https://github.com/crosswire/xiphos/issues/845
> ___
> 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] Front-ends in which search can find words in the canonical Psalm headings?

[DM Smith]

JSword indexes canonical titles as verse text.

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Apr 4, 2018, at 8:56 AM, David Haslam <dfh...@protonmail.com> wrote:
> 
> I suppose STEP Bible was going to be one most likely to succeed, seeing as 
> it's whole UI is based on a search field.
> 
> STEP is based on JSword.
> 
> Do any other JSword based apps support search within [Psalm] headings?
> 
> e.g. And Bible, Bible Desktop ?
> 
> Among SWORD based apps, neither Xiphos nor PocketSword has the feature in its 
> UI.
> 
> But even with -o h in the CL, Diatheke fails to find Neginoth, so I'm 
> thinking maybe the SWORD API itself is lacking this capability.
> 
> Either correct me if I'm wrong, or outline what steps it would require to add 
> the capability to SWORD.
> 
> Best regards,
> 
> Davi
> 
> Sent from ProtonMail Mobile
> 
> 
>> On Wed, Apr 4, 2018 at 12:58, Matěj Cepl <mc...@cepl.eu> wrote:
>> On 2018-04-04, 10:57 GMT, David Haslam wrote: > Do any front-ends support 
>> this? > > e.g. Search the KJV for Neginoth. 
>> https://www.stepbible.org/?q=version=KJV|xnave=neginoth=HNVUG 
>> Blessings, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz 
>> GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Courage is 
>> resistance of fear, mastery of fear, not absence of fear. 
>> ___ 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

Re: [sword-devel] Normalize the search string (comparing front-end apps)

[DM Smith]

Re case sensitivity, it was just a very simple example of the principle.

If it doesn’t find all then the search request and the index were not 
normalized the same. NFC and NFD are different normalizations.

Note, stripping diacritics may be an appropriate normalization.

JSword doesn’t properly handle Unicode either. 

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Mar 22, 2018, at 9:30 AM, David Haslam <dfh...@protonmail.com> wrote:
> 
> Thanks, DM.
> 
> My question was not about case-sensitivity, but about Unicode normalization.
> The main issue is composition vs decomposition and the canonical ordering of 
> diacritics in each glyph.
> 
> e.g. Suppose the module contains 181 instances of the name "Efraím" which has 
> 6 characters.
> Suppose a user enters in the search box instead "E f r a i ́ m" - (NB, remove 
> the spaces!)
> That's 7 characters when normalized to NFD, the acute accent now being a 
> separate character (U+0301 COMBINING ACUTE ACCENT).
> 
> In each front-end, will the search function find all the 181 instances (as 
> Eloquent does) ?
> Or (as with Xiphos) will it find none?
> 
> DM, what does BibleDesktop do here?
> 
> Best regards,
> 
> David
> 
> PS. ProtonMail converts automatically to NFC even though the text was keyed 
> in as NFD, hence the above kludge with spaces.
> 
> Sent with ProtonMail Secure Email.
> 
> ‐‐‐ Original Message ‐‐‐
>> On 22 March 2018 1:14 PM, DM Smith <dmsm...@crosswire.org> wrote:
>> 
>> It doesn’t matter that a search doesn’t use Lucene. The principle is the 
>> same. The search request has to be normalized to the same form as the 
>> searched text. For example a case insensitive search normalizes both to a 
>> single case. If it isn’t done, even on the fly, then search will fail at 
>> times. As they say, “even a blind squirrel gets a nut sometimes."
>> 
>> Regarding Lucene there are mulitple different analyzers (that’s what does 
>> the normalization in Lucene). Each normalizes differently. Each has it’s own 
>> documentation. The analyzer that SWORD uses is suited and was developed for 
>> English texts. It is not appropriate for non-Latin texts. There is a 
>> multi-language analyzer that is much better, ICUAnalyzer, which follows UAX 
>> #29 for tokenization. For details see: 
>> https://issues.apache.org/jira/browse/LUCENE-1488 You’ll note that I 
>> participate in its development.
>> 
>> The osis2mod proclivity for NFC is for display.
>> 
>> DM
>> 
>>> On Mar 22, 2018, at 8:19 AM, David Haslam <dfh...@protonmail.com> wrote:
>>> 
>>> Thanks DM,
>>> 
>>> Not all searches make use of the Lucene index !
>>> 
>>> e.g. In Xiphos, the advanced search panel gives the user a choice of which 
>>> type of search.
>>> Lucene is only one of these mutually exclusive options.
>>> 
>>> btw. Where is it documented that the creation of a Lucene search index 
>>> normalizes the Unicode for the index?
>>> Do we know for certain that this would occur irrespective of whether 
>>> normalization was suppressed during module build?
>>> i.e. With osis2mod option   -N do not convert UTF-8 or normalize UTF-8 to 
>>> NFC
>>> 
>>> 
>>> Best regards,
>>> 
>>> David
>>> 
>>> Sent with ProtonMail Secure Email.
>>> 
>>> ‐‐‐ Original Message ‐‐‐
>>>> On 22 March 2018 10:20 AM, DM Smith <dmsm...@crosswire.org> wrote:
>>>> 
>>>> The requirement is not that the search is normalized to nfc but rather 
>>>> that it is normalized the same as the index. This should not be a front 
>>>> end issue.
>>>> 
>>>> Btw it doesn’t matter how Hebrew is stored in the module. Indexing should 
>>>> normalize it to a form that is internal to the engine. 
>>>> 
>>>> — DM Smith
>>>> From my phone. Brief. Weird autocorrections. 
>>>> 
>>>>> On Mar 22, 2018, at 5:22 AM, David Haslam <dfh...@protonmail.com> wrote:
>>>>> Dear all,
>>>>> 
>>>>> Not all front-ends automatically normalize the search string to Unicode 
>>>>> NFC.
>>>>> e.g.
>>>>> Eloquent does
>>>>> Xiphos does not
>>>>> The data is incomplete for this feature in the table in our wiki page.
>>>>> https://wiki.crosswire.org/Choosing_a_SWORD_program#Search_and_Dictionary
>>>>> 
>>>>> Please woul

Re: [sword-devel] Normalize the search string (comparing front-end apps)

[DM Smith]

It doesn’t matter that a search doesn’t use Lucene. The principle is the same. 
The search request has to be normalized to the same form as the searched text. 
For example a case insensitive search normalizes both to a single case. If it 
isn’t done, even on the fly, then search will fail at times. As they say, “even 
a blind squirrel gets a nut sometimes."

Regarding Lucene there are mulitple different analyzers (that’s what does the 
normalization in Lucene). Each normalizes differently. Each has it’s own 
documentation. The analyzer that SWORD uses is suited and was developed for 
English texts. It is not appropriate for non-Latin texts. There is a 
multi-language analyzer that is much better, ICUAnalyzer, which follows UAX #29 
for tokenization. For details see: 
https://issues.apache.org/jira/browse/LUCENE-1488 
<https://issues.apache.org/jira/browse/LUCENE-1488> You’ll note that I 
participate in its development.

The osis2mod proclivity for NFC is for display.

DM

> On Mar 22, 2018, at 8:19 AM, David Haslam <dfh...@protonmail.com> wrote:
> 
> Thanks DM,
> 
> Not all searches make use of the Lucene index !
> 
> e.g. In Xiphos, the advanced search panel gives the user a choice of which 
> type of search.
> Lucene is only one of these mutually exclusive options.
> 
> btw. Where is it documented that the creation of a Lucene search index 
> normalizes the Unicode for the index?
> Do we know for certain that this would occur irrespective of whether 
> normalization was suppressed during module build?
> i.e. With osis2mod option   -Ndo not convert UTF-8 or normalize UTF-8 
> to NFC
> 
> 
> Best regards,
> 
> David
> 
> Sent with ProtonMail <https://protonmail.com/> Secure Email.
> 
> ‐‐‐ Original Message ‐‐‐
> On 22 March 2018 10:20 AM, DM Smith <dmsm...@crosswire.org> wrote:
> 
>> The requirement is not that the search is normalized to nfc but rather that 
>> it is normalized the same as the index. This should not be a front end issue.
>> 
>> Btw it doesn’t matter how Hebrew is stored in the module. Indexing should 
>> normalize it to a form that is internal to the engine. 
>> 
>> — DM Smith
>> From my phone. Brief. Weird autocorrections. 
>> 
>> On Mar 22, 2018, at 5:22 AM, David Haslam <dfh...@protonmail.com 
>> <mailto:dfh...@protonmail.com>> wrote:
>>> Dear all,
>>> 
>>> Not all front-ends automatically normalize the search string to Unicode NFC.
>>> e.g.
>>> Eloquent does
>>> Xiphos does not
>>> The data is incomplete for this feature in the table in our wiki page.
>>> https://wiki.crosswire.org/Choosing_a_SWORD_program#Search_and_Dictionary 
>>> <https://wiki.crosswire.org/Choosing_a_SWORD_program#Search_and_Dictionary>
>>> 
>>> Please would other front-end app developers supply the missing information. 
>>> Thanks.
>>> 
>>> Further thought:
>>> For front-ends that also have an Advanced search feature, would it not be a 
>>> useful enhancement to have a tick box option for Search string 
>>> normalization?
>>> Then if we do make any Biblical Hebrew modules with custom normalization, 
>>> search could at least still work for the "corner cases" in Hebrew, 
>>> providing the user gave the proper input in the search box.
>>> 
>>> cf. The source text for the WLC at tanach.us <http://tanach.us/> is not 
>>> normalized to NFC, but our module is.
>>> I'll refrain from going into a lot more detail here. There's an issue in 
>>> our tracker that covers this.
>>> 
>>> Best regards,
>>> 
>>> David
>>> 
>>> Sent with ProtonMail <https://protonmail.com/> Secure Email.
>>> 
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org 
>>> <mailto:sword-devel@crosswire.org>
>>> http://www.crosswire.org/mailman/listinfo/sword-devel 
>>> <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] Normalize the search string (comparing front-end apps)

[DM Smith]

The requirement is not that the search is normalized to nfc but rather that it 
is normalized the same as the index. This should not be a front end issue.

Btw it doesn’t matter how Hebrew is stored in the module. Indexing should 
normalize it to a form that is internal to the engine. 

— DM Smith
From my phone. Brief. Weird autocorrections. 

> On Mar 22, 2018, at 5:22 AM, David Haslam <dfh...@protonmail.com> wrote:
> 
> Dear all,
> 
> Not all front-ends automatically normalize the search string to Unicode NFC.
> e.g.
> Eloquent does
> Xiphos does not
> The data is incomplete for this feature in the table in our wiki page.
> https://wiki.crosswire.org/Choosing_a_SWORD_program#Search_and_Dictionary
> 
> Please would other front-end app developers supply the missing information. 
> Thanks.
> 
> Further thought:
> For front-ends that also have an Advanced search feature, would it not be a 
> useful enhancement to have a tick box option for Search string normalization?
> Then if we do make any Biblical Hebrew modules with custom normalization, 
> search could at least still work for the "corner cases" in Hebrew, providing 
> the user gave the proper input in the search box.
> 
> cf. The source text for the WLC at tanach.us is not normalized to NFC, but 
> our module is.
> I'll refrain from going into a lot more detail here. There's an issue in our 
> tracker that covers this.
> 
> Best regards,
> 
> David
> 
> Sent with ProtonMail Secure Email.
> 
> ___
> 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] The OSIS element inscription ?

[DM Smith]

All searches should be case insensitive, shouldn’t they? After all a word can 
begin a sentence.

And as noted elsewhere in the thread by you, once we have robust rendering for 
the inscription element and all the major frontends are using it, then we might 
make the change. We did it this way for the  element. At first for 
the KJV the content was LORD. Later it was changed to Lord with small-caps 
applied.

DM


> On Mar 21, 2018, at 4:26 AM, ref...@gmx.net wrote:
> 
> Hi DM, I am not sure I agree. For any number of reasons. 
> 
> We do not copy the presentation as such usually, but normally tag 
> semantically and then attach a presentation fitting to the original 
> presentation. So if small caps is wrong maybe textTransform=capitalize as 
> style, but ordinary text in the OSIS. 
> 
> The main positive result of the change I propose is that the inscriptions 
> turn up in searches, while they would not otherwise, unless one searches for 
> capitalized text. 
> 
> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
> 
> 
>  Original Message 
> Subject: Re: [sword-devel] The OSIS element inscription ?
> From: DM Smith 
> To: David Haslam ,SWORD Developers' Collaboration Forum 
> CC: 
> 
> 
> 
> 
> In the KJV, these are IN ALL CAPITAL LETTERS. I think that we are both 
> marking it semantically and having the text as given. I think this is correct.
> 
> I can see about rendering it differently. In the printed copy of the KJV, the 
> letters are spaced a bit more than otherwise.
> 
> DM
> 
>> On Mar 20, 2018, at 5:27 PM, David Haslam <dfh...@protonmail.com 
>> <mailto:dfh...@protonmail.com>> wrote:
>> 
>> Small caps style makes no change to UPPER CASE letters. The inscription text 
>> would have to change to Proper Case. 
>> 
>> But wouldn't this deviate from the KJV Oxford Edition of Benjamin Blayney?
>> 
>> 
>> Best regards, David
>> 
>> 
>> Sent from ProtonMail Mobile
>> 
>> 
>> On Tue, Mar 20, 2018 at 18:59, ref...@gmx.net <mailto:ref...@gmx.net> 
>> <ref...@gmx.net <mailto:ref...@gmx.net>> wrote:
>>> Hi DM, 
>>> 
>>> I am thinking that the "correct" presentation is capitalisation. Or better 
>>> small caps. Only to work the actual presentation needs to be taken out of 
>>> the text as it stands. Right now KJV inscriptions are both tagged and 
>>> capitalised. Can I ask for this being corrected? 
>>> 
>>> Thanks 
>>> 
>>> Peter 
>>> 
>>> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
>>> 
>>> 
>>>  Original Message  
>>> Subject: Re: [sword-devel] The OSIS element inscription ? 
>>> From: DM Smith 
>>> To: David Haslam ,SWORD Developers' Collaboration Forum 
>>> CC: 
>>> 
>>> 
>>> JSword -> Yes 
>>> 
>>>> On Mar 20, 2018, at 11:46 AM, David Haslam <dfh...@protonmail.com 
>>>> <mailto:dfh...@protonmail.com>> wrote:
>>>> 
>>>> No - I was just wondering whether we already did something in either SWORD 
>>>> or JSword. 
>>>> 
>>>> The likelihood is low, and a yes/no answer would suffice. 
>>>> 
>>>> cf. Examples of an inscription in Scripture include those in Acts 17:23 
>>>> and Revelation 17:5 & 19:16. 
>>>> 
>>>> btw. I'm aware that some front-ends support ancillary CSS files. 
>>>> 
>>>> Best regards, 
>>>> 
>>>> David 
>>>> 
>>>> Sent with ProtonMail <https://protonmail.com/> Secure Email. 
>>>> 
>>>> ‐‐‐ Original Message ‐‐‐ 
>>>> On 17 March 2018 2:31 PM, ref...@gmx.net <mailto:ref...@gmx.net> 
>>>> <ref...@gmx.net <mailto:ref...@gmx.net>> wrote: 
>>>> 
>>>>> Easily done with CSS, I would do little else. 
>>>>> 
>>>>> Do you have a list of occasions this could be used at? 
>>>>> 
>>>>> Sent from my mobile. Please forgive shortness, typos and weird 
>>>>> autocorrects. 
>>>>> 
>>>>> 
>>>>>  Original Message  
>>>>> Subject: [sword-devel] The OSIS element inscription ? 
>>>>> From: David Haslam 
>>>>> To: sword-devel mailing list 
>>>>> CC: 
>>>>> 
>>>>> 
>>>>> Does SWORD contain any code to render text 

Re: [sword-devel] The OSIS element inscription ?

[DM Smith]

In the KJV, these are IN ALL CAPITAL LETTERS. I think that we are both marking 
it semantically and having the text as given. I think this is correct.

I can see about rendering it differently. In the printed copy of the KJV, the 
letters are spaced a bit more than otherwise.

DM

> On Mar 20, 2018, at 5:27 PM, David Haslam <dfh...@protonmail.com> wrote:
> 
> Small caps style makes no change to UPPER CASE letters. The inscription text 
> would have to change to Proper Case. 
> 
> But wouldn't this deviate from the KJV Oxford Edition of Benjamin Blayney?
> 
> 
> Best regards, David
> 
> 
> Sent from ProtonMail Mobile
> 
> 
> On Tue, Mar 20, 2018 at 18:59, ref...@gmx.net <ref...@gmx.net 
> <mailto:ref...@gmx.net>> wrote:
>> Hi DM, 
>> 
>> I am thinking that the "correct" presentation is capitalisation. Or better 
>> small caps. Only to work the actual presentation needs to be taken out of 
>> the text as it stands. Right now KJV inscriptions are both tagged and 
>> capitalised. Can I ask for this being corrected? 
>> 
>> Thanks 
>> 
>> Peter 
>> 
>> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
>> 
>> 
>>  Original Message  
>> Subject: Re: [sword-devel] The OSIS element inscription ? 
>> From: DM Smith 
>> To: David Haslam ,SWORD Developers' Collaboration Forum 
>> CC: 
>> 
>> 
>> JSword -> Yes 
>> 
>>> On Mar 20, 2018, at 11:46 AM, David Haslam <dfh...@protonmail.com 
>>> <mailto:dfh...@protonmail.com>> wrote:
>>> 
>>> No - I was just wondering whether we already did something in either SWORD 
>>> or JSword. 
>>> 
>>> The likelihood is low, and a yes/no answer would suffice. 
>>> 
>>> cf. Examples of an inscription in Scripture include those in Acts 17:23 and 
>>> Revelation 17:5 & 19:16. 
>>> 
>>> btw. I'm aware that some front-ends support ancillary CSS files. 
>>> 
>>> Best regards, 
>>> 
>>> David 
>>> 
>>> Sent with ProtonMail <https://protonmail.com/> Secure Email. 
>>> 
>>> ‐‐‐ Original Message ‐‐‐ 
>>> On 17 March 2018 2:31 PM, ref...@gmx.net <mailto:ref...@gmx.net> 
>>> <ref...@gmx.net <mailto:ref...@gmx.net>> wrote: 
>>> 
>>>> Easily done with CSS, I would do little else. 
>>>> 
>>>> Do you have a list of occasions this could be used at? 
>>>> 
>>>> Sent from my mobile. Please forgive shortness, typos and weird 
>>>> autocorrects. 
>>>> 
>>>> 
>>>>  Original Message  
>>>> Subject: [sword-devel] The OSIS element inscription ? 
>>>> From: David Haslam 
>>>> To: sword-devel mailing list 
>>>> CC: 
>>>> 
>>>> 
>>>> Does SWORD contain any code to render text wrapped by the OSIS inscription 
>>>> element ? 
>>>> 
>>>> Best regards, 
>>>> 
>>>> David 
>>>> 
>>>> Sent from ProtonMail Mobile 
>>> 
>>> ___ 
>>> sword-devel mailing list: sword-devel@crosswire.org 
>>> <mailto:sword-devel@crosswire.org> 
>>> http://www.crosswire.org/mailman/listinfo/sword-devel 
>>> <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

Re: [sword-devel] The OSIS element inscription ?

[DM Smith]

JSword -> Yes

> On Mar 20, 2018, at 11:46 AM, David Haslam  wrote:
> 
> No - I was just wondering whether we already did something in either SWORD or 
> JSword.
> 
> The likelihood is low, and a yes/no answer would suffice.
> 
> cf. Examples of an inscription in Scripture include those in Acts 17:23 and 
> Revelation 17:5 & 19:16.
> 
> btw. I'm aware that some front-ends support ancillary CSS files.
> 
> Best regards,
> 
> David
> 
> Sent with ProtonMail  Secure Email.
> 
> ‐‐‐ Original Message ‐‐‐
> On 17 March 2018 2:31 PM, ref...@gmx.net  wrote:
> 
>> Easily done with CSS, I would do little else. 
>> 
>> Do you have a list of occasions this could be used at?
>> 
>> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
>> 
>> 
>>  Original Message 
>> Subject: [sword-devel] The OSIS element inscription ?
>> From: David Haslam 
>> To: sword-devel mailing list 
>> CC: 
>> 
>> 
>> Does SWORD contain any code to render text wrapped by the OSIS inscription 
>> element ?
>> 
>> Best regards,
>> 
>> David
>> 
>> Sent from ProtonMail Mobile
> 
> ___
> 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] osis2mod

[DM Smith]

Johan,

The output should be located at ./modules/texts/ztext/ts2009. Those folders 
should already be there. There should be some kind of failure message if it 
cannot open the output files for writing. If there are currently files there it 
should update them.

Since you didn’t include any flags for compression, the module that is put 
there won’t be compressed.

osis2mod doesn’t care about the module’s conf. That is supposed to be created 
based upon how you build the module, i.e. what flags you use for osis2mod. I’m 
guessing your conf doesn’t match with regard to compression. If that’s the case 
the module won’t work.

Also if you are on a modern version of Windows, you might not have permission 
to write to c:\Program Files (x86)\CrossWire\The SWORD 
Project\modules\texts\ztext\ts2009

Hope this helps,
DM Smith



> On Mar 11, 2018, at 10:00 AM, Johan <johan.mar...@messianic.co.za> wrote:
> 
> DM Smith,
>  
> It looks like this:
>  
> C:\Program Files (x86)\CrossWire\The SWORD Project>osis2mod 
> ./modules/texts/ztext/ts2009/ TS2009Ver100.osis.xml -c ts2009
> You are running osis2mod: $Rev: 3314 $
> Adding cipher filter with phrase: ts2009
> SUCCESS: osis2mod: has finished its work and will now rest
>  
> C:\Program Files (x86)\CrossWire\The SWORD Project>
>  
> Only the following are in the “The SWORD Project” folder:
> Utilities from Xiphos
> TS2009Ver100.osis.xml file
> ts2009.conf file in the “mods.d” folder
> The following folder structure, under “The SWORD Project”
> modules
>texts
>   ztext
>  ts2009
>  
> The .conf file starts with [TS2009] and the 
> DataPath=./modules/texts/ztext/ts2009/
>  
> Thank you,
>  
> Johan
> From: DM Smith [mailto:dmsm...@crosswire.org <mailto:dmsm...@crosswire.org>] 
> Sent: Sunday, 11 March 2018 14:18
> To: SWORD Developers' Collaboration Forum <sword-devel@crosswire.org 
> <mailto:sword-devel@crosswire.org>>
> Subject: Re: [sword-devel] osis2mod
>  
> Johan,
> Please tell us your entire command line. We can then answer your question. 
> 
> — DM Smith
>  
> 
> On Mar 11, 2018, at 7:43 AM, Johan <johan.mar...@messianic.co.za 
> <mailto:johan.mar...@messianic.co.za>> wrote:
> 
>> Good day,
>> I created a bible module (osis.xml) which I want to convert into a Sword 
>> bible module, using osis2mod.
>> It looks as if it works correctly, but there is no output.
>> I receive this message:
>> You are running osis2mod: $Rev: 3314 $
>> Adding cipher filter with phrase: xx
>> SUCCESS: osis2mod: has finished its work and will now rest
>> 
>> This is the message directly under the command line.
>> 
>> What could be the problem please?
>> 
>> Thanks for all the help.
>> 
>> Johan
>> 
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org 
>> <mailto:sword-devel@crosswire.org>
>> http://www.crosswire.org/mailman/listinfo/sword-devel 
>> <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 
> <mailto:sword-devel@crosswire.org>
> http://www.crosswire.org/mailman/listinfo/sword-devel 
> <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] osis2mod

[DM Smith]

Johan,
Please tell us your entire command line. We can then answer your question. 

— DM Smith


> On Mar 11, 2018, at 7:43 AM, Johan <johan.mar...@messianic.co.za> wrote:
> 
> Good day,
> 
> I created a bible module (osis.xml) which I want to convert into a Sword 
> bible module, using osis2mod.
> 
> It looks as if it works correctly, but there is no output.
> 
> I receive this message:
> 
> You are running osis2mod: $Rev: 3314 $
> Adding cipher filter with phrase: xx
> SUCCESS: osis2mod: has finished its work and will now rest
> This is the message directly under the command line.
> What could be the problem please?
> Thanks for all the help.
> Johan
> ___
> 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] Using Multiple Front-ends

[DM Smith]

JSword tries to discover all local repositories to present their modules to the 
user. It will install only to one location. By default, it will use ~/.sword on 
Un*x. I forget where on modern windows, but it is different than Xiphos. And on 
Mac it will ~/Library/Application Support/Sword.

Just looked at And Bible and it uses Environment.getExternalStorageDirectory() 
+ "/Android/data/"+PACKAGE_NAME+"/files/, for modules. So it is over-riding 
JSword’s mechanism for finding modules and installing them. Don’t know how 
Bishop was able to find them.

In Him,
DM


> On Mar 4, 2018, at 9:05 PM, Karl Kleinpaste  wrote:
> 
> On 03/04/2018 08:46 PM, bschroe...@internode.on.net wrote:
>> I am using Linux, Windows and Android.
> FYI in Sword, this is in swmgr.cpp:
> const char *SWMgr::globalConfPath = 
> "/etc/sword.conf:/usr/local/etc/sword.conf";
> /etc/sword.conf references /usr/share/sword by default. Typically, though, 
> this is unused, module installation tending toward being a personal matter.
> 
> And so then $HOME/.sword is also checked in swmgr.cpp.
> 
> Along the way, $SWORD_PATH is handled.
> 
> OS-specific hackery includes the Windows check:
> // for various flavors of windoze...
> // check %ALLUSERSPROFILE%/Application Data/sword/
> 
> No mention of Android in the code, but it's Linux, except that I'm not aware 
> that $HOME means anything in Android...
> 
> Don't neglect that SWMgr's general goal is the amalgamation of all discovered 
> module areas, e.g. you can have modules in both /usr/share/sword and 
> ~/.sword. I don't know the rules for precedence in that case, if e.g. 
> kjv.conf is found in each.
> 
> This is all in Sword. No clues about JSword's habits.
> ___
> 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] Using Multiple Front-ends

[DM Smith]

As reported earlier, Bishop and And Bible use the same module location on the 
one device. If you install on one it will be available on the other. I don’t 
know if a restart is needed by the other app.

On Un*x, they are all stored at ~/.sword by default.

In Him,
DM

> On Mar 4, 2018, at 8:46 PM, bschroe...@internode.on.net wrote:
> 
> I am using Linux, Windows and Android.
> 
> What prompted it this time is that I just installed Bishop on Android, and 
> was immediately prompted to download some texts to get started.
> 
> I will try SWORD_PATH on my computers later (thank you), but for now it is 
> Android I am particularly thinking of.
> 
> Brian.
> 
> 
> - Original Message -
> From:
> "SWORD Developers' Collaboration Forum" 
> 
> To:
> , "SWORD Developers' Collaboration Forum" 
> 
> Cc:
> 
> Sent:
> Sun, 4 Mar 2018 19:40:52 -0600
> Subject:
> Re: [sword-devel] Using Multiple Front-ends
> 
> 
> By default, all the desktop apps I know about should use the same paths. On 
> phones, this probably depends greatly on which OS you're in. I don't think 
> it's possible with iOS, but it might be possible with Android. That would 
> depend on the app, though.
> 
> On Sun, Mar 4, 2018 at 7:36 PM,  > wrote:
> 
> When installing multiple front-ends on a phone or computer, how do I 
> configure them all to use the same texts?  At the moment they all want me to 
> download a separate copy for each of them.  So, for example, if I have 3 
> front-end applications and want KJV in each of them I have to download it 3 
> times and store 3 copies.
> 
> I assume there has to be a (simple) way to do this.
> 
> Brian.
> 
> ___
> 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

Re: [sword-devel] Using Multiple Front-ends

[DM Smith]

Correction. Not SWORD_HOME but SWORD_PATH. (Thx Karl. My memory was faulty.)

> On Mar 4, 2018, at 8:41 PM, DM Smith <dmsm...@crosswire.org> wrote:
> 
> Depends. iOS requires sandboxing of it’s resources. The desktop applications 
> use the standard locations which has changed over time on Windows. Older apps 
> and newer apps may not play together. I’m pretty sure that if you set 
> SWORD_HOME environment variable to the folder/directory holding mods.d and 
> modules that all will play well together. You may need to merge different 
> local repos to that new location.
> 
> In Him,
>   DM Smith
> 
>> On Mar 4, 2018, at 8:36 PM, bschroe...@internode.on.net wrote:
>> 
>> 
>> When installing multiple front-ends on a phone or computer, how do I 
>> configure them all to use the same texts?  At the moment they all want me to 
>> download a separate copy for each of them.  So, for example, if I have 3 
>> front-end applications and want KJV in each of them I have to download it 3 
>> times and store 3 copies.
>> 
>> I assume there has to be a (simple) way to do this.
>> 
>> Brian.
>> ___
>> 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

Re: [sword-devel] Using Multiple Front-ends

[DM Smith]

Depends. iOS requires sandboxing of it’s resources. The desktop applications 
use the standard locations which has changed over time on Windows. Older apps 
and newer apps may not play together. I’m pretty sure that if you set 
SWORD_HOME environment variable to the folder/directory holding mods.d and 
modules that all will play well together. You may need to merge different local 
repos to that new location.

In Him,
DM Smith

> On Mar 4, 2018, at 8:36 PM, bschroe...@internode.on.net wrote:
> 
> 
> When installing multiple front-ends on a phone or computer, how do I 
> configure them all to use the same texts?  At the moment they all want me to 
> download a separate copy for each of them.  So, for example, if I have 3 
> front-end applications and want KJV in each of them I have to download it 3 
> times and store 3 copies.
> 
> I assume there has to be a (simple) way to do this.
> 
> Brian.
> ___
> 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] Bishop for Android and iOS / JavaScript bindings

[DM Smith]

David,
I’ve installed it on my iPhone 6. Will do my iPad 2 later today.

I don’t think the iOS app store supports 32-bit only any more, but they might 
allow dual 32/64. I have an old iPhone 5 on which I can test. I don’t have a 
32-bit iPad like yours.

It’s not something you’ll be willing to do. I’m describing the process that I 
went through in case others are interested.

To install it, you need to be running MacOS. This is possible to do in a VM on 
Windows or Linux. I think that’s what Troy does. I have a Mac, so it isn’t a 
difficulty for me.

Within MacOS you have to install XCode from the Mac App Store and in XCode open 
Window->Devices and Simulators with your iOS device attached to your “Mac". 
Make the window wide enough to see the entire device “Identifier”. Right click 
on that, select copy and send that to Troy.

Troy will have to add that to the list of authorized devices and rebuild 
Bishop.ipa.

Download that ipa and in the same window, click + under INSTALLED APPS, 
navigate to that download and “Open” it. This will install it to your device.

Later, I think it’ll be possible to build from source in XCode.

DM

> On Mar 4, 2018, at 3:26 AM, David Haslam  wrote:
> 
> Hi Troy,
> 
> I've been ignoring Bishop on the grounds that I'd only ever seen it described 
> as being an Android OS app.
> 
> This is the first time I've seen it mentioned in connection with iOS devices.
> 
> My devices are iPhone 5 and iPad Mini. My wife has an iPhone 5S and iPad Mini.
> 
> Even so, unless it's in the Apple iStore, only users who jailbreak could 
> install it?  AFAICT, it's not there.
> 
> btw.  Is it a 64-bit app ?
> 
> Best regards,
> 
> David
> 
> Sent from ProtonMail Mobile
> 
> 
> On Sat, Mar 3, 2018 at 21:53, Troy A. Griffitts  > wrote:
>> Thanks for the feedback Michael,
>> 
>> I have added a new menu choice:
>> 
>> [ Settings ]
>> 
>>   -   Font Size  +
>> 
>> It seems to work well on both iOS and Android.  Please let me know if it 
>> makes the app more usable for you.  The update should now be available for 
>> your phone.
>> 
>> Thank you again for taking the time to provide valuable feedback.
>> 
>> Troy
>> 
>> 
>> 
>> On 03/03/2018 04:05 AM, Michael H wrote: 
>>> I already had AndBible installed.  
>>> 
>>> Bishop installed and recognized all the modules (at least 20+ bibles, i 
>>> haven't confirmed "ALL") that AndBible has present. I haven't attempted any 
>>> more module installs after installing Bishop, either from AndBible or 
>>> Bishop. 
>>> 
>>> The text is small on my Samsung Galaxy On5. Not horribly unreadably small, 
>>> but small for me to use for any length of time. I don't see settings to 
>>> adjust that, so I haven't spent much time on it. I can and will test more 
>>> if you have something specific.. But this isn't ready for my eyes yet. Very 
>>> promising tho. :-) Based on the images in the store screen, I would be 
>>> using it more if the text had size adjustment.  
>>> 
>>> 
>>> On Fri, Mar 2, 2018 at 11:05 PM, Troy A. Griffitts >> > wrote: 
>>> I've had 2 instances of problems running the app.  One was a report from a 
>>> user here, and another was trying to install the app on my TV.  In both 
>>> cases, the app showed a blank gray screen after install and and startup.
>>> 
>>> I have had debug versions on all my devices here at some point, so I'm not 
>>> a very good clean test case.  Has anyone had any luck installing and 
>>> getting the basic set of modules running? Or any problems?  Thanks for any 
>>> feedback.
>>> 
>>> https://play.google.com/store/apps/details?id=org.crosswire.bishop 
>>> 
>>> Troy
>>> 
>>> On 03/02/2018 01:31 PM, David Haslam wrote: 
 Suggestion: 
 Please edit https://wiki.crosswire.org/Frontends:Bishop 
  
 and add these details. 
 
 Best regards, 
 
 David 
 
 Sent with ProtonMail  Secure Email. 
 
 ‐‐‐ Original Message ‐‐‐ 
 On 1 March 2018 2:26 AM, Troy A. Griffitts  
  wrote: 
 
> Dear team, 
> You all know we've been working on Cordova bindings for SWORD for quite 
> some time now.  We now have a simple reader written in JavaScript which 
> will run unchanged on both Android and iOS.Bishop includes an InstallMgr 
> to auto-discover remote installation sources and let a user install SWORD 
> content. 
> I've kept the development code name "Bishop", my favorite android (from 
> Aliens) and almost appropriate for a Bible app :)  I've also tacked on 
> our boring moniker from our Windows app, "Bishop: The SWORD Project for 
> Android".  Long name but should get more search hits. 
> Basically, Bishop's UI has 2 basic 

Re: [sword-devel] Error reading ulCompOffset

[DM Smith]

Great.

If you can isolate the problem in a small test file, we’d like to improve 
Osis2mod. 

In Him,
   DM Smith


> On Feb 20, 2018, at 5:26 PM, Andrew T. <thules...@gmail.com> wrote:
> 
> I was able to make progress on this problem.
> 
> To share the resolution - I used the FILE: osisCore.2.1.1-cw-latest.xsd that 
> Tom provided rather than the  FILE: osisCore.2.1.1.xsd originally downloaded 
> from http://www.bibletechnologies.net/2003/OSIS/namespace.  I compared the 
> two and indeed the newer one (Tom provided) contained additional lines which 
> both enabled me to use xmllint to resolve what was causing my osis2mod errors 
> AND it fixed some of the xml lint errors occasionally popping up in other 
> modules.  Tom, I think you're osisCore file fixes problems.
> 
> A big thanks to Tom for providing it and indeed Peter you were correct.  The 
> xmllint errors enabled me to find mismatched tags and correct fundamental 
> problems with the OSIS structure.
> 
> That said I think DM Smiths recommendation to build up a module book-wise is 
> wise.  Im going to try changing my approach in building modules to do just 
> that.
> Thanks all for helpful insights.
> 
> ~A
> 
>> On Mon, Feb 19, 2018 at 1:11 PM, DM Smith <dmsm...@crosswire.org> wrote:
>> Osis2mod does not care much about whether it is actually semantically valid 
>> OSIS. Just that it is well formed OSIS.
>> 
>> To do this each file has to have a container element surrounding the entire 
>> content. … should do. But you certainly can have each 
>> book be a semantically complete OSIS document of one book.
>> 
>> DM
>> 
>> > On Feb 19, 2018, at 11:32 AM, Tom Sullivan <i...@beforgiven.info> wrote:
>> >
>> > DM:
>> >
>> > Can you give some more info on the -a option? Normally, the complete OSIS 
>> > file will have a header, then a body. The body will be broken into books. 
>> > So when running osis2mod the first time, do we repeat the header? Does the 
>> > first segment simply end abruptly without closing tags for the body as one 
>> > would normally do?
>> >
>> > For example (abbreviated greatly)
>> > 
>> > 
>> >  stuff
>> > 
>> > 
>> >  
>> >   more stuff
>> >  
>> >  now this is where we would normally put the next div if making module all 
>> > at once.
>> > 
>> > 
>> >
>> > or
>> >
>> > without -a:
>> > 
>> > 
>> >  stuff
>> > 
>> > 
>> >  
>> >   more stuff
>> >  
>> >
>> > then with -a:
>> >  now this is where we would normally put the next div if making module all 
>> > at once.
>> > 
>> > 
>> >
>> > OR what?
>> >
>> > I think you get the drift of my question. (SwordHammer makes modules all 
>> > at once, but it would be helpful in debugging to think about a feature to 
>> > produce just the bad part and show it to the user.)
>> >
>> > Many thanks.
>> >
>> > Tom
>> >
>> >
>> > Tom Sullivan
>> > i...@beforgiven.info
>> > FAX: 815-301-2835
>> > -
>> > Great News!
>> > God created you, owns you and gave you commands to obey.
>> > You have disobeyed God - as your conscience very well attests to you.
>> > God's holiness and justice compel Him to punish you in Hell.
>> > Jesus Christ became Man, was crucified, buried and rose from the dead
>> > as a substitute for all who trust in Him, redeeming them from Hell.
>> > If you repent (turn from your sin) and believe (trust) in Jesus Christ,
>> > you will go to Heaven. Otherwise you will go to Hell.
>> > Warning! Good works are a result, not cause, of saving trust.
>> > More info is at www.esig.beforgiven.info
>> > Do you believe this? Copy this signature into your email program
>> > and use the Internet to spread the Great News every time you email.
>> >
>> > On 02/19/2018 11:17 AM, DM Smith wrote:
>> >> Recommend breaking your input into files by book. Run the Osis2mod for 
>> >> Genesis as before but the others w -a.
>> >> This will incrementally build a module.
>> >> Smaller files are better handled by other xml tools.
>> >> — DM Smith
>> >> From my phone. Brief. Weird autocorrections.
>> >> On Feb 19, 2018, at 9:43 AM, Andrew T. <thules...@gmail.com 
>> >> <mailto:thules...@gmail.com>> wro