Hi Konstantin Kulakov

This error may not matter. As you're using SDL Trados Studio 2014 it may be that the XML is of a more recent format than Studio 2014 was programmed for.

Are you able to save as Target successfully?

All the best,

Alison

Hi again Konstantin Kulakov

In that case, it may well be due to the difference between formats used at the time of Studio 2014 and Studio 2017.

However, the text of the error indicates that there is a sequence of elements/tags that should not contain text but text has been inserted. This can prevent saving to target format.

For example...

<stichworteintrag><haupt>Boiler, cleaning</haupt><unter>with brush</unter><stichworteintrag>

The above is a simple index entry and would appear like this in the final PDF:

B

Boiler, cleaning

- with brush...……………………….200

(page number)

If, however, the translator had typed any text between any of the end and starting tags, for example:

<stichworteintrag><haupt>Boiler, </haupt>cleaning<unter>with brush</unter><stichworteintrag>

the XML reimport process would throw an error and fail.

However, for example, the 'cannot contain text' error can also be triggered if a correct element is present that was not included the relevant XML file type in the version of Studio the error is triggered by.

Before I continue with further speculation, could either of the above describe what has happened in your scenario?

I should also point out that you can see the full tag text by clicking the relevant button on the View ribbon tab, here:

The document has to be open to access the above setting.

Let me know if any of the above helps...

All the best,

Alison

Hi Alison Field ,
What you described may very well be the case. The problem is actually identifying this potential source of error among several thousand strings. Is there a way to do it (other than manual)?
Thank you

Hi Konstantin Kulakov

Maybe, partially. For example, in Studio 2017 it is possible to search for elements or tags using the Advanced Display Filter, thus:

Then only the segments with the menucascade element will be displayed, which will narrow down the search field to only those segments containing that element. Then you can search visually - or you could use Ctrl+F to search for a frequently-used letter of the alphabet that might flag up text in the wrong place. This is very much a patchwork workaround, though.

If the menucascade element is not actually in a segment then you can't search for it (there is extra content visible if you click on the 'All content' display filter but you can't use the software to search in the non-segment content and there is also content that is behind that which is visible via 'All content').

Another workaround I use with XMLs if I'm able to generate the target XML is to open it in Trados TagEditor because that sometimes more precise at showing exactly where this type of error is happening... Do you have TagEditor (the Trados translation software before Studio 2009 came out).

I'll wait to see if either of the above suggestions helped before making any further suggestions. There may be an app available on the SDL AppStore that can search more precisely also...

All the best,

Ali

Firstly, Konstantin Kulakov , are you sure that the XML is faulty? The error message could simply mean that there is an element that was generated in the actual source and isn't an error. Is the client saying that the XML file does not work?

All the best,

Ali

Hi Alison Field 

Please see the actual error message. It is coming from XML Validator.

PS

The XML error will have been generated by the XML Validator but have you verified the file with Tag Verifier?

If not, here is where you need to tick then click to make it happen:

For example if text has been inserted, it may well have changed the spacing around tags. If a new tag has been inserted that isn't in the source, that will also be pinpointed.

All the best,

Ali

Hi again Konstantin Kulakov

This sort of XML Validator error can often simply be generated by a difference in previous and current tag format settings. They may not matter at all.

Try running just a tag verification (uncheck the other verifier boxes as here)

using the settings I gave you in the next image below that, then click Verify, and let me know what result that produces.

All the best

Ali