Due to essential maintenance, access to Trados cloud will be unavailable on Saturday 30 August from 00:00 to 12:00 UTC.
  • State Suggested Answer
  • Replies 9 replies
  • Answers 3 answers
  • Subscribers 437 subscribers
  • Views 5525 views
  • Users 0 members are here
Options
Related

Studio 2019 vs 2017 - a few questions

Piotr Bienkowski

Hi,

 

Just installed Studio 2019 and took a peek. I have a few questions:

  1. Do translation memories used in Studio 2017 need any upgrading to ver. 2019?
  2. Can I open the 2017 project templates directly in 2019 or will it break them? (I understand that I can use the migration utility to migrate them).
  3. Can I open projects created in Studio 2017 in Studio 2019 or will it break them? WIll they be backward-compatible if I open and save them in Studio 2019?

Thanks,

Piotr
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hi  

    Unknown said:
    Do translation memories used in Studio 2017 need any upgrading to ver. 2019?

    No

    Unknown said:
    Can I open the 2017 project templates directly in 2019 or will it break them? (I understand that I can use the migration utility to migrate them).

    You can't use the project migration utility to migrate templates.  It's always a good idea to recreate your templates because otherwise you potentially introduce legacy problems into the newer product.  There are also new features between versions and if you use the old template you create projects without access to the latest stuff.

    Unknown said:
    Can I open projects created in Studio 2017 in Studio 2019 or will it break them? WIll they be backward-compatible if I open and save them in Studio 2019?

    Yes you can. But as you can use Studio 2017 for as long as you like this time around it makes sense to finish them off in 2017 and start new ones in 2019.

    Paul Filkin | 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

  • 0 in reply to Paul
    Hi Paul,
    I have just installed Studio 2019 and used it on one job. Looking at one of my main TMs, It recommended an upgrade (red triangle in TM view). I ran it and it came up with this error while re-indexing:
    ***
    Process failed (02/08/2018 09:38:13)
    Sdl.LanguagePlatform.Core.LanguagePlatformException: The translation memory data file engine returned an error:
    constraint failed
    UNIQUE constraint failed: translation_unit_contexts.translation_unit_id, translation_unit_contexts.left_source_context, translation_unit_contexts.left_target_context
    at Sdl.LanguagePlatform.TranslationMemoryApi.FileBasedTranslationMemoryLanguageDirection.ReindexTranslationUnits(RegularIterator& iterator)
    at Sdl.TranslationStudio.Common.TranslationMemory.TranslationMemoryAutomation.Jobs.ReIndexTranslationMemoryJobRequest.Execute(IJobExecutionContext context)
    ***
    The upgrade (first routine) appears to have completed and the TM opened OK.
    I tried another re-index, same error.
    Next, I closed 2019 and went back to Studio 2017, where I was able to re-index the same TM successfully.
    Any thoughts, please?

    PS I was hoping for some drag & drop mouse functionality in 2019 - no change there, not impressed!
    Thanks and all the best
Reply
  • 0 in reply to Paul
    Hi Paul,
    I have just installed Studio 2019 and used it on one job. Looking at one of my main TMs, It recommended an upgrade (red triangle in TM view). I ran it and it came up with this error while re-indexing:
    ***
    Process failed (02/08/2018 09:38:13)
    Sdl.LanguagePlatform.Core.LanguagePlatformException: The translation memory data file engine returned an error:
    constraint failed
    UNIQUE constraint failed: translation_unit_contexts.translation_unit_id, translation_unit_contexts.left_source_context, translation_unit_contexts.left_target_context
    at Sdl.LanguagePlatform.TranslationMemoryApi.FileBasedTranslationMemoryLanguageDirection.ReindexTranslationUnits(RegularIterator& iterator)
    at Sdl.TranslationStudio.Common.TranslationMemory.TranslationMemoryAutomation.Jobs.ReIndexTranslationMemoryJobRequest.Execute(IJobExecutionContext context)
    ***
    The upgrade (first routine) appears to have completed and the TM opened OK.
    I tried another re-index, same error.
    Next, I closed 2019 and went back to Studio 2017, where I was able to re-index the same TM successfully.
    Any thoughts, please?

    PS I was hoping for some drag & drop mouse functionality in 2019 - no change there, not impressed!
    Thanks and all the best
Children