File export: Trados does not use chosen path but another path used before

Hello,

when I export files and I chose during the batch task the export path to whatever path (I tried different, existing ones) , the export goes always to the same fixed path I used the first time I exported files in this project.

Also any change to the version I want to export is not reflected, it exports always the current version of a file, not for instance the target file when I highlighted a file in .sdlxliff format and tried to export the target language version.

In other words: Changes to the settings during the export process are not working, although they get saved and can be seen the next time. But Trados just does not use them but a prior, fixed version of the settings.

Maybe some problem with broken project settings (I had a Trados crash a couple of days ago in this very project)?

*

This is Trados Studio Freelance 2022 with latest updates/SR on Windows 11 with all latest updates.

I re-started Trados, re-booted the machine - no change.

*

Thanks in advance for any ideas!

Best regards,

Jens Olaf



Typo
[edited by: Jens Olaf Koch at 10:42 AM (GMT 1) on 28 Oct 2022]
emoji
  •   

    Hope you are well. Is this still something that isn't working as you would expect?
    I assume you are talking about generating target files?

    There was an issue when the path was copied using copy paste, and not browsing for a new location, but it was fixed in Studio 2022 CU1

    Lyds

    Lydia Simplicio | 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

    emoji
  •  

    Yes, same effect still: When generating target files I can neither choose the output directory nor the file version. The batch processing always uses a prior setting (= old directory, prior old selected version).

    The same is true for new projects: Whatever I want to use, it sticks to the fixed output settings which I cannot change anymore whatsoever.

    Very odd and annoying.

    emoji
  •  

    For the sake of clarity please allow for me to confirm what we do support:

    1.  Export Files

    This is managed as part of:

    • default settings (File - Options) and would be a fixed location
    • project templates - could be a custom location based on project template definition 

    Regardless of it allows you to specify a path: 

    Trados Studio options menu showing Export Files settings with file path and version dropdown menu.

    2. Generate Target Files

    This comes as part of Batch Task processing or simply "File - Save Target As"
    The general rule is it saves the target native file in the project location. 

    Trados Studio batch tasks menu with Generate Target Translations option highlighted.

    With all of this in mind, the only flexibility I see is if you are using the Export option.
    Please can you confirm? 

    The only other bit of flexibility I am aware of is that with 2022, there is an issue whereby you have Project A active in project view. You are working on Project B in editor view.
    But when you are calling up certain features, it's not relevant to Project B as expected. In fact its Project A, as that is what is active in project view.

    This may explain your impression of 

    Maybe some problem with broken project settings

    If the latter proves to be true, then I am pleased to let you know that as of CU5 - this conflict of active project will be fixed.

    I hope this helps clarify some points by which we can progress your post

    Lyds

    Lydia Simplicio | 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

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 9:15 AM (GMT 0) on 29 Feb 2024]
  • Well, there is only one project A open, not two projects A and B.

    I will try again to explain what happens...

    1. I have this file, it is a .sdlxliff file, no target file.

    Screenshot showing a .sdlxliff file named 'author_bio.html.sdlxliff' with a warning icon in Trados Studio.

    2. I have these project settings with the path ending with "04. Export aus Trados" and version set ti "current".

    Screenshot of Trados Studio project settings with the export path ending in '04. Export aus Trados' and file version set to 'current'.

    3. Then I export the file with the command from, the batch taks:

    Screenshot of Trados Studio batch tasks dropdown menu with 'Export files' option highlighted.

    04. I export with these setting, exporting to a TARGET file, not the current version.

    Screenshot of Trados Studio batch processing settings with export path ending in '04. Export aus Trados' and file version set to 'Target version'.

    05. I end up with a file exported to the WRONG path ending "xx. Export aus Trados" (instead of "04. Export aus Trados" and the WRONG format (still .sdlxliff but not target file).

    Screenshot of a file explorer window showing an exported .sdlxliff file in the wrong path 'xx. Export aus Trados' instead of the intended '04. Export aus Trados'.

    *

    This is clearly not what to expect and seems unrelated to the project A/B bug being corrected in upcoming CU5.

    Plainly said: I still cannot export to the path I want nor to the file format I want, and it doesn't matter whether I set my intended path and file format in the project settings or during the batch task – it always uses settings that I used ONCE before in this project. That is what I mean with: prior settings of the same project seem to stuck somewhere and cannot be overwritten anymore.

    This is a serious problem.

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 9:15 AM (GMT 0) on 29 Feb 2024]
  • Really no solution??

    I now work on another project (book translation) and can STILL NOT CHANGE the target path for exports!!

    Even if I delete the "stuck" path Trados always uses, it recreates it - no matter what I enter as correct export path. That means that NO export is ever written to the path I specify!

    There must be a solution, right?

    Please - help! :-)

    *

    I think that is either a bug or something is corrupted in a project settings file. Maybe I can edit them manually?

    OK, I checked and find the current export settings in my .sdlproj file. They show the CORRECT path:

    <SettingsGroup Id="ExportFilesSettings">
      <Setting Id="ExportLocation">F:\Kunden\O'Reilly\07 - Learning TypeScript\Textversionen\98. Export aus Trados</Setting>
    </SettingsGroup>

    Then why does Trados alwaysuses a DIFFERENT path?

    emoji
  • Okay, after some digging I found the solution:

    In the project batch settings for the current language pair was the wrong path. And although I changed that manually when exporting files, Trados always chose the path from the settings - which should not be the case.

    So from my view it's clearly a bug. You just cannot offer the option to change the path while exporting when you are going to ignore that and use the one from the settings.

    emoji