Print Draft - marker errors; Basic checks - no marker errors

Question

One user wants to use print draft but is encountering an error which says “marker errors detected”, when certain chapters of the book in question are chosen. The error message suggests to the run basic checks / markers but this returns no errors.

I have tested with several different books, and in each case, if chapter 1 to chapter 1 is chosen in print draft, then there is no error message. If any other combination of chapters is chosen (e.g. chapter 1 to chapter 2, or chapter 2 to chapter 2) then the error message is seen.

Is this a known issue? Is there actually a marker missing from chapters after chapter 1? Is print draft running a different check to basic checks / markers? Should the user be concerned about the message seen in print draft?

舊文章 - 以原文顯示

Answer 1

Yes, the “marker errors detected” message that PrintDraft gives appears to be somewhat unconnected with the markers checking tool. I think the word “marker” in the PrintDraft warning is probably a mistake, and that you’re actually failing one of the other basic checks.

In practice I ignore that PrintDraft message. If the pdf compiles successfully, I’m happy. If it doesn’t, I start running through the basic checks trying to fix the problem.

Note that sometimes the PrintDraft appears to complete, but if you check carefully you’ll find that the Scripture range is truncated somewhere in the middle. Don’t assume everything is perfect just because you ended up with a pdf.

Remember that you can hold Control while clicking the OK button in the PrintDraft menu. This will allow you to look in the PrintDraft folder and read the .log file to discover what is going wrong.

舊文章 - 以原文顯示

Answer 2

Thanks. Apparently it is a known issue. To be fixed in a version after 8.0.100.56.

舊文章 - 以原文顯示

Comments

I still get the message ‘Marker errors detected’ in version 8.0.100.71 without finding any marker errors with the PT basic checks.

舊文章 - 以原文顯示

---

Yes, it i still an issue. You should be able to safely ignore the message (if you have run the check), but I have reported the issue to the developers.

Blessings,
anon848905

舊文章 - 以原文顯示