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. Based on the rules set up for a job, Plint Subtitler will look for errorspotential issues and report them in three different ways.
Live error reporting (LER) is displayeda feature that checks for certain problems and provides visual feedback/warnings in tworeal differenttime ways whileas you work,work. seeOther pointserrors 1are 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 2should below.be Thefixed Reportbefore Toolchanging gathers all errors in a concise and easy to use view.status.
Configuring which errors/problems to flag is explained here.
1. Live Suberror inforeporting
The live subsubtitle information window is placed just above the target language box and displays character count, reading speed and separation live while you type. These factors are checked against the client specific settings and any breach renders an error which is showed in red. It also renders a red triangle. A yellow triangle and sub signifies a warning which is not considered a blocking error.
2. SubThe errorsErrors tab
All of the errors in a project are also gathered in the "Error" tab in the top left corner of the editor. After clicking on the tab you can cycle through all the errors using the arrow buttons. The window below shows an explanation of the error while moving to the sub in question on the timeline at the bottom.
3. Report Tool
Select Review/Report tool to access the "Report Tool" and summarise all errors and warnings in a single view. This will gather all errors and present them in a concise manner, grouped by error type.
The gathered information allows you to quickly go through each category. The number on the left next to the error name indicates how many errors the project contains. By clicking a sub you get an explanation of the error and the sub is highlighted in the timeline at the bottom. If you want to make changes you can edit the target box as usual. The live sub info will give you the information you need in order to correct any errors.
Error explanations
Maximum characters per line (LER + Report tool): This rule indicates if you have too many characters on each line. This rule will gives you an instant feedback in the error tab, and also by changing the font color for the concerned line(s) in the ”Count” value box in the text editor. This rule also affects the behavior for Auto line-break if active.
Reading speed (LER + Report tool): This rule indicates how fast a subtitle should be presented for the end viewer to read. It can have both a max (too fast) and a mini (too slow) value. The rule gives an instant feedback in the error tab, and also by changing the font color for the ”reading speed” value box in the text editor.
The mathematical formula for this rule: Characters / (Frames/FPS) = CPS
Index discontinuity (Report tool): This rule indicates if there is a discontinuation for the clips index. It also gives a warning/error if the index start value is wrong. You can solve this issue:
- inside the Report tool by an option
- or by renumbering all clips on the timeline (right click)
- or in the drop-down menu (Clip>>Renumber all clips).
Extra spaces (Report tool): This rule checks if there are unnecessary spaces. It looks for three different types of extra spaces: Leading, trailing and double. All of them can be solved inside the list of the Report tool.
Match value (Report tool): This rule compares Reference text with the translated text, looking for a correct numeric value in the subtitle clip’s text for the current time span. If there is a mismatch or missing value against the reference subtitle clip in the current time span, there will be an error/warning. It looks mainly for numbers (0-9) but it can also be configured to look at other values, such as ½, ², ³.
Empty lines (Report tool): This rule looks for empty lines. In the Report tool you will get an option to remove these.
Clip duration: This rule checks for clips with too high or too low running times. Clips below the minimum value or above the maximum value will be flagged.