Once more error message while reconverting XLIFF back to Word 97-2003

Hello,

again I have the same problem as before when I try to reconvert a big XLIFF to Word, I get the error message "Sdl.FileTypeSupport.Framework.Adapter.Framework1.Writer". The last time it was due to a missing field tag, but I already checked all tags and cannot find the one that blocks. Could there be another reason why I cannot reconvert the file? The file was corrected in the correct mode and afterwards I accepted or rejected the changes...

Thanks for helping me out!

Susanne

Parents
  • Hi Susanne,

    Are you able to open the Word file using the single file project workflow and immediately save the target, so before you even translated it? If you can do this then the problem is related to something that occurred during the translation, either by Studio or by you. If you can't then the problem is with the file and we'd need to get to bottom of this by seeing your source file.

    However, if it did open and save then try pre-translating it immediately from your TM and then save the target. This may help if the problem was caused by Studio.

    You seem to get a lot of these problems, so I wonder if you have some aggressive anti-virus software, or a disk cleanup utility running that is corrupting the temp files while Studio is running? Just a thought and maybe worth checking.

    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

  • Hi Paul,

    I checked my anti-virus software or cleaner utility but the problem is not related to that.

    As stated the problem is often linked with the mix up of languages in the final word document.
    This error message error message "Sdl.FileTypeSupport.Framework.Adapter.Framework1.Writer" is still persisting and present even if I create a new project. The same problem occurs when I try to reconvert the XLIFF into Word from a different computer, so that it is something that happened to the XLIFFs during the translation process.

    I'm wondering if it could be related to one of the following:
    - Recently my operating system was updated automatically to Windows 10 Home
    - The automatic save function saves the files every 10 minutes
    - When I tried to work on the XLIFFs from another computer I had often the error message "depending file not found". Could this be the source?

    I also have a formatting problem: The figures are numbered as follows: 5.10, 5.11, etc. - Trados converts the format always to 05:10, 05:11, etc. How can I avoid this?

    I really don't know how to resolve this persisting error.

    Thanky you for your help.

    Susanne
  • Hi Susanne,

    Apologies for the late response... I was out my office yesterday and today so didn't get to everything I needed to.

    On the problem with saving files.

    Unknown said:
    When I tried to work on the XLIFFs from another computer I had often the error message "depending file not found". Could this be the source?

    Not the source of the error you reported.  Rather this is just information.  If you work on an sdlxliff by copying it from your other machine, and if the source file was too large to get embedded into the sdlxliff, then you will always see this message.  Doesn't stop you working on the file, but will stop you being able to save target etc. unless you can get a copy of the source to reference.  You could try increasing the value for this so larger files can be embedded but then you might find things get a little sluggish as the sdlxliff grows too large.  But if you want to try it's in here:

    Unknown said:
    I also have a formatting problem: The figures are numbered as follows: 5.10, 5.11, etc. - Trados converts the format always to 05:10, 05:11, etc. How can I avoid this?

    Go to the specific language pair and change the autosubstitution settings.  It looks as though Stydio sees your source numbers as a time:

    The other solution of course is to just let Studio do what it wants at the end search & replace across the project using regex.  Sometimes this is the best way to work with Studio so you take advantage of how it wants to work, without any errors in the number transposition, and then fix them at the end.

    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

Reply
  • Hi Susanne,

    Apologies for the late response... I was out my office yesterday and today so didn't get to everything I needed to.

    On the problem with saving files.

    Unknown said:
    When I tried to work on the XLIFFs from another computer I had often the error message "depending file not found". Could this be the source?

    Not the source of the error you reported.  Rather this is just information.  If you work on an sdlxliff by copying it from your other machine, and if the source file was too large to get embedded into the sdlxliff, then you will always see this message.  Doesn't stop you working on the file, but will stop you being able to save target etc. unless you can get a copy of the source to reference.  You could try increasing the value for this so larger files can be embedded but then you might find things get a little sluggish as the sdlxliff grows too large.  But if you want to try it's in here:

    Unknown said:
    I also have a formatting problem: The figures are numbered as follows: 5.10, 5.11, etc. - Trados converts the format always to 05:10, 05:11, etc. How can I avoid this?

    Go to the specific language pair and change the autosubstitution settings.  It looks as though Stydio sees your source numbers as a time:

    The other solution of course is to just let Studio do what it wants at the end search & replace across the project using regex.  Sometimes this is the best way to work with Studio so you take advantage of how it wants to work, without any errors in the number transposition, and then fix them at the end.

    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

Children
  • Hi Paul,

    Thank you for your answer. I can image that you have a flood of new support inquiries coming in each day...

    I'm not sure if I understood your explanation regarding the too large source file. Indeed, the initial Word files which I converted in Studio are very big as they contain a lot of figures, graphs, etc. Would it help to send only the original Word source file to the other workplace in order to avoid the above mentioned error message "depending file not found"? Or must I send the whole project file?

    What I'm even more concerned about is my "old" problem with the error message when I try to reconvert the XLIFF back to Word. I have this problem now with 3 files of the book I'm actually translating (there are 16 chapters in total). And the last time I tried to fix it as you suggested above with the single file workflow it did not work... I'm really about to despair. Would it help if you take a look at one of these files?

    Regards

    Susanne