Howdy!

project.RunAutomaticTask(fileGuid, AutomaticTaskTemplateIds.GenerateTargetTranslations)

With "project" being a FileBasedProject and fileGuid being an Array of target file Guids.

Note: Here the files will always be saved to the Studio target ISO folder. Would this do or do you need to specify an output path?

Hi Hoon Kim (HoonKim) ,

You are referring to the "SaveProjectFileAs" method right? I saw in my notifications that you suggested that, even if I cannot see that response appear in this thread now.

That method - as the name suggests - saves the _project_ file, not the resulting target file. So by saving it as .docx, you are actually not saving as .docx but just renaming the sdlxliff to docx, which _ruins_ the file.

As for specifying another path: you can't. What you _can do though is using the target file's language ISO code to determine the folder in your studio project and then use "File.Copy" method to copy the resulting target file to your desired location.

Example:

var studioFolder = Path.GetDirectoryName(project.FilePath);
var filName = Path.GetFileName(tFile.LocalFilePath);
if (Path.GetExtension(filName) == ".sdlxliff")
    filName = Path.GetFileNameWithoutExtension(tFile.LocalFilePath);

var pathFrom = Path.Combine(studioFolder, tFile.Language.IsoAbbreviation, filName);
var pathTo = Path.Combine(destinationFolder, filName);
File.Copy(pathFrom, pathTo, true);

Tristen Tan: I'll take a look at that import problem later and see what I find.

Best,

Andreas

I was and, still, am sticking to 'Save Target As' (shortcut key "Shif F12") as the topic of this post.
So, I've expected your code works like that.
Your recent explanation is different from that.

That's OK. That has its own functionality, though I'm not interested in at all.

-I was deeply surprised and embarrassed, when your code ruind both my real projects irrevocably.

Thanks.

You should look at running the ExportFiles automatic task, it does what you want.

And you should always check the API documentation to properly understand what is the code going to do before trying it out. It helps to prevent surprises...

You think the 'Document' is perfect.
You should always happy.
Good Luck.

(Ah, I'm happy with 'Shift F12')

Yet, the GenerateTargetTranslations task can't change the ENCODING of the exported target language. This is causing big issues for me. The encoding of the target native file can only be changed with the "Save target as" UI dialog. It would be nice to be able to invoke this dialog using the C# API.