So, the question is: why does Trados consistently (90-100% of the time) get numbers wrong and report errors that do not exist? There are literally hundreds of these false positives in bigger projects and it wastes my time.
Hello Pavel Tsvetkov
I can't reproduce this without changing the settings for spaces between number and unit, or using something other than the result I would get by pressing Ctrl+comma and inserting the result. Can you tell me what the actual error message is and can you also try it again allowing Studio to use what it thinks should be the right result?
As we don't allow you to create custom patterns the best approach for working with Studio is often to allow it to do what it wants (if the settings that are available are not the ones you need to fine tune this) and then search & replace afterwards. Or use the Number Verifier as Neil suggested.
It's worth checking when you start and then prepare the file so you can work with it in the most efficient way.