Publishing, Barbour. 199 Promises of God. Uhrichsville, OH: Barbour, 2007. has bad Bible Reference displays.
This is kind of common in some Vyrso editions. Probably nothing will be done, but this seems to be a Vyrso issue rather than an L6 one, so you should post there instead. Some resources have been able to be recompiled.
Wait - MJ - So your bible doesn't have the book of Amen-tations? Maybe its just a part of the baptist canon. Just kidding. I'd never seen this in a vyrso book. Thats interesting.
[:D]
. I'd never seen this in a vyrso book. Thats interesting.
I've seen it quite often lately - must be a compiler bug.
I'll forward this to the Vyrso converter team. Vyrso editions are converted straight from the publisher EPUB files. The EPUB format, based on HTML, doesn't have a great way to do small caps, so publishers often hack in weird things to make it work. It's likely this is a markup configuration we haven't seen before.
. I'd never seen this in a vyrso book. Thats interesting. I've seen it quite often lately - must be a compiler bug.
Let Every Heart Prepare Him Room is another example
"The Glory of Christmas" is also another example, which I bought recently from VYRSO. It is filled with misspellings, especially in names.
. I'd never seen this in a vyrso book. Thats interesting. I've seen it quite often lately - must be a compiler bug. Do you have examples? MJ's book is an older book. I need to narrow down if this is a case where A) the bug has been fix and only needs to be recompiled or something else.
and
from
LLS:9781630585648 / 2014-08-25 / T21:12:17Z / 9781630585648.logos4
or
LLS:9781624164798 / 2013-07-27 / T04:44:54Z / 9781624164798.logos4
and then
in the newer duplicate version of this book,
LLS:9781634096294 / 2015-09-01 / T21:27:50Z / 9781634096294.logos4
Here are some examples from THE GLORY OF CHRISTMAS:
You should create a new thread for this. Good catch though. [:)]
A new thread seems an unhelpful distraction. If it's a pattern the book compiler is not parsing correctly, the Faithlife team can just reprocess any source files with those patterns. There should be no reason for endless submissions of all the bugs as people find them.
In my view this is a simple software matter for the book compiler application to reprocess impacted source files.
A new thread seems an unhelpful distraction.
There were clearly two issues presented. Furthermore, the original post is suggesting an error in the compiler, whereas the second issue is a request for fixing a resource.
Knute is good at catching errors in resources and reporting them. In the case he presents, the issue is clearly bad OCR job, and this would come from the publisher. If this were a Logos edition resource, then FL would need to correct the error. In this case, FL needs to contact the publisher.
Alabama,
Yes I see there are two points, and your "new thread" comment was directed at the 2nd point. My ops on not reading careful enough.
Regards post count: I changed my email address and it seems the forum post count is driven off the email address and not my actual saved profile. I guess my post count might have been around 1000 or something, but not sure it really matters too much. But thanks for the hint if I want to get it adjusted.
Regards Jim
Thanks alabama24 I will do just that. [:D]
