Forum Discussion
Right to Left prompt for Arabic
Hello, I have set my player to read right to left but the invalid answer prompt still reads Left to Right. How can I fix this?
Happy to help here, QA!
To display your slide content in a right-to-left orientation, make sure the Right-to-Left Text Direction button is selected when you enter or edit text.
Here's more on Right-to-Left Language Support. Let me know if this helps!
That's not what I'm asking about. Please see the screenshots in my original post. The system pop up that appears when a user submits a question without making any selections (Invalid Answer) reads LTR even though the player is set to RTL.
Apologies for the misunderstanding, QA!
You're right; I see the same thing on my end with the Invalid Answer prompt. I've reported this to our QA team, but currently, I don't have an update to share. I've included this thread in the report so that once we have additional information, we can share it here.
In the meantime, I tested this in the Classic Player, and the Invalid Answer Text reads Right to Left. If it fits in your design, this is a workaround I'd suggest.
Me again! I came across this workaround to create a custom invalid answer message if the Classic Player doesn't fit your design. While it mentions Storyline 2, it should still apply to Storyline 360!
This is still an issue 9 months later. Is anyone working on this? When is this going to get fixed? It's literally right to left text in 3 fields. Why is this taking so long?
if you wan't to fix it - add to "story.html" or/and "index_lms.html"
<style>
.message-window-heading > p {
text-align: right !important;
}
.message-window-text {
text-align: right !important;
}
</style>e.g. to the end
result:
Jürgen
Thank you, Jürgen, I shall try this!
Jürgen, this works like a charm! 🙏🏻
Thank you for these 2 lines of code, that Articulate wasn't able to implement in the last 4 years.
Dear Jürgen,
Where exactly you find the files "story.html" or/and "index_lms.html" you mention? Inside the SCORM once packaged during <publish>? If so, does this mean that any editing done on the .story file in Storyline360 needs this lines of code added to the new SCORM as part of the post-packaging process?
Thanks for clarifying, be patient with me as I am not much into programming and normally I Publish, get the SCORM and upload as it is on a LMS.
Cheers
Andy
- if you publish to web, there is story.html in the publish folder
- if you publish to scorm, there is story.html and index_lms.html
- add the 8 extra lines to the html files and save a copy of the files
- on every publish the files are new created and overwrite the old versions
- as long as you don't change the storyline version, you can reuse the patches html files
normally you can include such css patches with javascript so that they survive a publish
-> examplebut that's not possible here, because the patch is needed before the slides are started
Dear Jürgen,
Thank you so much for your generosity. I learned a lot from you.
Cheers
Andy
