I have been having major issues with Storyline for the last two months. I'm creating my course (about 100 slides) and when I preview the slides, all looks good. However, when I publish to 360, I get a lot of textboxes with scrollbars. On the slide the textboxes fit just fine and they preview fine. However, when I publish to 360, it bloats the setting so that not all the text is showing and there are now scroll bars on the text. This is happening with tables as well, but instead of adding scroll bars, it just cuts text out.
\n
The really crazy part of this, is that sometimes it publishes it correctly and sometimes it doesn't. I can't figure out what makes it publish correctly vs with text all out of wack. I updated Storyline, I restarted my computer, I closed other applications. This doesn't seem to affect the outcome.
\n
This also is an issue when publishing to a web file or SCORM file.
\n
Can you please tell me why this is happening?
I have been having major issues with Storyline for the last two months. I'm creating my course (about 100 slides) and when I preview the slides, all looks good. However, when I publish to 360, I get a lot of textboxes with scrollbars. On the slide the textboxes fit just fine and they preview fine. However, when I publish to 360, it bloats the setting so that not all the text is showing and there are now scroll bars on the text. This is happening with tables as well, but instead of adding scroll bars, it just cuts text out.
\n
The really crazy part of this, is that sometimes it publishes it correctly and sometimes it doesn't. I can't figure out what makes it publish correctly vs with text all out of wack. I updated Storyline, I restarted my computer, I closed other applications. This doesn't seem to affect the outcome.
\n
This also is an issue when publishing to a web file or SCORM file.
\n
Can you please tell me why this is happening?
Hello Joe,
\n
If I'm understanding your article correctly, the accessible text is a feature that allows users to re-size text. However, when it is published, shouldn't it look just like it does in the preview? If not, then what is the point of the preview? Because you'll never know how your course will look to the learner, unless you are constantly re-publishing? And what about the chart that I sent a screen shot of that shows different font sizes on the chat?
Hello Joe,
\n
If I'm understanding your article correctly, the accessible text is a feature that allows users to re-size text. However, when it is published, shouldn't it look just like it does in the preview? If not, then what is the point of the preview? Because you'll never know how your course will look to the learner, unless you are constantly re-publishing? And what about the chart that I sent a screen shot of that shows different font sizes on the chat?
Yes, if you could, please keep me up to date if you find some useful information. I didn't try it with a \"properly\" translated xlf yet, but if even that wouldn't work then we might have a huge problem.
\n
From my understanding, there's 2 \"columns\" in an XLF file, the Source text and the Translated text. When you export, it would only fill the Source with your current text, and nothing in the Translated one, which is why it wouldn't work if you export then reimport.
I had contact with the support and importing a translated labelset should work. It doesn't matter if you export a built-in or a customized labelset for the translation. The important part is that you translate it using a tool that can work with XLIFF-files.
I didn't find out why my labelset doesn't work even though it was translated professionally, but it seems to be a problem with this specific translation and not a general problem.
\n
And you were right about the the manually translated labelsets: If you translate a labelset directly in Rise and export the file, it is not meant to be re-imported. So there is no direct way to give your labelset to someone else. I made a feature request and hope that this feature will be added- If you also want to make a feature request, here is the link: https://access.articulate.com/support/contact/feature-request.
