导致这种行为的一个非常古老的原因是，如果文件顶部的 \id 行被编辑且不再匹配。这一行标识文件，如果它被更改，Paratext 圣经术语工具就无法找到该卷书中的经文。
请执行查找 \id 的操作，勾选“显示文本”（show text）并选择所有卷书。每一卷书中的该行应该看起来像这样：
\id MAT - 项目名称
MAT 必须是 Paratext 用于标识卷书的三个字母卷书代码。当您选择要编辑的卷书时，会在顶部菜单栏看到它。团队有时会将其翻译成自己的语言，例如放入 Matiyu 之类的词。这是
错误的。
项目名称必须与您在“项目属性和设置”（project properties and settings）菜单中看到的长项目名称匹配。团队也经常更改此设置。如果他们希望更改此设置（合理的更改可能是从“语言名称 NT”到“语言名称 圣经”），他们应该先在项目属性中更改
它。
然后执行查找，确保每个 \id 行都完全匹配其他行，仅在使用正确的卷书代码方面有所不同，并且项目名称与项目属性中的项目名称匹配。
之后，圣经术语工具应该按预期工作。
祝福 Shegnada
A very old reason for that behaviour is if the \id lines at the very top of the file get edited and no longer match. This line identifies the file and if it is changed them paratext biblical terms tool can’t find the verses in that book.
Do a find on \id with show text ticked and all books selected. The line should look like this in every book
\id MAT - Project name
The MAT must be the three letter book code that Paratext uses to identify the book. You see it at the top menu line when you select which book you want to edit. Teams sometimes translate that into their own language, putting something like Matiyu instead. This
is wrong.
The project name must match the long project name that you see in the project properties and settings menu. Teams often change this too. If they wish to change this (a legitimate change may be from Language Name NT to Language Name Bible), they should change
it in project properties first.
Then do your find and make sure that every \id line exactly matches the others, differing only in using the proper book code and with the project name matching the project properties project name.
After that, the biblical terms tool should work as expected.
Blessings Shegnada
机器翻译自 English
