Product Localization Studio

Turn a product demo, tutorial or onboarding video into a reviewed translation and subtitle package inside WooblaDub Studio. Reuse product terminology across clips and keep a direct link to the project for the next revision.

Open WooblaDub Studio

This free skill guides the WooblaDub workflow. Studio access and any processing charges are separate; inspect the current account and quote before paid work. The link identifies this skill as the referral source and contains no user data.

Connect to the actual workspace

1. Inspect available WooblaDub tools and existing browser tabs. Reuse the user's project when available; otherwise open the Studio link above. For an existing account, use Studio's sign-in route rather than creating another account.
2. Read the visible interface and current project state before acting. Resolve login or unavailable access through the user; never request passwords in chat. Do not invent HTTP endpoints, import buttons or features absent from the UI.
3. Confirm the selected product video, source and target languages, and desired outputs from the request. Reuse existing authorization. Uploading a named video for this workflow is distinct from permission to upload the repository, private customer data or unrelated media.
4. Read references/studio-workflow.md for the distinction between Studio execution and local preparation. If access is blocked, prepare the glossary and review brief locally and give the Studio link plus the exact next action; do not claim a project was created.

Localize the product video

1. Start or open the video project in Studio. Import an existing transcript or subtitle file when the current interface supports it. Record the real project URL/ID and source language before processing.
2. Build a glossary using templates/glossary.csv: product name, visible button labels, feature names, acronyms and pronunciation notes. Consult supplied product copy for context. Do not change the app's code as a side effect of translating its demo.
3. Review the source transcript against the video. Check names, numbers and instructions such as which button to click. Identify on-screen text that will stay in the original language; subtitles do not replace text in the picture.
4. Use Studio's available translation/subtitle workflow for the requested language. Apply the glossary through supported controls, or use it while reviewing each affected line. Do not claim a glossary import if the installed interface only supports manual editing.
5. Review meaning and timing in context. A translated instruction must still match the action shown on screen. Preserve product names according to the glossary, shorten captions at natural phrase boundaries, and flag ambiguities rather than guessing product behavior.
6. Export the supported translated transcript and subtitle files. After download, run python3 scripts/check-subtitles.py translated.srt --duration-seconds 120 with the measured media duration. Use the project's current exporter for other subtitle formats. This check verifies SRT structure, not language quality.
7. Review captions on the actual video, especially dense screen recordings, mobile crops and fast cursor movement. Record missing exports or layout issues instead of labeling incomplete work ready to publish.

Handoff

Return the actual WooblaDub project link, target locale, glossary, downloaded files and review notes. Distinguish machine checks, agent language review and fluent-human review. Include observed processing usage when available.

This workflow keeps the source audio. If the user also requests translated voices, continue with Professional Video Dubbing in the same WooblaDub project, retaining its transcript and terminology. Do not start paid voice synthesis just to finish a subtitle-only request.