# Confirmed segments considered as untranslated in xliff file

**URL:** <https://forum.xbench.net/t/confirmed-segments-considered-as-untranslated-in-xliff-file/242>\
**Category:** Technical Support\
**Created:** [April 26, 2017, 9:14pm UTC](https://forum.xbench.net/t/confirmed-segments-considered-as-untranslated-in-xliff-file/242 "2017-04-26T21:14:25Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bpvilar](https://avatars.discourse-cdn.com/v4/letter/b/76d3ee/32.png) [@Bpvilar](https://forum.xbench.net/u/Bpvilar)\
**Post date:** [April 26, 2017, 9:14pm UTC](https://forum.xbench.net/t/confirmed-segments-considered-as-untranslated-in-xliff-file/242/1 "2017-04-26T21:14:25Z")

</div>

Hi all,

I usually work with OddJob/MemSource and, when trying to make a QA to the translated file, it always says \*\*\* untranslated \*\*\* for all the segments.

I’m importing it as XLIFF file (after changing the file extension from .mxliff to .xliff) and it only happens with Xbench 2.9, version 3.0 does not reproduce this issue.

Could you tell me the reason why this happens? Is there any way to solve this issue?  
Thanks in advance.

---

<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:** [April 27, 2017, 8:00am UTC](https://forum.xbench.net/t/confirmed-segments-considered-as-untranslated-in-xliff-file/242/2 "2017-04-27T08:00:49Z")

</div>

This happens because Xbench 3.0 supports the Memsource XLIFF dialect whilst Xbench 2.9 does not (because Xbench 2.9 predates Memsource).

One workaround you have for Xbench 2.9 is to manually add a `state='translated'` attribute in the `target` element.

The [state](http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html#state) attribute is standard of XLIFF 1.2 and Xbench 2.9 honors it, but unfortunately the XLIFF 1.2 specification says that it is optional and that its default value is _undefined_. Because of that, many CAT developers do not use the `state` attribute and use instead their own proprietary attributes for segment state in their XLIFF dialects.

---

<div class="post-metadata">

**Author:** ![Bpvilar](https://avatars.discourse-cdn.com/v4/letter/b/76d3ee/32.png) [@Bpvilar](https://forum.xbench.net/u/Bpvilar)\
**Post date:** [April 30, 2017, 8:32pm UTC](https://forum.xbench.net/t/confirmed-segments-considered-as-untranslated-in-xliff-file/242/3 "2017-04-30T20:32:26Z")

</div>

Thanks so much for your reply. I’ll try to do so.

---

<div class="post-metadata">

**Author:** ![Nur\_Demirci](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.xbench.net/nur_demirci/32/453_2.png) [@Nur\_Demirci](https://forum.xbench.net/u/Nur_Demirci)\
**Post date:** [July 10, 2023, 10:59am UTC](https://forum.xbench.net/t/confirmed-segments-considered-as-untranslated-in-xliff-file/242/4 "2023-07-10T10:59:39Z")

</div>

Hi there. Could you advise how we can do the following?

" One workaround you have for Xbench 2.9 is to manually add a `state='translated'` attribute in the `target` element."

---

<div class="post-metadata">

**Author:** ![oui3381](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.xbench.net/oui3381/32/480_2.png) [@oui3381](https://forum.xbench.net/u/oui3381)\
**Post date:** [November 29, 2023, 9:36am UTC](https://forum.xbench.net/t/confirmed-segments-considered-as-untranslated-in-xliff-file/242/6 "2023-11-29T09:36:03Z")

</div>

I have had the problem similar to the person asking this and I went to check how I can use the “state” attribute. It might be still useful for you or someone else. Here it is:  
Open the file with Notepad. Then use the Find-Replace menu and replace \< target \> with \< target state=‘translated’ \> (please remove the extraneous spacing). Save the file and it is ready to be used in xbench 2.9.

Many thanks to pcondal for your answer. It really really helps me.