Detecting language please wait for.......
Quite bad issue - a customer has send me an "old fashioned" project with physically merged files. The customer does so for all colleagues, who are still on 2011, so this will not change, as no one will create separate projects for different translators.
Now I cannot open the files within this project as virtual merge - but that is necessary due to many repetitions between files. When I take the files out of the project, I can open them, but not save, the corresponding error message has been forwarded to support. It reads:
<SDLErrorDetails time="3/16/2016 4:32:57 PM"> <ErrorMessage>Argument '0' is out of range. It should be between 1 and 2147483647.Parameter name: ChildFileDocuments.Count</ErrorMessage> <Exception> <Type>System.ArgumentOutOfRangeException, mscorlib, Version=184.108.40.206, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type> <ParamName>ChildFileDocuments.Count</ParamName> <HelpLink /> <Source>Sdl.Desktop.Platform</Source> <HResult>-2146233086</HResult> <StackTrace><![CDATA[ at Sdl.Desktop.Platform.Validation.WithinRange(Int32 argument, Int32 lowerBound, Int32 upperBound, String name) at Sdl.TranslationStudio.Api.Common.MergedFileChildrenPersister.SaveChildFilesDocuments() at Sdl.TranslationStudio.Api.Common.MergedFileChildrenPersister.SaveChildFiles(String outputFile, String bilingualFilePaths) at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.SaveBilingualImpl(String bilingualFilePaths, Boolean copy, IJobExecutionContext context, Boolean isAutoSaved) at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.Save(IJobExecutionContext context) at Sdl.TranslationStudio.Api.Editor.AbstractInternalDocument.SaveJobRequest.Execute(IJobExecutionContext context) at Sdl.Desktop.Platform.Implementation.Services.Job.<_worker_DoWork>b__3() at Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action) at Sdl.Desktop.Platform.Implementation.Services.Job._worker_DoWork(Object sender, DoWorkEventArgs e) at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e) at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)]]></StackTrace> </Exception> <Environment> <ProductName>SDL Trados Studio</ProductName> <ProductVersion>220.127.116.11</ProductVersion> <EntryAssemblyFileVersion>12.2.5087.4</EntryAssemblyFileVersion> <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem> <ServicePack>NULL</ServicePack> <OperatingSystemLanguage>1031</OperatingSystemLanguage> <CodePage>1252</CodePage> <LoggedOnUser>AzureAD\JerzyCzopik</LoggedOnUser> <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork> <ComputerName>SPITFIRE</ComputerName> <ConnectedToNetwork>True</ConnectedToNetwork> <PhysicalMemory>25103188 MB</PhysicalMemory> </Environment></SDLErrorDetails>
Why is this so? IMHO this is a productivity killer, which I have not supposed to find in Studio...
I see this correspondence is quite old, but it has now resurfaced for me with Trados Studio 2019 SR2 - 18.104.22.1685.
I can open the sdlxliff files I have been sent (which consists of many small xml files), but cannot save them, and get the error message described in this article.
Has any progress been made to find a solution to this problem. Apparently, it is not very common, because I could not find anything even remotely related in the knowledge base.
Hello Jon Kittilsen ,
I have checked our logs and this issue is indeed very rare. This is even the first ever case I can see to do with Studio 2019.
Unfortunately so far there has not been a proper solution to this.
This has been logged under the internal CRQ-5898)
If you have been updating the TM as you work, maybe you can take the sdlxliff file and pretranslate through the TM?
This is the only workaround that i can see.
Thank you for the reply. I "solved" it by getting original xml files from the client. The pretranslation solution wouldn't have worked, as the problem I had was that I was unable to save the files I was working on.
Hi Jon Kittilsen ,
Thanks for letting me know.