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

Number verification in QA checker

Steven Claesswinnen

Hi,


I know plenty of variations have been asked about this (I mainly refer to this one: https://community.sdl.com/products-solutions/solutions/customer_experience_cloud/language/translationproductivity/f/90/p/6364/22927#pi6614=4), but the issue I'm experiencing is a bit different.

I am using the QA checker in Trados Studio 2015 SR2 - 12.2.5082.0. The problem with Studio's Number Check (as opposed to the one in XBench for instance) is that it ignores numbers in combination with letters or even with non-breaking spaces. So, if there was a non-breaking space between 24 and GHz it will flag this as an error, if you omit the non-breaking space on the target side. Same if you add a non-breaking space on the target side, where there was none on the source side: it will flag this as a missing number.

An example of thish which I am currently experiencing:

When using the standard out of the box "Check numbers" it will flag everything as explained above which is silly and as you can see from this small screenshots: there are a LOT of numbers and measurements, so false positives immediately go to every segment in the project being flagged. I tried using numerous variations in RegEx like this one:

The issue with this example, is that it doesn't flag the 10 because it, for some reason, only looks if it can find the 1, regardless of what number follows it. So it doesn't look for extra numbers. I can turn this into 15998756 and it will still not flag it. But the second I remove the 1 it will flag it. But this is not enough: 10 is not 1.

In short my question is: do you know any method to make sure that the QA checker checks for different numbers AND if extra numbers have been added in order that this 10 will also be flagged. This can come in the form of a RegEx, I'm comfortable with using this. I also downloaded the 'Number Verifier' plugin, but this doesn't seem to work. Or I'm using it wrong. Or a combination of both :)

Kind regards,

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

    Try using (\d+)(m) or (\d{1,})(m) and then $1 $2 for the target.

    I think the expression doesn't like the fact there is a letter there too.

    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,
    Thanks for replying, your regex actually flags the 10. But it creates a new issue: if I then type in 11 - 31 - 101 - 131, or any variaty with 1 at the end of the number in the target, it will still not flag it. As in, it found the 1 followed with the measurement, so it's "fine". But it actually isn't.

    btw: I was able to get the Number verifier to work. But there seems to be something wrong with it: so it also flags this issue. Which is brilliant! However: it only flags this issue, if I change the status to "Translation unconfirmed" and then confirm the segment. When reviewing confirmed segments, this option becomes obsolete. And something more interesting: when an issue has been flagged and I just confirm the segment again, this warning/error (depends on your settings) automatically goes away. This also happens when you perform the verification (F8): every flagged instance will automatically dissappear as if repaired, which is not the case. So the number verifier only works when actively working in the document. Is this intended?
  • 0 in reply to Steven Claesswinnen
    No, certainly not.
    Would you please check your verification settings for segment exclusions? In my case the NV works both when confirming the segment (but only if doing this via CTRL+ENTER or any other shortcut, which confirms the segment - NOT when changing the segment status via right click or other means) and with F8.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • 0 in reply to Jerzy Czopik
    Hi Jerzy,

    I don't have any exclusions on, so all the "Exclude" options are unticked (both in the out of the box QA Checker 3.0 settings and the Number Verifier settings).

    And with the confirming of segments: F8 only works for me if the segment has not been confirmed yet. And yes, it also works when I press ctrl+enter if and only if the segment is not yet confirmed. But the problem is, it won't flag issues if the segment has already been confirmed. And when an issue has been flagged and you go to this segment and press ctrl+enter again, the warning/error automatically dissappears even if you have not corrected the issue. The same if you perform F8 when having these warnings. This leads me to believe that this plugin only works when actively translating. This should be enough: every translator should be worried when a big red cross starts flashing next to their segment, but the example I gave with 1m becoming 10 m is a real live example, for an actual client. So it DOES happen that translators overlook these things. Therefore, it would be handy if this also pops up during the QA/spellcheck stage of translation. Or that another set of eyes, so the reviewer, could have a look and maybe this person does notice the big red cross and acts on it, but if it doesn't work on already confirmed segments, then this is also not a viable option. Unless I'm really overlooking something here (which is probably the case).
Reply
  • 0 in reply to Jerzy Czopik
    Hi Jerzy,

    I don't have any exclusions on, so all the "Exclude" options are unticked (both in the out of the box QA Checker 3.0 settings and the Number Verifier settings).

    And with the confirming of segments: F8 only works for me if the segment has not been confirmed yet. And yes, it also works when I press ctrl+enter if and only if the segment is not yet confirmed. But the problem is, it won't flag issues if the segment has already been confirmed. And when an issue has been flagged and you go to this segment and press ctrl+enter again, the warning/error automatically dissappears even if you have not corrected the issue. The same if you perform F8 when having these warnings. This leads me to believe that this plugin only works when actively translating. This should be enough: every translator should be worried when a big red cross starts flashing next to their segment, but the example I gave with 1m becoming 10 m is a real live example, for an actual client. So it DOES happen that translators overlook these things. Therefore, it would be handy if this also pops up during the QA/spellcheck stage of translation. Or that another set of eyes, so the reviewer, could have a look and maybe this person does notice the big red cross and acts on it, but if it doesn't work on already confirmed segments, then this is also not a viable option. Unless I'm really overlooking something here (which is probably the case).
Children