Welcome! Sorry for your troubles. [:s]
Is there any work-around for this, please?
Some screen shots might be informative.
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?
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!!
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."
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.
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??
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.
