• State Suggested Answer
  • Replies 9 replies
  • Answers 2 answers
  • Subscribers 396 subscribers
  • Views 5023 views
  • Users 0 members are here
Options
Related

Project translation memory not in translator package

Martin Bächtold

I create a project with a project translation memory. To be sure, that the project translation memory I check in the project folder and we can see it here:

Now I want to create a project package for my translator: 

The project translation memory is missing!

In order to get the TM into the translator package, I have to go on pre-translate files. Not here!!! 

I go here …

And click on “Finish”. And now I create the package

There is not logic reason for this behaviour.

The problem is, that this trick does not work with the API. I tried to use

AutomaticTaskTemplateIds.PopulateProjectTranslationMemories

and other methods but I did not find a way to include the TM.

Please help!

R.

Martin
Rate translation
×
Suggest better translation
×
Parents Reply Children
  • 0 in reply to Evzen Polenka
    Dear Evzen

    thanks a million for your answer. We added the following lines to our code, but unfortunately it is not working:

    options.IncludeReports = true;
    options.IncludeExistingReports = true;

    This is our PackageSettingsBlock:

    private ProjectPackageCreationOptions GetPackageOptions()
    {
    #region "ProjectPackageCreationOptions"
    ProjectPackageCreationOptions options = new ProjectPackageCreationOptions();
    #endregion

    #region "IncludeRessources"
    options.IncludeAutoSuggestDictionaries = false;
    options.IncludeMainTranslationMemories = false;

    options.RemoveServerBasedTranslationMemories = false;
    options.IncludeTermbases = true;
    #endregion

    #region "RemoveAutomatedTranslationProviders"
    options.RemoveAutomatedTranslationProviders = false;
    #endregion

    #region "RecomputeAnalysisStatistics"
    options.RecomputeAnalysisStatistics = true;
    options.ProjectTranslationMemoryOptions = ProjectTranslationMemoryPackageOptions.CreateNew;

    options.IncludeReports = true;
    options.IncludeExistingReports = true;
    #endregion

    #region "ReturnOptions"
    return options;
    #endregion
    }

    Do you have an idea why it might fail?

    Best regards and thanks a lot in advance
  • 0 in reply to Marie-Christine Waldburger
    Hmmm, no idea... Which Studio version are you using it with? The separate options for including existing reports or recomputed ones were introduced only in Studio 2015 SR2 CU7 (they should be present in Studio 2017 API from the very beginning).
    Funnily enough, this made me debug my PowerShell code and I realized that due to a mistake I made, the workarounds are actually NOT applied... but still, the created packages DO include the project TM :-O
    I'm perplexed...