We released SDL Trados Studio 2017 SR1 Cumulative Update 10 (Build 14.1.10010.18573) earlier today. Find more details in the KB here:
gateway.sdl.com/.../communityknowledge
Best regards
Daniel Brockmann
Daniel Brockmann
Team Trados @ RWS
We released SDL Trados Studio 2017 SR1 Cumulative Update 10 (Build 14.1.10010.18573) earlier today. Find more details in the KB here:
gateway.sdl.com/.../communityknowledge
Best regards
Daniel Brockmann
Daniel Brockmann
Team Trados @ RWS
Excellent! Been meaning to say, Daniel, I noticed that Studio now updates the TM with or without non-breaking spaces rather than ignoring the difference between 'identical' segment and TU. This is very useful to me in my line of work! I guess this was a wonderful side-effect of the recent changes to how spaces are handled.
All the best!
Ali :)))
Hello,
Today we have downloaded the latest build of Studio 2017.
Although that we followed the instructions mentioned at the bottom of the page here, and we install the latest version of Microsoft Visual C++ (which is the 14.13.26020.0) we keep receiving a notification in Studio as can be seen below.
Actually the version that is mentioned above is older than the one that we downloaded from here.
What we have installed in our computers is:
Could you please confirm what the latest version of Microsoft Visual C++ is?
Regards
Pavlos
Hi NLG GmbH
Sorry for the inconvenience. Studio 2017 CU10 currently uses a slightly older version of Microsoft Visual C++ than the one you have installed, that is why you see the notification. We are working to fix this, but in the meantime, you can either ignore the notification, as Studio should work just fine or if it bothers you until we have it fixed, you can manually un-install Microsoft Visual C++ 2017 from your computer and install it again using the Studio notification.
I hope this helps. Let me know if you still have issues.
Cristina Nistor| Product Owner | SDL
Hello Cristina Nistor,
Thank you very much for your reply.
We will go with the Visual C++ version that is mentioned within Studio (having uninstalled first the latest one).
Just one further question: do you have any estimation when this fix will be ready?
Regards
Pavlos
Cristina Nistor| Product Owner | SDL