• Replies 3 replies
  • Subscribers 393 subscribers
  • Views 123 views
  • Users 0 members are here
Options
Related

Create Project Via API shows files as Reference

Mark Owens

Hi

I've recently upgraded to Trados 2024, and am running code that creates a new project from a Studio 2024 template, add files, and machine translates. All VS references are for Studio 2024 assemblies.

The template is setup exactly as you'd expect to do this. There is no memory selected, and the DeepL translation configuration is correct. The file types for the template have most entries in the list unticked, but XML2: MadCap Compliant is ticked.

The program steps are: 

  1. Create project
  2. AddFolderWithFiles (recursively)
  3. Save project
  4. Scan files
  5. Save project
  6. ConvertToTranslatableFormat (via RunAutomatiobTask)
  7. CopyToTargetLanguages (via RunAutomatiobTask)
  8. Save project
  9. Modify settings to applyAutomatedTranslation
  10. Save settings
  11. Save project
  12. PreTranslateFiles (via RunAutomatiobTask)
  13. Save project

It never seems to use the project template setting to recognise the .htm files are translatable.

If I create the project manually, with the same template, same source files, it performs the MT as expected.

There must be some sort of gotcha going on. Can anyone tell me where I'm going wrong?
Thanks

Mark
Rate translation
×
Suggest better translation
×
Parents Reply
  • in reply to Mark Owens

    hey  , I’ve investigated this issue and have been able to reproduce it.

    The problem appears to start during the Automatic Task Scan step. At that stage, the SourceFile role should normally be identified as Translatable, Reference, or Unknown. However, in my testing, the files are consistently being set to Unknown or Reference, even for file types that would normally be expected to be translatable (for example, a simple .txt file).

    Because the scan is not classifying the files correctly, the bilingual files are not generated, and as a result the downstream project automation steps do not proceed as expected.

    At this point, this appears to be a product issue rather than expected behavior. I have escalated it to the Studio team for review. I do not have an ETA yet, but I will update this thread once I have more information.

    Thanks for reporting it and for providing the sample materials, which helped confirm the behavior.

    Internal Reference: SRQ-30939

    Patrick Andrew Hartnett | Developer Experience | Team Lead | RWS Group

Children
No Data