Extension to kobo-translation skill specifically for translating video subtitles and transcripts in SRT format. Adds subtitle-specific guidelines for character limits, spoken language patterns, chunked translation context management, and maintaining readability on screen. Use this skill when translating SRT subtitle files for KoboToolbox tutorials, webinars, or educational videos.
This skill extends the kobo-translation skill with specialized guidelines for translating video subtitles in SRT format. All base translation rules still apply, but with additional considerations for on-screen readability, spoken language patterns, and subtitle timing constraints.
🔴 CRITICAL: This skill is for SUBTITLE TRANSLATION ONLY
When translating SRT files:
✅ , including:
Before translating subtitles:
While maintaining base rules, adapt for subtitle constraints:
Character Limits:
Conciseness:
Readability:
CRITICAL RULE: XLSForm terms in subtitles are ENGLISH ONLY
Unlike written documentation, subtitles have character limits and timing constraints.
| Context | Rule | Example |
|---|---|---|
| Documentation | English + translation on first use | "list_name (nom de la liste)" |
| Subtitles | English only | "list_name" |
Why?
Brand terms still follow base rules:
SRT files are translated in chunks (typically 20-30 subtitles at a time) to:
Each chunk includes:
Translation approach:
When translation is too long:
Compress naturally:
❌ "You're going to need to click on the NEW button"
✅ "Click on NEW"
Use shorter synonyms:
❌ "Vous allez devoir cliquer sur le bouton NOUVEAU"
✅ "Cliquez sur NOUVEAU"
Split across subtitles if needed:
Subtitle 1: "Para crear un nuevo formulario,"
Subtitle 2: "haz clic en NUEVO"
Never sacrifice accuracy:
Adapt written conventions for speech:
| Written | Spoken/Subtitle |
|---|---|
| "First, navigate to the Form page" | "Go to the FORM page" |
| "Subsequently, you will observe" | "Next, you'll see" |
| "It is necessary to configure" | "You need to configure" |
Spanish - Informal tone matches speech:
French - Formal but conversational:
Consider subtitle duration:
Reading speed:
Maintain conversational feel:
✅ GOOD (natural):
"Let's create a new form.
Click on NEW at the top."
❌ BAD (too formal):
"We shall proceed to create a new form.
Navigate to the NEW button located at the top of the interface."
Contractions are acceptable in subtitles:
When translating chunks:
Terminology consistency:
Narrative flow:
Technical accuracy:
Pattern: Instruction → Action → Result
English subtitles:
[1] "Now we'll add a new question to our form."
[2] "Click on the plus icon here."
[3] "And you'll see the question types appear."
Spanish subtitles:
[1] "Ahora agregaremos una nueva pregunta."
[2] "Haz clic en el ícono de más aquí."
[3] "Y verás aparecer los tipos de pregunta."
French subtitles:
[1] "Nous allons ajouter une nouvelle question."
[2] "Cliquez sur l'icône plus ici."
[3] "Vous verrez apparaître les types de question."
Key observations:
Pattern: Showing → Explaining
English:
[10] "Here in the Question Library,"
[11] "you can see all the template questions"
[12] "that are available for your project."
Spanish:
[10] "Aquí en La biblioteca de preguntas,"
[11] "puedes ver todas las preguntas plantilla"
[12] "disponibles para tu proyecto."
French:
[10] "Ici dans La bibliothèque de questions,"
[11] "vous pouvez voir toutes les questions types"
[12] "disponibles pour votre projet."
Key observations:
Pattern: Technical term → Usage
English:
[25] "In the list_name column,"
[26] "enter the name of your list."
[27] "This connects your cascading select."
Spanish:
[25] "En la columna list_name,"
[26] "escribe el nombre de tu lista."
[27] "Esto conecta tu cascading select."
French:
[25] "Dans la colonne list_name,"
[26] "saisissez le nom de votre liste."
[27] "Cela connecte votre cascading select."
Key observations:
Before finalizing subtitle translation:
🚨 Brand & Terminology (inherited from base skill):
📏 Subtitle-Specific:
🔄 Context & Consistency:
🎯 Language-Specific:
⏱️ Timing (if reviewing with video):
| Aspect | Documentation | Subtitles |
|---|---|---|
| XLSForm terms | English + translation first use | English only |
| Length | Can be verbose | Must be concise |
| Style | Formal written language | Natural spoken language |
| Formatting | Full markdown, HTML | Plain text only |
| Context | Self-contained sections | Sequential narrative |
| Character limits | No limits | 35-42 chars ideal, 50 max |
| Processing | Full document or diff | Chunked with context |
❌ WRONG (57 characters, too formal):
[5] "Vous devez maintenant naviguer vers la section des formulaires"
✅ CORRECT (28 characters, natural):
[5] "Allez à la section FORMULAIRES"
❌ WRONG (added translation, too long):
[12] "Dans list_name (nom de la liste)"
✅ CORRECT (English only, fits):
[12] "Dans la colonne list_name"
❌ WRONG (missing article):
[8] "Ouvrez bibliothèque de questions"
✅ CORRECT (capital L article):
[8] "Ouvrez La bibliothèque de questions"
❌ WRONG (too literal, awkward):
[15] "Procederemos a hacer clic en el botón"
✅ CORRECT (natural spoken language):
[15] "Haremos clic en el botón"
OR EVEN BETTER:
[15] "Haz clic en el botón"
When translating a chunk:
Read previous context (last 3 subtitles)
Translate current chunk (20-30 subtitles)
Check next context (first 3 subtitles)
If a term appears across chunks:
Example across chunks:
Chunk 1:
[5] "This is the KoboToolbox Formbuilder"
[5] "C'est l'interface de création de formulaires KoboToolbox"
Chunk 3:
[45] "Back in the Formbuilder..."
[45] "De retour dans l'interface de création..."
Keep the instructor's voice consistent:
Reference documents: All base translation reference documents apply:
Additional considerations:
Working document: This skill is an extension of the base kobo-translation skill. All base rules apply unless explicitly overridden here for subtitle-specific needs.