• State Verified Answer
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 393 subscribers
  • Views 780 views
  • Users 0 members are here
Options
Related

Programmatically Pre-translate a Project with Language Weaver as a MT resource

Mark Owens

Hi,

Got a strange one here.

I have a C# program that creates a project via a template, adds source files and pre-translates using the relevant Language pair resources specified in the project template.

The code works perfectly with any project templates that have:

  • A translation memory
  • And/or have a DeepL plugin

I have created a new template that uses Cloud-based resources (Language Weaver with the correct language pair, using Generic - NMT).

I run same program (no code changes) and it creates the project, adds the source files and runs through the code to do the pre-translate.

But, when I manually open the created project it has not done the pre-translate.

I can manually do a pre-translate and it does use LW to perform MT. 

Is there anything wrong with the code below that's stopping the PT?

Here's the method that does the PT:

internal void PreTranslateFilesMT(int minimumrate)
{

if (newProject != null)
{
    Console.WriteLine("START MT PreTranslateFiles with memory enabled");

    Console.WriteLine("Setting project minimum pre-translate match to {0}", minimumrate);
    var settings = newProject.GetSettings();
    var preTranslateSettings = settings.GetSettingsGroup<TranslateTaskSettings>();
    preTranslateSettings.NoTranslationMemoryMatchFoundAction.Value = NoTranslationMemoryMatchFoundAction.ApplyAutomatedTranslation;
    preTranslateSettings.MinimumMatchScore.Value = minimumrate;
    newProject.UpdateSettings(settings);
    newProject.Save();
    var targetFiles = newProject.GetTargetLanguageFiles();

    newProject.RunAutomaticTasks(targetFiles.GetIds(), new[]
    {
        AutomaticTaskTemplateIds.PreTranslateFiles,
    });
    newProject.Save();
    Console.WriteLine("END MT PreTranslateFiles with memory enabled");
}
else
    Console.WriteLine("NULL new project!");

}

Thanks

