Auto save temporary files are not purged


Auto save temporary files are not purged even after you exit Studio 2014.
They are in
c:\users\<user>\appdata\local\temp\, and must be deleted manually.
I'm using Windows 7 64bit.
There are copies for all auto save points.
This eats up the disk space quickly especially if you open multiple files as one and have large temp files.

Parents
  • Hi Yuji,

    I've never come across this before, and my auto-save files are not in this location.  They should be here (copied from the online help)

    Location of your AutoSaved documents

    When the AutoSave interval that you specified is reached, Studio creates AutoSaved versions of the *.sdlxliff files which contain pending changes and puts them in the AutoSave folder, located at the same place where you save your project data. The default location for your Studio project data is the My Documents area.

    I wonder if these temp files are something else?  Maybe you have some backup software running that's getting a bit carried away?

    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

  • Thank you, Paul. Could you try by opening multiple files as one (Quickmerge)?
    File names like tmpB901.tmp should be found in the location.
  • Hi Yuji,

    I see what you mean now... I have the same thing.  I guess it's simple enough to remove these on a regular basis, but I agree with you that they should not be stored here permanently.  I'll report this to development.

    However, there is a very interesting side effect to this one which I'm really pleased you have brought to my attention!  If you add .sdlxlif to the end of the file name then you can now open this as a standalone SDLXLIFF that contains the virtually merged files.  This is something many users would like to be able to do!  It would make it possible to quickly merge files, take the file and add it to your project, work on it to update your TM and then pretranslate the original files.

    In my quick test it even allowed me to save the target files but I wouldn't rely on this completely.

    So a very interesting and positive side effect to what you see as a problem.

    Thank you

    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 Yuji,

    I see what you mean now... I have the same thing.  I guess it's simple enough to remove these on a regular basis, but I agree with you that they should not be stored here permanently.  I'll report this to development.

    However, there is a very interesting side effect to this one which I'm really pleased you have brought to my attention!  If you add .sdlxlif to the end of the file name then you can now open this as a standalone SDLXLIFF that contains the virtually merged files.  This is something many users would like to be able to do!  It would make it possible to quickly merge files, take the file and add it to your project, work on it to update your TM and then pretranslate the original files.

    In my quick test it even allowed me to save the target files but I wouldn't rely on this completely.

    So a very interesting and positive side effect to what you see as a problem.

    Thank you

    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