0 votes
226 views

When I print Psalms I get the following Syntax Error warning:

Examine line 5386 in PSA on the 'Final SFM' tab of the View+Edit page to determine the cause of this issue related to marker: \x as found in the markers: id c. This warning was triggered due to 'Auto-Correct USFM' being enabled on the Advanced tab but is due to an orphaned marker. It means the marker does not belong in that position, or it is missing a valid parent marker.

Line 5386 in PSA doesn't appear to have an orphaned \x marker (I've included lines 5385 and 5387 for context):
5385 \q2 pukue te gonii na agutu sʼsule ba ti;
5386 \q2 eo, e thaurira na tinoni ghinia na lime made te tabu.
5387 \q1

There's nothing in Paratext at that point in the text that I can see. Where else should I look for the source of this warning?

PTXprint by (639 points) | 226 views

1 Answer

0 votes
Best answer

Once again, if you include PSA in the archive you send in (see previous issue), then I can try to decipher this error for you. Sometimes the line number reported is "off" by a few lines, so it is worth looking at the surrounding context to see if there is anything tripping it up near line 5386.

Another thing that sometimes helps discover errors in the USFM is the Schema check in Paratext which takes a deeper dive into examining the structure of your data. As a special technical check, it only shows up if you're holding SHIFT when you click "Run basic checks..." on the Project menu.

by (3.2k points)
selected by
Thanks for the tip about the Schema check. It didn't turn up anything for the Psalms. There were a number of errors elsewhere, however, some of which I was able to correct. But the bulk of them don't make sense to me as when I look at the USFM marking, everything looks fine; or at least exactly the same as countless other contexts that are the same but don't get flagged...
The error looks very familiar, and if it's the same cause as back then, it was an error in the USFM parser code, but I thought we'd fixed it a few months ago. Are you using a recent PTXprint?  
If you are, or updating doesn't fix it,  please send an archive demonstrating the error.
Hi DG, Mark discovered that this was caused by a x-reference attached to a chapter rather than a verse. i think he has updated the code to handle this?
Ok, well, there are different parts of PTXprint.... I hope that Mark or Martin parser have managed to fix that bug. I work far more on the bit of the code that actually does the low level usfm to PDF conversion, which has been able to cope with notes on chapter numbers years iirc.

Related questions

0 votes
1 answer 13 views
I am using PTXprint 3.0.11 but haven't used it for a while so there are new features. I want to print select verses using the configuration I used previously. thanks!
MnKN 134 asked Feb 21
0 votes
1 answer 12 views
I'm running Ubuntu 25.04, and I installed ptxprint like this: sudo apt install python3-ptxprint I experience ... this version of Python does not have the _posix_flavour attribute.
bit 495 asked Oct 8, 2025
0 votes
1 answer 18 views
Mailto: <*Emails are not allowed*> PTXprint [2.7.17] - Error! Failed to create: MSB_BookofMark_XXC_ptxp.pdf ! File ... various settings on the Advanced tab. PTXprint Version 2.7.17
MnKN 134 asked Sep 13, 2025
0 votes
4 answers 111 views
I'm trying to print a trial run of a single book (Gospel of John) with the Glossary entries contained in that ... various settings on the Advanced tab. PTXprint Version 2.4.21
aaron_wade 124 asked Jan 15, 2025
0 votes
3 answers 69 views
We have just installed 2.5.12 and get an error when changing the language. My team member can't change ... module> AttributeError: 'GtkViewModel' object has no attribute 'configId'
anon703820 215 asked Sep 13, 2024
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
May the God who gives endurance and encouragement give you the same attitude of mind toward each other that Christ Jesus had.
Romans 15:5
3,037 questions
5,994 answers
5,661 comments
2,022 users