Variables not working after translation

Aug 11, 2021

Wonderful Articulate world,

I have a presentation that works fine in English. When it gets translated into Spanish using Amazon translate the variables no longer work.

Any ideas?  

16 Replies
Judy Nollet

I'll add to what Phil said. Your variable references were likely translated, while the actual variable names remain the same.

So, for example, if you had a variable called "name," the on-slide reference would be "%name%." But if that were translated into Spanish, the on-slide reference would be "%nombre%" -- and Storyline would have no record of a variable called "nombre." 

If variables are used in multiple locations, it'd probably be quickest to update the variable name. Otherwise, you'll need to revert the on-slide text to the original variable name.

Maria Costa-Stienstra

Hi, Eric.

I am glad Phil and Judy were able to help you figure out the issue!

I just wanted to add a quick note: it looks like your email signature with contact information came through when you replied via email. You can remove it by clicking ‘Edit’ below your response. Here’s a quick Peek video if you need help.

Judy Nollet

Hi, Eric,

In the file you provided, the Proximo button activates on slide 1 if I enter the designated text. Note in the screenshot that the text shown on the slide is the same as the value in the trigger.

The button doesn't activate on slide 3. Well, it doesn't if one enters the text shown on the slide. It will work if one enters "PreSharedKey" -- because that's what the trigger is looking for. 

So be sure the desired variable value is the same as what you're telling people to enter.

(BTW, I noticed that the narration mentions typing it all as one word. But that isn't done with the translated text...)

Ren Gomez

Hi Eric,

Thanks for sharing your file! I'm not sure if something happened during the translation, but I spotted a space in between the "DF" and "700120000442", so it looks like the interaction won't move forward unless they include the space.

Also, as a design tip, I'm not sure there's a need for an Active state for that button.

I attached a different approach worth considering. I hope it helps!