Error during project preparation, source: xlf

When trying to prepare a huge project with over 2,000 files I get this error message:

 

TBH I do not really understand what it is all about. This error appears also, if I switch off the validation in the XML file type. How can I process the customer files now? 40 files are affected :(

_________________________________________________________

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.

  • Hi Jerzy,

    Have you tried preparing the project in 2015 to work on it in 2017?

    If you've successfully worked with Epic xlf before in 2015 that might be the easy workaround?

    Or, if these are custom xlf files, have you tried exporting their filetype settings file from 2015 and importing into 2017?

    Just a few quick random ideas 'off the top of my head'...

    Ali :)

  • I did not work with S2015 on this project. And I tried to prepare directly in S2017. But S2015 has delivered the same error. Do you happen to know Epic xlf? Do you know, how to make the named-groups elements visible in Studio?

    _________________________________________________________

    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.

  • Hi Jerzy,

    I have worked on them but always in projects received as packages from an agency. I will contact a colleague who has just joined the beta team as she's project manager for the agency who prepare these projects based on custom .xlf files... Hopefully she'll be able to share further knowledge on this specialised subject from the project management perspective.

    All the best,
    Ali
  • Hi again Jerzy,

    My colleague does have a few suggestions for you, she'll post them shortly. I also wondered if you split the files into 2 projects, those that work OK in one and the 40 that generated Warnings in the other, maybe Studio would cope better. Nikki has further ideas on this so I'll let her explain in her post. I hope she can help!

    Ali :)
  • Hi Jerzy

    I think we have had similar issues before. I don't think we have managed to get to the bottom of it but have you tried the following already:

    Have you got a template in place with a specific file type? I have found that with certain specific XML file types, we have them saved in a template. For allowing this to work in 2017, I could not use the same template, but if I exported the settings, created a new Default template in 2017 and imported the settings, it worked. I don't think that is the issue here, but may be worth a try in case it helps.

    My other thoughts are:

    It may be due to the amount of files?

    Because there are so many files, have you tried splitting the files and setting up four projects each with 10 files for the problematic files?
    This isn’t ideal, but this has also worked for us in the past.

    Another thing is – how many TMs are being used? I think in the past, we have had three selected and at the initial stage of preparing the project, Studio did not like this, so we had to remove the TMs at preparation stage and add them one by one after, maybe even pre-translating each file individually/in small batches for very problematic jobs

    I hope these suggestions help a little. Without looking at the files and file types, I am not sure what else to suggest at this stage.

    Nikki
  • What astonishes me really... I tried the same files on my main PC - and they work there. So why does my older PC with freshly installed Studio 2017 and file types resetted not want to process the files, while my new one does?

    There is only one empty TM in the project. All files are XLF, so I use the default XLF file type in Studio. Now the analysis runs on my main PC and I will see, what results we get.

    _________________________________________________________

    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.

  • Amazing, isn't it! No matter how much we learn, how expert and logical we become, we can still be tripped up by a simple combination of software and hardware setup without any reasonable explanation. It's all down to electronic impulses, those 0's and 1's!

    I'm glad you've found a way to make it work!

    Enjoy the rest of your day,
    Ali
  • There was an answer by Jesse Good, which I cannot see here. But he raises the question of turning of the file verification against the standard - but on BOTH PCs the setting is exactly the same, verification is on. Still the one can and the other cannot. However, the one which can process the files has not yet finished the analysis, but reports 7 errors. Let's wait and see or as the Germans say, wait and drink tea :)

    _________________________________________________________

    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.

  • I saw Jesse's suggestion, good idea even if that wasn't it.
    Let's hope the errors don't stop your project from working.
    Otherwise, you could create a project/s with the files that do work and just open the xlf files in an xml editor and either translate them manually or save the text to .txt and then sdlxliff?
    Wait and drink tea - very suitable for the English too, they drink a lot of tea ;-))
  • Hi Jerzy,

    Yes, I deleted my post once I realized you already said

    This error appears also, if I switch off the validation in the XML file type

    I was still curious why it would work on one PC and not the other though.
    What version of Trados are you using on the main PC? Also, are both PCs fully connected to the internet?

1 2