Articulate Rise Localization

Required files and assets from the client:

• • Rise project files: Rise 360 course files with all lessons, blocks, and content intact
• • Linked assets: All linked media files (images, audio, video) referenced in the course
• • Fonts: Information about fonts used, though Rise uses web-safe fonts primarily
• • 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 Rise's block editing: Leverage Rise's native block editing features for efficient text updates
• • Extract block content: Identify and extract all text content from blocks requiring localization
• • Handle text expansion: Rise blocks are responsive, but text expansion may require content restructuring
• • Update graphics separately: Extract text from graphics, translate, and update source graphics or create localized versions
• • Maintain block structure: Preserve block types, interactions, and layout while updating text content
• • Test responsive design: Verify that localized content displays correctly across different screen sizes
• • Handle audio synchronization: If audio is replaced, ensure proper synchronization with block content
• • Update course settings: Modify course settings, navigation, and UI elements for target languages
• • Test course functionality: Thoroughly test all interactions, quizzes, and navigation after localization

• • Text expansion: Rise blocks are responsive but may need content restructuring for text expansion in some languages
• • Block-based structure: Rise uses a block-based approach, which simplifies localization but may limit customization
• • Font limitations: Rise primarily uses web-safe fonts; ensure target language characters are supported
• • 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 block content and interactions
• • Responsive design: Test localized content across different devices and screen sizes
• • Version compatibility: Ensure Rise 360 version compatibility and feature availability
• • Publishing requirements: Consider publishing format, LMS compatibility, and delivery method requirements
• • Cloud-based workflow: Rise is cloud-based, requiring internet access and proper account permissions

1. File Preparation: Access Rise 360 course files, collect all linked assets, analyze blocks and content (30 minutes per project)
2. Block Content Extraction: Identify and extract all text content from blocks requiring localization
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 (blocks, 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. Block Localization: Update text content in Rise blocks, adjusting for text expansion and maintaining block structure (1 hour per 30 blocks)
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. Course Settings Updates: Update course settings, navigation, and UI elements for target languages
12. Quality Assurance: Review all text, graphics, interactions, and test course functionality across devices
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