0 suara
361 tampilan

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?

Postingan lama - ditampilkan dalam bahasa aslinya
Paratext oleh (135 poin) | 361 tampilan

2 Jawaban

0 suara
Jawaban terbaik

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.

Postingan lama - ditampilkan dalam bahasa aslinya
oleh (1,9k poin)
0 suara

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

Postingan lama - ditampilkan dalam bahasa aslinya
oleh (135 poin)

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

Postingan lama - ditampilkan dalam bahasa aslinya

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

Postingan lama - ditampilkan dalam bahasa aslinya

Pertanyaan terkait

0 suara
3 jawaban 1,2k tampilan
Apakah ada yang bisa memberi tahu saya apa yang perlu saya lakukan untuk menghilangkan kesalahan-kesalahan yang ditampilkan ... saya bisa memberi tahu PT bahwa ini bukan kesalahan?
skim1124 219 bertanya Mei 4, 2021
0 suara
1 jawaban 297 tampilan
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 bertanya Nov 7, 2017
+1 suara
1 jawaban 279 tampilan
Saya ingin mengekspor proyek bahasa Jepang yang memiliki teks ruby ke RTF (Print Draft juga bisa jika diperlukan). ... proyek diatur ke USFM 3. Terima kasih atas bantuannya.
anon180868 195 bertanya Des 28, 2020
0 suara
4 jawaban 601 tampilan
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 bertanya Jul 13, 2018
0 suara
0 jawaban 193 tampilan
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 bertanya Apr 9, 2018
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
Give proper recognition to those widows who are really in need.
1 Timothy 5:3
3,049 pertanyaan
6,007 jawaban
5,672 komentar
2,029 pengguna