NEW IN STORYLINE 360: Glossary Import and Export

Hello Wendy,
Thanks for your quick reply, I will try.
Now I'm having a metting, see you later.

Is there a way to export your glossary from an Engage file? I have a glossary I created with 890 terms and I cannot import it into Storyline. I am guessing there is an import limit for slides? Any suggestions? 

There is no attachment Jack?

Sorry Wendy, now inserted. :)

Hi Jack

like I said to Margit above, the Term and Definition need to be in their own column not using the ;

The .csv file you shared is setup like this

setup like this and the import works as expected - see this Peek video

Yes Jack I was the same with my file. Maybe we run into a language issue here. As we both look the German Excel and Windows version.
I don't know what exactly happen, but the semicolons are added automatically when we save a CSV (comma separated value) file.

Hallo Wendy,

Vielen Dank für Ihre schnelle Antwort, ich habe das Problem gefunden und es ist wirklich:

"Many operating systems and countless programs support CSV files, CSV actually stands for comma separated values and means comma-separated values.
But if you live in a German-speaking country, it will not be that easy. The reason: Excel writes on systems with one of the German-language keyboard layouts no commas (,) as delimiters in the CSV files, but semicolons (;). "

@Margit, ja es liegt an den deutschen Tastaturlayouts.
Wenn Sie die so geschriebene CSV-Datei mit dem Editor-Texteditor öffnen (Rechtsklick / Öffnen mit / Editor), sehen Sie die Datei anhand von:

Definition; Term
A;Alpha  
B;Beta
C;Cäsar  
Die Felder werden nicht durch Komma (,) getrennt, sondern durch die Excel-typische Singularität durch Semikolon oder Semikolon (;).

Solution: Natürlich können Sie mit einem Suchen / Ersetzen-Vorgang im Editor jetzt einfach alle Semikolons durch Kommas ersetzen. Wenn jedoch eines der Felder ein gewünschtes Semikolon wäre, würde dies ebenfalls durch ein Komma ersetzt:
Definition, Term
A,Alpha
B,Beta
C,Cäsar

Thanks Jack for your detailed investigations.

This is SO timely.  And wonderful!  Thank you so much.

This saves a lot of time, will incorporate this in the project I'm working on now.

Thanks :)

Oh i nearly missed this! . Now my weekend can start on an high. Thank you for this function Articulate development team!

Super excited to try this out! I have done a bunch of translated course, and the glossary was always a hassle.

So I have a problem....

In the file attached I want to acheive a comma separated definition. In the file it says:

This is term 3, the definition is def 3, but now 3. 

When I import that it displays as:

This is term 3, the definition is def 3

Surely You must be able to write a definition with , right?

As the file is comma separated it will split the terms at the comma, the file is not a complex file. You can enclose the comma in double quotes but will have to edit after import.

If you use excel to produce your CSV these should be added automatically (it adds them to beginning and end of the string) and looks like Storyline strips them out

Thanks Phil, that will be cumbersome though. I tried 

This is term 3, the definition is def 3"," but now 3.

Then the entire row is not imported, yes using excel. 

Great! the issue with the Glossary is the size of the font!! is so small and cannot be changed…. :-(

My problem is still unsolved, this is just an example of the glossary I would like to import, the real one consists of 500 rows...anyone who can help out?

Hi Christian,

Excel even strips out the comma when I reopen the file, so it seems that's a part of what's similarly removing it from Storyline upon import.  

Changing the separator in language setting in excel made it work

Get Outlook for iOS