Re: [sword-devel] Bishop for Android and iOS / JavaScript bindings

[Michael Johnson]

Hello, Troy & all!

After a bit of testing, I have concluded that the Bishop app is awesome. :-)
Its current version works well on both iOS and Android.
I like its Scripture display layout. OK, there is some room for improvement in 
poetry display, making secondary and tertiary lines indented a little more like 
the NIV and World English Bible official printed editions do, but other than 
that, most things I think of now fall firmly in the camp of feature addition 
instead of bug fixes; like maybe more complete localization to other user 
interface languages.

The biggest flaw is not yet being in the Apple App Store for general use on iOS 
devices. Sure sending Troy a UDID and side loading a special compilation works 
for me for now, but it would get really tedious for Troy after more than just a 
few testers... and there are limits to how many testers you can have. I think 
it is at least as good as many iOS apps that are in Apple's App Store. I have 
an active Apple developer account, so I could submit it if you like, after I 
get back from the conference I am
enroute to, now.
 

On 03/01/2018 10: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 modes:
>
> *Reader*: which simply shows 1 chapter of up to 3 Bibles in parallel.
> *Verse* *Study*: When in reader mode, as the user scrolls, one verse will 
> always be active, when "Verse Study" is chosen from the menu, the user can 
> then drill down into that active verse.  Verse Study has 4 tools:*
> *
>
> *Word* *Study*: shows the verse broken down word by word, showing the 
> original Greek or Hebrew behind each word, along with a simple definition.*
> Commentary*: shows all installed commentary for that verse.
> *Witness* *Study*: shows all available ancient New Testament 
> manuscript witnesses which attest to the current verse.
> *Variant* *Study*: shows all variant between the manuscript witnesses 
> for the current verse.
>
> Other features include very basic bookmarks and search.  The Android release 
> has an initial attempt at BibleSync support to send your current verse out to 
> all your friends running Bishop on the same network (thanks Karl!).
>
> The initial goal of Bishop was to be the thinnest client on top of the 
> bindings, as an example and thus uses no 3rd party libraries, save jQuery.  
> Now that the initial release is completed and can serve as an example, we're 
> free to improve the mobile user interface if anyone feels called to join the 
> team and give it a shot.
>
> Installation locations follow.  It's best to let Bishop install its basic set 
> of SWORD modules upon first run, so it has a minimal set of tools it can use 
> to operate.  It will prompt you to do this when you first launch the 
> application and it finds no modules installed.
>
> Android users can install the app from:
>
> https://play.google.com/store/apps/details?id=org.crosswire.bishop
>
> iPhone users will need to send me their UDID for testing while we try to get 
> through the Apple Store approval process.  I haven't even tried yet as I 
> don't have much hope that it is "pretty" enough for them, but the download 
> link for the iPhone binary is here:
>
> https://crosswire.org/bishop/manifest.plist
>
> https://crosswire.org/bishop.ipa
>
> The code can be had from:
>
> http://git.crosswire.org/main/bishop
>
> Please let us know what you think if you are a user, and offer your 
> suggestions from a usability perspective.
>
> If you are a developer, please offer comments and suggest features you have a 
> desire and are willing to add.
>
> Please give us a great rating so we show up in a search in the Play Store and 
> let others know.  I think we have some unique feature that other app don't 
> offer and I've been using Bishop as my morning reader for a while now.  The 
> default fullscreen text without clutter is pleasant.
>
> Christ's best for you!
>
> Troy
>
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


-- 
signature

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

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 > > 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  
>> > 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 > 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
> 

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

[sword-devel] Diatheke and MarkDown format?

[David Haslam]

A thread was begun in December 2015 with this topic. My reminder was sent on 21 
November, last year.

See 
http://sword-dev.350566.n4.nabble.com/Diatheke-and-MarkDown-format-tt4655468.html#a4657703

Is anyone willing to step forward to develop the code for this?

Best regards,

David

