# Numeric Mismatch

**URL:** <https://forum.xbench.net/t/numeric-mismatch/175>\
**Category:** Technical Support\
**Created:** [August 3, 2016, 3:39pm UTC](https://forum.xbench.net/t/numeric-mismatch/175 "2016-08-03T15:39:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MindyK](https://avatars.discourse-cdn.com/v4/letter/m/a183cd/32.png) [@MindyK](https://forum.xbench.net/u/MindyK)\
**Post date:** [August 3, 2016, 3:39pm UTC](https://forum.xbench.net/t/numeric-mismatch/175/1 "2016-08-03T15:39:21Z")

</div>

I was surprised that I didn’t receive an error on a numeric mismatch in this instance:  
Source: If the velocity is _.70_ m/sec, the de-aliasing velocity will be 1.40m/sec.  
Target: Si la velocidad es de _70_ m/s, la velocidad de de-aliasing será de 1.40 m-s.

It came up as under repeated word for ‘de de’, but not for the numeric mismatch. Does this not include decimal points?

---

<div class="post-metadata">

**Author:** ![pcondal](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.xbench.net/pcondal/32/305_2.png) [@pcondal](https://forum.xbench.net/u/pcondal)\
**Post date:** [August 4, 2016, 9:06am UTC](https://forum.xbench.net/t/numeric-mismatch/175/2 "2016-08-04T09:06:28Z")

</div>

In fact it does, but apparently it seems that there is a bug in the parser when the number omits the integral part and the correspoding number does not have decimals

So, currently it detects issues such as 7.0 -\> 70, or even .70 -\> 7,0 but due to the parsing bug, it does not detect your example, .70 -\> 70.

We’ll create a task in our DB to fix this bug in a future update.

In the meantime, your workaround to mitigate this bug would be to have a couple of checklist items (please note double quotes are significant):

A) Source number in the middle of the segment, preceded by a space:

```
Source: "[:space:]\.([0-9]+)=1"
Target: "[:space:]@1" or "^@1"
PowerSearch: ON
Regular expressions: ON

```

B) Source number right at start of segment:

```
Source: "^\.([0-9]+)=1"
Target: "[:space:]@1" or "^@1"
PowerSearch: ON
Regular expressions: ON
```