Let's assume the translators have chosen 2 context-sensitive renderings for προσκαλέω: which we might gloss as "call.to.come" and "send.someone.to.bring".
Root-based matching is working well, so entering both renderings into the key terms renderings tool gets lots of nice ticks, and the translators are happy.
As call.to.come is a slightly rare word which not everyone understands, after testing it's decided to add a glossary entry for it.
At present, (at least, in 9.3.103.16), if I instruct paratext to automatically link keyterm entries, then we end up with weird entries like:
and they \w sent.someone.to.bring|call.to.come\w* the apostles back in.
That link shouldn't have been inserted. At that point I have 2 options:
1. Hit undo and do all the linking manually.
2. I need to search-and-replace for things with a pipe/bar (|) and/or manually delete the wrong entries.
I'd love to be proven wrong!
Also, if there's an actual call.to.come later on in the section, then it gets skipped because of the false positive, resulting in readers wondering what that word means, and/or why there's no 'go hunt in the glossary' marking.
Because we're using stem-based matching, Paratext has the information it ought to need to get this right - e.g. it could restrict the matches it links to only ones that have the same stem as the glossary entry - it just doesn't seem to be able to do that at the moment.... a
Please tell me I'm wrong, and there's a control lurking somewhere?