Skip to content

Project-specific KBT's - cross-referencing another project's project-specific KBT list is not correctly supported #661

Open
@mmartin9684-sil

Description

@mmartin9684-sil

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:

  <BiblicalTermsListSetting>Project:aArp:ProjectBiblicalTerms.xml</BiblicalTermsListSetting>

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingpipeline 2: extractIssue related to extracting parallel corpora

    Type

    Projects

    Status

    🔖 Ready

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions