Left aside, that an option should do what expected, I would never work without viewing spaces.
Only then you are able to see a double space or a tab - and both are extremely important information. Leaving double spaces in translation is a major error and using several tabs for making tables or creating distance between words / text parts is also not a good solution. So only when viewing these parts you can react and remove as necessary. Also placing spaces around tags as needed in your target languages is much easier, when you see them.

I would really recommend everyone working on a screen with tools to view all possible non-printable characters. This helps to examine formatting and create properly formatted documents - ie. without separating pages with line breaks or similar.

Left aside, that an option should do what expected, I would never work without viewing spaces.
Only then you are able to see a double space or a tab - and both are extremely important information. Leaving double spaces in translation is a major error and using several tabs for making tables or creating distance between words / text parts is also not a good solution. So only when viewing these parts you can react and remove as necessary. Also placing spaces around tags as needed in your target languages is much easier, when you see them.

I would really recommend everyone working on a screen with tools to view all possible non-printable characters. This helps to examine formatting and create properly formatted documents - ie. without separating pages with line breaks or similar.

Thank you for understanding me, Jerzy.

I usually work with viewing spaces and mostly turn them off for more fluent reading,  when I do the last reading.

The topic you've mentioned is extremely important and it makes me sad that SDL doesn't get that, the more so as Trados is a big expenditure and for that money quick fixing of technical problems could be expected.

Great to hear - spaces are so important in translation and unfortunately my experience as supporter, layouter, translator and auditor shows, that so many people do not pay the least attention to these...

As you may know, developing software is a very complex process. Quite often you change a piece of a code here and see changes appearing in far separated parts of the program. In this very case what most probably happened is, that the code change made, which caused this bug, remained unnoticed during testing, as from what I know nearly all if not really all people testing the software prior to release work with spaces shown (me included) and NEVER change this view.

When changes are needed in software, simple things are not that simple anymore. Something like this here may appear very simple problem. But most probably the underlying code is complicated and alone finding out, what causes this bug, has taken time. This bug will be addressed by the next CU, as Paul mentioned, but from what I remember there has never been any CU WITHOUT testing - as otherwise the new release might bring new problems. So please be a little bit patient. 2 weeks is not really long in that complicated process. And as you note, it has been addressed and will be solved.

You may rest assured, that both SDL and all people testing do pay attention to deliver the best possible software. Nonetheless, as always in life - sh... sometimes happen. This said, you may also wish to upgrade to Studio 2019 (if you are a member of the German BDÜ, you can get discount codes there, so the upgrade will cost you just a few bucks), where this problem never occurred. Which of course does not mean, that S2019 is perfect - there is no perfect software in the world.

If you, like myself, are depended on the toggling of whitespaces and tags, you can always downgrade to the previous build (Studio 2017 SR1 CU15 and MultiTerm 2017 SR1 CU7). The installers are available in your SDL Account. I just downloaded them myself to be on the safe side.

If CU17 has not been released when I am back from my holiday in July, I will have to downgrade my office laptop. I have never done a downgrade before, but it might be necessary this time.

/Peter Bolin

Hi again

I wrote a long reply to you first agreeing with both of Jerzy Czopik 's posts but it appears to have vanished, I must have clicked incorrectly. Anyway, I now see that Peter Bolin has suggested the same as I then did, to install the previous versions again.

Here are shortcuts to download them:

SDL Trados Studio 2017 CU15

SDL MultiTerm 2017 CU7

You will need to first uninstall Studio and MultiTerm 2017 via the 'Remove suite of projects' shortcut for each of them reached via Control Panel > Small Icons > Programs and Features...

No need to release your license, it will associate itself to your next installation of Studio.

Restart your PC then install Studio first, then MultiTerm.

Then, it would be a good idea to run a Windows Repair as described in the following knowledge page:

Repairing your SDL Studio/MultiTerm installation

I hope this helps,

All the best,

Alison

Thank you Peter for your suggestion and Alison for your detailed instructions, which allowed to me to save valuable time! The problem has been solved!

Hi Małgorzata Gardocka

It is the logical thing to do, if a cumulative update causes unexpected issues, to return to the previous update until the problem has been resolved.

Glad it's all working OK for you again!

All the best,

Ali