• State Suggested Answer
  • Replies 18 replies
  • Answers 2 answers
  • Subscribers 435 subscribers
  • Views 6194 views
  • Users 0 members are here
Options
Related

Error during project preparation, source: xlf

Jerzy Czopik

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.

Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    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
Reply
  • 0
    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
Children
No Data