Mark
Rate translation
×
Suggest better translation
×
Parents
  • 0
    Thank you for bringing this to our attention. Our development team will review it in the context of our ongoing projects and priorities. Your understanding and patience as we assess this matter is appreciated. We have recorded the issue in our tracking system under the reference number CRQ-39797
  • 0 in reply to Community Jira

     

    Hi,

    I'm not sure whether you want a separate ticket for this but a similar problem occurs when creating packages for a project containing Cloud-based resources...

    The scenario is:

    1. Create a project using my normal project create API program. (As stated above, it does not do a pre-translate if Cloud-based resources are used).
    2. Open the project using Trados interactively.
    3. Run a pre-translate. This does work and provides lots of NMT translations.
    4. Close the project.
    5. Run my normal Trados package create program. This has always worked before. This time it fails.
    6. I open the project using Trados interactively.
    7. Remove the Cloud-based resource entry from the project.
    8. Close the project.
    9. Run my normal Trados package create program. It works.

    Yet again, having a project with Cloud-based resources is causing problems in API programs that do not happen when running interactively.

    1.             bool packageIsCreated = false;
            while (!packageIsCreated)
            {
                Console.WriteLine("{0}", projectPackage.Status);
                switch (projectPackage.Status)
                {
                    case PackageStatus.Cancelling:
                    case PackageStatus.InProgress:
                    case PackageStatus.Scheduled:
                    case PackageStatus.NotStarted:
                        packageIsCreated = false;
                        break;
                    case PackageStatus.Cancelled:
                    case PackageStatus.Completed:
                    case PackageStatus.Failed:
                    case PackageStatus.Invalid:
                        packageIsCreated = true;
                        break;
                    default:
                        break;
                }
            }

            if (projectPackage.Status != PackageStatus.Completed)
            {
                Console.WriteLine("Package problem: {0}", projectPackage.Status);
                throw new Exception("A problem occurred during package creation.");
            }
  • 0 in reply to Mark Owens

    Hey , we are working on providing a sample project that will help developers understand the requirements when working with LC projects/resources from project automation environment.

    What you're missing in your project is potentially the credentials, incl token, API key... that are needed in this case.  We'll circle back to you once we have completed the sample project that should help provide you the information you need to adapt your source code.
  • 0 in reply to Patrick Andrew Hartnett

    Interesting!

    I did have to supply credentials and API key when I coded the DeepL usage. That was because I did not include that info in the project template.

    With the LC coding, I did include the credentials and API key in the project template so my assumption was any project created from the template would automatically use those bits of info.

    Very keen to see your sample project.

    Thanks for your support

    Mark
  • 0 in reply to Mark Owens

    Hi Mark,

    The sample project for creating a project with a Language Cloud translation provider using the Project Automation API can be found here. It includes all the necessary code to help you set up the project and add the Language Cloud translation provider.

    To create a project and successfully add the Language Cloud translation provider, it’s crucial that the credentials (including API keys and tokens) are provided. Additionally, you must ensure that you are logged in to Language Cloud for the provider to function correctly within your automation environment.

    In the code snippet below (from Program.cs in the sample), after the FileBasedProject instance is created, the translation provider is added to the project along with the required credentials. This is followed by logging in to Language Cloud before running the project tasks.

     private static void Main(string[] args)
 {
     // Change the path with the actual directory where projects should be saved...
     var projectsDirectory = @"";

     // Change the path with the actual project template path
     var templatePath = @"";

     if (!Directory.Exists(projectsDirectory))
     {
         Directory.CreateDirectory(projectsDirectory);
     }

     var sourceLanguage = "en-US";
     var targetLanguage = "de-DE";

     var projectDirectory = GetOutputProjectDirectory(projectsDirectory);

     var projectName = "TestProject-" + DateTime.Now.Year + "-" + DateTime.Now.Month + "-" + DateTime.Now.Day + "-" +
                DateTime.Now.Hour + "-" + DateTime.Now.Minute + "-" + DateTime.Now.Second;

     var projectInfo = new ProjectInfo
     {
         Name = projectName,
         SourceLanguage = new Language(sourceLanguage),
         TargetLanguages = new[] { new Language(targetLanguage) },
         LocalProjectFolder = projectDirectory
     };


     FileBasedProject project;
     if (!string.IsNullOrEmpty(templatePath))
     {
         project = new FileBasedProject(projectInfo, new ProjectTemplateReference(templatePath));                
     }
     else
     {
         project = new FileBasedProject(projectInfo);
     }

     UpdateProjectProviderSettings(project);

     // Update this variable with the actual URI of the translation provider.
     // You can retrieve this value from an existing project or project template (.sdlproj/.sdltpl).
     // To do this, open the project file in a text editor of your choice.
     // Look for the XML element <CascadeEntryProvider> and its child elements.
     // These elements should contain the URI for the translation provider.
     //
     // For example:
     // - URIs starting with "languagecloud.translation.https://" indicate a Translation Engine.
     //
     // Copy the complete URI from the project/template file and assign it to the variable below.
     //
     // Example URI: 
     // If a project template is used, you would typically need to map the URI from the project template file to the actual URI.
     // For the sake of this example, change this value with the actual tpUri string.
     // This is because, when the project automation api is used, the credentials need to be provided explicitly as it works outside the context of Trados Studio.
     var tpUriString = @""; // Paste URI here

     // The API key can be obtained from the Language Cloud web interface.
     // Navigate to: Users -> Integrations -> API Keys.
     // Copy the API key from this section.
     var apiKey = ""; // Paste the API Key here

     if (string.IsNullOrEmpty(templatePath))
     {
         var tpConfig = project.GetTranslationProviderConfiguration();

         var tpReference = new TranslationProviderReference(new Uri(tpUriString), null, true);
         var tpCascadeEntry = new TranslationProviderCascadeEntry(tpReference, true, true, false);
         tpConfig.Entries.Add(tpCascadeEntry);
         project.UpdateTranslationProviderConfiguration(tpConfig);
     }

     project.Credentials.AddCredential(new Uri(tpUriString), apiKey);

     project.Save();

     // Update the second parameter with the actual path to the source files.
     // Example: @"C:\Path\To\SourceFiles"
     AddFilesToProject(project, @""); // Paste the source files path

     //Login to LC for projects with Translation Engine providers 
     var lcService = new LCService();
     lcService.LoginToLC();

     RunScanTaskFiles(project);
     RunAnalyzeTaskFiles(project, targetLanguage);
     RunPreTranslateFiles(project, targetLanguage);

     project.Save();
 }

    Please feel free to explore the provided sample, and let us know if you need further assistance.

    Best regards,

    Alexandru Florescu
