# "Name expected" error **URL:** \ **Category:** Technical Support\ **Created:** [August 24, 2017, 8:34pm UTC](https://forum.xbench.net/t/name-expected-error/270 "2017-08-24T20:34:41Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![domosz](https://avatars.discourse-cdn.com/v4/letter/d/8797f3/32.png) [@domosz](https://forum.xbench.net/u/domosz)\ **Post date:** [August 24, 2017, 8:34pm UTC](https://forum.xbench.net/t/name-expected-error/270/1 "2017-08-24T20:34:41Z")
Hi all, Do you happen to know what does “Error 112: Name expected” error message mean? Sometimes, when I want to run a QA check, Xbench 2.9 displays this error message during loading the files. I usually work with XLIFF files (extracted from Google Translator Toolkit) alongside with a tab-delimited text file used as glossary for key terms. If this happens, Xbench is able to process the file partially, until the faulty segment(?), I suppose, but the rest of the file is omitted. I tried to look at the XLIFF file many times, but I can see no difference between those segments that are sure to be good (because they are processed), and those that are not processed. Thanks for your help in advance. ---
**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 27, 2017, 11:15pm UTC](https://forum.xbench.net/t/name-expected-error/270/2 "2017-08-27T23:15:10Z")
For Google Translator Toolkit, with Xbench 3.0 there is the alternative of using the [Xbench Chrome Extension](https://chrome.google.com/webstore/detail/apsic-xbench-extension/hocobnhnpniphphccgaliheohnobbdjo) and the [Xbench Chrome Extension for GTT](https://chrome.google.com/webstore/detail/apsic-xbench-extension-fo/nhadbgflnognogbicnbeepnbpehlocgc). They Chrome extensions are shown in [this video](https://www.youtube.com/watch?v=Ghafpx_wQXw). If you do not have access to Xbench 3.0, you can try to find the offending segment with a [dihcotomic search](https://en.wikipedia.org/wiki/Dichotomic_search), by dividing in 2 part the XLIFF file until you find the segment that is failing. However if you have a file with 1,000 segments it might take 10 divides in the worst case. ---
**Author:** ![domosz](https://avatars.discourse-cdn.com/v4/letter/d/8797f3/32.png) [@domosz](https://forum.xbench.net/u/domosz)\ **Post date:** [August 30, 2017, 11:53pm UTC](https://forum.xbench.net/t/name-expected-error/270/3 "2017-08-30T23:53:41Z")
All right, it seems that I found out what the problem is. This answer might help those who encounter the same issue. I have made a proofreading job today, and the translator provided his XLIFF files, which were created with a Chrome extension very-very similar to the one that I use (the only difference—at least I believed it is the only one—is that my extension is able to exclude segments based on their status: CM, 100%, fuzzy, etc.). I compared the two versions in Notepad++, and noticed that the standalone & characters are missing from the translator’s files. I can only assume that his extension removes this character for some reason, while mine does not do this. I can also only assume that Xbench treats the & character as some kind of parameter, and expects a value (name?) for them. If there’s no value, Xbench will fail. After removing these standalone & characters, I was able to run a proper Xbench check. I’m not sure though how Xbench behaves with strings like & and >. It is yet to be confirmed whether these can also cause problems or not. ---
**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 31, 2017, 8:08am UTC](https://forum.xbench.net/t/name-expected-error/270/4 "2017-08-31T08:08:02Z")
Per your description, it seems that such extension created an invalid XML file. XLIFF is an XML format so Xbench expects XLIFF files to be a valid XML files. The XML specification requires that standalone ampersands (`&`) are escaped as the `&` entity. Probably if you try to load these files with standalone ampersands in some other application that reads them, such as Chrome or Firefox, you would also get a validity error. There are other characters that XML requires to escaped, such as _lower than_ (`<`), which should be escaped as the `<` entity. So it seems that `Error 112: Name expected` means that you are missing the name of the entity after the `&`.