You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a plug in that needs to create its own project level Biblical Terms list. It will not be acceptable to modify the project terms list. It needs to be an entirely separate list. Paratext is able to offer a user any BT list it finds in the project folder that has the correct file naming convention - and include that list in send/receive. We need to generate such a list from our plug in.
Most of the terms in this list will come from major biblical terms, but custom verse pointers need to be added to each term.
Also, some terms will be entirely new, with our own invented lemmas and a completely new set of verse pointers.
I see some obstacles in the current plugin api, but as I'm just beginning to use it, I'm not quite sure.
I don't see any provisions at all for adding an entirely new terms list.
I don't see any way of adding an entirely new term - one that doesn't appear on one of the two host lists.
I'm not sure if I see a way to add an entirely arbitrary verse reference to an existing term. We need to point to an XX book created with our own chapter verse arrangement.
Thanks in advance for any suggestions. If there is another, more appropriate forum for these kinds of fairly general questions, please let me know.
Thanks,
Steve
The text was updated successfully, but these errors were encountered:
Unfortunately, what you are wanting to do is currently not possible through the plugin API. I'd suggest you create a new feature request through Paratext (Help > Give feedback) detailing exactly what you need and why so we can look into getting it added.
Thanks, Tim. I will do that. This project is being done under the auspices
of SIL's Global Publishing Services. Hopefully that will help its
visibility.
In the meantime, it is straightforward to generate such a list myself. We
already have a working prototype written in VBA currently in use by a
number of teams. Is there a policy about what a plug is allowed to do
outside the API? I'm confident that GPS wants to "do the right thing" and
be a team player in this.
Thanks,
Steve
On Mon, Nov 28, 2022 at 11:18 PM Tim Steenwyk ***@***.***> wrote:
Unfortunately, what you are wanting to do is currently not possible
through the plugin API. I'd suggest you create a new feature request
through Paratext (*Help > Give feedback*) detailing exactly what you need
and why and we can look into adding it.
—
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQ4HZN2RTWWJXOL5WSS7CLLWKUOTXANCNFSM6AAAAAASLMVQMU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
I'm working on a plug in that needs to create its own project level Biblical Terms list. It will not be acceptable to modify the project terms list. It needs to be an entirely separate list. Paratext is able to offer a user any BT list it finds in the project folder that has the correct file naming convention - and include that list in send/receive. We need to generate such a list from our plug in.
Most of the terms in this list will come from major biblical terms, but custom verse pointers need to be added to each term.
Also, some terms will be entirely new, with our own invented lemmas and a completely new set of verse pointers.
I see some obstacles in the current plugin api, but as I'm just beginning to use it, I'm not quite sure.
I don't see any provisions at all for adding an entirely new terms list.
I don't see any way of adding an entirely new term - one that doesn't appear on one of the two host lists.
I'm not sure if I see a way to add an entirely arbitrary verse reference to an existing term. We need to point to an XX book created with our own chapter verse arrangement.
Thanks in advance for any suggestions. If there is another, more appropriate forum for these kinds of fairly general questions, please let me know.
Thanks,
Steve
The text was updated successfully, but these errors were encountered: