Articulate Storyline Localization

Required files and assets from the client:

• • Storyline project files: .STORY files with all slides, interactions, and content intact
• • Linked assets: All linked media files (images, audio, video) referenced in the project
• • Fonts: All fonts used in the course, especially custom or branded fonts
• • Graphics source files: Editable source files (.PSD, .AI, .SVG) for graphics containing text or requiring localization
• • Audio scripts: Original audio scripts or transcripts for voice-over and transcription services
• • Reference materials: Style guides, glossaries, terminology databases, and previous translations
• • Published output: Published course output for reference and testing

• • Use Storyline's text editing: Leverage Storyline's native text editing features for efficient text updates
• • Extract on-screen text: Identify and extract all on-screen text (OST) instances, categorizing by complexity
• • Handle text expansion: Design slides with flexible text areas that can accommodate text expansion in target languages
• • Update graphics separately: Extract text from graphics, translate, and update source graphics or create localized versions
• • Maintain interactions: Preserve slide interactions, triggers, and animations while updating text content
• • Test text rendering: Verify that target language fonts render correctly and maintain visual quality
• • Handle audio synchronization: If audio is replaced, ensure proper synchronization with on-screen text and interactions
• • Update player settings: Modify player settings, navigation, and UI elements for target languages
• • Test course functionality: Thoroughly test all interactions, quizzes, and navigation after localization

• • Text expansion: Storyline slides may need significant adjustments for text expansion, especially in complex layouts
• • OST complexity: Simple OST (editable text layers) is fastest; difficult OST (complex backgrounds, masking) takes longer
• • Interaction preservation: Text expansion can affect button placement and interaction areas; adjust as needed
• • Font availability: Ensure target language fonts support all required characters and maintain visual consistency
• • Graphics with text: Graphics containing text require separate localization workflow; uneditable graphics may need recreation
• • Audio synchronization: If audio is replaced, ensure proper timing with on-screen text and interactions
• • Player localization: Storyline player UI elements may need localization for better user experience
• • Version compatibility: Ensure Storyline version compatibility and feature availability across systems
• • Publishing requirements: Consider publishing format, LMS compatibility, and delivery method requirements

1. File Preparation: Receive .STORY project files, collect all linked assets, analyze slides and content (1 hour per project)
2. OST Extraction: Identify and extract all on-screen text instances, categorizing by complexity (simple, average, difficult)
3. Graphic Extraction: Extract text from graphics and identify graphics requiring localization (3 minutes per image)
4. SRT Creation: If subtitling is needed, create English SRT file with accurate timing (10 minutes per runtime minute)
5. Transcription: If transcription is needed, create STT transcription of audio content (2 minutes per runtime minute)
6. Translation: Translate all text content (OST, graphics, subtitles) using CAT tools, maintaining terminology consistency
7. Graphics Localization: Update source graphics or create localized versions (1 hour per 10 editable graphics, 1 hour per 5 uneditable graphics)
8. OST Localization: Update text layers in Storyline, adjusting slides for text expansion and maintaining interactions (1 hour per 30 simple slides, 1 hour per 20 average slides, 1 hour per 10 difficult slides)
9. Audio Services: If needed, record voice-over (TTS: 4 min/min (TTS + QA), Human: 1h/6min) or create subtitles (10 min/min runtime)
10. Audio Dubbing: If audio dubbing is needed, synchronize new audio with course content (10 minutes per runtime minute)
11. Player Updates: Update player settings, navigation, and UI elements for target languages
12. Quality Assurance: Review all text, graphics, interactions, and test course functionality
13. Output Publishing: Publish course in specified format (30 minutes per project file)
14. Revision: Implement client feedback and corrections (33% of total time excluding file prep)
15. Final Delivery: Deliver published course files and updated project files if requested