Smart Apostrophe Code in Closed Captioning
Oct 04, 2017
I would like to bring up an unexpected hiccup in the closed captioning tool in Storyline and see if anyone else has experienced this or has a work around for it. I was excited to use the closed captioning feature that Storyline is now featuring, but after a few weeks of using it, I'm going to have to go back to importing my files. It seems if you use an apostrophe or quotes in the closed captioning maker in Storyline it defaults to smart apostrophes and not standard or ascii apostrophes, which then is converted in Internet Explorer to smart code and makes the word illegible. Since most of our users are required to use IE, this is an unacceptable. We have tried copy and pasting from notepad to keep it from coding, but Storyline must be automatically changing it, because it reads code every time.
10 Replies
Brett Rockwood's analysis in this post https://community.articulate.com/discussions/articulate-storyline/find may help you.
Typing the code using the keypad may be a workaround.
Hi Sommer,
Thanks for reaching out, and I have good news for you! We just released an update for Articulate 360 that included a fix for this problem in Storyline. With this fix, special characters such as accented letters and apostrophes now display correctly in closed captions.
To take advantage of this update, just launch the Articulate 360 desktop app on your computer and click the Update button for each application.
Let me know if you have any questions!
Thank you, Walt.
That worked!
Hi Alyssa,
I've made the last two updates for Articulate 360 and am up to date and though that has solved the above mentioned problem. A new problem has now occurred when viewing from Internet Explorer. All the closed captioning I made in Notepad ++ will have to be redone in Storyline or another program because all apostrophes, quotes and many capitalized letters: Y, P, A, and O that won't display at all, also the letter q and z in lowercase and uppercase are gone. Is this something you are all are working on?
Hi Sommer,
Thanks for circling back. This is the first I'm hearing of this, so I'm really glad you brought it up. Could we have a closer look at your file to do some testing? You can share it directly with our team here. Thanks!
Is this issue being addressed in Storyline 3? I'm having the same issue. Thanks!
Hi Mary Ann,
Thanks for checking in. That fix in Storyline 3 is still in the works, but it will likely be released in the next update that goes out.
Thanks for checking in again, Alyssa.
We did some in house testing and discovered that our files were saved as vtt files, but coded as sbv files. We renamed the files and now they display correctly, so we're all set and hope this may help anyone else out there that is having issues.
That's great to hear, Sommer. I'm glad you got it sorted out. 🙂
Hi all,
Great news - Update 3 of Storyline 3 is available!
We released a fix for the issue where the closed captions don't support apostrophes and other special characters.
You can view the Version history here and you'll also be able to download Update 3 here!
This discussion is closed. You can start a new discussion or contact Articulate Support.