BUG: Bible Printing oddities

1. Inconsistency between versions:

From the NIV or the ESV, when printing by "Use current location" the printing goes to either end of pericope or chapter. I have not compared all versions, but in the NIV the print-preview consistently ends just before next heading, ESV (and other translations I checked) consistently go to the end of the chapter.

2. Oddities at last line of printing:

At the end of the print-preview, when printing by "Use current location," for text that has visual filters enabled (not sure if this is the deciding factor), the last line of the printed section does some funny things. See graphic below for sample:

I don't see this behavior with versions for which I don't have visual filters active for the passage. Note that something similar happens, even if the last word does not have a visual filter associated with it.

Also note that the above problem goes away if I chose to print by a specified text:

Obviously, the work-around is simple. But I'm reporting it anyway, as this is not expected behavior.

EDIT: Note that the above samples are from the LEB.

Find more posts tagged with

Comments

Frank Sauer

Wonder if it is the highlighting. I couldn't replicate this in the NIV, but I do not use the highlighting feature either, but do have it turned on in Visual Markings

Bob Pritchett

"Current location" is a temporary thing which uses the boundaries by which we mark articles internally, and/or how they're aligned to Table of Contents in that book. A future update will offer a ToC type picker.

Rich DeRuiter

2. Oddities at last line of printing:

At the end of the print-preview, when printing by "Use current location," for text that has visual filters enabled (not sure if this is the deciding factor), the last line of the printed section does some funny things

Just looked at this again. My notes are the deciding factor (not the visual filters). At least, when I remove the notes the printing issue described above disappears.

Jack Caviness

https://community.logos.com/discussion/comment/148493#Comment_148493

A future update will offer a ToC type picker.

Good move! [Y]

Jacob Carpenter (Faithlife)

https://community.logos.com/discussion/comment/148518#Comment_148518

Just looked at this again. My notes are the deciding factor (not the visual filters). At least, when I remove the notes the printing issue described above disappears.

Richard--

Thanks for narrowing down the issue. Unfortunately, we're still unable to reproduce the problem here. Can you post a screen shot of the state of your Visual filters dropdown (the three rings) for the LEB before initiating the print?

Thanks.

Rich DeRuiter

https://community.logos.com/discussion/comment/151013#Comment_151013

Just looked at this again. My notes are the deciding factor (not the visual filters). At least, when I remove the notes the printing issue described above disappears.

Richard--

Thanks for narrowing down the issue. Unfortunately, we're still unable to reproduce the problem here. Can you post a screen shot of the state of your Visual filters dropdown (the three rings) for the LEB before initiating the print?

Thanks.

Here you go. I get this problem only when printing "Use current location." This
offers to print the whole chapter. The only note in this section is the one attached to v.22 (I included it in the screen shot). That note is a note attached to a Reference (not to a 'Selection'), so it shows up in all Bibles (and other resources that are indexed by Scripture reference).

If you'd like, I could send the note file via email, though I don't see why my particular not file should be the issue.

Jacob Carpenter (Faithlife)

https://community.logos.com/discussion/comment/151265#Comment_151265

We were able to reproduce the problem of the paragraph breaking in the wrong location, and it should be fixed in the next beta.

Rich DeRuiter

https://community.logos.com/discussion/comment/151451#Comment_151451

We were able to reproduce the problem of the paragraph breaking in the wrong location, and it should be fixed in the next beta.

Just checked in 4.1b2. It's fixed.

Thanks!