• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 432 subscribers
  • Views 1104 views
  • Users 0 members are here
Options
Related

QA Checker flagging missing spaces and other punctuation problems where there are none

Carley Radford

Hi All,

I recently changed to Trados Studio 2021 Starter from 2019 Starter and have been having issues with QA checks ever since.

I haven't changed any of the QA settings, but when I verify a file I keep getting errors for extra spaces, space at the end of target segment and space before full stop when no such spaces exist. These are just plain text segments, so there is no issue with tags or anything, but I'm getting so many false positives that it's taking a good hour to go through them all manually.

Has anyone else had a similar problem and fixed it? It has happened on every single project since I switched over.

Thanks!
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

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

    Screenshot of Trados Studio QA Checker 3.0 settings showing various options for punctuation, numbers, and consistency checks with warnings for punctuation and numbers.

    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:

    Screenshot of Trados Studio QA Checker 3.0 settings under Language Pairs, showing options for punctuation, numbers, and consistency checks with warnings for punctuation and numbers.

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

    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

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 3:22 AM (GMT 0) on 29 Feb 2024]
Reply
  • 0

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

    Screenshot of Trados Studio QA Checker 3.0 settings showing various options for punctuation, numbers, and consistency checks with warnings for punctuation and numbers.

    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:

    Screenshot of Trados Studio QA Checker 3.0 settings under Language Pairs, showing options for punctuation, numbers, and consistency checks with warnings for punctuation and numbers.

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

    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

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 3:22 AM (GMT 0) on 29 Feb 2024]
Children
  • 0 in reply to Paul

    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!