The Paratext Markers Check is not working for me. For example, I typed \w bob\w* into the text of an otherwise Arabic script project, thinking there's no way that "bob" is in our glossary. But when I ran the markers check, it didn't say anything about that particular verse.
Some background might help, though I don't believe it's the main problem.
We can't use PT's "Bib Terms tool to Glossary linking" because PT can't handle all our glossary entries being in \c 1 of the Glossary. Quite a long time ago we found that PT was becoming completely unresponsive as it tried to display the (currently 253) glossary entries, so we split it up into chapters. I understand that the linking won't work when the glossary entries are in different chapters, and can't think of a viable way that it could be designed to work, so I'm happy to not complain about that loss of functionality.
But I don't see how or why that would affect connecting \w with \k in the glossary. The glossary is essentially a large text document, so the fact that some lines have \c 2 or \c 3 on them shouldn't affect that kind of check. But, as I said, the markers check isn't telling me that \w entries aren't in the glossary. (In fact, if PT is simplistically searching only \c 1 for some reason, I'd expect it to warn me about 100% of the entries since none of the \k entries are in \c 1.)