I've just exported an xliff for translation from Storyline. For pre translation testing reasons, I tried to
import it in commonly used translation tool (memoQ), where I set up a project with
source language English and target language Dutch.
I could not import the xliff, a message appeared that the target language of
the xliff did not correspond to the target language of the project in the translation tool (Dutch).
When examining the xliff in a text editor, I saw indeed that
the target language of the xliff file was German. Of course, this can be easily
changed to the desired target language, but I just wondered if I can change the
default target language somewhere in Articulate before exporting the xliff?
it seems like this is also not solved in Storyline 2 Update 9, right? What amazes me is that in Storyline 2 are 5 languages for authoring supportet. So the author designed a german content in a german Verison of storyline 2, but if the author export the xliff the source-language is still "en"! Our transaltion agency does have problems with the Xliff File because of that.
This is still not a set up with in Storyline - and although the UI language can be changed that doesn't have an impact on the content on the slide. I know you've asked a few other translation questions recently, if you need additional help it may be easier to ask them all at once to our Support engineers.
We don't have a public facing bug database or feature request process, and we're unable to share timelines about when or if particular elements will be included in future updates so I can't say anything for certain in regards to this behavior. Currently it's not deemed as a bug by our team by as a feature request, hence Adrian's earlier statement to submit thoughts on that feature here.
Thank you for the response. I don't understand why it is not listed as a bug. It is a function in Storyline which is not working as it should, so it has to be declared as a bug. A feature request only would make sense if there is no XLIFF Option in Storyline.
Thanks Evelyn and it looks like you sent in the feature request and a case for the other forum discussion we were communicating in. I'm following along in that one as well, so I'll be sure to share any additional updates in that forum discussion too.
7 Replies
Hi E.,
Welcome to Heroes! Currently, this isn't possible. It would make a nice feature request though.
-Adrian
Hi Adrian,
it seems like this is also not solved in Storyline 2 Update 9, right? What amazes me is that in Storyline 2 are 5 languages for authoring supportet. So the author designed a german content in a german Verison of storyline 2, but if the author export the xliff the source-language is still "en"! Our transaltion agency does have problems with the Xliff File because of that.
Thanks for response
HI Evelyn,
This is still not a set up with in Storyline - and although the UI language can be changed that doesn't have an impact on the content on the slide. I know you've asked a few other translation questions recently, if you need additional help it may be easier to ask them all at once to our Support engineers.
Hi Ashley,
I think it is also important for other users to see what happens with this bug. That might help other users to make decisions.
Hi Evelyn,
We don't have a public facing bug database or feature request process, and we're unable to share timelines about when or if particular elements will be included in future updates so I can't say anything for certain in regards to this behavior. Currently it's not deemed as a bug by our team by as a feature request, hence Adrian's earlier statement to submit thoughts on that feature here.
Hello Ashley
Thank you for the response. I don't understand why it is not listed as a bug. It is a function in Storyline which is not working as it should, so it has to be declared as a bug. A feature request only would make sense if there is no XLIFF Option in Storyline.
Thanks Evelyn and it looks like you sent in the feature request and a case for the other forum discussion we were communicating in. I'm following along in that one as well, so I'll be sure to share any additional updates in that forum discussion too.
This discussion is closed. You can start a new discussion or contact Articulate Support.