• State Suggested Answer
  • Replies 18 replies
  • Answers 2 answers
  • Subscribers 435 subscribers
  • Views 6207 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,

    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 :)
  • 0 in reply to Alison Field
    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.

  • 0 in reply to Jerzy Czopik
    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
  • 0 in reply to Jerzy Czopik
    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 :)
  • 0 in reply to Alison Field

    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.

  • 0 in reply to Jerzy Czopik
    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
  • 0 in reply to Alison Field
    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.

  • 0 in reply to Jerzy Czopik
    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 ;-))
  • 0 in reply to Jerzy Czopik

    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?
  • 0 in reply to Jesse Good
    Hi Jesse,

    It is interesting how software's performance can be different, even on two apparently identical computers. I remember when the agency I used to work for bought a batch of computers from the same local hardware house, all exactly the same make and spec, installed all on the same day with the same software yet they behaved differently and their Windows background settings were different from machine to machine before we did anything with them beyond plug them in and set them up. So it's not that strange that a product as wonderfully complex as SDL Studio should behave differently from one machine to another.

    I love the mystery of it all!
    Ali ;-))
  • 0 in reply to Jesse Good

    I tried again, after having updated the old PC (let's name it "Corsair", this is the network alias it uses) with the latest bells & whistles from Norton and MS Windows 10. This a i7 3500 machine. TM and the whole project are on a NAS. Studio is the current build 14.0.5746.0.

    And I got again the same error as above - some files are not recognized.

    The other PC (called "Spitfire") is a i7 6700k machine. It accesses the same NAS in my local network.

    Both Corsair and Spitfire have a full Internet connection. Both run Windows 10, both are protected with the same version of Norton AV. Studio was installed on both after having uninstalled the previous beta. The only difference is, that Spitfire has had the very latest beta, while on Corsair I had one of the first betas of 2017.

    Now Spitfire has finished the analysis and reported 7 errors - all were "Out of memory exceptions". So I think I will run the analysis again in the night, after a PC restart and with only Studio running there. So far we would have a basis for working.

    Now the next question:

    In customer files we have not only source and target, but also named groups elements. Here's an example:

        <trans-unit id='CAT.ALT.230.1.A' maxwidth='12' resname='ALT.230.1' restype='Category.Abbr' size-unit='x-characters'>

         <source>Overridden</source>

         <target>Overridden</target>

         <context-group name='Item Information'>

          <context context-type='x-info'>Category abbreviation in item [ALT-230-ALERT STATUS] for category title
           "Overridden". Item description: "alert status"</context>

          <context context-type='x-length'>12 characters</context>

         </context-group>

         <note>• INFO: Category abbreviation in item [ALT-230-ALERT STATUS] for category title "Overridden". Item description: "alert status" LENGTH:
          12 characters STRING ID: CAT.ALT.230.1.A</note>

        </trans-unit>

    We have to make sure, the translator can see this additional elements, while this elements do not need to be translated. Studio ignores these completely. When I would create a xml file type with only "target" as translatable item, could I declare this tags above as comments? Even if I know how to create a file type I do not yet know how to declare elements to be just comments in Stuido.

    _________________________________________________________

    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.

Reply
  • 0 in reply to Jesse Good

    I tried again, after having updated the old PC (let's name it "Corsair", this is the network alias it uses) with the latest bells & whistles from Norton and MS Windows 10. This a i7 3500 machine. TM and the whole project are on a NAS. Studio is the current build 14.0.5746.0.

    And I got again the same error as above - some files are not recognized.

    The other PC (called "Spitfire") is a i7 6700k machine. It accesses the same NAS in my local network.

    Both Corsair and Spitfire have a full Internet connection. Both run Windows 10, both are protected with the same version of Norton AV. Studio was installed on both after having uninstalled the previous beta. The only difference is, that Spitfire has had the very latest beta, while on Corsair I had one of the first betas of 2017.

    Now Spitfire has finished the analysis and reported 7 errors - all were "Out of memory exceptions". So I think I will run the analysis again in the night, after a PC restart and with only Studio running there. So far we would have a basis for working.

    Now the next question:

    In customer files we have not only source and target, but also named groups elements. Here's an example:

        <trans-unit id='CAT.ALT.230.1.A' maxwidth='12' resname='ALT.230.1' restype='Category.Abbr' size-unit='x-characters'>

         <source>Overridden</source>

         <target>Overridden</target>

         <context-group name='Item Information'>

          <context context-type='x-info'>Category abbreviation in item [ALT-230-ALERT STATUS] for category title
           "Overridden". Item description: "alert status"</context>

          <context context-type='x-length'>12 characters</context>

         </context-group>

         <note>• INFO: Category abbreviation in item [ALT-230-ALERT STATUS] for category title "Overridden". Item description: "alert status" LENGTH:
          12 characters STRING ID: CAT.ALT.230.1.A</note>

        </trans-unit>

    We have to make sure, the translator can see this additional elements, while this elements do not need to be translated. Studio ignores these completely. When I would create a xml file type with only "target" as translatable item, could I declare this tags above as comments? Even if I know how to create a file type I do not yet know how to declare elements to be just comments in Stuido.

    _________________________________________________________

    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.

Children
No Data