Mismatch in versification between project (original) and Biblical Terms (English)

Question

My team and I are currently revising our draft of Exodus, and while working on Exodus 8, I noticed that the versification of the project and the Biblical Terms Equivalents don’t match. It looks to me like the Biblical Terms tool/Biblical Terms Equivalents uses English versification, whereas our project uses original versification.
I tried to find a way of changing the versification for the Biblical Terms tool, but haven’t found that option anywhere. We are using Paratext in French, so if that option exists and you can tell me what it is called in the French user interface, that would be very helpful. But I could probably work it out from the English as well.
Thanks!

Answer 1

The Biblical Terms use the Original versification. The references are changed to be the versification of the project when viewing them, though.

I would guess that your versification is not quite set up correctly in Exodus 8. Do you have Original specified as the versification of the project (Project > Project settings > Project properties > General tab > Versification)? If so, then make sure that you are actually following the Original versification by comparing your project with the HEB/GRK in the Source Language Texts. If there are any differences, you will have to create a custom.vrs file for your project that contains the differences. If there aren’t any differences, then make sure that you don’t have a rogue custom.vrs file in your project and/or make sure it contains what you expect.

EDIT: Small clarification if you’re using a Project Biblical Terms list. They use the versification of the project. Any terms that are added to the Project Biblical Terms list are changed to the versification of the project when added.

Comments

Thanks for your reply!
The project versification was one of the first things I checked, and it’s set to original. But that wasn’t always the case - I remember changing it from “English” when I first ran into problems back in Genesis 31/32. So I don’t know if that could have anything to do with it.
As for creating a custom.vrs file, I should probably add that I am not a Paratext supporter, but more of a somewhat competent user. (We don’t currently have language technology staff in country, which is why I was asked to post my question here). So I wouldn’t really know how to create that file. I did run a search on my computer to see if there is a custom.vrs file anywhere in my Paratext files, but there doesn’t seem to be any.
As this problem only concerns a few verses, I may just have to put up with it for the time being if there is no easy way to resolve it.

---

If you do wish to try making a custom.vrs file to see if it will help, it is not difficult and will not hurt anything. Search the Paratext help menu for that topic and you will find quite complete instructions. If it doesn’t do what you want, simply delete it.

You will best see the impact in the Basic Checking chapter verse check where old missing verse issues that you had to deny will disappear or new issues will appear if you made a slight error in the file. And of course we would hope your Biblical Terms issue will disappear also.

Answer 2

Tip: You may want to try re-adding some of your terms to the project.

Method: When you identify a term that has weird versification, click the gold star (to the left) to remove the term from the project’s list. Then look up the same term in the list that it had come from (for instance, the “Major Biblical Terms” list) and then click the white star on that line item to add the term back into the list, changing the star back to gold. This should (or, may) fix the versification issue.

Explanation: As @anon291708 said (in his “EDIT”), the versification for each term in your project is set at the point that you add that term to your project. Now that the versification for your project is set to Original, terms that originate from Original-versification lists will come over with the identical versification at the point of adding the terms in.

NOTE: It may be good to jot down renderings before deleting terms from a project, just in case the new term does not register as being identical to the previous term.

Comments

Thanks, Phil!
I tried this with a few terms to see what would happen, and it looks like that actually takes care of the problem.