KNP / Term bases

In order to ensure consistent terminology, Excel sheets with termbases (aka Key names and phrases) can be uploaded into Plint Core, linked to projects and used within Plint Subtitler as a live help while translating.

Adding KNP to a project includes these steps

Create or update an Excel file with terms and phrases in all relevant languages
Import this file into Plint Core
Link it to a "Production KNP"
- This could be anything from a certain client, a topic or a TV show – anything with a specific terminology.
Create a project linked to the same Production KNP
Include a step in the workflow to add KNPs to the JSON work file

The Excel file

The file needs to follow a certain format (a template is available on request). Columns 2 and 3 (source and target language) are mandatory. The rest can be used for additional information, for example when working on a shared Excel book.

Specifying language

Each target language requires a corresponding tab in the file. The most important part is to specify the language code in quotes on this tab, e.g. "sv". This code must match the target language on the project exactly, including locale if used. ("sv-SE" will for example not match "sv").

Importing the file into Plint Core

Under "Tools & data", go to "Production KNP". This is always available to Workbench users and can be added for Manager roles. To introduce a new "Production KNP", click Create. You can also edit an existing one.

Please note that uploading a new file to an existing KNP will remove all current terms and phrases before adding new ones. This is to ensure that outdated terms are not used.

Upload athe ~~local~~Excel file and check the result before saving.

Link the KNP to the project

Add KNP jobs to the project

In order for KNP jobs to work, they must be run when the template text is in place.

This is by far easiest by adding these jobs to a joblist template