0 votes
517 views

We would like to use the cross reference link-href attribute to create references like this:
\xt arbitrary text|MAT 1:2-3:7\xt*

Doing this causes References check errors, and so I have a few questions.

Is this even possible? If so, should I use a different hyphen or is there some other way of dealing with it.

Do apps like Scripture App Builder (and maybe YouVersion or other DBL products) know how to handle that? Would they create a popup with the correct span of verses across multiple chapters?

Paratext by (1.9k points) | 517 views

4 Answers

0 votes
Best answer

From the USFM specification, it looks like that should be a valid link-href attribute (it matches the regular expression). I think it’s a bug that Paratext is calling it an error.
Please use Help > Give feedback to send the issue to us so we can take a closer look.

by [Expert]
(16.6k points)

reshown

Thank you. I’ve submitted it.

0 votes

It works for us where we have specified a long hyphen (m-dash) for marking chapter spans, whereas we specified normal hyphens for verse spans. We also set up autocorrect to change - - into an m-dash, so these get entered easily and correctly.

by (370 points)
reshown

Are you saying you’re using m-dashes in the link-href/attribute position? I know you can define that for parsing regular references, but I thought the reference that came after the | symbol had to be written using English-style references which couldn’t be changed in any way.

You are correct. A m-dash would not be accepted there since it must match the Regex:
[A-Z1-4]{3}(-[A-Z1-4]{3})? ?[a-z0-9\-:]*

0 votes

The formatting for all references needs to follow the how they are setup under Project/Setting/Scripture Reference Settings. You can then determine what characters or spacing that you would want to use in the reference.

by (142 points)
0 votes

@anon554738, You are correct for the human-readable reference part, but for the link-href part specified as an attribute, it must conform to the regular expression I posted (see the Attributes section of the \xt marker specification).

by [Expert]
(16.6k points)

Related questions

0 votes
1 answer 763 views
I'm a bit confused why USFM defines separate footnote and cross reference containers. Is it simply so that they can be ... is there a better forum to ask this sort of question?
mnjames 1.9k asked Jan 22, 2020
0 votes
3 answers 300 views
I'm finishing a consultant check for a book where the consultant check started several years ago so I want to be able to look ... it up to that date again. Is there a better way?
nomadic consultant 169 asked Oct 7, 2021
0 votes
3 answers 417 views
We are publishing a Genesis portions at this stage, but it's about 80% of Genesis, so it doesn't make sense to use a module ... , do we do the same, but simply omit \v's? Thanks.
viverechristus 296 asked Aug 5, 2021
0 votes
1 answer 275 views
I'm using Paratext 9 and the new SIL Project Plan. We have Luke 1-18 consultant checked but I can't check them off ... this a glitch in the plan or could I be missing something?
anon113466 142 asked Sep 13, 2019
0 votes
3 answers 259 views
I use a projector in workshop checking, to show the text on the wall for the whole team to see. I have to zoom into ... something wrong, or if I need to fix a setting or something.
Rɔnelh 199 asked Mar 16, 2019
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
For we were all baptized by one Spirit so as to form one body—whether Jews or Gentiles, slave or free—and we were all given the one Spirit to drink.
1 Corinthians 12:13
3,037 questions
5,994 answers
5,661 comments
2,022 users