Not Considering

This is not a feature request, nor it is a bug.

Please let trados studio be able to handle the sdlxliff documents created by previous version of trados studio.

Please let trados studio be able to handle the sdlxliff documents created by previous version of trados studio.

We received some documents created by other partners. After we finished the translation, we try to generate the target translation, but we received error report like this and can not continue the translation work.

 

 

Besides, when we try to verify the document with the "verify" in "review" of trados stuido, we received error report like this.

 

We are frustrated about this. Could you please tell me what is the cause for this unexpected error? Can you fix the bugs?

Besides, in some articles,  I found that this might be due to the sdlxliff documents created by early or previous version of trados studio. However, It is necessary for the latest version of trados studio can handle all the sdlxliff documents created by early or previous version of trados studio such as trados studio 2015 or earlier version.

Just imagine, if a translation company working with trados studio has survive for more than 10 years, they even can not handle the previous sdlxliff documents created in the past with different versions of trados studio.

Even today, the Microsoft office 365 with the latest version or all the Microsoft office version can handle the old version of word 2003 document. Will each version of trados studios be useful for only several years?

jack zhong
Parents

  • I don't believe this is a bug.  The problem is the sdlxliff was created using a version of Trados Studio that was too old so the appropriate settings required for that version are not available for you.  To fix this would require all the older versions of the filetypes to be installed on every version of Trados Studio which is not practical, and in some cases not even going to be possible.  You can always work with the sdlxliff files, you will just not be able to save the target files, or carry out some QA tasks.

    I think the most appropriate solution if we can't fully support older filetypes is to at least suppress the errors as they are meaningless.  You can still QA more important tasks around the translation itself.

  • in reply to Paul

    Dear Mr. PAUL,

    Thank you for your reply, but the error can not be suppressed. if I cotinue to click the next step, trados studio will show something like this, which means we can not generate the target translation with the old sdlxliff documents. So how are we going to deal with all the previous sdlxliff  documents stored in the computer for future reference or modification. 

Comment
  • in reply to Paul

    Dear Mr. PAUL,

    Thank you for your reply, but the error can not be suppressed. if I cotinue to click the next step, trados studio will show something like this, which means we can not generate the target translation with the old sdlxliff documents. So how are we going to deal with all the previous sdlxliff  documents stored in the computer for future reference or modification. 

Children
  • in reply to jack zhong

     

    I was referring to us using this solution not you!  The solution for you is to not even try to save the target file if it's clear yo don't have the correct filetype.

    To use previous sdlxliff documents for future reference you put them in a TM, or use them for Perfect Match.

  • in reply to Paul

    Dear Mr Paul. 

    1. To use previous sdlxliff documents for future reference you put them in a TM, or use them for Perfect Match.

    sdlxliff documents are also frequently used among the split translation for different translators, which requires the editing just on sdlxliff document without the presence of TM or perfect match. 

    Beside, TM can not keep all the tags in the sdlxliff document expecially after the exporting and importing process with TMX document.

    2.I was referring to us using this solution not you!  The solution for you is to not even try to save the target file if it's clear yo don't have the correct filetype.

    suppressing the error and allowing the translation work to continue might be a solution not only in this problem but also in many error case with trados studio. you can allow the trados studio to continue with all the necessary process to the final step of geting the target translation, and trados should be able to leave some  marks on the translated document so we can check what happen on that area.

    However, the better way is to allow the new version of trados studio to be compatible with all kind of sdlxliff documents

    Can you expect the solution in trados 2024?

  • in reply to jack zhong

    Let's step back and see what is the problem.

    You get SDL XLIFF which was created by file type discontinued years ago - meaning the SDLXLIFF file was created in very old version of Studio (pre 2019 I would guess).

    You can translate this file, you can use all your Studio resources, all will be fine - there are 2 exceptions - you cannot save as target and you cannot preview this file. 

    The reason you cannot save this SDL XLIFF as target is that it was created by file type which doesn't exist in your version of Studio.

    Nevertheless, after you finish your translation job, you will return the SDLXLIFF file to whoever sent it to you - and they can save as target with no problem.

    When opening such SDLXLIFF file, you will get notified that the file type used to created doesn't exist in your Studio version and what actions you cannot perform.

    There seems to be slight problem as if you use "Finish" batch task, you get the error you reported instead clearer instructions - tagging   for review.