# Trailing spaces

**URL:** <https://forum.xbench.net/t/trailing-spaces/173>\
**Category:** Technical Support\
**Created:** [July 26, 2016, 6:36am UTC](https://forum.xbench.net/t/trailing-spaces/173 "2016-07-26T06:36:36Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eliksir](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.xbench.net/eliksir/32/62_2.png) [@Eliksir](https://forum.xbench.net/u/Eliksir)\
**Post date:** [July 26, 2016, 6:36am UTC](https://forum.xbench.net/t/trailing-spaces/173/1 "2016-07-26T06:36:36Z")

</div>

Bonjour All, I’ve been looking for weeks about a way to verify that the trailing spaces (spaces at the end of a sentence) are identical in both source and target and cannot find information about this

Could anyone of you help me set this up? I’de be forever grateful

Josie

---

<div class="post-metadata">

**Author:** ![omartin](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.xbench.net/omartin/32/82_2.png) [@omartin](https://forum.xbench.net/u/omartin)\
**Post date:** [July 26, 2016, 7:47am UTC](https://forum.xbench.net/t/trailing-spaces/173/2 "2016-07-26T07:47:09Z")

</div>

As leading and trailing spaces are currently removed when loading in Xbench, it is not possible to check that trailing spaces match in both source and target.

However, we have created a task so that this issue can be considered for a future release.

---

<div class="post-metadata">

**Author:** ![Eliksir](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.xbench.net/eliksir/32/62_2.png) [@Eliksir](https://forum.xbench.net/u/Eliksir)\
**Post date:** [July 26, 2016, 10:09pm UTC](https://forum.xbench.net/t/trailing-spaces/173/3 "2016-07-26T22:09:51Z")

</div>

> [@omartin](#):
>
> be

Many many thanks, respecting source trailing space is actually a requirement for many clients

---

<div class="post-metadata">

**Author:** ![Magda\_Marcisz](https://avatars.discourse-cdn.com/v4/letter/m/edb3f5/32.png) [@Magda\_Marcisz](https://forum.xbench.net/u/Magda_Marcisz)\
**Post date:** [June 30, 2017, 9:59am UTC](https://forum.xbench.net/t/trailing-spaces/173/4 "2017-06-30T09:59:30Z")

</div>

Hi,

any news on this feature?  
I’d really like to check the spaces at the end of a segment with Xbench.

Best regards,  
Magda

---

<div class="post-metadata">

**Author:** ![agnus](https://avatars.discourse-cdn.com/v4/letter/a/4bbf92/32.png) [@agnus](https://forum.xbench.net/u/agnus)\
**Post date:** [July 28, 2017, 7:20am UTC](https://forum.xbench.net/t/trailing-spaces/173/5 "2017-07-28T07:20:33Z")

</div>

I actually logged in to this forum to ask if there’s a bug with trailing spaces in target being deleted 🙂 I created my own regular expression to detect final punctuation mismatch — it triggers when a segment that has a trailing colon in source doesn’t have it in target.

When I ran it yesterday it filtered a segment that had a colon and a space in source and just a colon in target. Good, a tiny detail, but worth noticing. However when I moved to Studio it appeared that target segment also had a colon followed by a trailing space.

I hope this will get solved soon, that’s functionality I’d very much like to have working. I just started working with a client who demands that trailing spaces be consistent across all files…

---

<div class="post-metadata">

**Author:** ![omartin](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.xbench.net/omartin/32/82_2.png) [@omartin](https://forum.xbench.net/u/omartin)\
**Post date:** [October 25, 2018, 1:51pm UTC](https://forum.xbench.net/t/trailing-spaces/173/6 "2018-10-25T13:51:12Z")

</div>

From build 1434 on, Xbench loads leading and trailing spaces. In fact, leading and trailing blanks mismatch QA check has been added.