0 votes
397 vues

I have multiple reference errors in a draft trans, when reference is over multiple verses.
I also have several similar instances that do not get flagged.
I have been unable to determine what is different.
Any ideas?

From MAJHI Project

GOOD
\v 19 राजा हेरोदिन आफ्‍ने भाएककरि बुएक हेरोदियासलाइ आफ्‍ने बुएक बानाइकइ धर्‌ल हुदान युहन्‍नान होलाइ डाङ् गरल्‍ते र होक्‍र आने धेरइ खराब काम पुनि देखाइदिल्‍ते।
\v 20 होइ हुदान हेरोदिन युहन्‍नालाइ झ्‍यालखन्‍डनाइ थुनल्‍ते। युहन्‍नालाइ थुनिकइ होइनिन आफ्‍ने सेब्‍बे खराब कामनाइ अर्‌को एउटो खराब काम थप्‍ले।\ x - \xo 3:19-20 \xt मति ४:१२; १४:३-४; मर्‌कुस ६:१७-१८\x*
** s येसुन बप्‍तिस्मा लिल
\r (मति ३:१३-१७; मर्‌कुस १:९-११; युहन्‍ना १:३२-३४)
\p

FAILING
\v 18 “पर्‌भु परमेसोरिकर आत्‍मा मुइ उप्‍रान आछि,
\q2 किनारइभने गरिबकाइ सुसमचार सुनाइलाइ परमेसोरिन मुइलाइ छानिकइ पाठाइलाछ।
\q1 बन्‍धननाइ पर्‌लाल्‍काइ छुटकारा देइ,
\q2 कानाल्‍काइ देख्‍नार बानाइ,
\q1 अत्‍याचारनाइ पर्‌लाल्‍काइ स्‍वतन्‍त्‌र गरइ,
\q2
\v 19 अनि परमेसोरिन आफ्‍ने मान्‍छेल्‍काइ मुक्‍ति दिनार समय आइलाछि
\q2 बाजिकइ सुनाइ मुइलाइ पाठाइलाछ।” \x - \xo 4:18-19 \xt यसइया ६१:१-२\x*
\p

Ancienne publication - affichée dans sa langue d'origine
Paratext par (1,2k points)
réaffiché | 397 vues

3 Réponses

0 votes
Meilleure réponse

Look at Project, Scripture Reference Settings, and the Origin Options tab. This is where you define what happens when you have a verse range in the \xo field. More specifically, it specifies where the cross-reference must appear in the text (at the first verse of the range, the last verse of the range, etc.) My guess is that you’ve got it set to either first verse or last verse, and sometimes the cross-reference has been inserted in the text at the first verse and sometimes at the last verse. The ones that match the setting will be OK, and the ones that don’t will be flagged as an error. If you’re not printing a caller (which I assume you’re not, since you have \x - ), you can set this to “Any verse mentioned in the xo or fr field”, and then it doesn’t matter where the cross reference is inserted in the text.

Ancienne publication - affichée dans sa langue d'origine
par (304 points)

Checking the “Any” option, did remove the reference error.

The option previously selected was the forth option in image. Shouldn’t the other multi-verse reference in the original post have been failing?

Ancienne publication - affichée dans sa langue d'origine

Just curious whether there’s any value in choosing, for example, the “first verse” setting and consistently entering the cross references, so that future use of the text (typesetting or digital publication) will be smoother. (I’m not arguing for this position, merely raising the question.)

Ancienne publication - affichée dans sa langue d'origine
0 votes

The difference appears to be the \q1 and \q2 tags. Try removing the tags and see if the error disappears. If so, I’d report this as a bug.

Ancienne publication - affichée dans sa langue d'origine
par (1,8k points)

Removing all \q1 and \q2, did not make a difference.

Ancienne publication - affichée dans sa langue d'origine
0 votes

You raise a good point, and I’ve always placed a high value on consistency. Certainly if printing the caller, normal practice (at least in English books) is that it’s printed at the end of the material being referred to.

If not printing the caller, then for the purpose of this error message it doesn’t matter where the cross-reference is placed. However, for the purpose of digital publishing it does matter. For example, in a phone app you don’t have physical pages where you can print the cross-reference at the bottom, so the only way to alert the user that there’s a cross-reference for a particular verse is either to display the cross-reference inline in the verse itself, or (more likely) display the caller in the text, and the cross-reference pops up in a separate window when the user taps the caller. So even if not printing the caller in the book, you will probably display it in the mobile app, and then you’ll want it to be consistent. Thanks for raising the question.

Ancienne publication - affichée dans sa langue d'origine
par (304 points)

Questions connexes

0 votes
1 réponse 51 vues
Depuis que j'ai changé pour PT9.5, lorsque j'exécute les vérifications de base (Basic Checks), je reçois de nombreux ... beaucoup, donc je ne veux pas simplement les rejeter tous.
anon380150 242 posée sept. 5, 2025
+1 vote
1 réponse 38 vues
Bonjour, Merci aux développeurs de PT pour tout votre travail remarquable ! Je suis linguiste, facilitateur de ... simplement partager ce retour d'information. Merci beaucoup !
alex_larkin 379 posée juil. 21
0 votes
2 réponses 30 vues
Lors de l'exécution de Basic Check dans mon projet Paratext, je reçois l'avertissement suivant : Parentheses ... cet avertissement ? Merci pour votre aide. Cordialement, Prabhu
Prabhu_beelagi 241 posée déc. 29, 2025
0 votes
1 réponse 149 vues
Low priority Bonjour, Début de cette année, j'ai commencé à suivre plusieurs tâches à faire dans un projet sur ... livre entièrement vide. Un développeur peut-il confirmer ? Merci.
Fork 184 posée août 1, 2024
0 votes
3 réponses 954 vues
Quelqu'un peut-il me dire ce que je dois faire pour éliminer ces erreurs affichées par les vérifications de base (basic checks) ... -je indiquer à PT que ce n'est pas une erreur ?
skim1124 219 posée mai 4, 2021
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
They devoted themselves to the apostles’ teaching and to fellowship, to the breaking of bread and to prayer.
Acts 2:42
3,048 questions
6,007 réponses
5,672 commentaires
2,028 utilisateurs