ParaTExt won't upload to DBL because of stopChars

Question

I am getting the following vague error during Create DBL Text Bundle, after the basic checks and USX have been generated:

having stopChars in the searchStr value is not supported

Is there something I can do about this?

Comments

This also happens when exporting to USX, although it creates the usx files in both cases.

---

It looks like it fails at ESG, since it processes up to that point.
Can someone with some experience with Esther Greek and its cross-reference and publisher verse number issues please have a look and advise https://drive.google.com/file/d/1V3WQc5s-j-FDbMhHsNPQkHPcsQv-Dbk_/view?usp=sharing.

This translation was able to upload to the old DBL.

Answer 1

What is the name of the project that is having this problem? I should be able to get the project from the Send/Receive server and determine what is causing the problem.
From a quick look at the Paratext code, the problem must be that a scripture reference contains a "|" or "\" character, but I wouldn't expect those characters to normally be used in a reference since they are USFM formatting characters.

Comments

We are using the bar character as per https://ubsicap.github.io/usfm/notes_basic/xrefs.html#xt since the references need to point to verses with publisher verses (see https://support.bible/14971/multiple-references-alternative-verses-reference-esther?show=14982#c14982). Does Paratext/DBL not support target reference attributes?

---

Would this sort of cross reference be a problem: \+xt EstGr 1:1\+it a\+it*\+xt*? I don't know if the nesting of formatting within the reference could be causing the error.

---

A single vertical bar between the vernacular reference and the standard reference is valid.

Valid cross reference: \xt vernacularRef|GEN 1:1\xt*

It is not valid to use multiple vertical bars in a single reference:

Invalid cross reference: \xt vernacularRef|GEN 1:1|GEN 1:7\xt*

---

Having a nested character style under \xt will get the error message "having stopChars in the searchStr value is not supported" that was first reported.
When converting the USFM to USX, we were not expecting nested character styles in the value of the \xt. The USX has added elements to make it possible for users of the USX to create clickable links. If you want to do extra formatting, you would need to have that in an \xta field after the \xt.

---

I will move the nested \+it ...\+it* outside the reference as \xta text for the remaining refs and see if that is enough.
Paratext also only adds linking where the ref with the bar is in a separate \xt, so I will see if there are others that need to be handled like that e.g.

\xt 9:1,15,21; \xt 10:3|ESG 10:13\xta \+it k\+it*

I will give feedback once I have done so.

---

I have made sure the \+it ...\it* reference letters have been moved to outside the \xt into an \xta tag
and I have made sure that any reference to an alternative ref location (using the "|") have been preceded by \xt (even if the previous references are in an \xt
but, it still fails.

Is it possible that the \+it ...\+it* letters in the \xo and \fr markers could be causing the problem?
e.g.

x - \xo 1:1\+it m-r\+it* \xt Vgl EstGr 2:19-23\x*

and

\f + \fr 8:12\+it p\+it* \fk Judeërs: \ft Vgl voetnoot by \+xt EstGr 8:3\+xt*.\f*

---

Or possibly the \+it ...\+it* verse letters inside the \vp ...\vp* ?

---

It looks like the need to style part of the \vp (publisher verse) text as italics was the main cause of the issue.
As suggested by John Wickberg, we have moved from lowercase italic characters to uppercase.
This will differentiate the italic verse letters from the footnote caller letters which will serve digital applications of the text. We can regex it to lowercase/italic for print via Publishing Assistant.