Unable to open xlf files in Windows 10 with SDL Trados Studio 2014 Freelance

I've recently updated to Windows 10 and now I'm unable to open xlf files in SDL Trados Studio 2014. I get an error that reads: "The identified target language does not match the expected project language". I know it has nothing to do with language codes, as I've had no problem opening the same files in a Windows 7 and Windows 8 PC. Any help?

I attach error message. Thanks in advance!!!!

Parents
  • 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

    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

  • 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 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

    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

  • 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!

    I think I got it now!! If there's any trouble, I'll let you know.

    thanks for your time and support!!!!!

    Violeta

  • Paul: I have the same problem as Violet. After upgrading to Windows 10 Trados 2015 started sending me the error of not recognizing the source language. I even tried files I had succesfully worked on in the past and could not open them either. I followed your suggestion of opening the file as a single file and noticed the source language said: Not set. Is there any way I can fix this? I do not want to open all my projects as single files from now on.
    Thank you for all your help.
  • Who is creating the files? I mean the person, who gives you the files is responsible for the file settings.
    Windows (neither 10 nor any other version) will interfere with the content of any file, which is not a system one. And XLF files are NOT Windows system files. So it is really unlikely the upgrade of Windows has something to do with this phenomenon...

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • Somehow it does cause this phenomenon since I tried an old file, right from my computer, which I had succesfully worked on in February and the same exact thing happened. I agree, it is really strange. Any way to set the source language in Trados when opening a file via "New Project"? It was nice I was able to set it when opening the file as a single file, but it is a long process to open the file. Love to use my templates.
  • Jerzy, I do think the error is due to upgrading to Windows 10. In fact, I had no trouble whatsoever opening XLF files when I worked on either Windows 7 or Windows 8 (I did that for over 1 year). The error messages started when I upgraded to Windows 10. I contacted Paul, who helped me a great deal and suggested two ways to work on this type of files: either as single documents (setting the target language, in my case) or saving the single document and then opening it as a New Project.

    The single document procedure worked fine, but the second one didn't. And, as well as Patricia, I always prefer and need to work files as projects rather than single documents.
    Paul, any ideas why I was unable to take your second option?
    Thanks!!
    Violeta
  • I understand it happens, but I fail to see the connection...
    But left that aside, you can simply search & replace the language codes in your files, or at least this is what I would do.
    There is a lot of software allowing S&R in files, but the most easy way, as you can even record a macro there, would be for me Notepad++. You can open all files in it, then run a S&R for all files, where the language codes would be set properly.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • Do you know how can the languages be set as single files but not as new projects? I would hope there is a way. How about uninstalling Trados and reinstalling it again? Would that be a solution? This cannot be happening just to Violeta and me. S&R sounds like a long procedure, or at least an extra one when we get lots of files with little time to deliver.
Reply Children