Carley Radford

I'm not aware of problems like this, t it would be helpful if you share your QA settings .  Perhaps in here for example?

Also make sure you look in your project settings in case you have different settings accompanying a project for example.  Also make sure you the language pairs because if these are overriding your settings they can also be specific for each language... for example:

Is this happening with every project you create or just certain ones?  Also.. out of interest, why did you change from 2021 to 2019?

Carley Radford

I'm not aware of problems like this, t it would be helpful if you share your QA settings .  Perhaps in here for example?

Also make sure you look in your project settings in case you have different settings accompanying a project for example.  Also make sure you the language pairs because if these are overriding your settings they can also be specific for each language... for example:

Is this happening with every project you create or just certain ones?  Also.. out of interest, why did you change from 2021 to 2019?

Hi Paul,

I changed from 2019 to 2021 - sorry, worded it a bit awkwardly!

It has been happening with every project from one client.

I've checked both settings and project settings and I think the warnings giving me trouble are the RegExs. If I disable the relevant ones, the false positives stop showing. But now I'm wondering why they aren't working.

This is the project regex setting for the 'space at end of segment' warning. Why would this not work? (Sorry, having trouble uploading the screen grab)

Space at end of segment

--RegEx source:

--RegEx target: \s$

--Condition: Report if target matches (target check only)

--Ignore case: flase

Let me know if you have any insights!

Thanks!