Problem with Key Terms Tool with custom Versification

Question

Our project is having trouble with the Biblical Key terms in Psalms (and eventually other books).

The Hebrew titles are considered part of the verse numbering in our area (unlike in most English Bibles). This creates a problem for versification which we fixed with a custom versification, but the Biblical key terms tool is off a verse or two. For example, if we click on Psalm 51:7 in our project, it displays the Key Terms for verse 9. It seems like the Biblical Key terms is following the English versification, rather than the versification for our project.

This basically renders the Biblical Key Terms tool useless for Psalms for us.

Any ideas what we do about this short of manually editing every key term?

Publicação antiga - exibida no idioma original

Answer 1

This problem is caused by changing the versification of the project after starting a project biblical terms list. I think I’ve come up with a procedure that seemed to fix this problem:

1. Close Paratext.
2. Move the ProjectBiblicalTerms.xml file from your project to the My Paratext 8 Projects folder.
3. Rename the file to something you can identify (I used {ProjectName} Old BiblicalTerms.xml). Note that the name must end with “BiblicalTerms.xml”.
4. Open up the file and scroll to the bottom and change the line “<Versification>Original-{ProjectName}</Versification>” to be “<Versification>English</Versification>”.
5. Start Paratext and open the Biblical Terms tool.
6. In the Biblical Terms tool, use File > Select Biblical Terms List to select the list you named in step #3.
7. In the Biblical Terms tool, use Tools > Copy all terms to the {ProjectName} project to copy all the terms over.
8. In the Biblical Terms tool, use File > Select Biblical Terms List to select the normal project biblical terms list for the project. (Closing and reopening the Biblical Terms tool will also work.)
9. The references should now be fixed.

Publicação antiga - exibida no idioma original

Answer 2

What versification is selected in “Project” > “Project Properties and Settings…”? Does Joel have 3 or 4 chapters? If it contains 4 chapters, having “Original” as versification is surley easier.
If only your Psalms were to follow the “Original” and the rest “English”, you could copy the verse mappings from the file eng.vrs, modify them, and put them in your custom.vrs file:

PSA 3:0-8 = PSA 3:1-9 would need to become PSA 3:1-9 = PSA 3:1-9

(To be clear: this applies to base versification “English”, but Hebrew titles in Psalms as verse 1)

Publicação antiga - exibida no idioma original

Answer 3

Our project is using “Original” with a custom.vrs file. I should have thought to include that information. Sorry.

I’ll look into if your suggestion will work in this case and report back.

Just to be clear, when we click on a verse in our text, PT (8 & 9) highlights the correct verse in resources texts (which have different versifications). The problem is that the Biblical Key Terms tool is off by a verse or two.

Publicação antiga - exibida no idioma original

Answer 4

I tried testing your suggestion to include SA 3:1-9 = PSA 3:1-9 in the custom.vrs file, but the Key Terms tool is still off by one verse.

Any other ideas?

Publicação antiga - exibida no idioma original

Answer 5

I saw a similar problem once, when I changed the versification after we’d already started working on biblical terms. I don’t remember exactly how I fixed it, but I know that I did a backup/restore into a temporary project and tried editing either ProjectBiblicalTerms.xlm or TermRenderings.xml. I think my editing was mostly successful, but I missed a couple words/verses which needed to be redone.

Publicação antiga - exibida no idioma original

Comments

For one of our projects I found in ProjectBiblicalTerms.xml the line <Versification>Original</Versification>

Publicação antiga - exibida no idioma original