Arabic Closed Captions

Hi, Peter.

Thank you for reaching out!

I can see from your screenshot that your player is set to RTL, so your captions should follow the same format. 

I opened a support case on your behalf, so you should hear from our team soon, and we'll take a look at what's going on with your project.

Support has given me no help on this request from three months ago.

Does Storyline 360 really support Arabic Closed captions???

Hi Peter!

Is the closed caption text missed with English text too? We have this logged as a bug where Arabic Title and Closed Caption mixed with English text is not displaying correctly. 

I've linked this conversation to our bug report so we can update you when we have more information.

There are captions with mixed languages but there are captions with Arabic only and the punctuation is incorrect (period on the right instread of the left).

Hi there,

How, we can manage the title of popup box in right for left for Arabic language. We already applied the setting Right to left. It applies for the message text, but title still remain in the left. See the attached grab.

a solution for the modern player

https://community.articulate.com/discussions/articulate-storyline/right-to-left-prompt-for-atabic

for the classic player you have to inject

<style>
  .message-window-heading {
     text-align:   right !important;
     padding-right: 15px !important;
  }
</style>

result:

Thanks Jurgen

Hi Jurgen, this is the exact issue I'm having and it looks like your solution will work perfectly. However, I'm new to adding script directly like that. 
Where do I add that script? How do I open a field/window that accepts script for captions specifically?

• if you publish to web, there is story.html in the publish folder
• if you publish to scorm, there are story.html and index_lms.html
• open the html files in an text editor (notepad++ is ok and free)
• add the 8 extra lines (modern player) or 6 lines (classic player) to the html file(s) and save the files and a copy of the file(s)
• on every publish the files are new created and overwrite the old version(s)
• as long as you don't change the storyline version, you can reuse the patches html file(s)
• if something goes wrong (e.g. the course don't start anymore) publish and try again

example: modern player -> story.html / index_lms.html

<style> if you use modern player

<style>
   .message-window-heading > p {
      text-align: right !important;
   }
   .message-window-text {
      text-align: right !important;
   }
</style>

<style> if you use classic player

<style>
  .message-window-heading {
     text-align:   right !important;
     padding-right: 15px !important;
  }
</style>

these are no scripts, these are css styles

• these rules are overwriting the default rules in "output.min.css"
• therefore they have to be behind all .css files and contains the word "!important;"

Important: this is not a solution for Close Captions - this is for invalid answer prompt (the thread title don't match anymore)

Oh I see thank you. Would something similar to this work for closed captions? Or is that particular issue still unresolved?

Please disregard that last message. I've actually discovered a partial solution. In case anyone in the future has the same problem I did:

Copying and pasting from a right-to-left oriented document worked EXCEPT for the punctuation. Storyline captions were incorrectly placing the periods on the right. However, the text itself was correctly right-to-left. 
To get the period to show up on the left, I pressed the "home" key, then the period key, and that placed it correctly.

Hopefully this continues to work for me!

It is working, Thanks

the RTL/LTR solution was helpful thank you - the home key solution was also good. Next issue to solve and I'm curious if you all see the same: The CC look correct in the editing tool inside SL, however upon publishing, all of text is converted to a nonsensical jumble of Arabic lettering. Side by side comparison attached - on the left is the CC from inside the editing tool in SL. On the right is what it looks like in review360 after publishing. Edit: just confirmed it's not a review 360 thing, the bug occurs publishing to Reach360 as well, so I'm officially out of ideas. Any help greatly appreciated. The punctuation I can work around (you all know how it goes - multiple languages in one course, I don't want to branch in the LMS, user picks language at first scene and each scene is the same content in a different lanuage) But if I can't get the closed captions to publish as they display in the CC editor it will be a problem. Thank you all!

strange - the chars should work correct out of the box (SL 3.86)

https://360.articulate.com/review/content/fc58910e-978d-4c4f-b064-70165361a135/review

and the dot on the wrong side can patched with one line of javascript

trigger: when the timeline start

document.querySelector(".caption-container").style.direction="rtl";

Thanks for confirming that it should work as displayed in the editor - now to figure out why it isn't. Maye becuase the player is set LTR for the other languages ...

Think its time articulate dealt with this issue. All of these workarounds are fine but any changes etc means having to go through all the hacks again. We should not have to hack the Rise file to get Arabic to display as expected.