Cross references without book name

Question

A project I’m involved with would like to create footnotes like this [suppose the footnote is in Luke]:

/f + /ft See the footnote in /xt MAT 3:1/xt*. This same topic is also mentioned in /xt 3:8/xt*./f*

Readers in our language would assume the 2nd reference is to MAT 3:8, and actually mentioning the book name sounds oddly redundant (among other reasons, book names are quite long and there is no short form). However a computer would hotlink that second reference to LUK 3:8.

It appear that USFM 3.0 solves this problem by allowing both what will be printed (“3:8”) and the true reference (“MAT 3:8”). This can be found at https://ubsicap.github.io/usfm/notes_basic/xrefs.html?#xt under the notes on “Attributes”. So in this example we would write:

\xt 3:8|MAT 3:8\xt*

However, when I create a xref in PT using that format, it results in an error which says

Invalid extra material: ~~MAT 3:8~~

Is this a place where PT just hasn’t caught up with USFM 3.0, or am I missing something?

Answer 1

Here is a solution that will work for both versions of usfm:
\f + \ft See the footnote in \+xt MAT 3:1. This same topic is also mentioned in 3:8\+xt*
Assuming in Scripture Reference settings your List of Chapters separator is semi-colon space, add a bar followed by the text This same topic is also mentioned in like this:
; |. This same topic is also mentioned in
Be sure there is one space after in.
You may not want to do this if something like this happens a lot with different texts. But this will work for a few odd footnotes.

Answer 2

Do you have USFM 3 selected for the style sheet on the Advanced tab of the Project Settings?

Comments

I temporarily changed it to that, but it didn’t affect things (I then ‘restored’ the project because some of the members may still be using PT8).

Answer 3

In my tests it worked as expected when the USFM is set to 3.0 in PT9.0.103.1. Even when I switched back to USFM 2.0 it continued to work.

Comments

I’ll reply in a PM.

---

That format is working for @anon848905, but not for me. Does anyone know if this could be caused by the fact that I’m working in a RTL language? Is the best solution for me to send a report in from within PT?

Answer 4

Returning to this a year later, I realized what I did wrong. I’ll document it here for others who might be searching with similar questions.

Short answer, the xref that follows the | symbol has to use English short codes, like MAT for Matthew.

I tried to translate my question on this forum into an English context, and as a result actually didn’t give people the information necessary to answer it. I had been typing book names in our local language expecting it to follow all the other xref rules, but it didn’t.