尊敬的 Paratext 开发团队:
我想报告一个与 Run Basic Checks 相关的问题,具体错误如下:
“引文的字母大小写与经文不一致。”
我们在多个项目(至少五个)中遇到了这个问题,这给翻译人员造成了困惑。
示例:
经文:
\v 19 Namun, karena tidak dapat menerobos kerumunan orang banyak, mereka naik ke atap rumah.
脚注:
\fr 5:19 \fq Atap rumah \ft di Israel datar, terbuat dari campuran tanah liat dan jerami...
Paratext 标记了此问题,并显示以下消息:
LUK 5:19 Capitalization of the quoted text does not match verse text: ||Atap rumah||
在这种情况下,脚注中的引语 “Atap rumah” 以大写开头,而在经文中它以小写形式出现(atap rumah)。
然而,在许多语言(包括印尼语)中,即使经文中的原始短语是小写的,脚注中的引语以大写开头也是自然且可接受的。
请求:
此前,Paratext 允许这种行为(即,即使经文是小写的,当 \fq 以大写字母开头时也不会标记错误)。我们希望恢复此行为,或提供一个选项来控制此规则。
此问题目前影响了多个项目,并在检查过程中让翻译人员感到困惑。
请问是否有办法调整此行为,或者考虑更新该规则?
非常感谢你们的支持。
此致
Prabhu
Dear Paratext Development Team,
I would like to report an issue related to Run Basic Checks, specifically the error:
“Capitalization of the quoted text does not match verse text.”
We are encountering this issue in multiple projects (at least five), and it is causing confusion among translators.
Example:
Verse text:
\v 19 Namun, karena tidak dapat menerobos kerumunan orang banyak, mereka naik ke atap rumah.
Footnote:
\fr 5:19 \fq Atap rumah \ft di Israel datar, terbuat dari campuran tanah liat dan jerami...
Paratext flags this with the message:
LUK 5:19 Capitalization of the quoted text does not match verse text: ||Atap rumah||
In this case, the quoted phrase “Atap rumah” begins with a capital letter in the footnote, while in the verse text it appears in lowercase (atap rumah).
However, in many languages (including Indonesian), it is natural and acceptable for quoted text in footnotes to begin with a capital letter, even if the original phrase in the verse is lowercase.
Request:
Previously, Paratext allowed this behavior (i.e., it did not flag an error when \fq starts with a capital letter even if the verse text is lowercase). We would like to request restoring this behavior or providing an option to control this rule.
This issue is currently affecting multiple projects and is confusing for translators during checking.
Could you please advise if there is a way to adjust this behavior, or consider updating the rule?
Thank you very much for your support.
Best regards,
Prabhu
机器翻译自 English