Vincent Partensky

What settings/plugins are you using for verification?

How much I appreciate your responses, Paul, but even SDL 2021 is a freaking disaster. Try translate and QA a 15k word file, let alone a 100k file. My 'confirm segments' on a 150k file now runs for 6 hours. Are you kidding me? The whole thing collapses. And yes, I have a P52 workstation, RAM enough, the thoroughbread in the house. But SDL can't run with it. Do you do testing? What the are these developpers doing? Or do you want me to guinee pig your developers work? Trados is a cardhouse and only suitable or 1k-2k projects. I use only 5% of all the junk features you added in the the last years. Do you listen to customers at all? The rest: unusable. And here is the catch: you guys know this. I know you do. Switch off AV blah blah, been there, done that. Try QA'ing a 50k file with termbase. Good luck. Go shopping, take a walk, whatever. SDL Trados is UNSUITABLE (yes, read that out loud) for projects of 5k or more. But, I know, and you know it: you can't fix it without starting from the ground up. Cut the crap, just admit it, you have a problem.

Do not get me wrong: SDL is the best tool. I love it. Nothing better than that, superior to Memsource and the likes : Best QA, highest productivitiy, But, how bad is this coded. I had to get this out. My lifehood depends on SDL (full time freelancer since 2012,  90% revenue doing work via Trados SDL); but you guys screwed it up. Big time. Stop telling the tricks to make anything faster, it is not the AV, it is not Word, it is not some other tweak, no: SDL is a cardhouse of poorly programmed amateur crap depending on external 3rd party junk.

Take that. And do something with it. I love Trados, it is my main source of income, but, I am reaching the end of my acceptance level. Please FIX THE JUNK. Your loyal customer.

How much I appreciate your responses, Paul, but even SDL 2021 is a freaking disaster. Try translate and QA a 15k word file, let alone a 100k file. My 'confirm segments' on a 150k file now runs for 6 hours. Are you kidding me? The whole thing collapses. And yes, I have a P52 workstation, RAM enough, the thoroughbread in the house. But SDL can't run with it. Do you do testing? What the are these developpers doing? Or do you want me to guinee pig your developers work? Trados is a cardhouse and only suitable or 1k-2k projects. I use only 5% of all the junk features you added in the the last years. Do you listen to customers at all? The rest: unusable. And here is the catch: you guys know this. I know you do. Switch off AV blah blah, been there, done that. Try QA'ing a 50k file with termbase. Good luck. Go shopping, take a walk, whatever. SDL Trados is UNSUITABLE (yes, read that out loud) for projects of 5k or more. But, I know, and you know it: you can't fix it without starting from the ground up. Cut the crap, just admit it, you have a problem.

Do not get me wrong: SDL is the best tool. I love it. Nothing better than that, superior to Memsource and the likes : Best QA, highest productivitiy, But, how bad is this coded. I had to get this out. My lifehood depends on SDL (full time freelancer since 2012,  90% revenue doing work via Trados SDL); but you guys screwed it up. Big time. Stop telling the tricks to make anything faster, it is not the AV, it is not Word, it is not some other tweak, no: SDL is a cardhouse of poorly programmed amateur crap depending on external 3rd party junk.

Take that. And do something with it. I love Trados, it is my main source of income, but, I am reaching the end of my acceptance level. Please FIX THE JUNK. Your loyal customer.

ML

You're lucky your post got through the pam filters... Lennert Fransen needs to look at that.  I removed the offensive language but left your overall post because we don't block criticism... we'd just rather it was written in a more constructive fashion.

The current release of 2021 is definitely in need of attention and the development teams are working to address this.  I don't expect you to have to worry about our problems in addressing complexities you won't even be aware of, or care about, but fortunately the problems you appear to be facing are not something affecting the majority of our userbase.  That doesn't mean we won't address them, we will.  It just means nothing is as simple as it may look on the outside and we are all doing our best to make sure all of our users have a better experience than the ones you are having at the moment.

In general it always make sense to create a new thread rather than tack onto the end of others, especially ones that seem to have been satisfactorily resolved for the original poster already.  Aside from the clarity a little organisation brings for others, it also means we can deal with your issues more appropriately.  You may not have a support contract or you would probably have used it, so please help us to help you by bringing specifics we can look at in a new thread.  Feel free to air your frustration, but please do give us something we can work on with you.

Dear Paul,

I apologize for my strong language. Forgive me when after struggling 6 hours with my most favorite tool (I even tell my clients: I prefer Trados) But yesterday, it was too much for me. And then, things you say may become a bit rough when you reread it. I stand with my comments, the strong wording was the moment of my emotion. Again, my apologies. But please folks: fix our favorite tool.

Michel

Fully agree. Studio is not made for larger projects and surprises me with new issues every other day.

Hi Paul,

How are you?

I am using Studio 2021 and - unfortunately - I am experiencing this extremely slow response when confirming segments. I have deselected "Enable verification of segment" in Editor > Automation, but it does not help. I am using 5 different TM's on a project, and I need all of them (though I checked only one for Update), but not it is almost impossible to go on. Please note all the 6 TM's are up-to-date. I would reallyh need a good and fast (as usual) solution for this!

THANKS A LOT!

adriana

Hi Adriana
I had the same problem yesterday (project package of >1 GB including four large TM's and two termbases). I've solved it by pre-translating the file over lunch with the four TM's attached and a minimum match value of 60%. Afterwards I've disabled three of the four memories, keeping only the largest one, which allowed me to translate a lot faster. After finishing the translation, I've then reattached the three remaining memories and updated them using the 'update main translation memories' command. The only downside of this method is you cannot use concordance for the disabled memories. You can however lower the minimum match value to 40% or 50% to (at least partially) counter that issue. Hope this helps...

Hello Jeroen,

Thanks for the precious tip! Usually I like to have everything under control, but this sounds like a necessary measure for big projects. Although, I admit I am really surprised that this (long-loved) expensive tool seems to be unable to handle big projects :/. And no replies from the manufacturer...

Hopefully they're working on this.

THANKS A LOT!

adriana

Hi, all!

I'm also having the same issue. I'm working on a 40k file and verifying each segment takes about 20-30 seconds. The segments are short, so verification is taking significantly longer than translation. It's absolutely ridiculous. 
At the moment I'm trying to "replace all" instances of one term (that doesn't appear too much in the file) and I've been waiting for over 40 minutes already to complete the task. This is absolutely nerve-wrecking. 

I prefer Trados over any other CAT-Tool. PLease fix this!

Best,

A.-