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 Violeta,

ok, so your project file is using this:

TargetLanguageCode="es-419" SourceLanguageCode="en-US"

es-419 is the correct code for Spanish (Latin America), so your xliff needs to have this same code to work in this project.  If you open an xliff as a single file project that has the code es-LA the  it won't be recognised and you'll get this:

Note the target language is "(optional)".  This is because it's not recognised and Studio will allow you to set any language you like.  You'll get warning messages but it won't prevent you from saving the file.

However, if you create a project then this is different and you won't be able add a file to an existing project because the languages are already set, and your file won't match.

So you have to change the codes in the xliff to match the recognised codes.

Regards

Paul

Paul,

Is this a problem with Windows 10? Because it does not explain why I was able to open those same files in Windows 7 or 8. Will this be fixed by SDL?

Additionally, we are sent those files by a cloud translation management company which does not support the es-419 code. This is going to be a problem as I have to create projects to send them back both the translated xlf and the tmx. 

Thanks!

Kind regards,

Violeta

Unknown said:

Is this a problem with Windows 10? Because it does not explain why I was able to open those same files in Windows 7 or 8.

Hello Violeta,

I don't have W10 and I can't open them either. At least I can't open the file I fabricated to match what you say you are getting from your client.  It would be immensely helpful if you provided two things:

1. A file you have opened successfully when you were using W7 or W8

2. The file you are trying to open now

It feels too much like guesswork at the moment and since I can't open the file I made up in any version of Studio and without using W10 I doubt we have the full story here.

Regards

Pau

Hi Paul

I can send you the following:

1) the sdlproj file I tried to open in a Windows 10 laptop

2) the same sdlproj file I successfully opened and completed in a Windows 7 PC

3) A prior sdlproj file I worked on a Windows 7 equipment.

If so, I'll do it as soon as I get access to the PC at my office.

Pls confirm if this is ok. 

I appreciate the effort and time you are taking in trying to work this out for me.

Thanks!!!

Violeta

Hi Violeta,

This won't really help me.  Can't you provide the XLIFF files?  Even if you edit them so I only have the header it would help.  You can delete the entire contents of the file apart from the header and one Translation Unit,  also replace the translatable text in there with anything you like.  Just so I'm getting the same type of file as you.

If you can do this I need to see one that worked for you earlier and the one that doesn't work now.

For example, like this.  Just edit your files to get me the header and one TU (trans-unit)... but it must be edited versions of the actual files you're working with:

Regards

Paul

OK Paul. We'll have our technical support guy do that for you, as I don't think I know how to do it properly. We've been using SDL Studio for 2 years only, mainly with Word and Excel files, which are ok, even when the target language code specified by our customer is still es-LA.

This is happening only with XLF files

I'll get back to you with what you need as soon as I can.

Thanks again!!!!!

Violeta

Hi Paul!

I'm sorry for taking so much time to get back to you. I understand what you requested from me, but as I am not 100% proficient in using the SDL tool yet, I do not know how to edit the files as per your request. So I asked our Trados instructor to help us out with your request. He has only gotten back to me with the following. Does it work? If not, I'll keep trying to deliver the files as you requested.

This is a file I was unable to open in Windows 10. However, I was able to translate it in Windows 7 from in a PC

<?xml version="1.0" encoding="UTF-8"?>

<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:okp="okapi-framework:xliff-extensions" xmlns:its="http://www.w3.org/2005/11/its" xmlns:itsxlf="http://www.w3.org/ns/its-xliff/" its:version="2.0">

<file original="CX Insider April 2016" source-language="en" target-language="es-la" datatype="x-text/html+plain">

<body>

Thanks!!

Violeta

Hi Violeta,

This works without a problem.  If I use the single document process when I first open the file the target language is not recognised, as expected:

So I can manually change the target language to whatever I want and it opens like this:

I am getting messages telling me the languages are not correct and not validating, but I can ignore them.  I can still translate the file and save the target.

If I create a project with en(US) - es(LA) and add this file then it just works.  I can translate and save the target.

As long as I don't change any settings that might "correct" the language code then the target file is exactly the same as the source, only translated.

Regards

Paul

Hi Paul!

Thanks for your reply. It seems clear to me.

However, I do not know how to use the "single document" process. So far, I've always created "projects", at least that's what I learned from my instructor here.

Can you walk me through the single document process so that I can create the relevant project after that?

Is this an issue with Windows 10 then?

I greatly appreciate your help!!!!

Violeta

Hi Paul!

Thanks for your reply. It seems clear to me.

However, I do not know how to use the "single document" process. So far, I've always created "projects", at least that's what I learned from my instructor here.

Can you walk me through the single document process so that I can create the relevant project after that?

Is this an issue with Windows 10 then?

I greatly appreciate your help!!!!

Violeta