File/version logic

A key concept with the online editing workflows is to minimise the need for file management. You can import a file into Plint Subtitler, for instance, but in an ideal workflow that's not necessary. 

The file, and its Milestones

When an online editing job is opened, the system will always look for an existing file linked to the same node and project. If one is found, work can simply continue. Every time a job changes status, a copy of the current state will be saved along with some information: job owner, time and date and – if added – a comment. This state is called a Milestone and can be used in various ways (such as comparing versions). However, it is the main file that is moved along to the next job in line. This is the current version, the one that will always be opened when the editor is opened, and the one that will be exported, from the joblist, from the Download subtitles page and with the automatic file export tools. 

Creating a new file

If no file is found, a new one will be created in one of two ways:

A blank placeholder file

This will contain a single block/clip and serves as starting point for the translator The translator may simply begin creating new translations, or the contents may be replaced by importing a subtitle file using the File menu.  A file based on a template

If a job is set to "Load template" and there is no previous file, the system will look for a file connected to the parent job. All clips from this file, including in and out times, will be automatically loaded into the editor. The text, however, will be copied into the reference text fields.

This allows a translator to start adding translations into timed blocks, with constant access to the source text as a reference.