• State Suggested Answer
  • Replies 17 replies
  • Answers 5 answers
  • Subscribers 433 subscribers
  • Views 6856 views
  • Users 0 members are here
Options
Related

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

Lilli Staehle

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!
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi ,

    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

  • 0 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!
  • 0 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!)
  • 0 in reply to Lilli Staehle
    Hi ,

    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

  • 0 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.
  • 0 in reply to Evzen Polenka
    Hi ,

    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

  • 0 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:
  • 0 in reply to Paul
    Hi Paul,

    I forgot to mention it in my e-mail and only wrote about it in a post in here further up, so you probably did not see it: checking "Report all non-excluded segments" was my last desperate try to generate ANY sort of report (which does not happen).

    I experienced all issues when this option was NOT yet checked and when I uncheck it the same thing as before happens - that is: nothing. Apparently you are getting proper reports on the mistakes in the text with my configuration file so the problem must lie somewhere else.

    I am so stumped and have been continuing to look for a possible cause in the last days but just cannot seem to find it. What confuses me most ist that some errors like an empty target segment ARE generating error messages, while some like punctuation errors don't.
  • 0 in reply to Lilli Staehle
    Hi ,

    Did you import the QA profile from a previous version, or did you create this from scratch in Studio 2017. I think it will be worth trying to recreate the QA profile from scratch.

    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 Lilli Staehle
    Okay, everyone I just had my big 'duh' revelation: the punctuation errors were acutally not checked in the project settings and I never thought to make sure they were because I thought that setting those in the general options would carry those settings over to all projects I am working on.

    This goes to show how not knowing a program properly can cause ridiculous issues...

    However, just so I know for the future: when I set the QA Chaecker in the general options, which projects are being affected by those settings? Those that I create myself? If this is the case - what are the setting of the project template for? If this is not the case - for which types of projects DO these settings apply?

    Background: I usually work on projects which are being sent to me by an agency via packages. Does that mean that all of the project-specific settings (including QA Checker) of the party who created that project package are being used and I have to re-set QA Checker every time (or import my preferred settings)?
  • 0 in reply to Paul
    I did create it from scratch - but please see my message above: I found the mistake and it was rather dumb. (But some follow-up questions remain)

    Thanks to you and Evzen for the input / suggestions and the discussion of some points that actually would profit from better wording/structuring!
  • 0 in reply to Lilli Staehle

    Unknown said:
    However, just so I know for the future: when I set the QA Chaecker in the general options, which projects are being affected by those settings? Those that I create myself? If this is the case - what are the setting of the project template for? If this is not the case - for which types of projects DO these settings apply?

    Hi  

    Existing projects are not affected. This is deliberate behaviour, the idea being that you can create new projects without affecting the settings of the existing projects. If you need different settings for different customers then you could create different templates with different settings and these will be used for all future projects, but changing the template settings will never affect existing projects.

    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

Reply
  • 0 in reply to Lilli Staehle

    Unknown said:
    However, just so I know for the future: when I set the QA Chaecker in the general options, which projects are being affected by those settings? Those that I create myself? If this is the case - what are the setting of the project template for? If this is not the case - for which types of projects DO these settings apply?

    Hi  

    Existing projects are not affected. This is deliberate behaviour, the idea being that you can create new projects without affecting the settings of the existing projects. If you need different settings for different customers then you could create different templates with different settings and these will be used for all future projects, but changing the template settings will never affect existing projects.

    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

Children
No Data