But I don't understand, Daniel Hug, why do you explicitly add an exclusión line to something you apparently want to check?

However, I find the help quite clear and it is as Paul says:

It says that "string-based exclusion will allow you to specify that these checks are overridden in such specific cases". I mean, the ONLY checks that string-based allows you to overrride are:

1-Check for forgotten and empty translations

2-Check for targets segments that are identical to their source segments

I understand that, for the rest of cases, the string-based exclusión does not apply. Of course, that includes QA regex checks, but also Punctuation checks and the like.

So I don't think it's a bug but works as intended. However, if you want extreme attention to detail you could remove the "ANY" in the following sentence in help.

Segments to Exclude settings to specify which segments will not have ANY QA Checker verifications performed on them.

Which I think is what you are referring to.

However, if you read the part related to string-based exclusions, I think it's quite clear what it does.

Your question, however, has been helpful to me because I had not read the help and understood that string based exclusión applied to all checks… but that was my fault for not Reading the help in the first place heh heh! I particularly was trying to use that feature and I know now why it never did anything!!!

So thank you for pointing that out!

But I don't understand, Daniel Hug, why do you explicitly add an exclusión line to something you apparently want to check?

However, I find the help quite clear and it is as Paul says:

It says that "string-based exclusion will allow you to specify that these checks are overridden in such specific cases". I mean, the ONLY checks that string-based allows you to overrride are:

1-Check for forgotten and empty translations

2-Check for targets segments that are identical to their source segments

I understand that, for the rest of cases, the string-based exclusión does not apply. Of course, that includes QA regex checks, but also Punctuation checks and the like.

So I don't think it's a bug but works as intended. However, if you want extreme attention to detail you could remove the "ANY" in the following sentence in help.

Segments to Exclude settings to specify which segments will not have ANY QA Checker verifications performed on them.

Which I think is what you are referring to.

However, if you read the part related to string-based exclusions, I think it's quite clear what it does.

Your question, however, has been helpful to me because I had not read the help and understood that string based exclusión applied to all checks… but that was my fault for not Reading the help in the first place heh heh! I particularly was trying to use that feature and I know now why it never did anything!!!

So thank you for pointing that out!

Hi Ignacio Niveiro

The "any" in your bold sentence should definitely go. Apart from that, as I said, I am very happy that it works the way it does. What I want is to mark segments which will not be translated (target left blank or URL copied or the like) in a way that they don't produce lots of errors and warnings. In the case of URLs and similar, I want to perform some Regex checks to make sure source and target actually match!

I stick to what I said earlier, that the function of string-based exclusions could and should be described more clearly.

Daniel