USFM Text Error on adding a change

Question

I'm a little baffled by some PTXprint behavior. I have copied the book of PSA from a project previously typeset into a test project, I have reset the configuration in PTXprint, selected PSA 1-16, changed to single-column layout and print, and it works fine. But as soon as I add ANY rule in changes.txt, it gives me:

Even if the rule is something simple like 'bad' > 'good'. I've looked at line 88 in the Final SFM tab, both when it works and when it gives the error, and line 88 is empty (in both cases), but I've copied the lines around there (in both cases) and compared them and they are identical.

After it produces the error, it seems to go ahead and produce the PDF file, which generally seems to be OK (at a quick glance).

Anyone know what is going on, or how to avoid the error?

Thanks, Jeff

Answer 1

In case you didn't catch it in the fine print of the comments, the error goes away when you DON'T have a limited chapter range for the book (specifically seems to be Psalms). Although if you limit the chapters, get the error and click OK, the PDF seems to be produced properly anyway.

Answer 2

Never mind... It turns out that the following line was a dedication (\d) with a footnote that had a cross reference (\xt) which pointed to a book name that wasn't defined in this project (since it was just copied from another project). So this is just a reminder that you do really need to run basic checks before you do your typesetting! What threw me off is that it ran without errors before adding in a change in changes.txt - don't know why that would make a difference...

Comments

No, I’m wrong. I’ve fixed up the errors in the text, and I’m still getting the problem. Puzzling...

---

More weird things happening... The Tidy Up button giving me a Traceback gtkview.py, line 5604 in onDeleteTempFolders, AttributeError: 'str' object has no attribute 'printPath'. Version 2.5.12

---

I have had problems where I have used the changes file to fix up a file that doesn't load properly otherwise. If you use the limited chapter range, ptxprint has to read and parse the file before it is run through the changes and so I couldn't use limited chapter ranges for that file (and yes it was PSA, sigh). I don't know if removing the limited chapter range will fix this for you.

---

YES! When I print PSA chapters 1 to 150, the error goes away! And then when I put it back to a limited chapter range (1-16), I get the error again. (But it does still appear to produce the proper output.) Well, I sent the project backup to the PTXprint support email address, so maybe that could help you track it down...