Walkthrough: a typical subtitling project

Explains common tasks and workflows with examples and screenshots.

Quick summary

Subtitling video generally involves a recurring set of steps. The chapters here walk you through a complete example workflow managed by a project manager using mainly manual tools and forms, used by both in-house resource and external freelancers. Understanding the general steps is helpful even when working on projects that rely more heavily on APIs, automation and integration. 

The basics steps are:

A typical subtitling project, as seen in the Tree view. After media is uploaded and verified, the time-coded template is created and reviewed. This is followed by translation into subsequent languages, based on the template, with a review/QC job for each translation.

project_tree_view.png

Setting up the project

Under Projects, using the advanced or simple form, a project manager creates a new project, typically specifying:

Simple project form. The main data such as title and deadline is added in the top section. 

fqgproject_with_simple_form_top.png

Specify parts information. (By updating the "Number of parts" value, you get additional lines.)

project_with_simple_form_parts.png

Select all target languages and specify which is "first".

project_languages.png

Besides this data, there are numerous other fields that can be used to provide additional information. 

Applying a joblist template

Once the project is in place, a joblist template is selected and applied to the project, creating the necessary jobs that need to be done in order to complete the project.  

Click the "Job list" icon in the project bar of the newly created project.

project_bar_joblist_icon.png

On the joblist page, click "Template" and select a joblist template. (Generic example templates are included, but you would normally have a tailor-made template ready before this step.)

joblist_selecting_joblist_template.png

After the template is applied, jobs have been added to the project structure. Depending on the settings for each rule in the joblist template, they may already be assigned to users. 

joblist_after_template.png

Assigning work or verifying automatic selections

Joblist templates can be set up to automatically assign the created jobs based on criteria. They can also be made to simply store the criteria with each job, to make assignment easier later. In some cases, you may want to override all criteria and simply select users for some or all jobs. 

The starting point in all these cases is usually the joblist. View the pre-assigned jobs, fill in the blanks, adjust where necessary, until relevant jobs have someone to do them. 

(Of course, in a perfectly set up system where all relevant information is available for all users, no visual confirmation is necessary and the assigned users can simply be notified.)

Notifying users / requesting job confirmation

Jobs, especially outsourced ones, typically require confirmation by the assigned user. Regardless of whether they have been selected automatically by the system or manually by the project manager, there are tools for notifying the selected users right from the joblist.

Under emails, select the relevant notification options. They are similar in use, but made for different scenarios.

job_confirmation_requests.png

At this point, the workflow is all set up and relevant users have been notified. However, there may still be work to do for the project manager before work can actually begin. Read more under "Handling project media".



Uploading source media

The starting point for most subtitling projects is one or more videos. Once a joblist has been created in Plint, the next step is often to make this media available to the online editor and other tools. The goal is to eliminate the need for any manual file handling by freelancers and other users. A job with Delivery method "Media upload" is a simple solution for accomplishing this. Please note that this is the most basic method and requires some manual action, usually from a project manager. Media can also be made available to the system through automated means and integration.

Read more about media logic and the technical aspects here. 

Using the "Media upload" job 

This is often the first job in a joblist, meaning it has no dependencies on other jobs and can be done as soon as the media itself is available. It is typically assigned to a project manager (but may be performed by anyone with an account, including Resource users). Select "Upload media" on the Dashboard to start. 

media_upload_dashboard.png 

Click the dropzone to browse for the file on your local computer or network (or just drop the file on it). Please note that only one file can be uploaded with this delivery method. With a correctly set up project and template, this means that the file will then be automatically linked to the correct project and part. 

media_upload_job_screen.png

Once a file has been selected, you will get some additional options before submitting the form. 

media_upload_options.png

You can follow the progress of these steps:

  1. In the project Filezone
  2. Under Tools & Data / Renders

