• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 432 subscribers
  • Views 1675 views
  • Users 0 members are here
Options
Related

New Cumulative Update for Studio 2017 SR1 - all errors came back ...

Mateusz Fatek

Right after the cumulative update rolled out I decided to apply it to my Studio, since it was supposed to correct all the troubles it had previously introduced for Polish users.

To my amazement, the updated actually made my Studio unable to work in. Again. Now even though my shortcuts are set as previously, nothing works correctly. 

Not even Ctrl+A... I tried resetting shortcut settings to default, I tried changing the shortcuts that don't work but using any shortcuts now causes the Studio to freeze.

Guys, can you PLEASE roll out updates that have been tested before, especially that you know your previous updated had actually made things worse for a lot of users (e.g. Polish ones)? Now I have to waste more time trying to fix something I had already fixed sometime ago (but now the previous methods simply do not work, so I need to try and find new ones, and I - as always - have deadlines to meet...)

Has anyone else had this problem with the cumulative update? Or perhaps I am just that unlucky that it is only my Studio that ceased working properly? :D

 

EDITED:

 

Oh wait, it seems that after restarting the computer and several resets of Studio's settings (reset to default clicked, like, 10 times) NOW the Studio seems to work. At least it has been working rather properly for the last 2 minutes, so maybe it will stay that way.

Advice for any Polish users who decide to apply this update - just to make sure, reset you shortcut settings to default several times before you actually open any project and start working. This could help.

 

EDITED #2:

Unfortunately I cannot set up the shortcut for Copy source to target. In standard Studio 2017 I used left Ctrl + Backspace for this. In SR1 my old shortcut did not work so I changed it to left Ctrl+Shift+Backspace. 

Now none of those seem to work. I tried changing this shortcut to several combinations, but it just seems that copying source to target ceased to work for me. :(
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    Hi ,

    I'd be interested to know if has these problems too as he's a heavy user into Polish?

    On your "copy source to target" problem, was this failing because you could not enter the shortcut, or it failed because the shortcut didn't work once it had been entered?

    Regards

    Paul

    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

    In my case the shortcuts I entered for this function did not work at all. Meaning I could change this shortcut to anything (like Shift+Del, Ctrl+Shift+Del, Ctrl+Backspace etc.) - and after saving the settings, even after restarting Studio, this particular shortcut would not work at all. What it sometimes would do, however, was crash Studio - after pressing this combination several times in a row sometimes (one in four instances, roughly) a TM error in Studio would pop up, suggesting that my TM connected to a specific project has just got corrupted. When this happened you can't move your cursor from any segment to another without this message reappearing all the time. The only thing left to do was to Ctrl+Alt+Del and shut Studio from there (the closing button stopped working in Studio, too).

    For some reason, however, now that I have set this particular shortcut to Ctrl+Ins, and having restarted my computer twice (I think), the shortcut began working properly, no crashes, not nothing.

    This is weird a bit. I wandered if it is due to some other software that I have (and I have a lot of stuff installed, since I need it), but I even tried switching practically everything down manually from the task manager and starting Studio with just about 70 processes ongoing (generally I run around 150 processes/apps/drivers simultaneously) and it still did not change anything before suddenly the shortcut began working properly.

    Anyway, now I can work in Studio, but it has been over an hour of trials and mistakes before I even (accidentally, I think) managed to stumble upon a key combination that works for me. I hope that it was an isolated case and others don't have these issues with shortcuts, because I personally know they can mess with your projects completely.
  • 0 in reply to Mateusz Fatek
    What kind of keyboard do you use? Polish programmer QWERTY? I do not use this, I use Polish 214, a typist keyboard QWERTZ, where the German Umlauts are replaced (fixed) by Polish letters.
    This said I wonder why you decided to use Backspace for anything else as it is designed? The common Windows shortcut CTRL+BACKSPACE deletes a word left to the cursor. And as this is nearly Windows wide, it would wonder me, if you could use it for anything else in Studio. But regardless this in the current CU7 I have no problems with any shortcuts, they work as desired. So it might be useful to reset the user profile to the default one, then reset Studio as described here gateway.sdl.com/.../communityknowledge
    On top of this you could also rename the Studio folder you'll find in AppData - Local and this one C:\ProgramData\SDL\SDL Trados Studio - here for Studio 14 and Studio 5.
    After this I would reset the window layout in all views in Studio and in the end create a new user profile with all the necessary settings. This profile should also be stored in a different folder as backup copy for future use.
    All this operations will reset Studio to nearly a fresh install. I hope, this helps.

    As for the testing you mentioned: we do test all releases, myself included. I do not test as play, but in my very case I take every single beta into production since Studio 2011 at least. So when I get the beta, I install this and work with it. I cannot remember the word count done with the big SR1 beta, but due to long testing period it must have been much more than 200,000 words. Even the last CU has produced about 50,000 words. So the betas are thoroughly tested by many of us, however it is not possible to imitate all supposed configurations, because no one of us has the same setup as the other. As you will certainly know, there are no 2 identical Windows computers, when in use, at least withing freelance translators - because every user adapts some parts or programs, making it impossible to simulate exactly the same environment. I also own the tw_users list on Yahoo or read and write in the German u-cat list. There I quite often read messages from people having the strangest problems with Studio, which I never encountered. And if that would be a systematic problem with the software, I nearly must encounter this, because I have many varying formats and over 1,000,000 words per year done in Studio.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.