Hyperlinks not working after translated text to arabic

Jan 20, 2023

Hello, I received a bug I created a new trigger for text hyperlinks but it does not work in the translated version to Arabic language.

In the same version of the English module, the hyperlinks worked correctly but when I translated the same module into Arabic, I observed that the hyperlinks did not work.

Note that I have integrated the links manually and I have tested on different browsers and also on scorm cloud the bug still exists you have a solution?
thank you

4 Replies
Andrea Borsoi

I found a workaround for this.

1) add (with the keyboard) a dot on each side of the arab world you want to hyperlink

2) style the dots as the background so they 'disappear'

3) hyperlink the arabic word including both dots at each side with whatever URL you need (in my case the landing page online is also in arabic

4) style the arabic word (without the dots) with a underscore so that it looks like a hyperlink (use automatically Normal state  colour).

Indeed, it does not show a Hover and a Selected state but the link works.

Alternatively, one could use a small Hotspot over the word and add a special layer (transparent, so showing the original background beneath) with text-box with the same arabic word, perfectly over imposed, and trigger a state with a mimicked Hoover and Visited states. Style the text only first with #49a1fa and the second with #955592 (or whatever colours your states in a Latin language have - a bit of colour picking and you can find the HEX codes); in  my case this is what I have as standard. And it also does the job.

Not the simplest ways to mimic an hyperlink, I admit, but it is not impossible I think (this one I have not tested it, as I rarely use hyperlinks in text (but normally use other ways get the user to get to the same information - which are not bringing them 'out of the screen/tag' in use. If you build the content well it can be done Iand to me it works better from the 'pedagogic flow'.

Indeed it would be nice that Articulate fix this, as it should be possible for any RTL languages to work in the same way as LTR. I cannot see why it should not be like that.

When a fix is implemented, it would be nice to know. Hopefully soon? (articulate support?)

Hope it helps you Saad. Let me know what you think Jürgen (it may not be the most elegant solution, but...it's better than not having this function, if one needs it).

Cheers

Andy