Weird interactions between KTOT and Trilingual Hebrew Lexicon

Question

The Key Terms of the OT (KTOT) is supposed to be a resource that you have to install manually for the moment. (See How Do I Install and Update the KTOT File - Paratext). For several years our French-speaking colleagues in Africa have seen this resource appear all by itself (maybe on major version Paratext installations?), but we have had to tell them to remove it (move the KTOT.p8z file out of the _Dictionaries folder), because when it is there, the Trilingual Hebrew-English Lexicon of the Old Testament (THLOT) didn’t show up (when you right-click on a Hebrew lexeme).

I was just trying to do some testing, and my THLOT was showing up, even though KTOT.p8z was in the _Dictionaries folder, but the KTOT was not showing up in the lexeme right-click. Well that KTOT was older anyway, so I downloaded the latest from the link above (KTOTSLD.p8z) and put it in the _Dictionaries folder, as stated in the instructions. Same thing - Trilingual shows up but KTOT doesn’t. Just for kicks I tried renaming KTOTSLD to KTOT (what I had before and got rid of), but then when I started up Paratext, it said there was a problem with source tools, and I lost most of my source tools! I renamed it back and source tools are back, but I still have Trilingual but not KTOT.

So what in the world is going on? Our French-only speaking colleagues are happy with just trilingual, but those who speak English as well would like both. I know my wife has submitted bug reports (most recently earlier this month), but there still seem to be issues. I don’t know why there would be interactions between these two resources, but they appear to be ongoing.

Answer 1

OK, things aren’t as bad as I thought… Apparently I didn’t actually right-click on one of the (relatively few) terms in the KTOTSLD, and that’s why it wasn’t showing up. If I right-click on a term that is in the KTOTSLD, then both it and the Trilingual show up as options.

What is still a problem is that the old KTOT file still keeps popping up from time to time. And when it does, the Trilingual Lexicon goes away, and the KTOT.p8z file has to be removed manually.

I just ran the patch for 9.2.102.20, and it did NOT install KTOT. So that’s good. But I’m pretty sure that running the main 9.2.102.1 installer DID install KTOT, because I’m running on a new computer and only ran that installer and the patches, and it was there.

Can someone confirm that we are no longer installing the KTOT file in _Dictionaries, with the 9.3 and later installers?

Answer 2

I just upgraded from 9.2.102.20 to 9.3.102.1 (which as you know is a full Paratext installation, not a patch), and the KTOT.p8z file returned again. So I deleted it again, to be able to use the trilingual lexicon.

June Mathias (Paratext tester) said that she observed this behavior, and “The Paratext team discussed this in our scrum meeting and we are looking into what to do.” Seems kind of simple from this side - don’t install the file! But maybe there is some complication that we don’t know about…

Answer 3

Yet again, when I run the Paratext installer 9.3.103.1, it installs this USELESS file called KTOT.p8z in the _Dictionaries folder. This file isn’t even used anymore in Paratext. (The more up-to-date KTOTSLD.p8z file is.) So PLEASE REMOVE IT from the installer! @anon291708 @John+Wickberg @dhigby

When it gets installed, it prevents the Trilingual Lexicon from appearing when you right-click on a Hebrew lemma. This lexicon is CRITICAL in French-speaking contexts. And EVERY TIME we install a new full version of Paratext (i.e. not just a patch), we have to go under the hood and delete this KTOT.p8z file YET AGAIN.

How hard can it be to remove a file from the installer? I have submitted yet another problem report from within Paratext. There are probably at least 4 or 5 problem reports for this in the system. Please make this happen, so we don’t have to keep telling people why the Trilingual Lexicon isn’t showing up, and going under the hood to delete the file. Or worse, trying to explain to the local translator over a bad phone call how to do it…

Thank you for making this happen!