QA Checker 3.0 (Studio 2022 SR2) keeps giving me false positives whenever it finds "is an" (correctly used!) in an English target segment. This seems to be a pre-defined check. Is there a way to get rid of it? Thanks!
This seems to come from the “Word List” module in QA Checker 3.0:
Beats me how the “Correct Form” can be empty, but this is defined by the user, so you can just go there and turn it off. If you did not set up the project/template yourself might be worth asking the creator why this was included in the word list.
Daniel
I'd figured that much and checked the Word Lists at all levels multiple times. The Word List at Editor level is deactivated. At the language pair level, the Word List does not contain "is a" or "is an". But thanks anyway.
Please chek the Word list at this level, as I agree with Daniel Hug that the message comes from the Word list:
I get this error message:
Thanks, but I repeat ;-)
1) I am aware that the error message seems to come from a word list check.
2) "Check word list" is deactivated at this level, i.e. no check is performed.
I'm afraid now of you repeating over and over…
This is strange in two ways.
1) You said you checked on both levels and the Word List checks are off - correct? There is a Word List under "Verfication" and there is a language pair specific Word List deeply embedded in the Project settings - Language pairs tree:
But what's really strange is that the proposed "correct word" is nothing: "" I can't enter this in my interface. I have to enter at least one character in order for the Word List entry to be accepted. I think I would need to see your project template (look at it with a plain text editor like EditPad Pro or Notepad++) in order to say more.
Daniel
Yes, it is strange indeed. The word list check at the verification level is deactivated, the word list check at the language pair (DE-EN) level is activated, but the word list does not contain "is an" - obviously, as such a check doesn't make any sense here.
And yes, the fact that "correct word" is missing is even stranger. And this is why I posted this question here - to find out whether anybody else has encountered this, whether it is a bug or whatever.
Is the project template that this project was created with originally from Studio 2022? That is the only place I could imagine as source of this unusual behaviour. I'd need to see the sdlproj file to say more.
Is the project template that this project was created with originally from Studio 2022? That is the only place I could imagine as source of this unusual behaviour. I'd need to see the sdlproj file to say more.
Translate
