Software feature launch · Production guide
Localize software demo subtitles against the recorded interface
Match each localized subtitle to the real UI action and its timestamp. Keep product names and button wording consistent with the captured UI language.
Input and decision
Create an action glossary from the visible build. Translate the explanation while retaining the exact on-screen label where that helps the viewer find it.
Set up the comparison
Use the longest cue first. Check line breaks, reading time and whether a subtitle covers the control the action refers to.
Make the comparison
Play the two translated cues on a phone with the selection border visible. Move a line break before changing the timing of the on-screen action.
Worked record
The downloadable worksheet includes the records below and a blank row for your own project.
| Cue | Source control | Translated line | Time range | Reading check |
|---|---|---|---|---|
| 01 | Original source | Introduce the cup | 0–3 s | Static opening |
| 03 | Select original | Create the warm setting | 7–12 s | Do not cover selected object |
| 04 | Select original again | Create the dark setting | 12–17 s | Check long translation |
Check the result
Test the longest translated cue at real size. When the picture remains in another language, say so rather than calling it a localized build.
Hand off the revision
Deliver the subtitle file alongside the exact video cut used for line-breaking and reading tests.
Review question
Which two subtitle cues are most likely to cover the selected image?
Check the warm edit at 7–12 s and the dark edit at 12–17 s. Test the longest translated lines against the selection border while the video plays.
Use the task on your own brief
Use a copy of the worksheet to keep the project’s source files, reviewed options and decisions together.