0 votes
567 vues

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 par (1,9k points) | 567 vues

4 Réponses

0 votes
Meilleure réponse

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.

par [Expert]
(16,7k points)

réaffiché

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.

par (370 points)
réaffiché

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.

par (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).

par [Expert]
(16,7k points)

Questions connexes

0 votes
1 réponse 819 vues
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 posée janv. 22, 2020
0 votes
2 réponses 441 vues
When printing a draft text, it places the start of each new chapter on a different page. So instead of having the end of ... a new chapter on a new page? image612 863 31.5 KB
anon827984 130 posée févr. 11, 2023
0 votes
3 réponses 327 vues
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 posée oct. 7, 2021
0 votes
3 réponses 456 vues
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 posée août 5, 2021
0 votes
1 réponse 285 vues
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 posée sept. 13, 2019
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
Make every effort to keep the unity of the Spirit through the bond of peace.
Ephesians 4:3
3,044 questions
6,003 réponses
5,671 commentaires
2,026 utilisateurs