0
398 次浏览

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 分) 发布
已重新显示 | 398 次浏览

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 发布 提问于 九月 5, 2025
Paratext
+1
1 个回答 38 次浏览
您好, 感谢 PT 开发人员所做的出色工作! 我是一名语言学家 翻译促进者和翻译顾问,负责五种不同语言的翻译工作 我们经常分阶段发布经文片段,因此我经常通过运行基本检查(Basic Checks)来协助团队处理翻译草稿 我需要对所有可分 ... 道你们正在忙于 PT 10 的开发,并且该功能更有可能在那里实现,但无论如何,我只是想分享这一反馈 非常感谢!
alex_larkin 379 发布 提问于 七月 21
0
2 个回答 30 次浏览
在我的 Paratext 项目中运行 Basic Check 时,我收到以下警告: 在本项目中,\r 中的引用通常不使用括号 观察: 我仔细检查了整个项目,并确认所有 \r 标记在引用周围一致地使用括号(例如:\r (John 3: ... 否与项目设置或遗留内容有关? 是否有需要解决此警告的项目级配置或刷新步骤? 感谢您的协助 此致, Prabhu
Prabhu_beelagi 241 发布 提问于 十二月 29, 2025
Paratext
0
1 个回答 149 次浏览
低优先级 您好, 今年早些时候,我开始跟踪我正在处理的一个项目中的若干待办事项 我们只翻译了少数几卷书,但已经从另一个项目导入了所有卷书的 USFM 文件 六月初,我运行了章节/节号基本检查(Chapter/Verse basic check)以查 ... 出大幅减少,因为所有空的 \s1 标记都被合并为一项,对应于一整卷空书 能否请开发人员确认? 谢谢
Fork 184 发布 提问于 八月 1, 2024
0
3 个回答 954 次浏览
有人能告诉我该怎么做才能消除基本检查(Basic Checks)中显示的这些错误吗? 对于一个使用罗马字母(Roman script)的项目: 无效的中部标点符号 PT9.1.104.59 告诉我这是一个错误:(21:1-22:1) 这位于书卷引言中 ... 缅甸文书写的) 似乎两个数字之间的连字符导致了无效前缀错误 我如何告诉 PT 这不是一个错误?
skim1124 219 发布 提问于 五月 4, 2021
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
Very truly I tell you, whoever accepts anyone I send accepts me; and whoever accepts me accepts the one who sent me.
John 13:20
3,048 个问题
6,007 个回答
5,672 条评论
2,028 位用户