Hi there, John. Thanks for sharing the image. That is a lot of translated captions, so let's figure out what's happening.
When creating captions in Storyline directly, I'm able to use your above text without issue. I don't have a translated SRT file to test, however. Could you share a video and the relevant SRT file with me for testing? You can attach both here in the discussion. If the content is sensitive, feel free to upload it to us privately here. You have a Team subscription, which means you get priority support!
Thanks. I can send along an SRT file , weird thing is , this course has 23 chapters, and some chapters are fine and some arent. I will upload an SRT used in one of the chapters to the private link shortly.
To add more info , this also happens when a French Lanquage SRT file is used.. The lines of text shown in the image are : La prochaine chose que vous devez faire est de calibrer vos écrans tactiles
La clé pour calibrer l'écran tactile inférieur
((Info has been sent to support with the case #)).
Thanks John for continuing to keep us updating and updating your case. I see that it's been escalated to our senior support engineers to take a look at - so they'll be in touch soon!
Hi, Amy. Very sorry this bug is getting in the way!
Our team is hard at work on a fix for the accented characters not displaying correctly issue and are committed to providing it as soon as possible. You're in the right place, and we'll update this discussion when it's ready.
I am guessing the fix will be found right after I complete these 9 courses with Spanish Translation Closed Caption. I wonder what language they tested this with in product assurance ? :)
I did some work this weekend and found that I had success with changing my captioning file, which was originally word and saved as a plain text file. I opened it in Notepad. From there I was able to change the Encoding settings to UTF-8 when I "Save As". Then manually changing the file type extension to .vtt in the folder it's housed in before importing again.
Not the easiest process, but it at least worked for my purposes. Hopefully it will help a few of you!
My text files were UTF-8 , however I saved them as .srt files , changing to .vtt seems to have "fixed" or eliminated the issue on the one file I tested. Now off to test the other files. Thank you Amy !!
A quick update to let you know we've released a fix for this issue where some accented characters in closed caption files became question marks in Storyline courses. You'll find that fix available in the latest update Storyline 360, build 3.28.18944.0.
To install the update, launch the Articulate 360 desktop app on your computer and click the Update button for Storyline - you'll find more details here.
13 Replies
Hi there, John. Thanks for sharing the image. That is a lot of translated captions, so let's figure out what's happening.
When creating captions in Storyline directly, I'm able to use your above text without issue. I don't have a translated SRT file to test, however. Could you share a video and the relevant SRT file with me for testing? You can attach both here in the discussion. If the content is sensitive, feel free to upload it to us privately here. You have a Team subscription, which means you get priority support!
Thanks. I can send along an SRT file , weird thing is , this course has 23 chapters, and some chapters are fine and some arent. I will upload an SRT used in one of the chapters to the private link shortly.
Thanks.
Just an FYI for anyone following , this is happening with any letter with a ' (accent) above it. Articulate is still working on a solution.
Thanks for popping in to share an update, John.
I'm linking this conversation to the report as well so that we can update anyone following along as well when we can.
To add more info , this also happens when a French Lanquage SRT file is used..
The lines of text shown in the image are :
La prochaine chose que vous devez faire est de calibrer vos écrans tactiles
La clé pour calibrer l'écran tactile inférieur
((Info has been sent to support with the case #)).
Thanks John for continuing to keep us updating and updating your case. I see that it's been escalated to our senior support engineers to take a look at - so they'll be in touch soon!
Any update on this? I've had to correct one entire course by hand so far, but would love to avoid that on my most recent project.
Hi, Amy. Very sorry this bug is getting in the way!
Our team is hard at work on a fix for the accented characters not displaying correctly issue and are committed to providing it as soon as possible. You're in the right place, and we'll update this discussion when it's ready.
In the meantime, we're happy to take a look at your current Storyline .story file to see if we can offer any other solutions!
I am guessing the fix will be found right after I complete these 9 courses with Spanish Translation Closed Caption.
I wonder what language they tested this with in product assurance ? :)
I did some work this weekend and found that I had success with changing my captioning file, which was originally word and saved as a plain text file. I opened it in Notepad. From there I was able to change the Encoding settings to UTF-8 when I "Save As". Then manually changing the file type extension to .vtt in the folder it's housed in before importing again.
Not the easiest process, but it at least worked for my purposes. Hopefully it will help a few of you!
My text files were UTF-8 , however I saved them as .srt files , changing to .vtt seems to have "fixed" or eliminated the issue on the one file I tested. Now off to test the other files.
Thank you Amy !!
Oh good! Glad I was able to help!
Hi All,
A quick update to let you know we've released a fix for this issue where some accented characters in closed caption files became question marks in Storyline courses. You'll find that fix available in the latest update Storyline 360, build 3.28.18944.0.
To install the update, launch the Articulate 360 desktop app on your computer and click the Update button for Storyline - you'll find more details here.
Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.
This discussion is closed. You can start a new discussion or contact Articulate Support.