Skip to main content

Plint Subtitler: error reporting

Common errors can be reported automatically in Plint Subtitler. They are defined by rules which are set centrally, for example by a project manager. A rule may be: "On this project type, the maximum number of characters per line is 38". The rules are loaded automatically for the job when you go to work so that Plint Subtitler can help you find potential issues. 

Live error reporting (LER) is a feature that checks for certain problems and provides visual feedback/warnings in real time as you work. Other errors are only checked for when you actively run a report, for example as a final step before changing status. 

When Plint Subtitler flags errors, there are two degrees of severity:
  • Warning (yellow): less severe, can be ignored in certain cases
  • Error (red): this is considered a blocking issues and should be fixed before changing status 

For example: "Empty clip" might be allowed – if the translator elects not to translate a sign or line – which makes it a good candidate for Warning. Exceeding "Maximum lines", on the other hand, is very rarely permissible and will typically be considered an Error. However, severity degrees are ultimately determined by administrators and project managers.  

Configuring which errors/problems to flag, and how to set the severity, is explained here.

Issues are reported in three different ways.  

1. Live error reporting

The live subtitle information is shown just above the target language box and displays character count, reading speed and separation information live while you type. It helps you spot the most common errors right away. Below, the Reading speed is too high and the second line has too many characters. 

2020-07-20-12_51_32-Subtitling-from-template-–-Project-Subtitling-and-QC_-webinar-5-example---NuTxT-.png

Note that fixing an error may create a new one. In this case the "Count" error is replaced by "two many lines".

2020-07-20-12_52_07-Subtitling-from-template-–-Project-Subtitling-and-QC_-webinar-5-example---NuTxT-.png

2. Report Tool

Select Review/Report tool to run the "Report Tool" and summarise all errors and warnings in a single view. This tool will look for all types of errors, including where a translation may differ from the template/reference text. The result will be presented in a concise manner, grouped by error type. 

The categorised information allows you to quickly go through each category. The number after the error name indicates how many errors of this type the file contains. By clicking a specific subtitle in this window, the subtitle will also be selected. You can then make any necessary changes, and also see more information on the "Error" tab (see below). 

2020-07-20-13_08_06-Subtitling-from-template-–-Project-Subtitling-and-QC_-webinar-5-example---NuTxT-.png

3. The Errors tab

Errors for the currently selected subtitle are also shown on the "Error" tab in the top left corner of the editor. This includes both those found by live reporting and those found when running the Report tool. After selecting this tab you can cycle through all subtitles with errors using the arrow buttons. The area below shows an explanation of the error(s). 

2020-07-20-12_51_50-Subtitling-from-template-–-Project-Subtitling-and-QC_-webinar-5-example---NuTxT-.png

Please note that fixing an error may not automatically remove the warning, until you run the Report tool again or reopen the job. The error report is a temporary log which is created when you use the tool. If you leave the job and open it later, you need to run the report again to show all errors. 

Back to top