When importing a translated document/version of the project, the system imports the document successfully, as usual. But in this particular case, the language of the course does not change after the import - the translated sentences does not substitute the original sentences, that is.
How can the import be successful when the translation does not work?
Based on your screenshot, it looks like you're doing a translation in Storyline. The first thing I recommend is looking at your translated XLIFF file (.xlf). You can open this in Notepad but it's a bit difficult to read as everything is one continuous line.
To help yourself out, you can make a copy of the file and change the extension from .XLF to .XML and then drag it into a browser (MS Edge, Chrome, Firefox, etc.)
You should see something like this:
The part that seems to cause the most problems is <target>. If this is missing and the translation is done in <source> then on import the translation will not be loaded as it's looking for the <target> items.
If you're doing this by hand then you have to match the <target> to the <source>. This is a difficult and tedious approach. Any mistake along the way will result in import errors.
Here's a better example of the <source> and <target> matching:
There are several options available to help with this - I have an automated solution that also does translations but I'm not allowed by forum rules to promote it as there's a small fee associated with it.
Please search 'translation' in the forums here to find what else users are doing here in the community.
I hope this helps give you some insights. I've also seen the forum moderators indicate that you can send your XLIFF file to their team to be routed to someone who can help, too.
The translated file is .docx format, as when exported from Articulate Storyline, and not XLIFF.
When importing the translated .docx-file into the course, all is "successful", but as mentioned above, nothing changes regarding to the text that should be translated.
3 Replies
Hello Jens -
Based on your screenshot, it looks like you're doing a translation in Storyline. The first thing I recommend is looking at your translated XLIFF file (.xlf). You can open this in Notepad but it's a bit difficult to read as everything is one continuous line.
To help yourself out, you can make a copy of the file and change the extension from .XLF to .XML and then drag it into a browser (MS Edge, Chrome, Firefox, etc.)
You should see something like this:
The part that seems to cause the most problems is <target>. If this is missing and the translation is done in <source> then on import the translation will not be loaded as it's looking for the <target> items.
If you're doing this by hand then you have to match the <target> to the <source>. This is a difficult and tedious approach. Any mistake along the way will result in import errors.
Here's a better example of the <source> and <target> matching:
There are several options available to help with this - I have an automated solution that also does translations but I'm not allowed by forum rules to promote it as there's a small fee associated with it.
Please search 'translation' in the forums here to find what else users are doing here in the community.
I hope this helps give you some insights. I've also seen the forum moderators indicate that you can send your XLIFF file to their team to be routed to someone who can help, too.
Good luck!
Hi,
The translated file is .docx format, as when exported from Articulate Storyline, and not XLIFF.
When importing the translated .docx-file into the course, all is "successful", but as mentioned above, nothing changes regarding to the text that should be translated.
Hi, Jens.
Thank you for opening a support case!
I see you're working with John Carlo, so you're in great hands! Please reach out through the case if you have additional questions.