How do we resolve an 'unfinished content model 'verse" issue with a schema check in Paratext 7.5.100.82

Question

We ran a schema check over one of our projects and see that there are 50 items marked as being wrong.
Some of them are
Unfinished content model 'verse"
unexpected characters
unfinished content model "char"
bad attribute name: “closed”

How do we go about cleaning these up?

Answer 1

Some very innocuous looking markers can cause a schema error, that in turn causes another schema error, and so on.

All the books in our project start with a \id\ and an \ide marker. Then, before the \h marker, I have a number of \rem makers followed by info/metadata about the ongoing project, and also one \sts status marker, thus:

\sts Сиёҳнависи 6-ум 

(The text after the marker means “Draft 6” – which is not really a draft, but the final version.) The schema check trips up totally on this marker, and produces 50 errors in chapter 1, verse 1 of each book.

I’m writing this in case anyone else is using the \sts marker, but also because, to me, this seems to be a bug, and one that the DBL folks have a responsibility to fix. I’m using a USFM marker in a place where it’s allowed, and I have to do half an hour of detective work to work out that the schema for XML export doesn’t understand my allowed marker! Even if it took a few hours of a programmer’s time to fix it, surely it would save more time by eliminating the need for so many of us to wrestle with it.

Answer 2

Unfortunately there is no easy answer as to how to correct errors listed in the schema check. Usually it requires detective work to try and figure out what might be causing the issue. Someone who has worked with the schema checks a lot might have more experience with a particular error.

The first assumption is that all other checks run clean (particularly the character and marker checks). One of the first things I’d look for is unusual formatting in footnotes or extra text. Are character styles nested when they are inside other character styles? Are there any unusual characters?

Comments

Thank you anon848905. On this project there was an issue where the reference check was failing. We found out why it was failing and the team will work on getting it cleaned up. Once we have that fixed, we’ll re-run the schema check and see where we are.

Answer 3

Hi MSEAIT/LT

If you have not yet figured it out, send me a backup via file, backup.
If you can place it on a drop box ot google drive and give me access to
it I can take a look at it. Those msgs are very cryptic and geared
toward the programmer, not the user.

We can’t receive zip files thru email, even if the it is renamed to
something other than a zip file, whicjh is why I requested access via
dropbox or google drive.

No promises, but I will take a look at it.

D anon467281

Global Publishing Services
Scripture Typesetting trainer & Regular Expression "specialist"
Dallas, TX