Reusing translations within the same project (Load translations)

The functionality which enables updating a template in mid-project can also be used to import translations from other jobs on the same project. It might be described as a simple, built-in translation memory.

Use cases include (but are not limited to):

• Importing text from from a similar language or language version as the starting point of your translation
• Importing completed translations from another part/episode on the same project
  • Recurring strings ("Previously on ...")
  • Different edits of the same programme

Requirements

• This function relies entirely on finding subtitles/blocks with the same reference text
  • Making it ideal for locked-template workflows
• With the right job settings, users can select other translations on the same project and import text from them

An example

• In the project below, work is completed on the Swedish translation in Part 1. The subsequent Spot QC job is also done (screenshot 1). 
• Part 2 has a completed English template with many identical strings. 
• The job settings for the "Subtitling from template" job in Part 2 allow importing subtitles from translations where all jobs are done (screenshot 2)
• When the owner of this job goes to Job details / Load translations in Plint Subtitler (screenshot 3), they can choose from translations where all jobs are done (screenshot 4). In this case, this means Swedish translations from part 1.  
  • (You can also allow import of subtitles from translations that are still in process, for example before the final QC is done. The right choice depends on your workflow.) 

1

2

Pro tip: With the setting below, you can make any job the "completion job" by adding any tag to it. The translation in this part/language will be considered ready for import and reuse when a tagged job within that node is Done.  

3

4