Software String Import as Reference

Aug 02, 2013

Hello Everybody,

We are currently using Articulate Storyline to create training material for our staff and customers.

Our products are patient monitors with a lot of user interface texts. In our content management system, we implement all these software strings as multi-language variables, the benefit being that we have the correct software text in all target languages automatically.

We were wondering if such a solution has already been implemented in Storyline by somebody?

Our software strings are available in an XML file, detailing the variable name and the variable value in a form that might be used to integrate this information in the list of references in Storyline.

Is it possible to do such things with Storyline via API?

Thank you for every kind of information that might help.

Regards,

Martin Allgeier

6 Replies
Mike Enders

Martin,

A bit over my head...

I pinged a couple people and they said... I hope it helps!

Mike

Person 1:

They'd probably use JavaScript triggers to GetVar and SetVar. I assume JavaScript can interact with an XML file to retrieve the appropriate values, but that's beyond me. I'd recommend reaching out to an ELH super hero or known JavaScript expert in the forums to ask for assistance with this one.

Person 2:

Good place for them to start is here:

http://thatelearningcompany.wordpress.com/2012/11/09/usingja…

Then, here's an article on how to retrieve data from an XML file with JavaScript:

http://stackoverflow.com/questions/10684145/how-to-retrieve-…

They still gotta do the leg work, but that's how I would start approaching it.

Martin Allgeier

Thank you, Mike

Maybe I try to explain in more detail:

1.)

a) The graphical User Interface of our Patient Monitors has an interface in the language of the user (not in all countries, but in more than 20 countries).

b) Our content management system offers building blocks (topics) that can be used by authors to assemble new text.

c) All words (up to sentences) on the monitor screen have a code ID (similar to the Reference IDs in Articulate Storyline)

d) Whenever a monitor GUI is set to a specific country, the system replaces the ID with the country-specific word.

2.)

a) In all electronic or written documentation (e.g. the Instructions for Use), all words that refer to a word that is visible on the monitor, is written as Reference to these Monitor SW Words. In our content management system we simply pic out the right term from a huge list of all terms that are available.

b) In the graphical user interface of our writing system, we can see the word in English with a highlighted background (and it is called "embedded topic").

c) When the text is printed, the systems assembles the text with all text elements, e.g. "Select the "Start Measurement" button". In this case, "Start Measurement" would be the English word for a Reference that is used in the monitor.

d) When the text is translated, the translation system picks out the already translated text for this ID; e.g. "Select the "Starte Messung" button." The translator has only to translate the rest of the sentence, e.g. "Wähle den "Starte Messung" Schalter."

e) The advantage is that:

- there is never a typo in a term (that is used in the monitor) that is written in the Instructions for use

- the translator does not have to ask what the meaning of a term is in the monitor, because this has already be done during the translation of the monitor software

- thousands of monitor terms are already translated into multiple languages

3.)

a) Since we have now these text strings already translated in a huge list, we could reference to these text with the Reference tool of Articulate Storyline.

b) However the number of references in Storyline is not limited, and the maximum string lenght is 80 characters, this tool does only allow to manually create one reference after each other.

c) The goal would be to import the whole catalog of Patient Monitor text IDs of a certain language into the Reference tool of Storyline. There, the author should be able to open the list of references and select the one that should be written at this point. Our content management system offers a search functionality to find the terms very fast.

d) If the Storyline project is ready, we would use the Tranlation Export tool of Storyline to create the DOC, or XLIFF file. In our example the text would then read "Select the %D6:NLS_NBP_SCO_1_START_MEASUREMENT% button." In the preview then again "Select the "Starte Messung" button."

e) The German translator woud then be able to read  "Select the "Starte Messung" button."

f) The translation Import would then be: "Wähle den %D6:NLS_NBP_SCO_1_START_MEASUREMENT% Schalter." In the preview then again "Wähle den "Starte Messung" Schalter."

In Summary:

We would need an interface that creates automatically a catalog of References in Storyline, by using an XML file that is already available in our content management system.

Is this now more transparent? Do you have any open questions?

Thank you in advance for your ideas.

Regards,

Martin

Phil Mayor

There is no way to create a variable externally, these variables would need to be created individually in Storyline, you could then populate the variables  in Storyline externally using Javascript in the published file but could not do this in the source file.  I also do not know of a way to get round the character limit in variables.

THis is more like a feature request than something that is possible with the current feature set.

onEnterFrame (James Kingsley)

I think the closest you could come (in the current state of the software) is a solution similar to what "Person 1" suggested. 

In Storyline create a variable for each piece of text that will need to be replaced. Use the ID you currently use for these pieces of info. 

Write some JavaScript that will run on launch to find the value of each ID in your XML for the language selected and then update it in Storyline (SetVar).

I haven't run into any character limit for variables. 

This seems like a fun project let me know if you need more help. 

This discussion is closed. You can start a new discussion or contact Articulate Support.