Forum Discussion
Closed Captions flash bug
Hello,
I started using the closed captions feature of Storyline 360 yesterday. I like the tool and it works well. However, I did find a bug. The closed captions in the flash output doesn't support an apostrophe. The html5 output works. I have attached a couple of pictures.
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!
I'm really glad you brought this up, Russell, as I don't see that this has been reported by anyone else. I did a quick test, and I'm seeing the same thing you're seeing. I'll get it reported to my team so we can begin looking at next steps.
Thanks again for letting us know what's going on, and I'm sorry if it's been a headache for you!
- CynthiaPareCommunity Member
Hi there!
We are working on a french course that we have to deliver today and we just noticed that all special caracters (ie : ç, é, è, etc) doesn't come up properly in the closed captions.
The HTML5 output does work, but it doesn't work properly once in Flash. It is really important that the course also works in Flash, because the text (on the slide) doesn't appear correctly (all replaced by Times!) in Internet Explorer at our client location (all computers are setup the same way).
We tried copy/pasting the text in Notepad before pasting it in the Clsoed Caption tool, but still no luck.
Anyone can help us?!! It's a major issue for us and really not a good suprise this morning.We are trying to figure it out on our hand, be we are running out of time.
Thanks a lot! Hi Cynthia, thanks for chiming in, and I'm really sorry this is causing you frustration. We're seeing a problem in Storyline 360 where some special characters don't appear correctly in the Flash output. Our team is looking into this, and you're in the right place to stay updated on this bug's progress.
- CynthiaPareCommunity Member
Hi Alyssa!
Is there any progress on this issue? Should we expect an update soon or not? As it is, we cannot use the Closed Caption tool embedded in Storyline at all and have to do it all by hand in Notepad... And frankly, that is not a task we had planned.
Please keep us posted.
thank you!
Hi Cynthia,
Although I don't have any updates to share yet, I'll certainly share your feedback with my team. I'm sorry this has been a frustration for you, but I'll be sure to let you know when I have more information!
- rachelatkaiserCommunity Member
Hi Alyssa,
Just chiming in here, letting you know that I'm also experiencing this problem with apostrophes not appearing correctly in the captions in Flash. Unfortunately, I have to publish the course in Flash with HTML5 fallback because certain users cannot view the video otherwise in IE. Hope there will be an update soon.
- EmilioJeffries-Community Member
Howdy!
We've got a huge project coming through that is very far along in its progress. We've utilized the caption feature in 360 (which is amazing!) It saved us so much time until it didn't.
We're going through the same situation. We need to publish in Flash with HTM5 fallback because of our user base. This project is not particularly small and would take a lot of extra time out of the budget to go through and add individualized captions. For now we are keeping the file without captions on until I can republish with the fix.
Hoping that this patch is making it's way sooner than later.
Best,
Emilio
- WaltHamiltonSuper Hero
I. too have a complete curriculum republish depending on these captions. As you may imagine, as an educational institution, we can't publish with substandard grammar.
- NataliaSaldarriCommunity Member
Just checking if there is any solution to this since I am working with german courses where we need also special characters (ä ö ü ß). We have the same problem with Storyline 3
Hello everyone - Yes, we are aware of the impact and this bug has been prioritized to reflect this. I wanted to share some information on how we define bugs and how we tackle them when they occur.
Any user using HTML5 output should not see this error.
Hopefully we will have an update to share here soon.
Thanks for your patience.