Forum Discussion
Translating entire Storyline files with an alternative method
Great dialogue everyone! As we're all looking from the outside in, I think we're getting to the same realization - the holdup for the approach we're taking (all sound very similar) to function reliably is the inability to convince Storyline to either refresh its internal cache, generate a new ID to match the replaced file, or a combination of both.
We know the functionality is within Storyline as it occurs in the Media library or simply right clicking the file and choosing replace audio. However, this is manual and isn't a good solution when you have a course of any significant length.
Manuel, 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.
Thor
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 BERRI
Thor Melicher
Manuel, 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...
