Dear anon308016,
I am not sure why the Biblical Terms tool is not recognizing your words, but you are correctly using your sfm’s. You should report a problem. For at least \pn and \png it seems like an error. For \tl it is possible that that is expected behavior since \tl is meant to identify transliterated words as NOT belonging to the language of the project. I myself can quite see situations where we would want \tl text as a rendering and so it should be included in the problem report also.
While there might be some hard-wiring involved somewhere, I do know that a lot of this behavior is controlled by the stylesheet. If you look at the usfm.sty stylesheet in your My Paratext 8 Projects folder, you can see that the text properties assigned for the sfms you mention are:
\tl - \TextProperties publishable nonvernacular
\pn - \TextProperties publishable vernacular
\png - \png* \TextProperties publishable vernacular
Here you can see that \tl is nonvernacular whilst \pn and \png are vernacular (as are most other markers.)
We never edit the usfm.sty file, but you could create a custom.sty file and place it in your project folder and set the TextProperties for \tl to vernacular and see if the Biblical Terms tools then does what you want at least for the \tl text. Of course, this would then make it \tl text convert-able and have other impacts so it should be considered a temporary measure. Take a look at custom styles in the Paratext Help menu for guidance.
Blessings,
Shegnada James
Language Technology and Publishing Coordinator, SIL Nigeria
Text Processing Specialist – Complex Script, GPS, SIL Intl
Skype: Shegnada.james.
[Email Removed]
+1 972 974 8146