Copy Bible Verses Customization Question

MJ. Smith said:

Dave Hooton said:

I thought of [ShortBookName] [ChapterNum].[VerseNum] but it does not work in the Header!  Hopefully others will know.

I would have sworn this had been fixed. Aaargh

What was fixed (as of 4.0c Beta 1) was the bug I reported which said that [FullBookName], [ShortBookName], and [ChapterNum] were not working when they appeared in the header. It hadn't occurred to me to test [VerseNum] because I'd never use a header when copying just one verse, but I suppose some people might.

Yep,

I discovered the same bug today, and found this thread pertaining to the subject. 

I couldn't tell from the thread whether someone had reported the bug to Logos.  Has someone?  Anyone have an idea how long it might take for it to get fixed?

Thanks,

me

While we're on the topic of CBV, how do I change it so that the closing speechmarks aren't spaced from the last character?

<!--
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-unhide:no;
mso-style-qformat:yes;
mso-style-parent:"";
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoFootnoteText, li.MsoFootnoteText, div.MsoFootnoteText
{mso-style-noshow:yes;
mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Calibri","sans-serif";}
-->

“Your righteousness is like the mountains of God; Your judgments are like a great deep. O Lord, You preserve man and beast. ” (Psalm 36:6, NASB95)  Should be "...and beast."

David Gullick said:

While we're on the topic of CBV, how do I change it so that the closing speechmarks aren't spaced from the last character?

“Your righteousness is like the mountains of God; Your judgments are like a great deep. O Lord, You preserve man and beast. ” (Psalm 36:6, NASB95)  Should be "...and beast."

This appears to be a problem only with certain versions (I've confirmed it with NASB95, ESV, LEB, and NKJV). But when I used the Quotation CBV style and copied from TNIV, the extra space wasn't in there between the end of the sentence and the closing quotation mark. The interesting thing is that TNIV is my preferred Bible. However when I changed my preferred Bible to ESV and tried it again, it still had the superflous space. This seems like a bug to me. I will report it as such and refer back to this thread.

UPDATE:

Further info, I tried copying a different verse (I tried, Gen 1:1 and John 1:1) in TNIV, and the extra space did appear for those ones, but it doesn't for Psalm 36:6, or any other verse in Psalms that I randomly tried. Weird.

I looked at the Quotation style definition, and here it is:

%NoCharFormatting
%NoRedLetter
%NoFootnotes
%NoCitation

=Header
<p>“<i>

=ForEachVerse
[VerseText]

=Footer
</i>” ([FullPassageRef], [Version])</p>

I wondered whether maybe it could be reconstructed to fix the problem. I made a new style My Quotation like this:

%NoCharFormatting
%NoRedLetter
%NoFootnotes
%NoCitation

=Header
<p>“

=ForEachVerse
<i>[VerseText]</i>

=Footer
” ([FullPassageRef], [Version])</p>

The problem still occurred. I also played around with putting some text immediately after [VerseText] inside the italic HTML markers.

It seems that the extra space is being added when the token [VerseText] is replaced. I don't know why it doesn't happen for certain verses in the TNIV.

UPDATE: Reported on wiki: http://wiki.logos.com/Bug$3a_Extra_space_included_at_end_of_replacement_for_[VerseText]_token_in_Copy_Bible_Verses

Fred Greco said:

Is there a way to have interleaved versions?

You could sort of get that using Text Comparison, with Horizontal Layout (choose that from the panel menu):

The text in this panel is selectable and you can right click on it and copy/paste to Word or wherever.

EDIT: If you paste the above into Word, it would come out in a table, but then you can do Convert Table to Text and it will come out interleaved (but without the full verse references and version in front of each verse):

English Standard Version

Nestle-Aland Greek New Testament, 27th Edition

Mt 1:1 The book of the genealogy of Jesus Christ, the son of David, the son of Abraham.

Mt 1:1 Βίβλος γενέσεως Ἰησοῦ Χριστοῦ υἱοῦ Δαυὶδ υἱοῦ Ἀβραάμ.

2 Abraham was the father of Isaac, and Isaac the father of Jacob, and Jacob the father of Judah and his brothers,

2 Ἀβραὰμ ἐγέννησεν τὸν Ἰσαάκ, Ἰσαὰκ δὲ ἐγέννησεν τὸν Ἰακώβ, Ἰακὼβ δὲ ἐγέννησεν τὸν Ἰούδαν καὶ τοὺς ἀδελφοὺς αὐτοῦ,

3 and Judah the father of Perez and Zerah by Tamar, and Perez the father of Hezron, and Hezron the father of Ram,

3 Ἰούδας δὲ ἐγέννησεν τὸν Φάρες καὶ τὸν Ζάρα ἐκ τῆς Θαμάρ, Φάρες δὲ ἐγέννησεν τὸν Ἑσρώμ, Ἑσρὼμ δὲ ἐγέννησεν τὸν Ἀράμ,

4 and Ram the father of Amminadab, and Amminadab the father of Nahshon, and Nahshon the father of Salmon,

4 Ἀρὰμ δὲ ἐγέννησεν τὸν Ἀμιναδάβ, Ἀμιναδὰβ δὲ ἐγέννησεν τὸν Ναασσών, Ναασσὼν δὲ ἐγέννησεν τὸν Σαλμών,

5 and Salmon the father of Boaz by Rahab, and Boaz the father of Obed by Ruth, and Obed the father of Jesse,

5 Σαλμὼν δὲ ἐγέννησεν τὸν Βόες ἐκ τῆς Ῥαχάβ, Βόες δὲ ἐγέννησεν τὸν Ἰωβὴδ ἐκ τῆς Ῥούθ, Ἰωβὴδ δὲ ἐγέννησεν τὸν Ἰεσσαί,

Update:

The other replacement tokens will not be supported in header and footer text.  The thinking is that [FullPassageRef] and [ShortPassageRef] make more sense in that context than [FullVerseRef] and [ShortVerseRef]. And [VerseNum] is not supported because ranges cannot be reasonably rendered. An example: John 1:50-2:2. Rendering "50-2" is not useful.

MickeyEllis01 said:

So...will I ever be able to customize the format to be like the following:

(Mt 1): 1 The book of the genealogy of Jesus Christ, the son of David, the son of Abraham.  2 Abraham was the father of Isaac, and Isaac the father of Jacob, and Jacob the father of Judah and his brothers,

Try this code

=Header
<p><b>([ShortBookName] [ChapterNum])</b>: =ForEachVerse
 [VerseNum] [VerseText]

=Footer
</p>

MickeyEllis01 said:

Instead of putting (Mt 1), it puts ([ShortBookName] [ChapterNum])

Any ideas?

Ah, I forgot, this was a bug that was fixed in 4.0c Beta 1, sorry about that. This will work when 4.0c is released (or you could decide to join us in Beta testing).

MickeyEllis01 said:

Thanks for the invite, but I already have too much on my plate

Any idea when 4.0c will be released?

Not really, 4.0b was a really long Beta cycle and Logos has said that 4.0c would be shorter, but they haven't indicate how much shorter.