How can I share Biblical Terms renderings for a resource text?

Question

(john_nystrom writes)

How can I share with my teammates work I have done marking Biblical Terms renderings in resource texts. It would be especially nice if we could collaborate together on this. I don’t see a way we can share a resource text via send/receive.

Publicação antiga - exibida no idioma original

Answer 1

I have just seen this message which the computer tells me is very old but it is very relevant now for ParaTExt 8. In previous versions we would add the renderings to resource texts as normal and then just copy/paste the Biblicaltermsxxxx.xml file from the resource folder to the next computer. But I can’t even get ParaTExt 8 to allow me to add any rendering in any resource texts. This is very disappointing as marking Biblical Terms renderings in the resource texts was so invaluable, particularly for obscure verses. Is this a bug with 8.0 or a new feature?

Publicação antiga - exibida no idioma original

Comments

anon703820:

Is this a bug with 8.0 or a new feature?

This is not a bug. Resources in Paratext 8 are now completely locked down. You can not edit anything (no notes, Biblical Terms, etc.) for a resource text. This is mainly to make resources more protected because of our increased visibility since Paratext 8 will be available to anyone. Unfortunately, it has the side-effect of annoying people that are used to doing these kind of edits. Hopefully this will entice the resource owners (or someone with access to the resource projects) to do this work on their resources so it will be available to everyone.

Publicação antiga - exibida no idioma original

---

Can you give us an example of what you were using this for?

Ideally all resource texts would come with all renderings already entered. If you had a specific resource text that you would like to mark the renderings in perhaps we could negotiate a deal with the resource owner to give you an unlocked copy of the text so that you could mark the renderings and return them to the owner so that they could be distributed with the resource.

Publicação antiga - exibida no idioma original

---

Well for ParaTExt 7.x I had done a draft of the TOB88, FC97L, NSV78 and RSV52 for the SIL NT Key terms list and most of the proper names for TOB88 and NSV78 from the Major Biblical Terms list.

The idea is to make it easier for teams when they are doing their checks. Especially in cases where the meaning isn’t obvious or it isn’t explicit. So when they are having trouble finding the terms in their texts they can look across to the resource text and see the rendering highlighted or the rendering denied.

It would be wonderful if all resources would come with their renderings already done! But it would be a huge job.

anon703820

Publicação antiga - exibida no idioma original

---

Wow! What a cool idea! You should definitely make this a feature request.

Blessings,

Shegnada J.

Language Technology and Publishing Coordinator, Nigeria

Text Processing Specialist GPS Dallas

Skype: Shegnada.James.

+[Phone Removed]

Publicação antiga - exibida no idioma original

---

It would be very helpful IMO as a way of illustrating or teaching both translation principles and Paratext tools, and using Send/Receive and some carefully agreed protocols could be a collaborative effort. Essentially we would be reverse-engineering the resource texts. This is definitely something I am interested in. Using the mechanisms available for PT7.x I had been starting to work through a few English versions. I find it interesting to see how different reference versions handle polysemy and other reasons for key term rendering variation.

Publicação antiga - exibida no idioma original

---

I have been wondering the same thing. Being able to do this has been a big
part of our Biblical Terms work.

john_nystrom

Publicação antiga - exibida no idioma original

Answer 2

(anon451647 writes)

The only way to do this currently would be to request a copy of the resource as a regular editable project from the resource owner and then share this copy via send/receive.

Publicação antiga - exibida no idioma original