Studio 2017 Folders

I have noticed that since using Studio 2017, when I finish translating a document and I click on ‘Batch Tasks’, ‘Finalise’, the target text is automatically saved under a different location than where the original text is.
This doesn’t happen all the time, but is rather random. The missing target document together with the XDL XLIFF file and the SDL Trados Studio Project File go to a created folder in my C: drive (C/Users/XXX/documents/Studio 2017/Projects/DropFiles). How can I prevent this from happening? I don’t remember having to select a folder destination to save my files in previous versions of Studio as they used to automatically be saved wherever the original file for translation was.

  • Re: do you want your target file to overwrite the source

    This is the least worrying problem. First, I always make a copy before proceeding with translation. Second, you always can add 2 or 3 letters at the end of your file name (target lang for example). Not a problem at all provided that you are computer literate enough.

    On the other hand, when adding different files to same project (unlike you, I prefer to avoid creating a new project each time – why at all?), I don't need new settings for each new file, and it takes time and HD space to 'create projects for ALL jobs' as you mentioned. I am far from computer illiteracy, I just value my precious time.

    Further, I don't want to clog my computer with new folders (often empty or needless/not worthy of creating). Just imagine: you have hundreds of identical project folders (BackupByRetrofit, en-GB, Reports, Retrofit, ru-RU, Tm, *sdlproj, whatever else?). You hardly need them all for one translation, not to mention that you forget about them once you are done, but they will still occupy their 5 MB on your hard drive. Multiply it by dozens (or hundreds?) of new translation tasks/projects. As to me, I have only one set of project folders – searching for destination folder is still better for me than passing all the steps to create a new project.

    Ok, if they cannot arrange 'Create Project' pattern in the way it works for 'Drag&Drop' in terms of saving target (to the same path as source), then why can't they at least use time saving ‘save as’ pattern (as in case of 'Save Copy As') for 'Save Target As' too?

    I am sure, as a tech-savvy user you can easily catch the difference: