• State Suggested Answer
  • Replies 9 replies
  • Answers 2 answers
  • Subscribers 432 subscribers
  • Views 3514 views
  • Users 0 members are here
Options
Related

Severe SDL Trados Studio 2015 flaws

Boss Nob

       The flaw is that SDL Trados Studio 2015 SR2 (12.2.5087.4) takes into processing
corrupted *.sdlxliff files without alerting it. It is very bad.
SW have to check the input *.sdlxliff file(s) rigorously prior to take it into operation. It does not do it. As a result: translator translates the *.sdlxliff file OK, but cannot save it in the original format (*.docx), so the huge work
is appeared to be performed for nothing and for free. Errors of *.sdlxliff files are described in the SDL KB ("enumeration already finished" and "object reference does not point to the object instance") - both errors require source *.docx files which often are not available for the translator. Developers: how to fix these SDL Trados Studio severe flaws? A? ( ....silence.....as usual...)
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Unknown said:
    The flaw is that SDL Trados Studio 2015 SR2 (12.2.5087.4) takes into processing corrupted *.sdlxliff files without alerting it. It is very bad.

    Hello Mr Nob,

    Thank you for posting into the SDL Community with your concerns.  I echo your wishes in that it would be brilliant if the software could identify when it was going to fail.  But in all fairness to the development team, I think the performance hit we would have to take in order to check whether an sdlxliff file had corrupted in such a way that it prevented certain operations you may not even wish to tackle yet (such as saving the target file) would outweigh the benefits.  It's simple enough to test a file before you start work with just a simple keyboard shortcut.

    What might be more helpful would be if we were able to reproduce the problems reported so we can work on preventing them from occurring in the first place.  Perhaps this might be possible if you were to ask your client as this would obviously benefit them too?

    It's very difficult to fix problems, or even be able to build something into the software to detect them, if we don't know what causes it in the first place.  For this we need examples, and then we are very willing to take a look.  There may even be better ways of preparing files that can avoid some issues, but again we would need to see the problems in the first place.

    I hope this makes sense... I am trying to be helpful.

    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

  • 0 in reply to Paul
    Hello, Paul
    Yes, I can submit 1 example with an error description.
    Here are links to *.sdlxliff file (9.3.docx.sdlxliff)
    yadi.sk/.../g7NsJhGFqvvHr
    and corresponding error report file ( generated by SDL Trados Suite 2015):
    yadi.sk/.../msRh7VL_qvvHn
    This 9.3.docx.sdlxliff was taken by the SDL as an OK file and it did not alert it as a bad file.
    But it cannot save it as *.docx (Shift-F12)
    F8 shows "No Errors".
    Solve this puzzle (if you can).
  • 0 in reply to Boss Nob

    Hello Boss,

    Thank you for this test file.  Unfortunately I can't reproduce the error and if I open this sdlxliff and save target it works.

    t_9.3.docx

    This does present a couple of things worth trying though as I don't know whether you used this file in your project as part of a package, or a standard project, or whether you used the single document approach to work on the file.  So perhaps you can test this for me:

    • Use the single document approach on this file alone.  So just open the sdlxliff as a new single file project and immediately see whether you can save the target.  So don't even save it, just open it up and save target.

    If this works then can you explain how you created your original project so I can follow the steps and see if I can reproduce the same problem?

    It may also be associated with your Russian operating system... maybe something in there is conflicting for us.  It wouldn't be the first time that we have seen a problem that only occurs in one or more languages of the operating system.  So the more information we can glean the better.

    But so far, I don't have a problem with your sdlxliff file so in a way this is good.  This means the problem is related to your environment and even this helps us to narrow it down a little.

    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

  • 0 in reply to Paul
    Hello, Paul,
    Thanks for your help. I use this file as a single file translation. None of your recommendations helped.
    The project file is created automatically by the SDL.
    Meanwhile, I've also made an experiment.
    I have another computer that is also running by Windows-7, Russian,
    but it is 32-bit - and at that computer - this error did not occur (like at your side), so, I found out that this error occurs on the same operating system, but the 64-bit (Windows-7, 64-bit).
    Another difference: on that computer where the error occurs, installed MS-Office 2007, and on another where the error does not occur,- MS-Office-2010 - may this be the cause of the error?
    It is clear that the error is purely system incompatibility type.
    But in any case, it is a SDL Trados flaw - it must be able to adapt to any OS and environment. Both my OS-s are licensed and permanently updated.
    I think that you will not reproduce this error - there is something incompatible with the operating system. But no program at this my computer and OS did not complain on it so far. SDL-Trados - is the first.
    So, my solution is - to keep working at my another computer where this error does not occur. But it is not a good solution, if to be honest.
Reply
  • 0 in reply to Paul
    Hello, Paul,
    Thanks for your help. I use this file as a single file translation. None of your recommendations helped.
    The project file is created automatically by the SDL.
    Meanwhile, I've also made an experiment.
    I have another computer that is also running by Windows-7, Russian,
    but it is 32-bit - and at that computer - this error did not occur (like at your side), so, I found out that this error occurs on the same operating system, but the 64-bit (Windows-7, 64-bit).
    Another difference: on that computer where the error occurs, installed MS-Office 2007, and on another where the error does not occur,- MS-Office-2010 - may this be the cause of the error?
    It is clear that the error is purely system incompatibility type.
    But in any case, it is a SDL Trados flaw - it must be able to adapt to any OS and environment. Both my OS-s are licensed and permanently updated.
    I think that you will not reproduce this error - there is something incompatible with the operating system. But no program at this my computer and OS did not complain on it so far. SDL-Trados - is the first.
    So, my solution is - to keep working at my another computer where this error does not occur. But it is not a good solution, if to be honest.
Children
  • 0 in reply to Boss Nob
    Hello Boss,

    Interesting observations. I'm actually running W8.1 64-bit machine with Office 2016. I think we can test a few scenarios around this and see whether we can reproduce the problem so the information you have provided is useful. It's not always helpful to compare SDL Trados with other applications because often problems occur because of the level of integration with other applications and operating systems. Studio is quite heavily invested into your operating system using more of the native resources than many other applications, but of course this doesn't matter, it should still work. At least it should work for all supported systems and applications, so W7 64-bit with Office 2007 in Russian should work... I think.

    I'll ask the team to test this one and see what we can reproduce.

    Thank you for your efforts.

    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