Finally, after upload, a "Verify media" job may be waiting for you on the Dashboard. This is to ensure that the media will work with the online editor. Please note that processing the file may take some time. 

media_upload_verify.png

Other files

If there are additional files that may be of use to people working on the project, the simplest way is to upload them to the project Filezone and then edit their visibility setting. For example, dialogue lists may be of value to people working on a specific episode whereas a glossary might be useful to everyone. 

 

Creating a time-coded template

Once the workflow is in place and media is uploaded and prepared for the online editors, a time-coded template is typically created. This can be done by an external freelancer or as an in-house job. It will facilitate translation into any number of additional languages by providing properly placed clips/blocks as well as a reference text. For this reason, the template is often in English, even if the actual source language of the content is another. 

A template can be created offline in a number of editing applications and then imported into the system, but Plint subtitler has all the necessary tools to complete this job online.

For a detailed guide to Plint Subtitler, go here. 
For a video walkthrough of origination/time-coding, go here.

Keep in mind

An example view of the Plint Subtitler

ps_adding_clip.png

Script annotations can be used to help translators

ps_script_annotation.png

Once the timed template is complete, the user selects "Change status" to hand over to the next job in in line. This may be a proofing/QC job done by a project manager or freelancer, or the workflow may be set up to allow translation to begin as the very next step. 

 

Subtitling from template

Time-coding subtitles is a complex task requiring skill and special training. By populating the editor with time-coded blocks along with reference text, translators can focus on the text itself. This is called, among other things, "Subtitling from template" or "Second translation". 

For a detailed guide to Plint Subtitler, go here.
For a video introduction to subtitling from template, go here.

When the translator clicks "Go to work", the file will be created/opened automatically in the editor. The work of the translator consists of filling the text fields with translations that adhere to the rules for the job type and language. The editor, if properly set up, will warn the user when rules are broken. 

A job set to "Load template". Subtitles are loaded automatically from the parent job, but with the text copied to the read-only reference text fields. The translator enters text into the black boxes. 

ps_subtitling_from_template.png

Changes are saved automatically at regular intervals. Hitting CTRL + s will save manually. 

Using the built-in checking tools

Plint Subtitler comes with built-in tools to help ensure the subtitles are of good quality before signoff. These include:

Changing status

Once translation is complete, the user selects "Change status" to hand over to the next job in in line. Depending on job settings, this phase may include additional steps to confirm that a spell check and/or technical check have been completed. 

Once you have gone through those panes, you can click "Change status" to mark the job as Done. 

change_status_self_check.png

 

Proofing and QC work

Often, the translation step is followed by some kind of review step, sometimes called QC, as in quality check/control. This could be done by another external resource, a project manager or a client representative. There are also built-in tools allowing the translator to perform a language and technical check in the editor before signing off. In this example, another freelancer is assigned a QC job. 

Checking the translation in the editor

Click the "Go to work" button on the Dashboard to get started. The QC job uses the same editor, but additional tools may be used/activated. 

Adding comments

Whether you are requesting changes to be made or have made the change yourself, adding a comment is often very useful. Comments can be added (and replied to) for individual clips/subtitles.  

commenting_a-clip.png

Comparing versions / Track changes

If the job settings allow, you can compare the current version of the translation with previous versions. Select Review / Track changes to open this window. 

track_changes.png

Returning a job for adjustments

If changes are to be done (or confirmed) by the person who did the original translation, the QC job should be set to "Proofing-type". This means that when the QC person changes status, they will get the option to approve or not approve the translation. 

change_status_not_approved.png

Selecting "No" will set the parent job (the "Subtitling from template" job in this case) to status "Awaiting corrections". It is in effect the same as "In process", but with a different label on the Dashboard to clarify that this is an old job that has been reopened for more work. The user will also get an automatic email notification.

 

 

Deliverables

Once a subtitle/translation is completed and has gone through all review/QC steps in the workflow, it needs to go somewhere.  Here are a few possibilities.