QA-Checker is not reporting any errors no matter what I do

QA-Checker is not reporting any errors even if I build some in to trigger it (adding multiple spaces or having different ending punctuation in source and target).

I have enabled QA Checker in the general options and in the project settings as well.

I have also checked "Enable Verification of Segment" under Options - Editor - Automation. Now I am utterly stumped but feel like I am just not seeing the elephant in the room. Any ideas what I am forgetting? (I am fairly new to Trados Studio)

Thanks in advance!

Translate

Rate translation

Suggest better translation

Moderator UI

Thread Subject & Description
QA-Checker is not reporting any errors no matter what I do QA-Checker is not reporting any errors even if I build some in to trigger it (adding multiple spaces or having different ending punctuation in source and target). I have enabled QA Checker in the general options and in the project settings as well. I have also checked "Enable Verification of Segment" under Options - Editor - Automation. Now I am utterly stumped but feel like I am just not seeing the elephant in the room. Any ideas what I am forgetting? (I am fairly new to Trados Studio) Thanks in advance!
Get AI Suggestion

AI Reply

Accept answer Reject Answer

Parents

0 Paul over 7 years ago

Hi Lilli Staehle ,

Good explanation of what you've tried so far... but it would be a little more helpful if you gave us the sample text you are checking and what QA options you are using to find the problem and then we can test it or at least provide a sensible answer.

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Lilli Staehle over 7 years ago in reply to Paul

Hi Paul,

thans for getting back to me!

As for providing a sample text: I am fairly certain that this issue is independet of the file I am working on. I often work on smaller objects and for none of the multiple files I have tried to run QA Checker on any errors have ever been reported - at all.

The options I am using specifically to try and trigger error reports / warnings / notes are under Punctuation - "Check that source and target end with same punctuation"and "Check for multiple spaces". I am also fairly certrain that I tried "check brackets" and added brackets to the target segement to no avail at some point in the past.

I suspect this could be connected to file type settings or language-pair specific settings?

And some additional info: I just bought Studio 2017 but have been working for a while with Studio 2014 before that using my client's license. I remember having the same issue there as well and that it just went away at some time and all of a sudden I could successfully check my translations. I have no idea what I did to cause that change...

I'd be grateful for any ideas and suggestions!

Thanks!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Reply

0 Lilli Staehle over 7 years ago in reply to Paul

Hi Paul,

thans for getting back to me!

As for providing a sample text: I am fairly certain that this issue is independet of the file I am working on. I often work on smaller objects and for none of the multiple files I have tried to run QA Checker on any errors have ever been reported - at all.

The options I am using specifically to try and trigger error reports / warnings / notes are under Punctuation - "Check that source and target end with same punctuation"and "Check for multiple spaces". I am also fairly certrain that I tried "check brackets" and added brackets to the target segement to no avail at some point in the past.

I suspect this could be connected to file type settings or language-pair specific settings?

And some additional info: I just bought Studio 2017 but have been working for a while with Studio 2014 before that using my client's license. I remember having the same issue there as well and that it just went away at some time and all of a sudden I could successfully check my translations. I have no idea what I did to cause that change...

I'd be grateful for any ideas and suggestions!

Thanks!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Children

0 Paul over 7 years ago in reply to Lilli Staehle

Hi Lilli Staehle ,

You said you made the appropriate changes in Project Settings for the active project, so I really have no idea. The filetype settings should not have any impact here at all, and I doubt the language pair is at play either. Can you share your project? If you please send it to pfilkin@sdl.com and I'll be happy to try and help. Otherwise I don't really have any idea why this doesn't work for you.

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Evzen Polenka over 7 years ago in reply to Lilli Staehle

Doublecheck that you have QA Checker enabled (check box set) in the Project Settings...

...and that you have not excluded the segment type(s) which you actually WANT to check:
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Lilli Staehle over 7 years ago in reply to Evzen Polenka

