So sorry that's happening, Scott. You came to the right place for help!
Would you be willing to share the PowerPoint file with me, so I could try importing it into a test Storyline course? You can share it publicly here or privately by using this upload link. I'll delete it after taking a thorough look!
Also, what version of Storyline are you using? You can find this detail by clicking on the Help tab, then About Storyline.
We are experiencing the same thing with Korean. When we try to create a text box in Articulate Storyline, it converts the text to blocks. Please let me know if you need a sample. Thanks.
Thank you for letting us know that you've run into this as well! It would be helpful to see your course to understand the nature of this issue. Please use this link to share your file with our Support Engineers.
I'm replying publicly so we can share the behavior with others who find this conversation! We have an issue where imported or pasted Korean text does not appear correctly in Storyline 360.
Our team is looking into its cause, and we'll keep this discussion posted on any new developments. Thank you for bringing this oddity to our attention!
Hi, I'm experiencing the same when I'm doing my translation projects... Is there any quick way that I could solve this problem? E.g. downloading new Korean fonts etc.. Or else we could only wait for your new updates.
I'm so sorry we haven't discovered a workaround yet. I'm going to share your experience in our report, and promise to keep this discussion posted on any new developments.
After more testing, it looks like this issue isn't present in Storyline 360, Version 3.30.19518.0. To continue authoring your course, you can temporarily install this previous version. Here's how!
I can appreciate that this isn't an ideal workaround, so we'll keep you posted if we hear of other options!
After more testing, it looks like this issue isn't present in Storyline 360, Version 3.30.19518.0. To continue authoring your course, you can temporarily install this previous version. Here's how!
I can appreciate that this isn't an ideal workaround, so we'll keep you posted if we hear of other options!
I tried and version 3.30.19518.0 works! Really appreciate your prompt response to quickly solve the problem! Will wait for your long term solution later. :)
I get daily notifications from Articulate 360 that new versions are available. Should I just ignore these notifications until the problem with the Korean translations is fixed?
Great question. We were sharing information about updating the Desktop App because we now have a minimum supported version. You can still run previous versions of Storyline 360 if needed.
I hope that clarifies a bit and we will share updates regarding the issue you're experiencing with your Korean text when we can.
I was having a similar issue with importing a translated Korean PowerPoint into Storyline 360 (translated characters were all blocks) and found a post here from someone in 2017 that indicated the following workaround. Change the translation document font to Malgun Gothic. Then when it is loaded into Storyline, change Player/Colors & Effects/Player fonts to Malgun Gothic. This enabled publishing without the language error.
HI I am experiencing the same issue when inserting translated Korean word file in Storyline 3. Is there a reulution?? It is a really important customer project.
Hi, my colleague tried this last night with one of her projects and commented with the following: If you have any issues with the Korean Language not reading correctly and showing as all blocks, change the font to Arial Unicode MS and it will display the Korean text correctly π Previously we had to uninstall and revert back to a former version of Storyline 360
Sounds like from the comment from Patti Swietch above that she too changed the font type and it worked fine. Hopefully, this will work for your project.
Hi! I have just that version of Storyline 3, but collegues of mine that have not done that update dont have the same problem. Is there possible for me to download an older version of Storyline 3?
No I cant right now, thats why I am wondering if there is an older version somewhere online.Otherwise I haft to delay this customer project and let a collegue do it when they have the time.
It would be great if you could look over the latest version.
24 Replies
So sorry that's happening, Scott. You came to the right place for help!
Would you be willing to share the PowerPoint file with me, so I could try importing it into a test Storyline course? You can share it publicly here or privately by using this upload link. I'll delete it after taking a thorough look!
Also, what version of Storyline are you using? You can find this detail by clicking on the Help tab, then About Storyline.
Thank you, I am using Articulate 360 version 3.33.206... Just downloaded the other day. I uploaded the PPT through the link.
The project I am doing provides an intro page then branches for Chinese (simplified and traditional), Japanese and Korean, ending on a common slide.
Only the Korean gave me issues and it is probably something silly...
Thank you for sharing your file with me, Scott!
Confirming receipt, and I'll be in touch in our case shortly after testing!
We are experiencing the same thing with Korean. When we try to create a text box in Articulate Storyline, it converts the text to blocks. Please let me know if you need a sample. Thanks.
Hi Susanne!
Thank you for letting us know that you've run into this as well! It would be helpful to see your course to understand the nature of this issue. Please use this link to share your file with our Support Engineers.
Hi, I have opened case 02037474 for this issue.
I am also attaching sample picture and .story file for your records. Thanks.
It appears that the timeline shows the correct Korean text, but the screen itself either shows blocks or in this case, strange squiggly lines. Thanks
Appreciate you sending your file in, Susanne!
I'm replying publicly so we can share the behavior with others who find this conversation! We have an issue where imported or pasted Korean text does not appear correctly in Storyline 360.
Our team is looking into its cause, and we'll keep this discussion posted on any new developments. Thank you for bringing this oddity to our attention!
Hi, I'm experiencing the same when I'm doing my translation projects...
Is there any quick way that I could solve this problem? E.g. downloading new Korean fonts etc..
Or else we could only wait for your new updates.
Hi, Chloe!
I'm so sorry we haven't discovered a workaround yet. I'm going to share your experience in our report, and promise to keep this discussion posted on any new developments.
Here's a glimpse into how we tackle bugs!
Hi again, Chloe!
After more testing, it looks like this issue isn't present in Storyline 360, Version 3.30.19518.0. To continue authoring your course, you can temporarily install this previous version. Here's how!
I can appreciate that this isn't an ideal workaround, so we'll keep you posted if we hear of other options!
This post was removed by the author
This post was removed by the author
I tried and version 3.30.19518.0 works! Really appreciate your prompt response to quickly solve the problem! Will wait for your long term solution later. :)
Is there any update as to when this will be fixed in the future? The older version is good as a stop-gap but....
Thanks!
I get daily notifications from Articulate 360 that new versions are available. Should I just ignore these notifications until the problem with the Korean translations is fixed?
Hi Susanne,
Great question. We were sharing information about updating the Desktop App because we now have a minimum supported version. You can still run previous versions of Storyline 360 if needed.
I hope that clarifies a bit and we will share updates regarding the issue you're experiencing with your Korean text when we can.
Hi Scott,
I was having a similar issue with importing a translated Korean PowerPoint into Storyline 360 (translated characters were all blocks) and found a post here from someone in 2017 that indicated the following workaround. Change the translation document font to Malgun Gothic. Then when it is loaded into Storyline, change Player/Colors & Effects/Player fonts to Malgun Gothic. This enabled publishing without the language error.
Hope this helps!
HI I am experiencing the same issue when inserting translated Korean word file in Storyline 3. Is there a reulution?? It is a really important customer project.
Hi, my colleague tried this last night with one of her projects and commented with the following: If you have any issues with the Korean Language not reading correctly and showing as all blocks, change the font to Arial Unicode MS and it will display the Korean text correctly π Previously we had to uninstall and revert back to a former version of Storyline 360
Sounds like from the comment from Patti Swietch above that she too changed the font type and it worked fine. Hopefully, this will work for your project.
Hi! I have already tried to switch to Arial and other fonts but it doesn't work unfortunately., and I am not using 360, Im using Storyline 3... :(
Hi Malin!
Sorry you've hit this snag as well! Which version of Storyline 3 are you using?
We haven't heard anything about this bug in Storyline 3. We've tested in update 7 and the Korean text was displayed perfectly.
If you're not on an updated version of Storyline 3, here's where you can download the newest version!
Hi! I have just that version of Storyline 3, but collegues of mine that have not done that update dont have the same problem. Is there possible for me to download an older version of Storyline 3?
Hi Malin
could you uninstall the existing install on your computer and get the SL3 download file file from your colleagues?
No I cant right now, thats why I am wondering if there is an older version somewhere online.Otherwise I haft to delay this customer project and let a collegue do it when they have the time.
It would be great if you could look over the latest version.
You'll need to contact Articulate support to get previous versions
This discussion is closed. You can start a new discussion or contact Articulate Support.