Layout issue with numbers
I've translated a course using the Localization feature from English to Spanish & Portuguese and I've noticed a layout issue with numbers that I wouldn't expect. We have a series of shapes with numbers to create an ordered list. When this is translated, scroll bars are added to each number (see attachments). The text size, margins, spacing, and line spacing are all the same when I compare with the original, but for a scroll bar is being added even though nothing is being translated. How would we prevent this when using Localization?Erratic behavior after our network drive moved
Hello, I need an advice from someone who knows more about how Storyline works, than I do. :) First of all: I've already read, it's a bad idea to work on a storyline file on a network drive, but I didn't read that in time and in our organization that's how we usually work. It worked pretty well for quite a long time and we only noticed some objects moving a tiny little bit once in a while, but nothing that really concerned us. Well, a few weeks ago our servers moved and since then we only can add audiofiles from the local hard drive and no longer from the network drive, objects moved a lot while opening the file on the server and we noticed several other kinds of "erratic behavior", we can't explain. My question: Is it possible to "repair" the file by only opening it on the local hard drive from now on and making changes there until all observable erratic behavior is gone? Or is the file "broken" and (new) erratic behavior will occur/persist? Thanks for your advice! ElkeStoryline 360 "Export to Word (Legacy Mode)"
For Storyline 360, we use "Export to Word (Legacy Mode)" for translation. (We cannot use the Enhanced Word Translation because of the multiple text string splits for formatting such as font size. color, etc.) We are worried that the Legacy Mode option may be retired at some point. We would like to know if there are any plans in the foreseeable future to remove the option to use the legacy Word translation workflow?Localization Layout Issues
Hello! I'm playing around with the localization feature for a course that we will be revamping in the future. I did the translation into Kiswahili and Spanish, and it came up with some layout issues. 99% of the issues are that scrollbars have been added as the languages translated to use more words than English. However, when I try to adjust the text box size to accommodate, it doesn't allow me to extend it down, only horizontally which doesn't fit with the layout on many of the slides. I included a video to demonstrate. Any ideas?Articulate Localization - Shrink Text on Overflow Bug
Hi all, Articulate Localization is a dream come true that my team and I have been waiting for for years. We are however running into an issue/bug in Storyline 360 with 'shrinking text on overflow' Currently we use the settings you see below. The text of each box is 'wrapped' and if there is too much text the size of the text automatically decreases. This functionality is essential, because it allows you to easily manage multiple translations because if there is too much text then the text simply slinks a little bit to still fit in the box. As a result you don't need to make ridiculously large boxes for lengthy languages like Ukrainian and Bulgarian (these versions of the training then simply have text that has smaller font). However, Articulate Storyline 360 breaks this functionality when there are multiple translations. Here is the Ukrainian Translation for example: As you can see, suddenly, scrollbars have appeared. This should not be possible but it still happened, if you Publish or Preview the Project the scrollbars are still visible. Therefore, our trial of Articulation Localization has come to a very short end because we cannot use this for our clients if the text of each text box does not shrink in other languages other than the source language. Is anyone else experiencing this bug and/or can this bug be resolved so we can use this feature as well. Secondly, when using Upgraded Project Text the option to 'Shrink text on Overflow' disappears whilst this feature is 100% necessary for running multiple translations in the same Storyline file. Japanese uses about 50% of the space Bulgarian uses, so making huge text boxes for everything just because there are languages that need a lot of room means there is also a lot of empty space on other languages. In short, it's MUCH better if Storyline simply reduces the font size of these languages so you don't need to leave insane amounts of room. We are excited about Articulate Localization, but it needs to work perfectly in Storyline 360, because we (on average) would like to have twenty languages running in one file. Best regards. Kaj DekkersLocalization and AI Audio
Hi I've posted another comment regarding localization not translating the AI audio and a solution was offered to put the script in the Notes. Yes if I do that the script is translated but if I add the script to the AI audio dialogue box, not only does it change the script in the translated version but also the english version. Thankfully I noticed that before I got through the entire course but what a huge pain. Clearly I need to detach the english and translated version but that too is a pain because if any changes are made to one verison, I need to make sure I go into the other language and update it too.Localization and audio files
We have a library of courses in British English, with voiceovers recorded by a voice artist. Obviously this isn't ideal when translating using the localization feature (which seems great so far otherwise). We have courses in both Rise and Storyline - Does anybody know of a way to edit the different language versions separately so that the audio can be changed independently?Latin American Language - Translate
I have several courses written in Latin American Spanish. However, when I try to use the new Translate functionality, it does not recognize it as the Source Language and always appears as American (English). The other two Spanish options are: European (Spanish) and Mexico (Spanish). Is there any way to consider adding Latin American (Spanish)?
