Versification for Key Terms

Question

I got a question from a colleague and I couldn’t find any solution.

For our project the Versification is “English” and by default there is no problem with BT tool references when we add renderings for the already existing Key Terms in our current KT list. The problem only occurs when we want to add new Hebrew Keyterm manually to our KT list (which is not part of Major Keyterms that is the base for our project’s Keyterms list). When doing this, the verse references (i.e. all the verses in the project’s text where the tool tries to find rendering) are according to Hebrew Bible versification and thus differ in some Psalms, Deuteronomy etc.

The verse references are to be checked and decided in BT tool when one adds new keyterm to the project’s Keyterms list (in HEBREW resource text: right click the Hebrew word, choose lemma and from the menu “Add to project Biblical Terms for”, choose your project name) and the first thing that openn is the gloss and references window (see attachment) where you can modify the gloss and check the references for the new Key term - so here one can change the verse references which should follow your project’s versification but by default are according to Hebrew Bible. So for new added Keyterms one has to change these manually - at least as far as I know, unless there is a way to do this automatically somehow.

Is there a way to get these verse references correct when adding a Keyterm manually?

Ancienne publication - affichée dans sa langue d'origine

Answer 1

Hi Jonathan+Robie,

It’s a project in a neighboring country and they use English versification.
You can see an example of it in the picture below. It’s not an actual project file, but just my example.
When I add ‘my foe’ to KT, its reference is taken from Hebrew OT versification.
Its reference is PSA 3:2, but in English and project file ‘my foe’ is on 3:1.
So when I put ‘my foe’ in 3:1 it’s not found on KT as you can see the picture below.

0011363×901 183 KB

But when I add ‘my foe’ in 3:2, KT shows it’s found.

0021383×883 183 KB

Because of this, the team has to change reference whenever they add a KT.
Is there a way to make it done automatically?

Ancienne publication - affichée dans sa langue d'origine

Answer 2

Hi anon483457,

Does your project use Septuagint versification for the Old Testament?

Jonathan+Robie

Ancienne publication - affichée dans sa langue d'origine

Answer 3

It looks like this was broken in 9.0 (it should work in 8.0). Can you send in a problem report (Help > Give feedback) about this problem?

Ancienne publication - affichée dans sa langue d'origine

Comments

Yes, In the past Paratext was good at moving between known versifications. In Indonesia and French West Africa both use variants of the “original” versification. Projects in those areas used a customized version of the original versification. Even with this, Paratext shows the correct verses in Biblical terms tool, and parallel passages tool. What versification is your project using? When you look at the Project properties do you see something like this?

Ancienne publication - affichée dans sa langue d'origine

Answer 4

Thanks FR.
Yes, I sent a problem report.
It’s good to hear PT8 worked correctly at least.

Ancienne publication - affichée dans sa langue d'origine

Answer 5

The versification in the project is English.

Ancienne publication - affichée dans sa langue d'origine