Storyline 360 users: What are your localization pain points?

I filled out the form but wanted to add more detail about multiple languages in one Storyline file.

• This is a HUGE copy/paste exercise (pasting slides/graphics, not translated text). We'll be supporting 10 languages in our next output and for me, combining slides/assessments from the translated course is always a long process.
• Even after doing this and having a multi language Storyline file, I then need to import my closed captions and voice over files again. My folder structure is such that I have the sounds files and SRT files in folders with the same filenames, just pointing to these for automatic substitution would be great.
• Copying and pasting assessments across files is always tricky too and involves bringing over the assessment slides/question banks and a lot of tweaking to get the correct language to show.

If I could select my translated course '.story' files and somehow combine them with my base English version, that would be perfect!

This is how you (Articulate) can best leverage AI. Look at what companies like "HeyGen" are already doing. I upload a video of myself talking in English (a "talking head" video) to their website (or, in Storyline, I'd want to be able to drop a video on a slide). 

Then I select what language I want (for example, Spanish).

That's it. That's all I have to do. HeyGen automatically:

• Creates an AI clone of my voice based on what it hears in the video I uploaded
• AI transcribes what I say in the video
• AI translates the English transcription into Spanish
• Reads the translated transcription using AI text-to-speech with my AI-cloned voice so it sounds like I am speaking the target language (Spanish, in this case)
• AI adjusts the lips in my video so that they now sync up with the Spanish-speaking AI voice clone, completing the illusion that I am speaking Spanish.

Add to this some other AI-powered processes to take the Spanish transcription and use it to create timed closed-caption files synced with the new Spanish audio.

While you're at it, have a different voice generate an audio description of whatever is happening in the video (this is for accessibility purposes).

In other words, nearly everything in the localization and accessibility workflows should be AI-powered and automatic. As soon as I put any media on a Storyline slide, closed captions, translations (if I so desire), audio descriptions of visuals, secondary audio tracks, etc. should all be generated automatically and in the background. For images, ALT tags should be auto-generated.

This would be a HUGE time saver. And I think most of the technology to do this already exists.

Thanks for sharing ! really informative 

Great to hear that you're working on improving the localization process! I'll be happy to complete the survey and share my thoughts. Thanks for taking steps to make this easier for us!

I have a Twine branching scenario. Can I some how import it to Articulate (RISE or Storyline 360) ?

Hi there!

First of all a big thank-you for bringing up this topic and all efforts to improve on the Articulate side!

My 2 cents:

The need to work with XLIFF is a big downfall and reason to sometimes choose alternatives.

Reason is that it takes exotic software or external services to read this file type.

In the Netherlands, where a lot of us work in companies or universities where English is the base language we like to be in control of the process.

Also because we use our own proof-readers who can more and more often on AI based translation the exclusive XLIFF method can be a showstopper.

It seems right now that Articulate (Rise) is pushing users towards working with translation companies. 

Are there others experiencing this? Does anybody have a good workaround tip?

In addition to agreeing with many of the pain points mentioned, here's what I would love to see: 

1. Selecting PUBLISH in Storyline
2. Being given the option to TRANSLATE CURRENT COURSE
3. Being give a LANGUAGE choice option (perhaps from a drop down menu)
4. Being able to chose ADDITIONAL FEATURES (such as: notes, closed captions, narration)
5. Clicking PUBLISH - and having the output be a completely translated course. 

I'd like to add another item. I'd love it if the photo library could include a filter for "find more pictures like this." Often the photographer will take a series of photos at the same location or using the same subjects. If the keywords are not the same for every photo they might not all come up in the search. I recently used a series of four photos using the same couple and what I am calling their insurance agent. It took a lot of effort to find them. But it made the project look more cohesive. 

I think one of my big pain points if not having the closed captions exported together with the rest of the text for translation. I often embed small videos made with Camtasia in my projects that contain audio. I use Storyline to show the captioning - it's actually easier to work with captions in Storyline than Camtasia, in my opinion - although Camtasia made some recent improvements with their captioning, that may cause me to change my mind...

Normally when producing multiple language courses, I have the "master" in English, and export the project for translation to Word. When I get the translation back, I make a copy of the original English language project and then import the translation. I will then create a new scene in the "master" with the translated slides, and from there make an interaction where the user will select their preferred language. Maybe there's an easier way, but this is how I'm working.

In addition, I love the idea of having the Storyline UI follow the selected language.

I have filled the form, hoping things gets fixed