# "Untranslated" segments that appear translated in the XTM environment

**URL:** <https://forum.xbench.net/t/untranslated-segments-that-appear-translated-in-the-xtm-environment/381>\
**Category:** Technical Support\
**Created:** [August 8, 2018, 1:57pm UTC](https://forum.xbench.net/t/untranslated-segments-that-appear-translated-in-the-xtm-environment/381 "2018-08-08T13:57:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![roabelleira](https://avatars.discourse-cdn.com/v4/letter/r/94ad74/32.png) [@roabelleira](https://forum.xbench.net/u/roabelleira)\
**Post date:** [August 8, 2018, 1:57pm UTC](https://forum.xbench.net/t/untranslated-segments-that-appear-translated-in-the-xtm-environment/381/1 "2018-08-08T13:57:02Z")

</div>

Some segments that appear translated in XTM appear as “Untranslated” in Xbench when the QA is run on the exported files.

Inside the .xlf that is exported the state-qualifiers appear to be correct (“Translated”) so maybe Xbench is not reading the properties in the XLIFF correctly?

Do you have any idea or possible workaround for this situation?  
 ![XTM%20-%20Xbench](https://cdck-file-uploads-canada1.s3.dualstack.ca-central-1.amazonaws.com/flex035/uploads/xbench/original/1X/b24dc51342bf3d19159dc1e640421fdc938f779a.jpeg)  
Thank you!

Rocío Abelleira  
Amplexor Language Lead

---

<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 8, 2018, 4:13pm UTC](https://forum.xbench.net/t/untranslated-segments-that-appear-translated-in-the-xtm-environment/381/2 "2018-08-08T16:13:51Z")

</div>

How do you obtain the XLIFF file? Are you using the Xbench integration introduced in XTM 11.2?

If you are exporting the XLIFF files manually (not via the new Xbench-XTM integration), are these XLIFF files that you imported on XTM? If so, then make sure that you export the XTM XLIFF, not the “target” XLIFF.

---

<div class="post-metadata">

**Author:** ![roabelleira](https://avatars.discourse-cdn.com/v4/letter/r/94ad74/32.png) [@roabelleira](https://forum.xbench.net/u/roabelleira)\
**Post date:** [August 9, 2018, 8:05am UTC](https://forum.xbench.net/t/untranslated-segments-that-appear-translated-in-the-xtm-environment/381/3 "2018-08-09T08:05:48Z")

</div>

Hi,

Thank you for your quick reply. I am using hte Xbench integration with XTM 11.2.

Thank you!

![](https://cdck-file-uploads-canada1.s3.dualstack.ca-central-1.amazonaws.com/flex035/uploads/xbench/original/1X/aed74693406229c2f74827406d307f89e759a34c.png)

---

<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 9, 2018, 8:58am UTC](https://forum.xbench.net/t/untranslated-segments-that-appear-translated-in-the-xtm-environment/381/4 "2018-08-09T08:58:15Z")

</div>

I wonder if perhaps there is some issue in the identification of the XTM XLIFF dialect and then the parser defaults to vanilla XLIFF.

Would it be possible that you send us via [Xbench support](https://www.xbench.net/index.php/support/submit-bug) the .xbpkg file that is downloaded after you click **Open Xbench**?

---

<div class="post-metadata">

**Author:** ![roabelleira](https://avatars.discourse-cdn.com/v4/letter/r/94ad74/32.png) [@roabelleira](https://forum.xbench.net/u/roabelleira)\
**Post date:** [August 10, 2018, 10:49am UTC](https://forum.xbench.net/t/untranslated-segments-that-appear-translated-in-the-xtm-environment/381/5 "2018-08-10T10:49:06Z")

</div>

Hi,

I could not submit the actual file (as this is client confidential) but I replicated the issue in a fake project and the issue is still there. I have submitted the file as a bug through your support page.

Thank you very much for your help 🙂

Rocío