Translate Single Document not working in case of Serbian (Latin/Cyrillic, Serbia and Montenegro (Former)) missing in Studio 2015 (windows 10)

Hello everybody,

This topic is related to the one described here. As already mentioned, there's no problem with Studio recognizing those files within a project package.



However, opening a single document via "Translate Single Document" or double-click is impossible. The following error occurs:


Moreover, after double clicking the file, the language selection drop-down lists are non-responsive (they are frozen):



The only thing to do is press OK or Cancel. After pressing OK, the error report is as follows:

<SDLErrorDetails time="3/28/2017 2:04:41 PM">
  <ErrorMessage>The detected target language does not match that expected by the project.</ErrorMessage>
  <Exception>
    <Type>Sdl.TranslationStudio.Api.TranslationStudioException, Sdl.TranslationStudio.Api, Version=12.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888</Type>
    <HelpLink />
    <Source>Sdl.TranslationStudio.Editor</Source>
    <HResult>-2146233088</HResult>
    <StackTrace><![CDATA[   at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.ResolveLanguages(IMultiFileConverter converter)
   at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.Load(IJobExecutionContext context)
   at Sdl.Desktop.Platform.Services.JobRequest.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>12.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>12.3.5262.0</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1250</CodePage>
    <LoggedOnUser>DESKTOP-PH835QQ\Dragana</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>DESKTOP-PH835QQ</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>3977600 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>


My 5 languages in Freelance SR3 edition are: English, Croatian, Macedonian and Serbian - I intentionally selected Serbian Latin Serbia and Serbian Latin Montenegro as separate languages to see whether the problem would be solved, but that didn't work.

Is there a workaround to this problem (anything in the registry I could do or any Studio or Windows settings to adjust)?

EDIT: This problem applies to Studio SR2 as well in Windows 10. There were no problems with it whatsoever in Windows 7. Moreover, this issue affects creating new TM's for the mentioned SR variants (which means SR-Latn-CS and SR-Cyrl-CS cannot be crated). As this is not a problem concerning Studio thanks to Any TM option, it affects projects in e.g. Passolo 2011 where (as far as I know) there is no option to recognize TM's with different language variants ("Accept translation memories that only match the general language pair" option).

 

Dragana

Parents Reply Children
  • Hi Paul,

    Great! I use Notepad++ as the text editor for the issue in this thread because it has an option to open multiple files at once (each in a separate tab) and the option "Replace All in All Open Documents". The software is also helpful in creating sr-Latn-CS/sr-Cyrl-CS TMs. As there is no Serbia and Montenegro (Former) language variant in a drop-down list, I create a new sr-Latn-RS/sr-Cyrl-RS TM (when I need to use it in Passolo 2011 which doesn't have the option to recognize TM's with language variants other than those in translation files). Then, I open the TM via Notepad++ and replace all instances of RS with CS. However, to avoid conflicts within Studio, one has to either clear the Translation Memories list in Translation Memories View or rename the converted TM. And voila! The new CS TM is ready for work or TMX import and works perfectly as Studio has no trouble in recognizing it.

    Dragana
  • Thanks Dragana... nice editing tool. I use EditPadPro which had similar functionality. Definitely a good idea to have a decent text editor in this profession and Notepad++ is a good choice.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub