QA Checker and Number Verifier - need them to ignore formatting

Is there a way to set up the numer checking options so that it does not flag AT ALL any number formatting?

I just need it to check that all numbers are correct and present. As it is, I am getting a huge number of false-positive errors in large files only because Trados thinks the number is "missing or is not properly localized". Checking several hundred of false positives is so tedious (and a risk of overlooking a real error so high) I am seriously considering transferring files to Wordfast Pro only to perform a simple number check.

Example: a legal file with subsection numbers formatted as 1.1, 1.2 etc. - Trados wants to "localize" those numbers as 1,1  , 1,2  etc, which of course is unacceptable.

  • Hi Anna,

    I guess the best approach might be to use the number verifier from the SDL AppStore and disable the built in QA Checker. This has simple to use and more versatile mechanisms for checking. You can read more on this here:

    multifarious.filkin.com/.../

    Alternatively you could create your own custom QA rules using regex to just check the numbers as you prefer and disable the built in number checker.

    Regards

    Paul

    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

  • Thank you Paul, I had read your blog but I must be doing something wrong - when I disable "Check numbers" in the built-in QA Checker, and only use Number Verifier (it is checked in the QA options under Verification) I get no errors even when the numbers are wrong. Perhaps I should reinstall Number Verifier? Will try that. Unfortunately, I do not know how to create custom QA rules but I assume I'd be able to find some info on that, thank you. It just seems like it would be a useful built-in option to have.
  • Hi Anna,

    Well there are really two things to this.  First of all there should no sections of subsections formatted like this in the file in the first place.  But this is probably down to poorly formatted source files... so not your fault at all.  You could change your segmentation rules to deal with that, but as you haven't let's look at the QA approach.  If you want to look at the segmentation rule approach maybe this will help (old and no sound but the principle seems good):

    https://youtu.be/fGzRiWBeMao

    On the QA approach.  Just use this option:

    If you use this then you'll only get errors reported if the number is incorrect completely, so 1.1 becomes 1.2 for example.  It won't report a localization omission at all.  Just make sure you make all these  settings in your Project Settings and not File Options as it's too late for that.

    Regards

    Paul

    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

  • Unfortunately, I cannot do anything with segmentation - the files come from the client. All I can do is to change language codes. Thank you for telling me about the prevent localization option, that's what I was looking for!!!! Unfortunately, it turns out the Number Verifier is simply not working. It shows nicely, with all the customable options, but it is not doing anything. I uninstalled it using the PlugIn Management Utility and installed it again, but still no signs of life. However, thank you very much for your help, I now know what settings I need.
  • Hi Anna,

    ok - sorry to hear you can't make this work.  Maybe this will help?

    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

  • Thank you Paul! I ran the repair on Studio, uninstalled the Number Verifier and installed it again, and fiddled with it for 10 minutes switching it on and off and restarting Trados, and now it is working as it should, thanks to your settings. I think my installation might have some issues. All versions of Trados, including the WorkBench, were installed on this machine at one point... Thank you so much!