0 votes
361 vues

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?

Ancienne publication - affichée dans sa langue d'origine
Paratext par (135 points) | 361 vues

2 Réponses

0 votes
Meilleure réponse

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.

Ancienne publication - affichée dans sa langue d'origine
par (1,9k points)
0 votes

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

Ancienne publication - affichée dans sa langue d'origine
par (135 points)

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

Ancienne publication - affichée dans sa langue d'origine

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

Ancienne publication - affichée dans sa langue d'origine

Questions connexes

0 votes
3 réponses 1,2k vues
Quelqu'un peut-il me dire ce que je dois faire pour éliminer ces erreurs affichées par les vérifications de base (basic checks) ... -je indiquer à PT que ce n'est pas une erreur ?
skim1124 219 posée mai 4, 2021
0 votes
1 réponse 297 vues
In our project, we have, I believe, three active projects* that are all for the national language. Clearly, they ... has its own project, then see Separate project for publishing?
wdavidhj 1,4k posée nov. 7, 2017
+1 vote
1 réponse 279 vues
Je souhaite exporter un projet japonais contenant du texte ruby vers RTF (l'aperçu avant impression fera l'affaire si ... projet est configuré pour USFM 3. Merci pour votre aide.
anon180868 195 posée déc. 28, 2020
0 votes
4 réponses 601 vues
Tildes (used in USFMs as non-breaking spaces) disappear when the view is changed in Preview view, as expected. ... . Am I missing some step that would make these disappear?
Alex W. 191 posée juil. 13, 2018
0 votes
0 réponses 193 vues
While I have submitted a problem report, it does not include one of the screen shots, so I thought someone ... Roman (but trying different fonts changed nothing.) Iver+Larsen
Iver Larsen 869 posée avr. 9, 2018
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
If anyone destroys God’s temple, God will destroy that person; for God’s temple is sacred, and you together are that temple.
1 Corinthians 3:17
3,049 questions
6,007 réponses
5,672 commentaires
2,029 utilisateurs