0
399 次瀏覽

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

舊文章 - 以原文顯示
Paratext (1.2k 點) 提出
已重新顯示 | 399 次瀏覽

3 個回答

0
最佳回答

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.

舊文章 - 以原文顯示
(304 點) 提出

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?

舊文章 - 以原文顯示

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

舊文章 - 以原文顯示
0

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.

舊文章 - 以原文顯示
(1.8k 點) 提出

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

舊文章 - 以原文顯示
0

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.

舊文章 - 以原文顯示
(304 點) 提出

相關問題

0
1 個回答 51 次瀏覽
自從我改用 PT9.5 之後,執行 Basic Checks 時出現許多關於空白字元的新錯誤訊息,儘管專案中並未啟用「空白與不可見字元」功能,而且這些空白字元對於此專案來說絕對是正確的。我該如何阻止這些訊息出現?因為數量很多,我不想直接全部拒絕。
anon380150 242 提出 已提問 9月 5, 2025
+1
1 個回答 38 次瀏覽
您好, 感謝 PT 開發團隊所有出色的工作! 我是一名語言學家 翻譯協調員,同時也是五種不同語言的翻譯顧問 我們經常分批發布經文片段,因此我經常協助團隊對其翻譯草稿執行基本檢查(Basic Checks) 我需要對所有已準備好分發的書卷 ... 們正在努力開發 PT 10,而且這個功能更有可能在那個版本中實現,但無論如何,我只是想分享這些回饋 非常感謝!
alex_larkin 379 提出 已提問 7月 21
0
2 個回答 30 次瀏覽
當我在 Paratext 專案中執行 Basic Check 時,收到以下警告: 「在此專案中,\r 中的引用通常不使用括號 」 觀察: 我仔細檢查了整個專案,並確認 所有 \r 標記均一致地在引用周圍使用括號(例如:\r (John 3 ... 案設定或舊有內容有關? 是否有需要解決此警告的專案層級設定或重新整理步驟? 感謝您的協助 敬上, Prabhu
Prabhu_beelagi 241 提出 已提問 12月 29, 2025
0
1 個回答 149 次瀏覽
低優先級 您好, 今年早些時候,我開始追蹤我正在進行的專案中的幾項待辦事項 我們目前只翻譯了幾卷書,但已經從另一個專案匯入了所有書卷的 USFM 檔案 六月初,我執行「章節/節號基本檢查」(Chapter/Verse basic check)以查看 ... 的 \s1 標記都被合併為一個針對完全空白書卷的項目,輸出結果大幅減少 能否請開發人員確認? 謝謝
Fork 184 提出 已提問 8月 1, 2024
0
3 個回答 954 次瀏覽
有人能告訴我該做什麼才能消除這些由基本檢查(Basic Checks)顯示的錯誤嗎? 對於使用羅馬字母(Roman script)的專案: 無效的中間標點符號 PT9.1.104.59 告訴我這是一個錯誤:(21:1-22:1) 這是在書卷引言中,我 ... 用緬甸文書寫的) 似乎是兩個數字之間的連字符導致了無效前綴錯誤 我如何告訴 PT 這不是錯誤?
skim1124 219 提出 已提問 5月 4, 2021
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
Dear friends, since God so loved us, we also ought to love one another.
1 John 4:11
3,048 個問題
6,007 個回答
5,672 則評論
2,028 位使用者