Thanks for the patch, Greg. Yes. Agreed it is not intuitive to the uninitiated.
The warring factions are that a module key can be changed with a reference
directly to its key, the module being oblivious to that fact that it changed.
Also, a module position might be incremented but never asked to
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 commentar
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.
On March 20, 2018 8:13:41 PM MST, Greg Hellings wrote:
>To be quite specific: diatheke does not encount
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
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,
I'm not so sure your initial assertion is correct.
$ diatheke -b KJV -o h -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 fo
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, 20
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 -
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?ThanksPeterSent from my mo
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:
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 ancil
Hi everyone,
The LCSH key in our .conf files is the Library of Congress Subject Heading
It may be helpful for someone with access to the server to perform a suitable
grep operation on all our .conf files
to extract the module name and the line[s] with an LCSH key (with the output
directed into
13 matches
Mail list logo
