+1 vote
207 vues

There appear to be two obstacles to using the interlinearizer to create a Back Translation of the Glossary.

(1) The Glossary doesn’t have verse numbers. However, verse numbers can be temporarily added for breaking up the text for purposes of interlinearization, then removed.

(2) Even with verse numbers added, the interlinearizer tool doesn’t work in GLO. I’m guessing this is because there is no appropriate model text. But there’s no way of telling. There’s no error. The tool opens but won’t go past 1:0 (chapter 1, verse 0), even as I navigate through verses (in both the project text and the corresponding BT text).

Hack: After adding verse markup to the Glossary, I can copy the GLO text into some chapter of Scripture that hasn’t be translated yet. (Our glossary has 82 entries right now, so I chose Numbers 7, a nice long chapter.) The interlinearizer now works (but in NUM). I can interlinearize the glossary, copy the results from NUM to the GLO book of the BT, then remove verse numbers - and delete NUM.

But is there a non-hacky way to do this? It would be nice for the interlinearizer to do two things: (1) treat \k like a verse in GLO so that we don’t have to add verse numbers, and (2) actually work in the GLO book.

Ancienne publication - affichée dans sa langue d'origine
Paratext par (296 points) | 207 vues

2 Réponses

+1 vote
Meilleure réponse

In Paratext 7 and 8, in the extra books, chapter and verse numbers worked mostly as they did in the normal books of scripture. There were problems, but you could navigate using chapter and verse numbers, both for the interlinearizer and for the same extra book in another language, such as translating a tract/story book, etc, from one language (eg.English or Lozi) to another, with the interlinearizer producing the glosses that could then be exported to a back translation document. If you to the end of a chapter and were trying to go to the next verse, it would not go to the next chapter, but choosing the next chapter in the tool bar would go there. This worked without any model text. In Paratext 9, this “feature” (if it was a feature) seems to have been broken. It would useful is this could be restored.

Ancienne publication - affichée dans sa langue d'origine
par (136 points)
+1 vote

I was told once that there is no support for verse numbers in the glossary or extra books (like XXA). It would also be a big help for our team if we could use the interlinearizer to back translate these books without adding verse numbers.

Ancienne publication - affichée dans sa langue d'origine
par (1,3k points)

Questions connexes

0 votes
6 réponses 990 vues
We have a small glossary (currently 1 page), and we are using the interlineariser to provide back translations. To ... does accept? What's the best practice for this?
anon542642 294 posée févr. 21, 2022
0 votes
1 réponse 34 vues
We're using /xt in footnote cross-references, set to use 'short name' of book. But in the glossary I'd like to use ... name, is there a different USFM code I could use for that?.
Lenice 180 posée oct. 7, 2025
0 votes
4 réponses 519 vues
I'm trying to use a software that displays a lexicon of Paratext Interlinearizer. However, both Glossy and Glossinator ( ... wonder how I can get these programs to work properly.
anon838041 109 posée févr. 9, 2022
0 votes
3 réponses 362 vues
What is the order of the suggested glosses in the interlinearizer tool? In other words, if you click a gloss and ... frequency, though that seems like it would be most logical.
mnjames 1,9k posée sept. 11, 2018
0 votes
0 réponses 172 vues
Is there a way to extract the Find/Replace history from the Project History? I found that I could do this: ... other suggestions, I'd appreciate those as well. Thanks, james_post
[Moderator]
james_post
2,1k
posée août 6, 2020
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
How good and pleasant it is when God’s people live together in unity!
Psalm 133:1
3,044 questions
6,003 réponses
5,671 commentaires
2,026 utilisateurs