Hi José,

I think the best thing for this is to set up a Regular Expression verification rule, where you use a grouped expression for the source and the condition to throw a warning or error if the source matches but no the target. Something like this, but with the right regex for your text, of course:

Then you would get a warning like this:

Hola, Nora:

Paul's suggested Number Verifier app worked out for my purposes. However, I did promise to provide you with specific false positive examples, so here's four of them in case you'd like to look into this any further. And so you know, inaccurate placement of alphanumeric strings by themselves (e.g., "S505" or "S505A" in source segments and "S50" or "S505B" in target segments respectively) was correctly identified. Once again, thank you very much.

Yes, it worked out -- it appropriately identified inaccurate placement of alphanumeric strings in my target segments. Thank you very much, Paul. Great app!

Yes, it worked out -- it appropriately identified inaccurate placement of alphanumeric strings in my target segments. Thank you very much, Paul. Great app!

Hi all,

I've been using Number Verifier since it first came out and the BEST feature of it is the alphanumeric verification, it's SO useful!

However, lately I've found it flags up false positives and I end up trawling through a list of things that aren't wrong just to pick out the ones that are wrong... Paul am I missing something? I've repaired Studio and it still isn't giving me specific results. I guess I need to set up a separate thread on this...

It is very much the best tool for number checking apart from this one strange feature that wasn't there to begin with...

Maybe it's my settings...

The above are the settings I use for DE>EN proofreading, working in Review mode.

Sorry to be a pain, I'm usually a troubleshooter myself but I can't figure this one out. Maybe it's my age...

All the best,

Ali :)