Forum Discussion
Translating entire Storyline files with an alternative method
Sure. I am away until the end of the month, but I will definitely try to keep you posted if I am provided with some useful information from Articulate support.
Manuel BERRIThor MelicherManuel, please keep us up to date on what you hear back from Articulate, that is if you're able to share :). I think your two files illustrate the problem well and with our sharing of what we're seeing may lead to a viable solution for everyone.
Sure. I am away until the end of the month, but I will definitely try to keep you posted if I am provided with some useful information from Articulate support.
Hi everyone,
Finally back to work, and back to this annoying issue.
I received a standard answer from Articulate support :
"[...]it appears that your process of translating your courses isn't using the standard procedure of exporting the XLIFF file or Word file, and you're modifying the content of the published output. Articulate software and its published output are supported as they are. I'm sorry, but modifying the published output isn't something we are equipped to handle, and we don't offer advice on it so that it will work in a specific environment.[...]"
This was not a surprise, really. But still, this is a disappointment.
So I guess we have to find our own way to solving this. Any idea where this "internal cache is located, anyone ?
Quite interesting discussion. Although i donot use it for translation at times i dove into Storyline360 inners dark secrets. As you unzip a .story file and open up all files there you can find all IDs and change them. I used that to dynamically create default starting templates from Google Sheets as a base setup.
When changing things changes are your .story files wont work anymore when zipping them up back again and change the extension back to .story , but it might give a clue to how to solve your issues.I am searching the "mysterious" not (???) local cache
with a normal local publish to web with storyline 360 (C:\Users\...) "articulate 360 Desktop Services" communicates with 2 amazon aws services
example
- ec2-52-45-64-241.compute-1.amazon.aws.com (Ashburn, Virginia, United States)
- ec2-44-196-72-199.compute.1.amazon.aws.com (Ashburn, Virginia, United States)@ariculate: why are my (european) data with local publish copied to us amazon cloud ???
Really hope this aint true... else all Articulate tools get banned from EU-governmental and university use im afraid...
if this turns out to be true and not just a short-term routing error - storyline will unfortunately no longer be usable in europe
articulate has to stop copy (user ???) data to the cloud, when publishing NOT to the cloud
I see no problems with review 360, because i do not need to use the server - for review I use our own company server
Hi Jürgen,
But Storyline uses AWS anyway when generating the audio from the TTS content (Amazon Polly is the name of the API)...
Still I am wondering: is this mysterious cache file that we cannot locate on a distant Amazon server? It could be the answer. To validate this hypothesis, we could try to publish again a .story file that has been already puslished and has not been changed while putting the local computer offline. Thus we could ensure no external communication is necessary, and that no external cache file is needed.
I cannot do this at the moment, but feel free to precede me if you can.
