• State Suggested Answer
  • Replies 11 replies
  • Answers 3 answers
  • Subscribers 434 subscribers
  • Views 5261 views
  • Users 0 members are here
Options
Related

Studio 2017 Folders

Paul Davis

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.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    Oh, this is NOT random. It just depends on how you start the translation. If you use the single file approach (previously called "Translate single document"), then the target translation is in the folder for "Drop files", however when you create a project, the target file goes to the target language folder within the project folder.
    The "Drop files" folder is always used, when you use the Drag&Drop process.
    To avoid this, just start the translation using "Create new project" button. This way you can decide, where the files will go.
    But nothing happens randomly.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • 0 in reply to Jerzy Czopik
    Wouldn't it be WAY more intuitive if the target files originating from drag&drop would go to the ORIGINAL LOCATION of the source files?!
    I believe that drag&drop operation passes the full paths of the files to the receiving object, so there should not be any serious obstacles to do it that way.
    The current "solution" has all signs of yet another programmer-designed UX :-\
  • 0 in reply to Evzen Polenka
    Not really - or dou you want your target file to overwrite the source?
    TBH, I do not use Drag&Drop, as I follow a strict procedure of creating projects for ALL my jobs in my personal folder structure.
    The problem with Studio is, that it is also used by people, who seem not even to understand what is folder structure. And as SDL has to satisfy us all, they developed several ways of working in Studio. The folder Drag&Drop is created to prevent problems with such people - at least IMO. Many user have cried to have default folders for Studio - as would they not be able to control their folders on their own. So now you can say a big thank you to many (IMO far too many) translators, who are computer illiterates. Due their problems with creating folders and managing them now we have so many ways of working with Studio...

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • 0 in reply to Evzen Polenka

    Unknown said:
    Wouldn't it be WAY more intuitive if the target files originating from drag&drop would go to the ORIGINAL LOCATION of the source files?!

    Actually I agree with Evzen here if you use the single document approach.  Also worth noting that if you use the single document approach without the drag and drop then that's exactly what happens.  I don't know why we changed this to use a drop files folder where I think you end up with quite a smorgasbord of files.  Most likely it wasn't a programmer designed solution though... more likely an effort to ensure the files were all put in a location where they could be found as this is one the problems many new users using the single document approach  identified as a source of confusion.

    But I think creating projects is always a better solution and the drag and drop makes this quite easy now, especially if you use project templates.

    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

  • 0 in reply to Jerzy Czopik

    Unknown said:
    Not really - or dou you want your target file to overwrite the source?

    It won't be overwritten, target files are placed into language-tag subfolders.
  • 0 in reply to Paul

    Unknown said:
    I don't know why we changed this to use a drop files folder where I think you end up with quite a smorgasbord of files.  Most likely it wasn't a programmer designed solution though...

    To be honest, from my perspective, whoever designed/programmed the drag&drop "feature" was, uhm, how to say it politely enough... not very educated in computers...
    Why on Earth do we need the latest Internet Explorer for drag&drop to work?!?!?!?! What does it have to do with GENERIC drag&drop ability of ANY piece of modern software?!?!?!

    To me the entire thing looks like some elementary-school-level homework, sorry...
  • 0 in reply to Evzen Polenka
    In single document approach, if you use the command "Open document" at least, the file will of course be overwritten. The SDXLIFF file is then located in exactly the same folder as the source file. So logically the target will be stored in the same folder too - and as it keeps the same name as the source, the source will be overwritten.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • 0 in reply to Jerzy Czopik

    Unknown said:
    In single document approach, if you use the command "Open document" at least, the file will of course be overwritten. The SDXLIFF file is then located in exactly the same folder as the source file. So logically the target will be stored in the same folder too - and as it keeps the same name as the source, the source will be overwritten.

     
    True, unless you use Shift-F12 and change the name, something I think most users working with this approach do.  But I'm with you on this Jerzy and think projects are the way to go for a more consistent way to work.

    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

  • 0 in reply to Paul
    Dear Paul
    You may already know that - I use "Single document" approach only for testing. In "real life" I use ONLY the project approach, and this also with no "Drag & Drop" via the Home page of Studio, but the "classical" way. And this way is just perfect. My only wish would be, that Studio shall keep the size of the project wizard window not only within the session, but also between the sessions.
    And I do not use SHIFT+F12, it is F12 in my case - exactly the same as in Word, where it says "Save as...".
    Best regards, Jerzy

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.