When verifying the translation I get an error message:
The element 'menucascade' cannot contain text. List of possible elements expected:'uicontrol sfigure'
And I am unable to identify where exactly the error is coming from. Clicking on the message does not lead to any specific segment. How can I fix it?
Thanks
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 Alison Field I do not have Tag Verification in my Project Settings. Tried searching for it on the SDL App Store but did not find anything.
You should have Tag Verifier as an intrinsic part of Studio 2014.
Have you the latest version of Studio 2014, SP2? This definitely incorporates tag verification. I've checked this on the Studio 2014 Help pages.
Here's the documentation home page for Studio 2014:
It contains, along with lots of other stuff, instructions for upgrading to Studio 2014 SP2 - Service Pack 2.
Here is the Studio 2014 Help home page:
Here is where it describes how to use tag verification:
If installing SP2 does not bring in the tag verification then perhaps a Windows Repair of Studio via Control Panel will do so...
If you're in a big hurry, ask the translator to verify the tags for you in Studio 2017.
All the best for now...
Ali
Hi again Konstantin Kulakov
How come you're working with Studio 2014 if your colleague is working with 2017? Are you a project manager in the same company? It would be better if you had Studio 2017 also. I guess it's a matter of cost.
It is better in this case that the translator ensures that all errors they have created are eliminated before delivery. This would usually involve using XML verifier (ticked in the XML filetype settings), QA checker, Tag verifier and Term verifier if a termbase is used, before the job is returned to you.
Did your colleague perform the same tests and get the same errors as the client did?
Questions, questions!
[:D]
Ali
In this scenario, I would create a copy of the project under a new name then copy the whole source to target in the sdlxliff in Studio then verify it with XML Validator.
If the error messages still appear, it is not the translator who has introduced the errors.
If they do not, then the translator is the one who needs to find and solve the error created by their translation.
If you would like to send me a copy of the file to check, my email address is alimay.field@btinternet.com
All the best,
Ali
Thanks for the files. I exported the sdlxliffs to xml then searched in those files using a combination of XML editors and SDL Trados 2007 TagEditor to ascertain the quickest way to find the errors.
As indicated by the XML Validator in Studio, the translator/s had accidentally included text between tags that should not surround text.
The quickest and only 'automated' way to find these errors was to establish a settings file that would enable SDL Trados 2007 TagEditor to see the xml correctly, then use Tools>Verify to find the errors very quickly indeed. Each was listed with a line number and character number which could be used to search in an xml editor. But even better, on double-clicking the list entry, the file scrolled to somewhere close to the fault in TagEditor. Then I was able to go back to Studio and search for nearby text to find the actual segments affected.
However, ultimately the solution must be for translators to take more care and double-check that they have not inserted text in the wrong places. This is helped by having Full Tag Text ticked on the View ribbon. I know it makes it harder to read the text but it is essential when tag pairs have to be present to enclose text correctly to protect associated outer tag pairs that cannot contain bare text.
Someone may know of a more recent xml handler than TagEditor that could use the existing dtd settings file or the sdl filetype settings to verify the xml elements correctly so that they pinpoint the exact position of each error, but until I find such a piece of software it will continue to be TagEditor every time I come across something like this as it works so well. Only in such cases though as I'm no dinosaur!
I have emailed you images, Konstantin, of the position of all of the errors in both files so you can correct them.
Let me know if you need deeper explanation...
All the best
Ali
Thanks for the files. I exported the sdlxliffs to xml then searched in those files using a combination of XML editors and SDL Trados 2007 TagEditor to ascertain the quickest way to find the errors.
As indicated by the XML Validator in Studio, the translator/s had accidentally included text between tags that should not surround text.
The quickest and only 'automated' way to find these errors was to establish a settings file that would enable SDL Trados 2007 TagEditor to see the xml correctly, then use Tools>Verify to find the errors very quickly indeed. Each was listed with a line number and character number which could be used to search in an xml editor. But even better, on double-clicking the list entry, the file scrolled to somewhere close to the fault in TagEditor. Then I was able to go back to Studio and search for nearby text to find the actual segments affected.
However, ultimately the solution must be for translators to take more care and double-check that they have not inserted text in the wrong places. This is helped by having Full Tag Text ticked on the View ribbon. I know it makes it harder to read the text but it is essential when tag pairs have to be present to enclose text correctly to protect associated outer tag pairs that cannot contain bare text.
Someone may know of a more recent xml handler than TagEditor that could use the existing dtd settings file or the sdl filetype settings to verify the xml elements correctly so that they pinpoint the exact position of each error, but until I find such a piece of software it will continue to be TagEditor every time I come across something like this as it works so well. Only in such cases though as I'm no dinosaur!
I have emailed you images, Konstantin, of the position of all of the errors in both files so you can correct them.
Let me know if you need deeper explanation...
All the best
Ali
You're very welcome, Konstantin Kulakov
All the best, Ali :)
Translate
