Hi Violeta,

I do think it may be related to language codes.  Studio takes the codes it supports from the operating system, so if you were to check in three different operating systems you would see different languages available to you.

However, it would be a good idea to tell us exactly what languages are in your project (main language and sub language, so en-GB or de-AT for example) and also take a look with a text editor and see what languages are in the XLIFF file you are working with.

It might also be helpful if you did attach the error message in full.  You can do that by saving the error message to your desktop and then attach that file (it's an xml file) to here:

Regards

Paul

Hi Paul. Thanks for your reply. The project languages are these:

source language: en-US

target language: es-LA

This happens with XLF files only.

I thought it was all about Windows 10, as I'd had no problem at all with xlf files in Windows 7 or 8. 

I attach details of the error message. 

My SDL Trados instructor does not know how to solve this issue and suggested my getting back to you for an answer. What shall I do?

Thanks in advance,

Violeta

<SDLErrorDetails time="15/04/2016 04:33:03 p.m.">
  <ErrorMessage>El idioma de destino detectado no coincide con el idioma esperado por el proyecto.</ErrorMessage>
  <Exception>
    <Type>Sdl.TranslationStudio.Api.TranslationStudioException, Sdl.TranslationStudio.Api, Version=11.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888</Type>
    <HelpLink />
    <Source>Sdl.TranslationStudio.Editor</Source>
    <HResult>-2146233088</HResult>
    <StackTrace><![CDATA[   en Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.ResolveLanguages(IMultiFileConverter converter)
   en Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.Load(IJobExecutionContext context)
   en Sdl.Desktop.Platform.Services.JobRequest.Execute(IJobExecutionContext context)
   en Sdl.Desktop.Platform.Implementation.Services.Job.<_worker_DoWork>b__3()
   en Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action)
   en Sdl.Desktop.Platform.Implementation.Services.Job._worker_DoWork(Object sender, DoWorkEventArgs e)
   en System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   en System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>11.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>11.2.4422.11</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home Single Language</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>3082</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>Viole\Violeta</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>VIOLE</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>8285464 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Hi Violet,

>target language: es-LA

I don't think es-LA is supported by Trados.

es-LA doesn't seem to be a valid code:

However Trados follows RFC 1766 and doesn't seem to have that code:

Hi Violet,

>target language: es-LA

I don't think es-LA is supported by Trados.

es-LA doesn't seem to be a valid code:

However Trados follows RFC 1766 and doesn't seem to have that code:

Hi Jesse

Thanks for your response.

I'm really lost.

es-LA is a valid Spanish variant in SDL Trados Studio 2014 Freelance version. It appears on the language list displayed when creating projects. In fact, we've been using it as the requested target language variant for other xlf projects we successfully handled on Windows 7 and Windows 8. The code for es-LA is actually es-419. God knows why. When turning in the TMs we open them in Notepad and replace the es-419 code by the es-LA variant requested by the customer. But that was no problem at all. I started having trouble "opening" the xlf files in SDL after installing Windows 10.

Again, this only happens with xlf files. I've had no trouble at all with Word or Excel files.

Below is the

<SDLErrorDetails time="15/04/2016 04:33:03 p.m.">
  <ErrorMessage>El idioma de destino detectado no coincide con el idioma esperado por el proyecto.</ErrorMessage>
  <Exception>
    <Type>Sdl.TranslationStudio.Api.TranslationStudioException, Sdl.TranslationStudio.Api, Version=11.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888</Type>
    <HelpLink />
    <Source>Sdl.TranslationStudio.Editor</Source>
    <HResult>-2146233088</HResult>
    <StackTrace><![CDATA[   en Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.ResolveLanguages(IMultiFileConverter converter)
   en Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.Load(IJobExecutionContext context)
   en Sdl.Desktop.Platform.Services.JobRequest.Execute(IJobExecutionContext context)
   en Sdl.Desktop.Platform.Implementation.Services.Job.<_worker_DoWork>b__3()
   en Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action)
   en Sdl.Desktop.Platform.Implementation.Services.Job._worker_DoWork(Object sender, DoWorkEventArgs e)
   en System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   en System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>11.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>11.2.4422.11</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home Single Language</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>3082</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>Viole\Violeta</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>VIOLE</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>8285464 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Thanks!!!

Violeta

Hi Paul,

These xlf files are are created by our client company in Marketo and are sent to us through a Cloud translation management company.

My client just selects the source and target languages to create the project in the Cloud company Workspace.

The source language has always been "en-US" and the target language, "es-LA", as we translate for the Latin American region.

I know that the Spanish code in Studio is es-419. All we have to do to upload the relevant TMs into the Workspace is to open the Notepad and replace the es-419 code by the es-LA variant requested by my customer. But this is just additional information, as it did not prevent us from opening the projects in Studio when using Windows 7 or 8. 

Now, I cannot open the same files in Windows 10.

I'd like to provide you with the xlf file, but cannot do it for confidentiality reasons.

I'm really lost. I'm not much of a techie and do not understand much about codes or technical matters. My only certainty is that this has to do with Windows 10, as I had no problem whatsoever in Windows 7 or 8.

Awaiting your comments.

Thanks for your help!!

Violeta

OK Paul.

I'll do it as soon as I can and I'll get back to you.

Thanks!!!!!

Violeta

XLF

source-language="en" target-language="es-la"

SDLPROJ

en-US Folder in Project: source-language="en" target-language="es-la"

es-419 Folder in Project: source-language="en-US" target-language="es-la"

Just a quick note to tell you that our customer has always created the projects in the same way and choosing the same language codes/variants. Again, no problems at all before Windows 10. In fact, I was able to open the files and complete the project in a desktop computer running Windows 7.

Thanks Paul!!!!!!!

Violeta

Hi Paul:

I'm trying to attach the "sdlproj" file but cannot post it. I get a warning that it's not a valid file extension to attach to this message. [:(] What shall I do?

Thanks in advance!!!

Violeta

Hi Paul,

Here's the zipped file (sdlproj).

Thanks!!

Violeta

CXInsider_sdlproj.zip