Hi, Just installed Studio 2019 and took a peek. I have a few questions: Do translation memories used in Studio 2017 need any upgrading to ver. 2019? 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). 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

Hi Piotr Bienkowski Piotr Bienkowski said: Do translation memories used in Studio 2017 need any upgrading to ver. 2019? No Piotr Bienkowski 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. Piotr Bienkowski 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.

Hi Michael Friedli , If you have a support contract then you should definitely be logging this with support. If not then can you provide me with the TM so I can investigate this?

Hi Alexa Dubreuil-Storer This a fairly uncommon problem caused by a bug in 2017 where it should be ensuring CM info doesn’t get lost when reindexing due a tokenization change. (Formerly, if you did something like switched off Number recognizer, then reindexed TM content, you’d no longer get CMs where the context involved a number; now the reindex converts the CM hashes.) Under certain rare circumstances that’s causing a constraint violation because the code is trying to update a CM entry but there’s another CM entry that already has the same hash values. 2017 just ignores the CM info loss whereas 2019 does not. The best solution is to create a new TM in Studio 2019 and then import a TMX created with 2017 into the new TM, or upgrade the TM in Studio 2017 first and then use it in 2019. Fortunately 2017 can still be used with 2019 so it should be a one-off workaround. Regards Paul

Studio 2019 vs 2017 - a few questions

Piotr Bienkowski over 8 years ago

Hi,

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

Do translation memories used in Studio 2017 need any upgrading to ver. 2019?
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).
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

Translate

Rate translation

Suggest better translation

Moderator UI

Thread Subject & Description
Studio 2019 vs 2017 - a few questions Hi, Just installed Studio 2019 and took a peek. I have a few questions: Do translation memories used in Studio 2017 need any upgrading to ver. 2019? 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). 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
Get AI Suggestion

AI Reply

Accept answer Reject Answer

Parents

0 Paul Filkin over 8 years ago

Hi Piotr Bienkowski

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

No

Piotr Bienkowski 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.

Piotr Bienkowski 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

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Michael Friedli over 7 years ago in reply to Paul Filkin

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul Filkin over 7 years ago in reply to Michael Friedli

Hi Michael Friedli ,

If you have a support contract then you should definitely be logging this with support. If not then can you provide me with the TM so I can investigate this?

Paul Filkin | RWS

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Michael Friedli over 7 years ago in reply to Paul Filkin

Hi Paul,
Thanks for that - I have sent the TM (plus an older, not upgraded version) via WeTransfer.
I don't have a support & maintenance contract.
Best
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Alexa Dubreuil-Storer over 7 years ago in reply to Michael Friedli

Unknown said:

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

Hi Michael

I have the same issue with several of my TMs, also in Studio 2019.

Did you find a solution to this problem? (I don’t have a contract either)

Alexa

Generated Image Alt-Text
[edited by: Trados AI at 2:03 PM (GMT 0) on 28 Feb 2024]
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul Filkin over 7 years ago in reply to Alexa Dubreuil-Storer

Hi Alexa Dubreuil-Storer

This a fairly uncommon problem caused by a bug in 2017 where it should be ensuring CM info doesn’t get lost when reindexing due a tokenization change. (Formerly, if you did something like switched off Number recognizer, then reindexed TM content, you’d no longer get CMs where the context involved a number; now the reindex converts the CM hashes.) Under certain rare circumstances that’s causing a constraint violation because the code is trying to update a CM entry but there’s another CM entry that already has the same hash values.

2017 just ignores the CM info loss whereas 2019 does not.

The best solution is to create a new TM in Studio 2019 and then import a TMX created with 2017 into the new TM, or upgrade the TM in Studio 2017 first and then use it in 2019. Fortunately 2017 can still be used with 2019 so it should be a one-off workaround.

Regards

Paul

Paul Filkin | RWS

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Reply

0 Paul Filkin over 7 years ago in reply to Alexa Dubreuil-Storer

Hi Alexa Dubreuil-Storer

This a fairly uncommon problem caused by a bug in 2017 where it should be ensuring CM info doesn’t get lost when reindexing due a tokenization change. (Formerly, if you did something like switched off Number recognizer, then reindexed TM content, you’d no longer get CMs where the context involved a number; now the reindex converts the CM hashes.) Under certain rare circumstances that’s causing a constraint violation because the code is trying to update a CM entry but there’s another CM entry that already has the same hash values.

2017 just ignores the CM info loss whereas 2019 does not.

The best solution is to create a new TM in Studio 2019 and then import a TMX created with 2017 into the new TM, or upgrade the TM in Studio 2017 first and then use it in 2019. Fortunately 2017 can still be used with 2019 so it should be a one-off workaround.

Regards

Paul

Paul Filkin | RWS

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Children

0 Francesca Collodo over 7 years ago in reply to Paul Filkin

Hi Paul, this isn't uncommon - it's happening on every TM I try and upgrade in 2019. Also, clicking on "Details" in the log generates an unhandled exception. Are we really living with this (cumbersome) workaround?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul Filkin over 7 years ago in reply to Francesca Collodo

Hi Francesca Collodo

I think it's uncommon in terms of the affected users, but if you get the problem it's possible you'll get it for all your TMs. For now, yes, you are living with this workaround I'm afraid. The fix is with development and once they are happy to release it then it will be delivered in an automatic update.

Paul Filkin | RWS

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Francesca Collodo over 7 years ago in reply to Paul Filkin

What is the priority on this fix? I've just found another issue this morning which means a quick translation is taking forever. Fuzzy matches not found in the editor? Is this related? Also, as 2017 was heavily marketed based on this new improved handling of TMs, enabling us to obtain more leverage, I *assume* that the priority is super high? When can we expect a patch?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Trados Studio > 1. Trados Studio

Studio 2019 vs 2017 - a few questions