Studio 2019 - Verification not working

I've just started using Studio 2019. Having completed an 8,000-word translation, I ran verification only to find... zero errors. I created a test project with some deliberate errors in it, and the result is the same (see screenshot below). I've ticked all the necessary options (numbers, repeated words, punctuation etc.), but to no avail. Any ideas anyone?

Trados Studio verification dialog box showing 'Verification complete. No errors were reported.' despite the user indicating deliberate errors in the text.



Generated Image Alt-Text
[edited by: Trados AI at 2:20 PM (GMT 0) on 28 Feb 2024]
emoji
Parents
  • Hi 

    Please check if you have the termbase enabled in Project settings, here:

    Trados Studio Project Settings window showing Termbase section with 'Add' and 'Remove' buttons, and a list of termbases with 'Enabled' checkboxes.

    And have you ticked the box here:

    Trados Studio Verification settings window with options for 'Check for possible non-usage of termbase entries' and 'Check for missing target termbase equivalent'.

    Ticking the boxes after the event you'll have to re-verify.

    If you're working using 'Translate single document' and you want the same termbase to be used each time, using the same settings as above under File>Options will enable this in future single document translations.

    Hope this is enough info to help you...

    All the best,

    Alison

    PS: If you're working via 'Project > New project' from the start, you can select the above before or after you create the project. Using 'Translate single document' adops the settings under File>Options but you can change the settings in the automatically created project after creation.

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 2:19 PM (GMT 0) on 28 Feb 2024]
  • Thank you so much, Alison. Greatly appreciated. I have no idea how, but I think I've managed to get it working using your method. I came to Studio 2019 from the 2015 version, where there was no requirement to use termbases - I managed just fine without them. Hence I have no idea what a termbase is, what it does, or what it smells like. But I managed to create some empty ones and then follow your instructions. One observation: once I'd added the termbases all the boxes I'd ticked for the various verification options had been wiped, so I had to retick them.

    Hopefully this will have resolved the issue, so thanks again!
  • Hi 

    A few facts...

    A termbase is a list of source words with preferred target translations, a type of bilingual glossary. Each entry can have explanations/notes/images and other resources added.

    I must have given you a wrong impression. A termbase is not required in any version of Studio for F8 to work. It is only required if you wish to use Terminology Verifier itself to check that translated terms match a list that the client provides or that you compile as you work.

    If you've never used a termbase, then you will only have been verifying with QA Checker which verifies a list of things. You will have made this work by ticking the correct boxes. You may also have been verifying with Tag Verifier, the second verification tool that is part of SDL Trados Studio.

    Take a look here to see a description of the 3 types of verification that were available as standard with both Studio 2015 and 2017:

    Verification

    Now, here's an explanation of verification in 2019:

    Verifying translations

    You'll see a Search box at the top right of the page and you can also click the SDL Trados Studio link top left and look through the index to the whole of Studio 2019 Help manual. There's also a searchable MultiTerm Help manual site.

    Happy reading! Feel free to come back and ask further questions on the Community

    All the best

    Ali

     

     

     

  • Interesting, thank you. In that case I have no idea why it failed to verify my latest translation. Anyway, it appears to be working now, so I probably shouldn't fiddle with it any more in case I break it again.

    However, I have discovered another snag in 2019 which dogged me all through my Studio 2015 career, which is that almost every single segment with a numeral in it is flagged up as a verification error. The error messages are "Extra number in target segment", "Date is missing in target segment or is not properly localized" and "Number is missing in target segment or is not properly localized" even though the target segments are most definitely correct. Is it me doing something wrong? (Probably).
  • Hi again 

    It may be that you use a different target language number localisation than that which is programmed into Studio for your specific target language.

    However, many do report that QA Checker's number verification isn't accurate.

    Personally I don't use that part of QA Checker, i.e. I have all the number options unchecked here:

    Trados Studio Project Settings window showing QA Checker options with errors in checking numbers, dates, and measurements.

    this is because I prefer to use the Number Verifier plug-in. I do this using the following settings, customised for my target language:

    Language Pairs settings in Trados Studio with Number Verifier options and various checkboxes for number localisation and verification.

    That works pretty well for me.

    You can download the Number Verifier plug-in from the SDL AppStore, here:

    Number Verifier

    You have to sign in to download it. Unzip if necessary and run it to install. Then you can select it in the Verification section of your Project settings (or via File>Options if you use Translate Single File rather than Create Project. Then you can select the settings that work best for your target language.

    It isn't perfect but it's pretty good! It also verifies alphanumerics (letter and number combinations) which is pretty useful (that is where I find it isn't perfect because it will include full stops or other punctuation in alphanumeric verifications). On the whole though, it's better than the QA Checker's number verifier.

    I keep QA Checker ticked for verification though as it has a lot of other very useful functionality which can be customised to search for all kinds of things.

    All the best,

    Ali

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 2:19 PM (GMT 0) on 28 Feb 2024]
Reply
  • Hi again 

    It may be that you use a different target language number localisation than that which is programmed into Studio for your specific target language.

    However, many do report that QA Checker's number verification isn't accurate.

    Personally I don't use that part of QA Checker, i.e. I have all the number options unchecked here:

    Trados Studio Project Settings window showing QA Checker options with errors in checking numbers, dates, and measurements.

    this is because I prefer to use the Number Verifier plug-in. I do this using the following settings, customised for my target language:

    Language Pairs settings in Trados Studio with Number Verifier options and various checkboxes for number localisation and verification.

    That works pretty well for me.

    You can download the Number Verifier plug-in from the SDL AppStore, here:

    Number Verifier

    You have to sign in to download it. Unzip if necessary and run it to install. Then you can select it in the Verification section of your Project settings (or via File>Options if you use Translate Single File rather than Create Project. Then you can select the settings that work best for your target language.

    It isn't perfect but it's pretty good! It also verifies alphanumerics (letter and number combinations) which is pretty useful (that is where I find it isn't perfect because it will include full stops or other punctuation in alphanumeric verifications). On the whole though, it's better than the QA Checker's number verifier.

    I keep QA Checker ticked for verification though as it has a lot of other very useful functionality which can be customised to search for all kinds of things.

    All the best,

    Ali

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 2:19 PM (GMT 0) on 28 Feb 2024]
Children
No Data