0
424 次浏览

I’m having trouble using \w … \w* markers when the word in the text is a different form of the word than is in the glossary.

I found in the online USFM documentation that I should be using a pipe (by the way, is there a pdf version of the USFM 3.0 documentation?).

When I type something like \w ہِرودِ|ہِرود\w* (note the small vowel point under the last letter) it solves my “Citation Form (“ہِرودِ”) is missing from the glossary: \w” errors, but both words are still showing in the text. No matter which of the views I go to (Preview, Basic, Formatted, Unformatted, or Standard) both words show.

In Preview view, which would typically remove the \w markers and replace them with a * before the word, the markers are gone but the * is not present.

Basic view is the only place where the glossary version (the second of the two words) is grayed out.

较早的帖子 - 以原始语言显示
Paratext (1.9k 分) 发布
已重新显示 | 424 次浏览

2 个回答

0
最佳答案

Which version of Paratext are you using? What stylesheet is the project using?

I tried it in version 8.0.100.63 and it seems to work fine in a test project (Standard view):
image

较早的帖子 - 以原始语言显示
[Expert]
(16.7k 分) 发布

I’m using 8.0.100.62.

In looking at stylesheets, I noticed my usfm.sty is version 2.503. Has usfm.sty version 3.0 not been incorporated into PT yet?

There was a fairly innocuous line in custom.sty pertaining to \w, but I removed it to no effect.

I’m not seeing that grayed out look in Standard view.

较早的帖子 - 以原始语言显示

No, the USFM 3.0 specification was only finalized a couple months ago so it has not been incorporated into any released version of Paratext, yet. Support for USFM 3.0 will be in 8.1 when it releases later this year.

However, having a pipe separating the parts of \w was in before USFM 3.0 so the version of the stylesheet you have should be fine. Could you tell me the name of the project with the problem (if it’s not sensitive)?

较早的帖子 - 以原始语言显示

I’ve sent an email.

较早的帖子 - 以原始语言显示
+1

In case someone else has a similar issue, it turns out it was caused by the spell checking. If the word following the pipe (’|’) was marked as incorrectly spelled (or unknown), that caused the word to not show up in its typical gray color.

较早的帖子 - 以原始语言显示
[Expert]
(16.7k 分) 发布

相关问题

0
0 个回答 210 次浏览
Paratext 只能自动排序在 圣经术语 (Biblical terms)工具中正确链接的词汇表条目 在词汇表中更改引文形式的拼写会破坏 圣经术语 工具中的链接 您需要打开 圣经术语 工具,并将引文形式重新链接到相应的圣经术语 您可以通过查 ... 将根据您项目语言设置中的排序顺序正确排序该词汇表条目 对所有已更改且不再正确排序的条目重复此过程
[Expert]
Jeff_Shrum
2.9k 发布
提问于 三月 23, 2021
0
1 个回答 449 次浏览
I'm working on basic checks for a project, and it keeps coming up with Citation form (x) is missing from glossary every ... difference. (P.S. I am using Paratext 8.0.100.84)
Rɔnelh 199 发布 提问于 十一月 16, 2019
0
1 个回答 41 次浏览
我们在脚注交叉引用中使用了 /xt,设置为使用书籍的“短名”。但在词汇表中,我想使用书籍名称的缩写,是否有不同的 USFM 代码可以实现这一点?
Lenice 180 发布 提问于 十月 7, 2025
+1
1 个回答 428 次浏览
当您通过 圣经术语 工具或 圣经术语译法 窗口输入词汇表条目时,Paratext 会将这些条目链接到相应的圣经术语,并确定如何对词汇表条目进行排序 (它使用项目设置中的排序顺序来实现这一点 )如果您在使用 圣经术语 工具之前手动创 ... 帮助中的 如何将现有词汇表条目与圣经术语关联 部分阅读有关此内容的说明 以下视频更详细地描述了此过程:
[Expert]
Jeff_Shrum
2.9k 发布
提问于 三月 23, 2021
0
1 个回答 403 次浏览
我是此项目的管理员。另一位管理员在 GLO 和其他书中进行了更改并执行了“发送/接收”(Send/Receive)。她在其他书中所做的更改已正确更新,我在执行“发送/接收”后可以看到这些更改。但她在 GLO 中所做的更改在“最近更改”和“项目历史”中对我可见,但在 GLO 书中并未更新。
anon399461 123 发布 提问于 三月 13, 2024
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,051 个问题
6,010 个回答
5,676 条评论
2,030 位用户