Sent with [ProtonMail](https://protonmail.com) 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

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

[Peter Von Kaehne]

Hi David,

 

Wrt KJV etc Yes, and no. I would not want to issue a module if there is a serious problem with a frontend. I would not call this a serious problem by any account. The text remains unchanged. The inscription is recognisable without problem. So, I would not hesitate to update the KJV or any other relevant module for this matter irreespective of whether all frontends have cought up.

 

If a current libsword dependent frontend does not display the hi element with small caps the right way then this suggests that that frontend uses the the older html filter instead of the xhtml filter (or alternatively loads a different CSS sheet than supplied). The older filter hardcodes display while the xhtml filter has a by and large a semantic markup which then is CSS driven - which allows frontends to override the supplied CSS  either in general or specifically for some modules (which reminds me we need a Wiki article on that). In the old filter all hi elements which do not allow a hard coded non CSS dependent translation are automatically italicisied in order to do something useful with them.

 

Peter

 

Gesendet: Mittwoch, 21. März 2018 um 09:36 Uhr
Von: "David Haslam" 
An: "David Haslam" , "SWORD Developers' Collaboration Forum" 
Cc: "ref...@gmx.net" 
Betreff: Re: [sword-devel] The OSIS element inscription ?


Corrigendum

 

I should have written type="small-caps" for the hi element.

 

btw. The testing of this in Eloquent was done by someone else.

 



Best regards,

 

David


 

Sent with ProtonMail Secure Email.


 

‐‐‐ Original Message ‐‐‐

On 21 March 2018 9:19 AM, David Haslam  wrote:

 


Thanks Peter,

 

Whatever view each of us may have about the KJV module, this thread is more general.

Its about any modules that potentially may contain the inscription element.

 

Aside:

Small-caps already works for the divineName element in most front-ends.

Small-caps doesn't work for the hi element with type="small caps" for at least one front-end (Eloquent).

Currently, this defaults to italics.

 

We should also bear in mind that altering a module before all front-ends have implemented the proper rendering in a new release would reduce the quality of the output.

i.e. A Proper Case inscription for " The Mother Of Harlots " might not "cut the mustard" for some KJV readers.

 



Best regards,

 

David


 

Sent with ProtonMail Secure Email.


 

‐‐‐ Original Message ‐‐‐

On 21 March 2018 8: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  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  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  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 

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

[David Haslam]

Corrigendum

I should have written type="small-caps" for the hi element.

btw. The testing of this in Eloquent was done by someone else.

Best regards,

David

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On 21 March 2018 9:19 AM, David Haslam  wrote:

> Thanks Peter,
>
> Whatever view each of us may have about the KJV module, this thread is more 
> general.
> Its about any modules that potentially may contain the inscription element.
>
> Aside:
> Small-caps already works for the divineName element in most front-ends.
> Small-caps doesn't work for the hi element with type="small caps" for at 
> least one front-end (Eloquent).
> Currently, this defaults to italics.
>
> We should also bear in mind that altering a module before all front-ends have 
> implemented the proper rendering in a new release would reduce the quality of 
> the output.
> i.e. A Proper Case inscription for " The Mother Of Harlots " might 
> not "cut the mustard" for some KJV readers.
>
> Best regards,
>
> David
>
> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> On 21 March 2018 8: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  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  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  
>>> 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  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
>>> 

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

[David Haslam]

Thanks Peter,

Whatever view each of us may have about the KJV module, this thread is more 
general.
Its about any modules that potentially may contain the inscription element.

Aside:
Small-caps already works for the divineName element in most front-ends.
Small-caps doesn't work for the hi element with type="small caps" for at least 
one front-end (Eloquent).
Currently, this defaults to italics.

We should also bear in mind that altering a module before all front-ends have 
implemented the proper rendering in a new release would reduce the quality of 
the output.
i.e. A Proper Case inscription for " The Mother Of Harlots " might not 
"cut the mustard" for some KJV readers.

Best regards,

David

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On 21 March 2018 8: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  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  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  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  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___
sword-devel mailing list: sword-devel@crosswire.org

Re: [sword-devel] Diatheke ?

[David Haslam]

Has the UI changed without me noticing?

This is what I got using version 4.7 of diatheke that comes with Xiphos 4.0.6a 
for Windows.

S:\>xiphos\diatheke -b KJV -o h -k Ps 3
Psalms 3:1: LORD, how are they increased that trouble me! many are they that ris
e up against me.
Psalms 3:2: Many there be which say of my soul, There is no help for him in God.
Selah.
Psalms 3:3: But thou, O LORD, art a shield for me; my glory, and the lifter up o
f mine head.
Psalms 3:4: I cried unto the LORD with my voice, and he heard me out of his holy
hill. Selah.
Psalms 3:5: I laid me down and slept; I awaked; for the LORD sustained me.
Psalms 3:6: I will not be afraid of ten thousands of people, that have set thems
elves against me round about.
Psalms 3:7: Arise, O LORD; save me, O my God: for thou hast smitten all mine ene
mies upon the cheek bone; thou hast broken the teeth of the ungodly.
Psalms 3:8: Salvation belongeth unto the LORD: thy blessing is upon thy people.
Selah.
(KJV)

By contrast, this is what I get with one of the latest Windows binaries that 
Greg built.

S:\>utils32\diatheke -b KJV -o h -k Ps 3
Psalms 3:1: Lord, how are they increased that troub
le me! many are they that rise up against me.
A Psalm of David, when he fled from Absalom his son.Psalms 3:2: Many there be which say of my soul, There is no help for hi
m in God. Selah.
Psalms 3:3: But thou, O Lord, art a shiel
d for me; my glory, a
nd the lifter up of mine head.
Psalms 3:4: I cried unto
the Lord with my voice
, and he heard me out of
his holy hill. Selah.
Psalms 3:5: I laid me down and slept; I awaked; utils32\diatheke /?
...
Valid output_format values are: CGI, GBF, HTML, HTMLHREF, LaTeX, OSIS, RTF,
  ThML, WEBIF, XHTML, plain, and internal (def)

cf.
S:\>xiphos\diatheke /?
...
Valid output_format values are: GBF, ThML, RTF, HTML, HTMLHREF, XHTML, OSIS,
  CGI, and plain (def)

But had it been discussed and officially announced?

The really odd thing is that the diatheke version number is unchanged and is 
still 4.7...
S:\>utils32\diatheke /?
Diatheke command-line SWORD frontend Version 4.7
Copyright 1999-2014 by the CrossWire Bible Society
http://www.crosswire.org/sword/diatheke/
...
The copyright date range has not been refreshed either!

I trust this clarifies why I reported the matter, and explains how my output 
was different than Greg illustrated.

I suspect that we've had a series of patches to diatheke, including Peter's 
provision of LaTeX format.
Yet for none of these has diatheke been made subject to version number 
increments.

With so much water under the bridge since 2014, I suggest it's high time to 
release it as diatheke version 5.0

Best regards,

David

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On 21 March 2018 2:53 AM, Greg Hellings  wrote:

> It's easier to see the problem when using plain formatting:
>
> $ diatheke -b KJV -o h -f Plain -k Ps 3
> Psalms 3:1: LORD, how are they increased that trouble me! many are they that 
> rise up against me.
> A Psalm of David, when he fled from Absalom his son.
> Psalms 3:2: Many there be which say of my soul, There is no help for him in 
> God. Selah.
> Psalms 3:3: But thou, O LORD, art a shield for me; my glory, and the lifter 
> up of mine head.
> Psalms 3:4:
> I cried unto the LORD with my voice, and he heard me out of his holy hill. 
> Selah.
> Psalms 3:5: I laid me down and slept; I awaked; for the LORD sustained me.
> Psalms 3:6: I will not be afraid of ten thousands of people, that have set 
> themselves against me round about.
> Psalms 3:7: Arise, O LORD; save me, O my God: for thou hast smitten all mine 
> enemies upon the cheek bone; thou hast broken the teeth of the ungodly.
> Psalms 3:8: Salvation belongeth unto the LORD: thy blessing is upon thy 
> people. Selah.
> (KJV)
>
> --Greg
>
> On Tue, Mar 20, 2018 at 9:50 PM, Greg Hellings  
> wrote:
>
>> I'm not so sure your initial assertion is correct.
>>
>> $ diatheke -b KJV -o h -k Ps 3
>> Psalms 3:1: > savlm="strong:H03068">Lord, > savlm="strong:H07231">how are they increased > savlm="strong:H06862">that trouble me! many 
>> are they 
>> that rise up against me.
>> A Psalm 
>> of David, when he 
>> fled from > savlm="strong:H053">Absalom his 
>> son.Psalms 3:2: Many > type="added">there be which say 
>> of my soul, There 
>> is no help > savlm="strong:H0430">for him in God. Selah.
>>
>> If you notice carefully, the canonical title is there. It is just misplaced. 
>> It comes after the text of Psalm 3:1 and not before.
>>
>> --Greg
>>
>> On Tue, Mar 20, 2018 at 4:40 PM, David Haslam  wrote:
>>
>>> Maybe someone could patch diatheke to fix this?
>>> Best regards, David
>>>
>>> Sent from ProtonMail Mobile
>>>
>>> On Wed, Mar 14, 2018 at 12:14, David Haslam  wrote:
>>>
 Diatheke does not output the canonical Psalm titles when output option h 
 is used.

 Try this and 

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

[ref...@gmx.net]

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.DMOn Mar 20, 2018, at 5:27 PM, David Haslam  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  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  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






  

Re: [sword-devel] Diatheke ?

[David Haslam]

Thanks Greg for the patch.

Thanks also to everyone who provided insightful input.

Best regards,

David

Sent from ProtonMail Mobile

On Wed, Mar 21, 2018 at 03:33, Greg Hellings  wrote:

> On Tue, Mar 20, 2018 at 10:21 PM, Troy A. Griffitts  
> wrote:
>
>> If I had to guess, I suspect diatheke is not calling renderText before 
>> asking for the header. The renderText method triggers all entryAttributes to 
>> be filled. The header is an entryAttribute.
>
> Spot on. If I were offering commentary, I would call that a bug in the UX of 
> the API. But I do get why it is that way. Attaching a patch that solves the 
> problem.
>
> --Greg
>
>> On March 20, 2018 8:13:41 PM MST, Greg Hellings  
>> wrote:
>>
>>> To be quite specific: diatheke does not encounter that header in the 
>>> preverse content until it reaches Psalm 3:2 for some reason that is beyond 
>>> my ken. Therefore, it is properly rendering that content as preverse, but 
>>> it has attached it to the wrong verse. Output from my slightly modified 
>>> diatheke confirms this:
>>>
>>> $ ./inst/bin/diatheke -b KJV -o h -f Plain -k Ps 3
>>> key: Psalms 3:1
>>> header:
>>> Psalms 3:1: LORD, how are they increased that trouble me! many are they 
>>> that rise up against me.
>>> key: Psalms 3:2
>>> header: A 
>>> Psalm of David, >> savlm="strong:H01272">when he fled from >> savlm="strong:H053">Absalom his 
>>> son.
>>> A Psalm of David, when he fled from Absalom his son.
>>> Psalms 3:2: Many there be which say of my soul, There is no help for him in 
>>> God. Selah.
>>>
>>> --Greg
>>>
>>> On Tue, Mar 20, 2018 at 9:53 PM, Greg Hellings  
>>> wrote:
>>>
 It's easier to see the problem when using plain formatting:

 $ diatheke -b KJV -o h -f Plain -k Ps 3
 Psalms 3:1: LORD, how are they increased that trouble me! many are they 
 that rise up against me.
 A Psalm of David, when he fled from Absalom his son.
 Psalms 3:2: Many there be which say of my soul, There is no help for him 
 in God. Selah.
 Psalms 3:3: But thou, O LORD, art a shield for me; my glory, and the 
 lifter up of mine head.
 Psalms 3:4:
 I cried unto the LORD with my voice, and he heard me out of his holy hill. 
 Selah.
 Psalms 3:5: I laid me down and slept; I awaked; for the LORD sustained me.
 Psalms 3:6: I will not be afraid of ten thousands of people, that have set 
 themselves against me round about.
 Psalms 3:7: Arise, O LORD; save me, O my God: for thou hast smitten all 
 mine enemies upon the cheek bone; thou hast broken the teeth of the 
 ungodly.
 Psalms 3:8: Salvation belongeth unto the LORD: thy blessing is upon thy 
 people. Selah.
 (KJV)
 --Greg

 On Tue, Mar 20, 2018 at 9:50 PM, Greg Hellings  
 wrote:

> I'm not so sure your initial assertion is correct.
>
> $ diatheke -b KJV -o h -k Ps 3
> Psalms 3:1:  vineName>Lord, how are 
> they increased that trouble  savlm="strong:H07227">me! many  type="added">are they that rise 
> up against me.
> A 
> Psalm of David,  savlm="strong:H01272">when he fled from 
> Absalom his 
> son.Psalms 3:2: Many 
> there be  savlm="strong:H0559">which say of my 
> soul, There is  savlm="strong:H03444">no help for him in 
> God. Selah.
>
> If you notice carefully, the canonical title is there. It is just 
> misplaced. It comes after the text of Psalm 3:1 and not before.
>
> --Greg
>
> On Tue, Mar 20, 2018 at 4:40 PM, David Haslam  
> wrote:
>
>> Maybe someone could patch diatheke to fix this?
>> Best regards, David
>>
>> Sent from ProtonMail Mobile
>>
>> On Wed, Mar 14, 2018 at 12:14, David Haslam  
>> wrote:
>>
>>> Diatheke does not output the canonical Psalm titles when output option 
>>> h is used.
>>>
>>> Try this and see what I mean.
>>>
>>> diatheke -b KJV -o h -k Ps 3
>>>
>>> This is a significant lack of feature.
>>>
>>> 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
>>
>> --
>> 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