Brian Vorderburg

First thing to do is switch to TagID mode and it's impossible to tell if you have the right tags in the right place using the view you have now.  This article will help:

https://multifarious.filkin.com/2012/09/10/working_with_tags/

You can also toggle the tag mode using Ctrl+Alt+D.  It's easier.

Thank you for your reply Paul and sharing with me the document and telling me how to toggle the tag mode. After reading the document I am still lost. I have never done translations before or worked with software such as this. This to me is a whole new language. I am still trying to figure out:

1) Why the errors exist?

2) What do the errors mean?

3) What do I need to do in order to fix these?

I don't have time to find another translator for I am already past due on the deadline to finish this project. I kindly need a little more direction on what I need to in order to complete this project. Thanks again for your advice and I would kindly appreciate even more help from the community. 

Brian Vorderburg

Brian Vorderburg said:

1) Why the errors exist?

Because you have mismatched, missing or additional tags in your document.  The tags are controls that are in the underlying source document to define things like formatting, fields, urls etc. 

Brian Vorderburg said:

2) What do the errors mean?

They mean, for example:

A tag pair, somewhere in your file, is missing in the translation.  It is in the source, but the translator has not correctly placed it into the target.  This sort of thing could prevent the target file from being created correctly, or even from being created at all.

I cannot tell you which one because you are not showing me the fll error message which will contain the segment number, and you are also not using TagID mode.  TagID mode will use numbers so they are easy to read and you can quickly spot which ones are wrong.  Since you are only displaying the short tags (g,g,g,g,g etc.) I can't tell one from the other!

Brian Vorderburg said:

3) What do I need to do in order to fix these?

Put the correct tags in the target translation for each one until all the errors are gone.  You should probably send this back to the translator to make sure that thy are not only in the target but they also match the language used and are in the right place in the target.  Looking at how many you have there it sadly looks as though the translator didn't really know how to work with a CAT tool either.

If it was a Word file, or Powerpoint for example you might get away without needing all the tags.  But your underlying file seems to be XLF so I'd say you really need to get this done correctly.  Wherever the XLF is destined to be used these tags may be very important.

Brian Vorderburg said:

I don't have time to find another translator for I am already past due on the deadline to finish this project. I kindly need a little more direction on what I need to in order to complete this project.

Please do this, and don't shy away from digging in.  Given your situation it looks as though you are going to have to bite the bullet and learn quickly!

1. change to TagID mode as I suggested.  Easy way is Ctrl+Alt+D when the file is open in the Editor.  Then you'll have something like this:
   
   Note how the tags have numbers and not letters so it's easy to see which ones are missing in the target compared to the source.
   
   
2. Then double click one of the errors... the first one seems a good place to start.  This will open up a small window telling you exactly what's wrong, like this for example, and the relevant segment will be highlighted:
   
   
   
3. I would close the small window at this point and just manually fix the tags in the target to match the source.  So in this case I can see visually that tags 5, 6 and 8 are missing:
   
   
   
4. So I can place them into the target using Ctrl+comma, copy paste or any of the methods described in the article I shared earlier.  Until it looks like this and hen press Ctrl+Enter to confirm the changes and add the corrected TU to my TM:
   
   
   

If this isn't enough to help then you really are going to have to engage someone to do this for you, preferably someone who knows what they are doing!

Thanks Paul! Your instructions were extremely helpful and useful. I can tell you that I have tried this and have come up with issues of "ghost tags". 

I did the copy paste method, where I found the tag numbers not matched and when I pasted it in the target, the ghost tags showed up and I don't know why this came up and how to fix it. I tried to restore the ghost tag, but when you do this then of course an error occurs because the tags in the source don't match in the target. 

Any insight as to how or why I get these ghost tags?

Brian Vorderburg

Brian Vorderburg said:

Any insight as to how or why I get these ghost tags?

Yes.  You have tag pairs and you either haven't got the correct closing tag where it's needed, or you just didn't add the closing tag yet.  The fact it's a ghost tag is a reminder that this isn't a placeable and you need to find the matching closing tag to complete the pair.

This short explanation may help:

Thank you so much Paul! Sorry for my late reply. I did exactly what you said from the video instruction and that helped out tremendously. I was able to get rid of all of the errors. Unfortunately though when I tried to upload the translated file to the training course it gave an error. I reached out to the company that we use to create content which is Articulate, and they said that when looking at it they saw the reason it failed was due to having duplicate tags.

I find this hard to believe because the original file that I exported was like this as you can see in the file. The first picture is the origial without translations and the second picture is the project that I just corrected that had all of the errors.  

Do you have any insight on this as to why it would create duplicate tags and if you have any suggestions as to what to do within Trados without having to translate the document again? Thanks again for your help on this. You have been a beacon of light.

Brian Vorderburg

open the file in Studio and press F8. What errors are you seeing?

I hit F8 and no errors or notes appeared

Then I would ask your client to explain and also provide an example.

Brian Vorderburg

my guess is that because the source was xliff the translator used the option to include segmentation information. This adds stuff to the file that some applications don’t like.

woukd need to prepare the project again without this option and pre translate from your TM.