• 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

    Dear Boss Nob

    I tested your SDLXLIFF file and could not find any corruption. The file opens fine in Studio 2015 SR2 and the target document can be created without any problems.

    This means that the error is not inherent to the SDLXLIFF file itself but to the computer on which you got the error, the more as you say that it does not happen on another PC. It may be a configuration issue of your Studio installation. Maybe there is something wrong with your filetypes.

    Did you try to reset your Studio installation as described in workaround 2 of KB article 6225?

    Regards

    Walter
Reply Children
  • 0 in reply to Walter Blaser
    Hello, Walter,

    Unfortunately, my 30-days trial SDL Trados licence has expired.
    So I cannot check out your recommendations.
    The situation is not so simple.
    If to assume that the problem is in my OS incompatibility,
    how to explain the fact that any other large files are processed OK
    at the same computer and OS? Only THIS file is nor processed.
    It is interesting that SDL KB
    (see kb.sdl.com/
    explains this error ("enumeration alreday finished") because the "source file has AutoText entries".
    I checked out this my source file and found no AutoText entries.
    So, the KB explanation is not correct.
    Resuming, I may say that I consider existing SDL Trados Studio software
    as unfinished and it cannot be purchased at its exisiting state.
    Thanks for your help.
  • 0 in reply to Boss Nob

    Unknown said:
    Hello, Walter,

    Resuming, I may say that I consider existing SDL Trados Studio software
    as unfinished and it cannot be purchased at its exisiting state.

    Do you know any software on the market that works flawlessly in all possible situations, with all sorts of files, on any PC, with all versions of operating systems .....?

    It is virtually impossible to test all possible configurations and there will always be some particular situations that cause the software to fail. Your situation is one of those because the same file you have problems with works fine on at least two other PCs.

    The software works fine for thousands of people who use it daily without problems. And when a problem does appear, there is help as you just experienced on this forum. So, in my opinion, this makes the software "very usable" in its "existing state".

    Please think about this.

    Walter
  • 0 in reply to Walter Blaser
    Hello, Walter
    My opinion is that software developer must thoroughly test its SW on many platforms and file types prior requesting money for it. This product has a lot of flaws and not fully tested by the SW developer.
    I have the evidences of poor performance of this SW, not only for this specific error. In particular, SDL Trados badly converts WORD files back to the original format - namely, the resulting format is not the same as the original. It brings a lot of problems, because you have to correct resulting format manually.
    In short - the product is unfinished and cannot be purchased.