Storyline 3 error with translation imports
May 08, 2018
SL3 won't let me import a translated xliff file. As soon as I click the file to import, an error reporting box pops up. Here is the text in the "provide more information" link:
<?xml version="1.0" encoding="utf-16"?>
<ErrorReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<FirstName />
<LastName />
<EmailAddress>bmjenson@amazon.com</EmailAddress>
<MachineName>SEA-1800030315</MachineName>
<HardwareId>WF3LU-AUFL6-UAX2R-WQ9RP-1TV9U</HardwareId>
<Message>An item with the same key has already been added.</Message>
<StackTrace> at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 comparer)
at anw.pw(String A_0, anc A_1, IEnumerable`1 A_2)
at Articulate.Globalization.TranslationProvider.a(IList`1 A_0, String A_1)
at Articulate.Globalization.TranslationProvider.f()
at Articulate.Globalization.TranslationProvider.a(Object A_0, EventArgs A_1)
at Articulate.Globalization.TranslationImportResult.OnShown(EventArgs e)
at System.Windows.Forms.Form.CallShownEvent()
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()</StackTrace>
</ErrorReport>
5 Replies
Hi, Betsy – thanks for reaching out!
Sorry you're running into this roadblock – we're here to help! I see you also submitted a support case, in which my colleague, Chino, has been assigned to your case. In the meantime, would you be able to share your .XLIFF file with him using your unique, private upload link?
Thank you, and keep an eye out for an email from support@articulate.com shortly! ☺️
Hello,
did you find a solution, or the source of th error?
Thank you.
Welcome, Martin! I'm really sorry you're getting stuck, too. I'd love to continue to help here!
We weren't able to get a copy of that particular XLIFF file to test; however, I saw you're working closely with my teammate, Renz. Looks like he isolated the issue to something in the file – e.g. a missing header column, a translated variable.
We'd like to keep digging, though! Have you had a chance to run another export and compare the original file with your translated one?
Pro-tips on translating content here!
Hello Katie,
we had a previous (and working, means importable) version of the translated file, and we compared it with the new one (the faulty one you had from us).
We think that something in the XML.Structure of the newer translated XLF-File was wrong, because we couldn't open it in a XLIFF-Viewer.
Thank you very much!
Best regards
Martin
Really appreciate you keeping us in the loop, Martin! I shared this update with Renz, and we're both standing by if you need anything else!
P.S. Looks like you may have replied via email in which your contact information came through. No worries, as this Peek video will show you how to edit it out!
This discussion is closed. You can start a new discussion or contact Articulate Support.