Personal Book Builder: Non-Recognizable Bible References Tags issue

Grover B. Proctor, Jr.

I have discovered a feature of the "Non-Recognizable Bible References Tags" which is causing a bit of concern. Maybe I'm just not using them correctly.

It seems that if the passage I am enclosing inside the double square brackets contains a RETURN or ENTER, the entire tag is ignored when the book is built. 

I suppose I could tag every single line of, say, a Psalm -- but if it gets lengthy, that's quite a bit of work.

I've looked in all the online FAQs, helps, guides -- plus all of Morris Proctor's Personal Books videos -- and I find nothing about this issue.

Is there any work-around for this, please? Many thanks!

JT (alabama24)

Welcome! Sorry for your troubles. [:s]

Grover Proctor said:

Is there any work-around for this, please?

Some screen shots might be informative. 

Grover B. Proctor, Jr.

Thanks for the suggestion for screenshots. Never even crossed my mind. Here is a combined shot of the .docx file as tagged (top) and the built book (bottom). I think this illustrates the problem. Also note... when the tag WORKED (middle example), the word Lord lost its small-cap formatting -- but it was kept in the other two. Strange, isn't it?

JT (alabama24)

https://community.logos.com/discussion/comment/920511#Comment_920511

What happens if you use shift-return instead?

Grover B. Proctor, Jr.

https://community.logos.com/discussion/comment/920714#Comment_920714

alabama24 said:

What happens if you use shift-return instead?

I had not tried that -- but it WORKED PERFECTLY! Thanks so much! Makes me wonder what other little nuggets there are in the Logos Personal Book Builder that I don't know about!    Have you any thoughts about why the tagging (as shown in the screen shots above) eliminates the small caps formatting? Any suggestions on how to maintain that formatting?  Many thanks!!

JT (alabama24)

https://community.logos.com/discussion/comment/920876#Comment_920876

Grover Proctor said:

I had not tried that -- but it WORKED PERFECTLY! Thanks so much!

Glad to help. I assume that a "hard return" disassociates the beginning syntax from the end. The soft return lets the compiler know that it is all "one unit." 

Grover Proctor said:

Have you any thoughts about why the tagging (as shown in the screen shots above) eliminates the small caps formatting?

No, except that the font in Logos might not have small caps OR the compiler isn't programmed to look for that. A FL employee would likely have to comment. 

Grover B. Proctor, Jr.

https://community.logos.com/discussion/comment/920714#Comment_920714

alabama24 said:

What happens if you use shift-return instead?

Sorry, but I spoke too soon. Actually, using the shift-return DOES enable the tagging. However, it does so apparently by ignoring the shift-return altogether. The result is a paragraph, not individual lines. See this in the 4th example in these screenshots. Can anyone come up with any alternatives, please??

JT (alabama24)

https://community.logos.com/discussion/comment/920965#Comment_920965

Grover Proctor said:

Can anyone come up with any alternatives, please??

Since the soft return doesn't work, my guess is that FL hasn't created the ability to do what you are trying to do. The only other option I can think of is to create the syntax for each and every line... and I am not convinced that will work.