Hi Evzen,

thanks for your input! I did make sure that QA Checker is also enabled in the project settings and also have made sure that no segment types I don't want to be excluded are checked (my settings are the same as yours - which is the default setting I think).

So, the culprit must be something else.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Lilli Staehle over 7 years ago in reply to Paul

Hi Paul,

thanks for the offer, I sent you an email with a sample file and my exported QA Checker settings.

Also, one thing I forgot to mention in my e-mail but which might be relevant: I tried and checked "report all non-excluded segments" because I was curious to see what would happen and when I verfied the file STILL nothing was reported - neither segemens with nor without errors.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Evzen Polenka over 7 years ago in reply to Lilli Staehle

And are you triggering the verification manually (by pressing F8) or expecting it to be triggered automatically in editor?

The thing is that in editor it's triggered only if you manually confirm the segment by pressing Alt-+. It's NOT triggered by simply moving the cursor to next segment, or setting the segment status e.g. using the context menu, etc.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Lilli Staehle over 7 years ago in reply to Evzen Polenka

Thanks for the input! I am triggering the verification manually by chosing it in the review bar or by pressing F8. Also, I always confirm all segments by pressing ctrl+enter to also move on to the next segment as well. I never confirm using context menu options etc. (good to know that this might make a difference though!)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul over 7 years ago in reply to Lilli Staehle

Hi Lilli Staehle ,

Thanks for the file. Try unchecking "Report all non-excluded segments" in the "Segments to Exclude" options. It's at the bottom. If you uncheck this then it works fine and all your errors are correctly picked up.

When you use this option it overrides the normal results because it's giving you a different kind of report. Glad you sent the file though... I would never have thought of that!!

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Evzen Polenka over 7 years ago in reply to Paul

Unknown said:
Try unchecking "Report all non-excluded segments" in the "Segments to Exclude" options. It's at the bottom. If you uncheck this then it works fine and all your errors are correctly picked up.

Huh, but that doesn't sound like correct functionality of that option, does it?

In fact I'm not really able to decipher its meaning. The option itself, including the description in the dialog, and its description in the help are so cryptically worded that I simply don't understand what is it supposed to do...

EDIT:
The below is my understanding of the settings. If my understanding is correct, then the entire settings section/dialog is VERY confusing, given the fact that it's called Segments to Exclude and the fact that all the settings with various and sometimes contradicting meanings are all placed inside the same Segments to Exclude groupbox.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul over 7 years ago in reply to Evzen Polenka

Hi Evzen Polenka ,

I'd agree this isn't the best documented feature. I can only imagine the problem the tech writer had trying to get his head around it.
I only found this because I could not see why the QA settings would not work so I created them again myself, and they worked... then I looked for the differences.

My reading of this feature is as confused as yours! The first part of the help says this:

"Select this if you want to see a list of all segments that were included in the check, displayed in the Messages window when the check is complete."

So it's reporting the exclusions that were inclusions :-| Even without the contrary options I think it could use some attention.

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Evzen Polenka over 7 years ago in reply to Paul

It all seems to work as actually intended in the end... just the GUI and its wording is confusing. It dates back to at least QA Checker 2.0 in Trados 2007 (couldn't check the QA Checker in Trados 7.x as its settings didn't want to open due to some missing DLL in my test install).
If the GUI gets fixed - i.e. options grouped to correctly named group boxes and the settings pane named appropriately, reflecting the fact that it does NOT concern only exclusions - everything will be pretty much fine, IMO.
Yes, the problem is that even a small change incurs additional work/costs (help, documentation, etc... and all that in multiple languages), but it all tracks back to not doing things properly right at the beginning and letting them unfinished. The minimal savings back then just add up and multiply over the years to way bigger spendings later.

A quick idea, not necessarily perfect:
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Trados Studio > 1. Trados Studio

QA-Checker is not reporting any errors no matter what I do