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
A project using a project-specific KBT list can be configured in Paratext to refer to another project's project-specific KBT list. For instance, the bPou project is configured to use the aArp project's project specific KBT list, as shown in this line from the bPou project's Settings.xml:
When the bPou project is extracted, a metadata file (bPou-metadata.txt) and a renderings file (wra-bPou-Project-renderings.txt) are created, but a vref file (bPou-vrefs.txt) file is not created.
Subsequently, when the bPou project is used in a corpus_pair with the key term glosses enabled, no key terms are included in the training data.
The text was updated successfully, but these errors were encountered:
A project using a project-specific KBT list can be configured in Paratext to refer to another project's project-specific KBT list. For instance, the bPou project is configured to use the aArp project's project specific KBT list, as shown in this line from the bPou project's Settings.xml:
When the bPou project is extracted, a metadata file (bPou-metadata.txt) and a renderings file (wra-bPou-Project-renderings.txt) are created, but a vref file (bPou-vrefs.txt) file is not created.
Subsequently, when the bPou project is used in a corpus_pair with the key term glosses enabled, no key terms are included in the training data.
The text was updated successfully, but these errors were encountered: