Hi Małgorzata Gardocka

This is interesting!

Take a look at the following thread:

Two functions not working in Studio 2017 after the install of CU 16

Both Peter Bolin and Joel Earnest are experiencing this occurrence too, since installing the latest cumulative update of Studio 2017.

What I can do, though, is ask Paul Filkin and Daniel Brockmann to look into this as it is obviously happening since the launch of Studio 2017 CU16. I did not experience this myself as I don't have a 2017 license any more.

So, basically this issues that the toggle function is not working on whitespaces or on tag displays.

I hope that a solution can be found soon...

All the best,

Ali

Hi Alison,

Thank you so much for trying to solve this problem and answering me.

I would be very grateful, if you asked Paul and Daniel about this issue.

If you or Paul or Daniel or somebody else finds a solution, could you please post it in this thread?

Kind regards,

Malgorzata

Hi Małgorzata Gardocka 

Yes, if we discover a solution we will certainly post it in this and in the other thread.

All the best,

Ali

Hi Alison,

Has a solution to my problem been found? I've reported the issue 14 days ago and must say that I'm dissapointed that SDL has apparently ignored this problem.

Kind regards

Małgorzata

Małgorzata Gardocka

As noted in the thread Ali pointed you to it has been reported to support already and they have acknowledged it's a bug.  I just checked on this and the refresh problem that causes this has been fixed already.  I don't have a release date for this yet but I expect it to be in the next update.

Thank you. I hope the issue will soon be fixed.

Hi Małgorzata Gardocka

I'm sorry you though that SDL was ignoring your problem. I've been soooo busy working that I haven't been keeping close watch on the threads I've been involved in (I don't work for SDL, I'm a freelancer) or I'd have suggested you follow the other thread as it was progressing. There have been new posts added over the past days. Take a look.

As Paul said, a solution is intended to be included in the next update. Thus, it won't be too long to wait.

All the best,

Ali

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.