Hi Yuki Tsukuda

You also need to set your source and target localization requirements.

For example, here are the settings I use for English source and French target:

Hi, Alison Field

Thank you for your kind advice.  I tried your way, but I still have a question because there were no errors.

As you suggested, I set the source (English) and target (Spanish) requirement.

After verifying, there were no errors. I thought segment 1 and 3 will be marked as errors because there are no changes   between the source and the target.

(Segment 1: comma to comma, Segment 3: period to period)

Could you please review it again?

Thank you,

Yuki

Hi Yuki Tsukuda

Please try changing 'Require localizations' to 'Allow localizations' and run your test again... I don't know if it will help but that's what I'd do...

All the best,

Ali

Hi Yuki Tsukuda

Me again...

You don't need to make the Number Verifier settings via File>Options unless you are working with single files rather than projects. 

The project settings ALWAYS overrule the same settings in your proflle via File>Options.

Just in case you didn't know this.

All the best,

Ali

Hi Yuki Tsukuda

I'm adding a link to the online help pages for Number Verifier, for future reference for anyone reading this thread and needing help...

SDL Number Verifier

Sorry I've added 3 posts instead of one but I'm busy working so in a rush...

All the best,

Ali

Hi Yuki Tsukuda

I'm adding a link to the online help pages for Number Verifier, for future reference for anyone reading this thread and needing help...

SDL Number Verifier

Sorry I've added 3 posts instead of one but I'm busy working so in a rush...

All the best,

Ali

Hi, Alison Field

Thank you for your support and the reference. 

I tried 'Allow localizations' and still there are no errors. Below is the screenshot just for your reference.

It might work properly only with trados 2019 and above.

Anyway, thank you so much for your support!

If anyone knows about the cause of the phenomenon, please let me know.

Thank you,

Yuki 

Hi Yuki Tsukuda

This is interesting. Your settings should find that error, even in Studio 2015.

Have you unchecked the QA checker numbers boxes? This is what I do.

Paul, is there any other numbers setting that could undermine the correct functioning of Number Verifier? Have I missed anything? Would uninstalling Number Verifier then reinstalling it help?. I guess a Windows Repair of Studio wouldn't sort this?

I have to be out all day today but Yuki Tsukuda in the meantime, you could try a Window Repair as here:

1. Close all SDL applications.
2. Open the Control Panel:
   • Windows Vista/7: Start > Control Panel > Programs > Programs and Features.
   • Windows 8: Right-click on the screen at bottom-left corner and choose Control Panel > Uninstall a Program.
   • Windows 10: Right-click on Start > Control Panel > Select View by: Small Icons > Programs and Features
   • - or type 'Control Panel' in the search line on your bottom Windows toolbar.
3. Click/highlight the relevant SDL product from the list (e.g. SDL Trados Studio 2015 etc) and click 'Repair' either on the top toolbar or on the right-click dropdown menu.
4. Restart Studio.

It's useful to run a Windows Repair on any complex software from time to time.

All the best,

Ali

Hi, Alison Field,

Thank you for your advice during a busy time.

I checked the  QA checker number boxes. 

Also, I have run Windows Reapair, but the situation is still the same.

I will try other ways in the meantime. (Paul, if you could give me advice, I would appreciate it.)

Thank you,

Yuki

Hi Yuki Tsukuda

Another question:

If you tick 'Enable verification of segment' under File>Options, here:

Does the faulty number then get picked up each time you confirm a segment manually?

If not, Paul can you think of anything I've missed that could explain Number Verifier failing to find numerical errors?

All the best,

Ali

Yuki Tsukuda Alison Field

Alison Field said:

If not, Paul can you think of anything I've missed that could explain Number Verifier failing to find numerical errors?

Yes... a bug!  We're looking at this app today because the last Studio update has broken it somehow and the results are not reliable.  Once we have resolved this I'll let you know and we'll publish an update.

Hi Paul

Excellent, thanks! 

In that case, Yuki Tsukuda, it would be best to tick these boxes in the QA checker settings in Project settings:

Hi, Paul,

Just to confirm, you mean that the CU6 for Studio 2019 SR2, introduced some changes that affected the Number Verifier app, right? Is there more information about any backward compatibility issues introduced in the latest CU? I guess other plugins might be affected.

Thanks!

Daniel

Daniel García Magariños

Daniel García Magariños said:

Is there more information about any backward compatibility issues introduced in the latest CU? I guess other plugins might be affected.

For sure other plugins have been affected... I don't actually know why yet.  But as we have been upgrading apps for 2021 we are also addressing problems we're seeing in the 2019 version at the same time.  At a guess I would think some things snuck in that were in preparation for the 2021 release and might have caused an issue... but I can't validate this for sure yet.

So we know applyTM Template and TU2TM are broken as well for example.  The mxliff filetype is broken and won't save proper target files but it's fine before the CU.  We're working on fixes for these and you'll see the releases in due course.

Once we can clearly identify what changed we'll publish something in the developers forum.

Thanks, Paul. It will be great to have have additional information about what has changed that causes this issue on this and other plugins so that people can also test on their own internal plugins. It's a pity because CU6 had some very interesting fixes.

Daniel

Hi, Paul

Thank you so much for your answer. I will be waiting the update!
I heard Number Verifier is more specific than the QA checker, so hope to see it working!

Thank you,

Yuki