Reply
  • 0 in reply to Mark Owens

    Hi Mark,

    The sample project for creating a project with a Language Cloud translation provider using the Project Automation API can be found here. It includes all the necessary code to help you set up the project and add the Language Cloud translation provider.

    To create a project and successfully add the Language Cloud translation provider, it’s crucial that the credentials (including API keys and tokens) are provided. Additionally, you must ensure that you are logged in to Language Cloud for the provider to function correctly within your automation environment.

    In the code snippet below (from Program.cs in the sample), after the FileBasedProject instance is created, the translation provider is added to the project along with the required credentials. This is followed by logging in to Language Cloud before running the project tasks.

     private static void Main(string[] args)
 {
     // Change the path with the actual directory where projects should be saved...
     var projectsDirectory = @"";

     // Change the path with the actual project template path
     var templatePath = @"";

     if (!Directory.Exists(projectsDirectory))
     {
         Directory.CreateDirectory(projectsDirectory);
     }

     var sourceLanguage = "en-US";
     var targetLanguage = "de-DE";

     var projectDirectory = GetOutputProjectDirectory(projectsDirectory);

     var projectName = "TestProject-" + DateTime.Now.Year + "-" + DateTime.Now.Month + "-" + DateTime.Now.Day + "-" +
                DateTime.Now.Hour + "-" + DateTime.Now.Minute + "-" + DateTime.Now.Second;

     var projectInfo = new ProjectInfo
     {
         Name = projectName,
         SourceLanguage = new Language(sourceLanguage),
         TargetLanguages = new[] { new Language(targetLanguage) },
         LocalProjectFolder = projectDirectory
     };


     FileBasedProject project;
     if (!string.IsNullOrEmpty(templatePath))
     {
         project = new FileBasedProject(projectInfo, new ProjectTemplateReference(templatePath));                
     }
     else
     {
         project = new FileBasedProject(projectInfo);
     }

     UpdateProjectProviderSettings(project);

     // Update this variable with the actual URI of the translation provider.
     // You can retrieve this value from an existing project or project template (.sdlproj/.sdltpl).
     // To do this, open the project file in a text editor of your choice.
     // Look for the XML element <CascadeEntryProvider> and its child elements.
     // These elements should contain the URI for the translation provider.
     //
     // For example:
     // - URIs starting with "languagecloud.translation.https://" indicate a Translation Engine.
     //
     // Copy the complete URI from the project/template file and assign it to the variable below.
     //
     // Example URI: 
     // If a project template is used, you would typically need to map the URI from the project template file to the actual URI.
     // For the sake of this example, change this value with the actual tpUri string.
     // This is because, when the project automation api is used, the credentials need to be provided explicitly as it works outside the context of Trados Studio.
     var tpUriString = @""; // Paste URI here

     // The API key can be obtained from the Language Cloud web interface.
     // Navigate to: Users -> Integrations -> API Keys.
     // Copy the API key from this section.
     var apiKey = ""; // Paste the API Key here

     if (string.IsNullOrEmpty(templatePath))
     {
         var tpConfig = project.GetTranslationProviderConfiguration();

         var tpReference = new TranslationProviderReference(new Uri(tpUriString), null, true);
         var tpCascadeEntry = new TranslationProviderCascadeEntry(tpReference, true, true, false);
         tpConfig.Entries.Add(tpCascadeEntry);
         project.UpdateTranslationProviderConfiguration(tpConfig);
     }

     project.Credentials.AddCredential(new Uri(tpUriString), apiKey);

     project.Save();

     // Update the second parameter with the actual path to the source files.
     // Example: @"C:\Path\To\SourceFiles"
     AddFilesToProject(project, @""); // Paste the source files path

     //Login to LC for projects with Translation Engine providers 
     var lcService = new LCService();
     lcService.LoginToLC();

     RunScanTaskFiles(project);
     RunAnalyzeTaskFiles(project, targetLanguage);
     RunPreTranslateFiles(project, targetLanguage);

     project.Save();
 }

    Please feel free to explore the provided sample, and let us know if you need further assistance.

    Best regards,

    Alexandru Florescu
Children