Glossary entries in Arabic not appearing

Apr 13, 2023

Hi All,

I have a Storyline360 that needs a translation in Arabic and I am building a mock-up to test how this plays out. Whilst I changed the direction of text easy and changed the language of the menu in Arabic easily, I am now trying some details out. The first one is to use a Glossary (standard built-in from Storyline).

The title translates alright in the player.

The entries though (text translated in Arabic) a simple term of Glossary (see attached) and a description as 'An alphabetical list of words relating to a specific subject, text, or dialect, with explanations; a brief dictionary' do not appear at all. 

I translated the text in Google Translate as for the mock-up I am not much concerned about precision (later we will use proper professional translations) and imported text all around the mock-up, with no problem at all. But in the Glossary any entry in Arabic is not showing. 

Does anyone has a clue why this is so?

Thanks in advance for your help.

Best

Andy 

4 Replies
Luciana Piazza

Hi Andrea,

Thanks so much for reaching out! I'm sorry to hear you're having this issue with your Glossary not displaying the terms and descriptions you need. Happy to help!

I have a few questions in order to better understand your setup: 

  • What version of Storyline are you currently using? Our latest update is (Build 3.74.30180.0).
  • Are you using the Modern or Classic Player? 

To double-check that your Player Properties are set up correctly for Arabic, please try the following:

1. Open Up the Player Properties and double-check that the Glossary is selected.

2. Then, go to the gear shift icon Others and select Text is read from: Right to Left. Click on the Glossary in the Player Preview to see if you are able to view your terms and descriptions.  

Looking forward to hearing from you! 

Andrea Borsoi

Ciao Luciana,

Yes the version is the one you indicated and also all the rest is how you showed.

Attached is a screen-capture collection that shows you the setting used are as per your email. Note that (A) there is the Term/Description properly inserted but it does not show (both in this Player Setting screen but also on the normal Preview screen - all shows black. Also the title (I discovered meanwhile) is not proper RTL (B). I wonder also what happens with the CC text (this is next in my test list, as I am building a mock-up for a client before we embark into 7 modules in French, that have also to be translated in Arabic (I would like to know what works and what doesn't with the latter language, before to embark into this path and then discover when it is too late that some is not possible....cause in that case we may opt for non-Articulate authoring tool, which is a pity though, cause I convinced everyone that Storyline is the best tool - Rise was discarded cause we do not want to have to intervene at CSS level (non-standard and in my view it is best avoided). So it is:

1-Glossary Term/Description not showing in pull-down menu;

2-Orientation RTL in a) Course-Title and b) Glossary-Title

3-If you have any pointer to CC text RTL I would appreciate. But I can search this first as I have not yet done this (if the above is not solved, there is a good chance we will not use Articulate)

Thanks for the help! 

Kind regards (o Ciao se preferisci :-) )

Andrea

Jürgen Schoenemeyer
Andrea Borsoi

Dear Jürgen,

Guten Abend aus Deutschland.

Thank you SO MUCH for all these info. Feel stupid not to have spotted that I was using the Resource function. In the rush to go all Arabic (which clearly I do not read!) I admit that it is a little confusing. But I am going to implement it. I should have thought of it but at times one gets so puzzled that forgets the basic checks. It goes into narrow vision. 

Thanks also for the other links. I am going to study them!! Precious help. You are the man!

Going to test also the rest. Will report back so it can be useful also for others. 

I owe you a few beers I think. Thanks a lot!!!!

Tschüssi

A