Translation
Scriptix includes powerful translation features that allow you to convert your transcripts into multiple languages automatically. This guide covers how to translate your transcripts and best practices for multilingual content.
What is Transcript Translation?
Translation automatically converts your completed transcript from its original language into one or more target languages. This feature enables:
- Multilingual Distribution - Share content with audiences in different languages
- Accessibility - Make content available to non-native speakers
- Localization - Adapt content for different markets or regions
- Batch Translation - Translate to multiple languages simultaneously
How It Works
Scriptix uses AI-powered translation technology to:
- Analyze your source transcript
- Translate text while preserving structure
- Maintain timestamps and speaker labels
- Generate translated documents
- Deliver multiple language versions at once (packaged in a ZIP file)
Supported Translation Languages
Scriptix supports translation to 49 languages:
Complete Language List
| Language | Code | Language | Code | Language | Code |
|---|---|---|---|---|---|
| Albanian | SQ | Burmese | MY | Gujarati | GU |
| Arabic | AR | Catalan | CA | Hebrew | HE |
| Bengali | BN | Chinese | ZH | Hindi | HI |
| Bulgarian | BG | Croatian | HR | Hungarian | HU |
| Czech | CS | Latvian | LV | Sinhala | SI |
| Danish | DA | Lithuanian | LT | Slovak | SK |
| Dutch | NL | Malay | MS | Slovenian | SL |
| English | EN | Malayalam | ML | Spanish | ES |
| Estonian | ET | Maltese | MT | Swahili | SW |
| Finnish | FI | Marathi | MR | Swedish | SV |
| French | FR | Nepali | NE | Tamil | TA |
| Galician | GL | Norwegian | NB | Telugu | TE |
| German | DE | Persian | FA | Thai | TH |
| Greek | EL | Polish | PL | Turkish | TR |
| Gujarati | GU | Portuguese | PT | Ukrainian | UK |
| Hebrew | HE | Punjabi | PA | Urdu | UR |
| Hindi | HI | Romanian | RO | Vietnamese | VI |
| Hungarian | HU | Russian | RU | Welsh | CY |
| Icelandic | IS | Sinhala | SI | ||
| Indonesian | ID | Slovak | SK | ||
| Italian | IT | Slovenian | SL | ||
| Irish | GA | Spanish | ES | ||
| Japanese | JA | Swahili | SW | ||
| Kannada | KN | Swedish | SV | ||
| Khmer | KM | Tamil | TA | ||
| Korean | KO | Telugu | TE | ||
| Lao | LO | Thai | TH |
Translation Direction
You can translate:
- From any transcribed language → To any supported language
- Multiple target languages at once (e.g., English → French + German + Spanish)
- Any combination of the 49 supported languages
Accessing Translation Features
Translation is available from the transcript editor toolbar:
Translation Button Location
The translate button appears in the export toolbar:
- Located in the top area of the transcript editor
- Icon: Languages icon (🌐)
- Position: Between the Finalize/Editable toggle and Export button
- Label: "Translate" (or translated equivalent in your interface language)
Button Visibility:
- Always visible in authenticated transcript editor
- Available in shared transcript editor (token-based access)
- Also available in caption editor
Translating Your Transcript
Follow these steps to translate your transcript:
Step 1: Open Translation Modal
- Click the Translate button (Languages icon) in the toolbar
- The translation modal opens
Modal Title:
- "Translate Document [filename]"
- Shows your current session's filename
Modal Size: Medium
Step 2: Select Target Languages
Language Selector:
- Multi-select dropdown showing all 49 languages
- Alphabetically sorted by language name
- Shows language name (e.g., "French", "Spanish", "Japanese")
- Can select multiple languages at once
How to Select:
- Click the language dropdown
- Click each language you want to translate to
- Selected languages appear as tags in the dropdown
- Remove a language by clicking the × on its tag
Example Selection:
- Select: French, German, Spanish
- Result: Translation to 3 languages
Validation:
- At least one language must be selected
- Error toast if no languages selected: "Select at least one language"
Step 3: Enter Filename (Optional)
Translation Name Input Field:
- Label: "Translation name"
- Placeholder: Pre-filled with current session filename
- Optional: Leave blank to use default naming
Filename Behavior:
- If you enter a custom name: Used for output file
- If left as default: Uses session filename
- File extension automatically added (
.zip)
Step 4: Start Translation
Footer Actions:
- Cancel button: Closes modal without translating (variant: 'smoke')
- Translate button: Starts translation process (variant: 'primary')
Click "Translate" to begin:
- Validation check (at least one language selected)
- Toast notification: "Translating document"
- API request sent to translation endpoint
- Modal shows loading state during translation
Step 5: Receive Translation
Processing:
- Translation happens on the server
- Duration depends on transcript length and number of languages
- You can close the browser - file will still be generated
Delivery Method:
For Authenticated Editors:
- Result depends on document state
- If plain document mode: Direct download as ZIP file
- Otherwise: New translated document added to workspace
- Success toast: "Document translated successfully"
For Shared Editors (Token-Based):
- Always downloads as ZIP file
- Automatic browser download triggered
- Filename:
[your-filename].ziportranslated.zip
Displays as: languages: field required
Translation Quality
Understanding translation quality helps set appropriate expectations:
Accuracy Factors
Translation accuracy depends on:
-
Source Language Clarity
- Clear, grammatically correct source text → Better translation
- Errors in original transcript → Errors propagate to translation
-
Language Pair
- Common pairs (e.g., English ↔ French) → Higher quality
- Less common pairs → May have lower quality
- Related languages → Generally better results
-
Content Type
- Simple, conversational content → Better translation
- Technical jargon → May have issues
- Cultural references → May not translate well
- Idioms and slang → Often translated literally
-
Context
- Formal content → Usually translates well
- Casual speech → May lose nuance
- Humor and wordplay → Rarely translates effectively
Expected Quality Levels
| Content Type | Expected Quality |
|---|---|
| Formal presentations, news | 85-95% accurate |
| Interviews, conversations | 75-90% accurate |
| Technical content | 70-85% accurate |
| Casual speech with slang | 60-75% accurate |
| Humor, cultural references | 50-70% accurate |
Important: All translations should be reviewed by a native speaker for professional use.
Quality Improvement Tips
-
Fix Source Transcript First
- Correct all errors in the original transcript
- Ensure proper punctuation and capitalization
- Fix speaker labels and formatting
- Clean source = better translation
-
Use Clear Language
- Avoid ambiguous wording
- Use standard vocabulary where possible
- Spell out acronyms in source language
-
Review and Edit Translations
- Always have a native speaker review
- Expect to make corrections and adjustments
- Focus on meaning over literal translation
Working with Translated Transcripts
Translated Document Structure
Translated documents maintain the structure of the original:
Preserved Elements:
- Utterances - Same speaker turns
- Paragraphs - Same paragraph breaks
- Timestamps - Identical timing (if included)
- Speaker Labels - Same speaker names (not translated)
- Formatting - Same structure
Translated Elements:
- Text Content - All spoken words translated
- Punctuation - Adjusted for target language conventions
Reviewing Translated Transcripts
Post-Translation Review:
-
Extract the ZIP file and open translated documents
-
Read through each translation
-
Check for:
- Mistranslations (incorrect meaning)
- Awkward phrasing
- Missing or added words
- Technical term accuracy
- Cultural appropriateness
-
Make corrections directly in the translated document (Word, text editor)
-
Final review by native speaker if possible
Common Translation Issues
Watch for these common problems:
-
Literal Translations
- Idioms translated word-for-word (often nonsensical)
- Expressions that don't exist in target language
-
False Friends
- Words that look similar but mean different things
- Example: "actually" (EN) vs "actuellement" (FR) = "currently"
-
Gender and Formality
- Languages with formal/informal forms (tu/vous in French)
- Gender agreements in Romance languages
-
Technical Terms
- Industry-specific terminology may be incorrect
- Acronyms sometimes translated unnecessarily
-
Proper Names
- Names should generally NOT be translated
- Place names may have official translations
Translation Best Practices
Before Translation
-
Complete and Perfect the Source
- Fix all transcription errors
- Verify speaker labels
- Check punctuation and capitalization
- Review for clarity
-
Identify Translation Needs
- Which languages are required?
- Who is the target audience?
- What's the intended use?
-
Prepare Terminology
- List technical terms that need specific translations
- Provide context for ambiguous words
- Note cultural references that may not translate
During Translation
-
Select Appropriate Languages
- Choose target languages carefully
- Consider regional variants if needed
-
Use Consistent Settings
- Same filename convention across translations
- Consistent approach to document preparation
-
Translate to Multiple Languages at Once
- More efficient than separate requests
- Ensures all versions created from same source
- Single ZIP download with all languages
After Translation
-
Native Speaker Review
- ALWAYS have a native speaker review professional content
- Machine translation is good but not perfect
- Review for accuracy, tone, and cultural appropriateness
-
Compare to Source
- Verify no information was added or omitted
- Check that meaning is preserved
- Ensure timestamps still make sense (if included)
-
Create Translation Memory
- Keep notes on how specific terms were translated
- Maintain consistency across multiple documents
- Build organizational glossaries
Translation Limitations
Current Limitations
Cannot:
- Edit translations directly in Scriptix (download and edit externally in Word, etc.)
- Re-translate from one translated version to another language (always translate from original)
- Provide real-time translation progress indicator
- Customize translation engine parameters
Workarounds:
- Download translated ZIP files and edit in Word or text editor
- Always translate from the original source language
- For large documents, split into sections if needed
Language Coverage
- 49 languages supported
- Quality varies by language combination
- Some rare language pairs may have lower quality
Troubleshooting
Translation Button Not Visible
Possible Causes:
- Feature not enabled for your organization
- Insufficient permissions
- Document access restrictions
Solutions:
- Contact your organization administrator
- Verify your user role and permissions
- Check document sharing settings
"Select at Least One Language" Error
Issue: Cannot proceed with translation
Cause: No languages selected in the dropdown
Solution:
- Click the language dropdown
- Select at least one target language
- Click Translate again
Translation Failed or Error
Possible Causes:
- Source transcript too large
- Temporary server issue
- Invalid language codes
- Network connectivity problem
Solutions:
- Check error message in toast notification
- Try again after a few minutes
- Verify language selections
- Check your internet connection
- Contact support if issue persists
ZIP File Won't Download
Possible Causes:
- Browser popup blocker
- Browser download permissions
- Disk space full
Solutions:
- Allow popups for Scriptix domain
- Check browser download settings
- Free up disk space
- Try a different browser
Poor Translation Quality
Possible Causes:
- Errors in source transcript
- Complex or idiomatic language
- Technical content without context
- Uncommon language pair
Solutions:
- Review and perfect source transcript first
- Simplify language where possible
- Provide glossary or notes for technical terms
- Have professional translator review output
Frequently Asked Questions
How many languages can I translate to at once?
You can select as many as you need from the 49 supported languages. All selected languages are processed together and delivered in a single ZIP file.
Will speaker names be translated?
No, speaker names/labels are preserved in the original language and not translated.
Can I edit translations in Scriptix?
No, translations are delivered as downloadable files (ZIP containing DOCX or other formats). Edit them in external applications like Microsoft Word.
How long do translations take?
Processing time varies based on transcript length and number of target languages. The translation happens on the server, and you'll receive a download when complete.
Can I translate the same transcript multiple times?
Yes, you can retranslate as needed. Each translation is independent.
Are timestamps preserved in translations?
Yes, timestamps (if included in the original) are preserved with identical timing in translated versions.
What file format are translations delivered in?
Translations are packaged in a ZIP file containing the translated documents (typically DOCX format, but may vary).
Can I cancel a translation in progress?
No, once translation is initiated, it runs to completion on the server. However, you can close your browser and the translation will continue.
Do I need to finalize a document before translating?
No, documents can be translated at any stage (draft, editable, or finalized).
Can shared documents be translated?
Yes, if the sharing permissions allow exports (allow_magic_link_export flag), translations are available in shared editors.
Next Steps
Related features and workflows:
- Edit Text - Perfect source transcript before translation
- Export Overview - Learn about export formats
- Navigate by Timestamps - Understand timestamp preservation
Ready to translate? Open your transcript and click the Translate button in the toolbar!