I am creating a course in Storyline 360 in Arabic and all the Arabic is turning out fine (I use Akhbar font). But now I published a course and when you type an answer in the text entry field the letters are shown seperately (instead of connecting).
Any ideas on how I can solve this? I added an image for reference.
Thanks for replying. I'm not sure I understand what you mean. I copied your text entry box and when I enter in the preview mode in storyline it does indeed connect the letters, but when I publish the project for review it doesn't.
I see that you've been getting some great help from Jurgen, but I just wanted to pop in and offer some insight as well!
Testing the file Jurgen shared on my end (Storyline 360 ver 3.79.30834.0 via Windows Parallels on a Mac M1 in Chrome/Firefox) I was unable to reproduce the behavior you are encountering. The Akhbar font characters all display as connected in my example. Here's a quick Peek sharing my results!
To clarify, is the behavior you are experiencing replicable across all browsers or specific to one?
Also, it would be helpful to take a closer look at your project file and test it further on our end. Would you be willing to share a copy here in the discussion or privately through a support case?
8 Replies
just tested - combination of input char seems to work for me*
Peek: https://360.articulate.com/review/content/63614f21-6ff9-4c16-852b-13e8c1837fc1/review
tested (Windows 11 + Firefox/Chrome)
https://360.articulate.com/review/content/fd6cd5b8-6bcd-4135-82d8-bc9878cfeda3/review
* I have installed Win 11 language pack arabic (egypt) and tested with the Accessibility OnScreen keyboard
Thanks for replying. I'm not sure I understand what you mean. I copied your text entry box and when I enter in the preview mode in storyline it does indeed connect the letters, but when I publish the project for review it doesn't.
Hi Anneruth!
I see that you've been getting some great help from Jurgen, but I just wanted to pop in and offer some insight as well!
Testing the file Jurgen shared on my end (Storyline 360 ver 3.79.30834.0 via Windows Parallels on a Mac M1 in Chrome/Firefox) I was unable to reproduce the behavior you are encountering. The Akhbar font characters all display as connected in my example. Here's a quick Peek sharing my results!
Also, it would be helpful to take a closer look at your project file and test it further on our end. Would you be willing to share a copy here in the discussion or privately through a support case?
Looking forward to hearing from you!
Hi Steven,
Sure. I tested my course in Edge and in Safari (on my iphone).
Here is the link to review the course: Prayer_B | Review 360 (articulate.com)
And I have attached the .story.
This post was removed by the author
very interesting behaviour
your input text is working in my example
https://360.articulate.com/review/content/11d10722-24c0-4dbe-b043-51bfd65bbf7e/review
my input text in your course is not working
https://360.articulate.com/review/content/50afdc6e-a15a-40e3-9449-658bf9e3bcb6/review
something in your course triggers the problem - it's not the input field
more tests
result: if you use for static text and input text the same font -> input text is broken
Wow, interesting. So the conclusion is: use two fonts?
Thank you Jurgen for taking the time to test this.
yes, change the font of all input text fields e.g. to Open Sans and test it in detail
here is the review link to my patched version
https://360.articulate.com/review/content/5e694272-6e91-477d-9e5c-cc38d97ed40d/review
@articulate: you should investigate what happens here with the fonts and fix the problem