I use Studio quite a bit for proof reading texts, as well as translating, not necessarily with bilingual documents but also monolingual documents. The problem is the same in both situations and also in the normal translation process. But to demonstrate what I mean I will just describe proofreading a monolingual file.

I first create a project using a template for the job and insert the files. The template is et-up to use a TM and also to copy source to target if no fuzzy is found.

When I move to next segment, by whatever means, I can see the TU is highlighted and for example I can see there is a word in the target segment that has been misspelled. But it is not marked with the usual red wiggly line underneath it. Even if I click in the target segment it is still not marked. I need to either type something in the target segment or change something (for example delete a character) before the misspelled words are marked.

This means that I must physically do something in the target segment before I can see the mistakes and many segments are perfectly all right and do not need any corrections. Which means I could miss errors because the spell check did not kick-in. If I miss an error and move down to the next TU then the errors in what is now the previous target segment are shown. But this means going back to correct the error.

All this means I need more time, hence it costs me more.

My idea is that when moving to the next TU the spell check is automatically carried out at that point in time so that any spelling mistakes are immediately visible to the user.

I hope this reaches a friendly ear ;-)

Regards,

Ben