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). The second and third columns (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 the Excel file and check the result before saving. 

Link the KNP to the project

Add KNP jobs to the project

KNP jobs are automatic jobs that add information to the work file. They must be run when the template text is in place but before the subtitler starts working in Plint Subtitler. This is typically solved by adding these jobs to a joblist template, but KNP jobs can be added manually for testing, as long as the workflow is intact.

In this example, the KNP jobs have already run, triggered by the status change when the English template was completed. The jobs need the Delivery method "KNP" and what they do (besides importing the template if needed) is to augment the JSON file with suggestions based on the reference text. 

Seeing and using the result in Plint Subtitler

We now have a work file prepopulated with the refefence text and suggestions for how certain terms are to be translated.  

When the user moves to a block with such a term, it is highlighted. In order to simply insert the suggested term, just click on it in the list under "Production KNP".