RTF conteneur file type can't be found... and the exported files can't be opened

Hello everyone.

I have several RTF files to translate, and I can't change the file format. I prepared a package with Studio 2017 SR1 and sent it to a translator. When he makes changes in the target, saves everything and prepares the return package, he gets several errors, the main one being the advertisement message: "the conteneur file type for FRT 2.0.0.0 can't be found". When I open his return package, I can export the files, but I can't open them in any RTF application (Word for instance).

Can you please help on this?

Thanks a million in advance, and kind regards,

Guillaume

  • Hi ,

    The message your translator gets is probably because he's using an older version of Studio to you that doesn not contain this version of the RTF filetype. So he can translate the file, but he can't save the target , use quick inserts (not that that's a bad thing!) etc. You should be able to open the file after generating it however.

    Perhaps you can import the contents of the sdlxliff he returned to a TM, then create a new project yourself and pretranslate the files. See if this helps you to recover the RTF files.

    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

  • Thank you Paul.

    It appeared that this translator used a cracked version of Trados (I didn't know it was possible).

    I managed to work with another one, who has SDL Trados 2017 SR1 Freelance Edition (I have 2017 SR1 Professional). We do not have this error message anymore.

    But Word can't open the target files I have saved from her return package, saying that the files are corrupt. I do not know how to solve this. I can't start this big project knowing that I will not be able to get the target files.

    Thanks for your help.
    Kind regards,
    Guillaume
  • Unknown said:
    It appeared that this translator used a cracked version of Trados

    The error has absolutely nothing to do with cracked Studio.
    As Paul pointed out, it's caused by missing "RTF v 2.0.0.0" file type, which was newly introduced only in the very last update for Studio 2017 SR1 release: https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0027380

    In other words, using the cutting-edge latest updates is pretty unfortunate for cooperation with "wider translators' audience"... simply because there is (and always was and always will be) quite a number of user who deliberately do not - and will not, until "it's worth it" and risk-free! - use the very-very-very latest updates, mainly due to number of problems and incompatibilities they cause.

    As the release notes say, the latest RTF filetype v 2.0.0.0 works differently from the previous one - it does not use Microsoft Office's components for reading/writing the RTF format, i.e. it's likely that the problems you describe (that you cannto open the generated files in Word) are caused precisely by using this newest file type.

    Regarding your "what to do" question - first, is it really absolutely necessary to use RTF? Can't you use some other format like Word, etc.?
    If RTF is a must, then you may consider uninstalling the latest update (CU8) to get back the previous RTF v1.0.0.0 file type and try with that one.

  • Thank you very much Even for your detailed answer.

    Once I could see that I was unable to open in Word the RTF target files from my own package, I decided to convert all the files into .DOCX and to re-create the package. The problem is solved, then.

    However, I feel disappointed to understand that I will not be able in the future to open in Word the files Studio saved into RTF.

    Thanks again anyway, and kind regards.