[ISSUE] Korean translation cause Storyline to crash

Jul 27, 2016

Hello everybody,

I'm on a Storyline module at my job, which needs to be translate over multiples languages, including Chinese, Japanese and Korean. Those translations were given to me in .doc files, that I put into Storyline.
The Chinese one was perfectly incorporated into the soft, the Japanese one causes the soft to be very slow but was OK. But the Korean translation just don't let me previsualise anything, causing an neverending loading screen, and crashes when I'm trying to publish it. 
I've asked to the translators we're working with to check their files, but they confirmed me that it was clean. 
I'm kind of stuck right now. (I would gladly give you the project files, but I'm unfortunately under NDA.) 

Any thanks will be greatly appreciated ! 
Have a good one

19 Replies
Ashley Terwilliger-Pollard

Hi Julian,

We've seen an issue where the publish crashes when using Korean in the player, but I haven't seen it just when importing in the text. Are you overwriting the same file each time? Did you confirm that all these files are saved locally and adhering to the guidelines here for project files? 

Our team can sign an NDA with you if you're able to share that way, and you could upload it here. 

Julian Bouleux

Hi Ashley, 

Each time I'm importing the translation, I do it on a freshly duplicate file of the original one. My files are saved locally, and seems to be clean in their path names. 

Thank you for aiming me towards this assistance website, I got the permission to share my project files over there, as long as it is confidential. 

Ashley Terwilliger-Pollard

Hi Metiu,

Thanks for reaching out here and sorry we didn't get back to update this forum discussion. We've seen the publish crash when the player is using Korean characters or the slide titles are using Korean characters - but you just have them on the slides themselves and are still running into problems? Have you reached out to our Support engineers so that we could take a look at your individual set up? 

Ashley Terwilliger-Pollard

Hi James,

Do you have the Korean characters in the slide titles as well or using the Korean player language? That's an issue still with our QA team, so nothing new yet. We’re still working on this bug, and we’ll definitely let you know when we know more.

If you're experiencing something else with Korean characters, could you share a bit more information including a sample file with us? You can send it along to our Support Engineers here. 

Shawn Stiles

I'm experiencing the same problem with the Korean language options but only in the Player. If I leave the player setting as English and the screen content is in Korean the file publishes just fine.  If I include the title in the player frame in Korean the file will no longer work properly.   Is there a solution for this yet? Attached is the result of adding just the title in Korean.

Alyssa Gomez

Hi Sara, we've still got this issue on our radar for Storyline 2. We’ll continue to keep an eye on it to evaluate how many customers are impacted and what impact it has on courses. The number of customers and depth of impact are two of the elements that help us prioritize bugs and fixes.  

Here's some more detail about how we tackle bugs.  I'm really sorry that I can't say if this issue will be fixed, but you're in the right place to stay updated on this bug's progress!

Erick Reinikka

I'm very surprised to see you say "if this issue will be fixed". That's not an acceptable answer to me. On one hand you say you have a multilingual platform, and on the other you say you don't support Korean (due to the number of customers impacted). Korea is an important market for us, and it should be for you too.

Alyssa Gomez

Hi everyone,

I've done some testing with my team, and I wanted to share what we found.

We've seen that installing the Korean language pack on Windows resolves this issue in Storyline 2 Update 12. Here's how:

  1. Go to the Control Panel.
  2. Go to Language.
  3. Click Add a language.
  4. Search Korean and click Add.
  5. Restart the computer.
  6. Publish the course again.

We've also seen that this is not an issue in Storyline 360/Storyline 3

If you'd like for us to look into your file and do some further testing, you can share it privately with our team here. Our Engineers are around 24/7 to assist!

This discussion is closed. You can start a new discussion or contact Articulate Support.