Forum Discussion
Translating entire Storyline files with an alternative method
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.
Related Content
- 1 year ago
- 10 years ago